http://bugs.winehq.org/show_bug.cgi?id=11797
--- Comment #7 from alfredo software@zas.gwz-berlin.de 2008-03-08 14:05:26 --- (In reply to comment #0)
http://www.winehq.org/pipermail/wine-users/2008-March/029362.html discusses the use case where a user wants to install a bunch of apps, then move .wine somewhere else. This works except that .lnk files have absolute Linux paths in them. Perhaps .lnk files should be Windows paths only, to allow for this sort of relocation?
(In reply to comment #6)
(In reply to comment #5)
The only remaining truth to this bug report is that strings shows fragments of Unix paths in .lnk files.
winedump is able to decipher/print the contents of .lnk files, so it may be used to try figure out why you see them.
I havn't forget to set WINEPREFIX. After installation a haved moved the winedir to a new name. Starting the application gives me the error! Then i have patched the winedir name in the lnk file (only one char twice) with emacs and rerun the app. Now it work again. Could be that it is application depending. I don't know why the lnk file was used in my case. I'm calling the simulator exe direct, but something in the application needs (or calls) the lnk file. The fragments (are not really fragments) are important for this program - maybe others (the most?) without looking at lnk files.