http://bugs.winehq.org/show_bug.cgi?id=12369
--- Comment #7 from Dmitry Timoshkov dmitry@codeweavers.com 2008-04-06 23:53:45 --- (In reply to comment #6)
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.
Although that might work for some application that setup is not supported through Wine bugzilla because there are a lot of potential problems with it: missing registry keys, lack of shared write memory mapping support, etc.
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 it's distributed as RPM and supposed to be installed under /usr/local then presumably that setup has been tested by the program distributors, and in that case you should be able to receive support from them.
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.
There should an install program bundled with your Windows application which should be ran to setup it.