https://bugs.winehq.org/show_bug.cgi?id=38817
--- Comment #10 from Daniel Palos daniel.palos@mail.com --- Thank you for your suggestions.
I merely included the terminal output for your ease and convenience, not because the installation does not result in proper application initialization and execution.
Do you have a simple method to delete all associated files? A batch type file will do for future reference should I need to find files and delete them from a command prompt.
In any case, I don't understand the snip well enough to offer a more technical rebuttal. Can you explain why it is a user error instead of an application failure that generates an OLE error?
I did delete the virtual drive in winetricks or wine.
Why should that Windows application (FXTS2Install.exe) recognize anything external to any new installation of a new virtual drive?
In any case, from the literature I read about wine, it is intelligent enough to clean up any wine associated files; except for custom settings that should reside on the virtual drive for the windows application to recognize within its environment, presumably.
How do I find the virtual drive from a terminal?
Not sure why the version was changed except for maybe Vista compatibility or previous OS on the platform I am currently using. XP should be ok as a Standard, for now, I suppose. There is no apparent option for any different software versions of that application other than the one bundled with FXTS2Install.exe.