http://bugs.winehq.org/show_bug.cgi?id=18089
--- Comment #13 from Igor Tarasov tarasov.igor@gmail.com 2009-04-19 21:18:27 --- (In reply to comment #10)
That's reverse-engineering, isn't it?
Really? Never thought so. Anyway, I've downloaded that piece of software from MS site: http://technet.microsoft.com/en-us/sysinternals/bb896652.aspx This is just a logger. If this is reverse-engineering, then studying logs produced by wine is too, since it records calls that are produced by third party software.
(In reply to comment #11)
Wine already has all that implemented. From terminal run: cd ~; wine start program.exe
Nope, didn't work, I've got import_dll error, as usual.
This bug is invalid. You see exactly the same behavior as on windows.
Then why double-clicking programs from winefile does not work (it does not change the environment according to App Paths registry data)? Why 'wine start app.exe' does not work?
The only possible valid point - Wine doesn't create proper .lnk & .desktop files. They always specify full path and work directory.
.desktop files do work well, since they have Path specified.