http://bugs.winehq.org/show_bug.cgi?id=12369
--- Comment #6 from Robert Bradbury robert.bradbury@gmail.com 2008-04-06 08:10:41 --- Dmitry, your last statement IMO is complete caca. For wine to work properly, it is not necessary to install applications under the ~/.wine directory.
I have my old Windows XP C: drive (NTFS) partition mounted as /frodo/c. I create wrapper shell scripts that run both SOL.EXE and EXCEL.EXE from that drive by invoking them with something of the form:
$WINE $SOL or $WINE $EXCEL
where the shell variables are set to the proper UNIX paths for wine and the windows executable ON the old C: NTFS partition.
Now, it is sometimes necessary to make sure the application gets access to various DLL libraries (wine is very good about informing one regarding missing DLLs, e.g. msc42u.dll (which is required for running SkypeMate.exe). One can resolve these problems by either symlinking them from the old /frodo/c/WINDOWS directory into the $HOME/.wine/dosdevices/c:/windows directory, or copy them from the old WINDOWS directory to the wine windows directory if one feels like wasting disk space. One can also setup the WINEDLLPATH environment variable to point to various directories on the old Windows C drive, e.g. /frodo/c/Program\ Files/Microsoft\ Office-various-sub-directories-, if one doesn't want to copy or symlink the various DLL's from their install position on the Windows C: drive into the wine pseudo-windows drives.
If there was a problem with MEGA4.EXE accessing a DLL or file in /usr/local/bin/MEGA/... I would expect that it would inform me of such (trying to run the visual basic editor from Excel.exe generates a host of such errors). This is not the error I get trying to start MEGA4. The fact that the normal file access routines, when searching for DLL's, spew out a number of directories being scanned (and Excel, Word, etc.) find files that are located in sub-directories, suggests to me that the file locating aspects of wine work just fine. The fact that the MEGA4 program does start up and display the copyright window suggests that is is fine as well. The program fault appears to occur when it attempts to bring up the primary program window which has the menus that allow it to load gene sequences.
Now, the fact that MEGA is documented as working on RedHat under wine and the fact that the paths are *in* the distribution RPM as being under /usr/local/bin/MEGA (Do a "strings MEGA-4-01.i386.rpm | grep local") strongly suggests to me that it is *supposed* to be installed in /usr/local/bin and it is supposed to work from that location.
If you give me a good reason why it is supposed to be installed under ~/.wine and tell me how I am supposed to go about doing it (and whether it should be installed under ~/.wine/drive_c, ~/.wine/drive_c/Program Files, ~/.wine/dosdevices/c:/Program Files/ or some other location) I'll be happy to relocate or stick in a symbolic link to the MEGA directory. But from where I sit that doesn't seem to be the problem.
And I have pointed out the problem to both the developers and the book publisher and have yet to receive a response. My primary interest is in determining which version of wine MEGA once ran under as I have had experiences in the past where programs which once worked under wine seemed to stop working as it was upgraded.