HI, I am confused. I am running Wine 1.0-rc3 on MEPIS 7 I have a MSWindows program that I want to install. It has been downloaded from its website onto my (local, not root) Desktop. When I install it with Wine, it does not seem to work. On further investigation I discover that the installation has created a .wine folder etc. in root, rather than in my local directory (where there is already a .wine folder with other programs in it.) Can anyone tell me what I am doing wrong please? Thanks. Stephen Carter
On Sun, Jun 1, 2008 at 10:40 AM, stevecarter <wineforum-user at winehq.org> wrote:> HI, > > I am confused. > > I am running Wine 1.0-rc3 on MEPIS 7 > > I have a MSWindows program that I want to install. It has been downloaded from its website onto my (local, not root) Desktop. > > When I install it with Wine, it does not seem to work. > > On further investigation I discover that the installation has created a .wine folder etc. in root, rather than in my local directory (where there is already a .wine folder with other programs in it.) > > Can anyone tell me what I am doing wrong please? >How did you install it with wine? John
I right-clicked on the desktop icon and followed the "Action" menu. When invited to choose a program with which to open it, I typed "Wine" in the bar at box at the top, and clicked on "Run in terminal" so that I could follow progress. It was as the install started that I noticed it forming a new .wine directory at root and then installed into it. The program did not work after installation. Thanks for your help. Stephen Carter
Hi dimesio, OK - tried that. I get the same message about not finding a DOS drive followed by: wine: could not load L"C:\\windows\\system32\\bksetupE.EXE": Module not found But it is there!!!!!! Thanks again Stephen Carter
stevecarter wrote:> Hi dimesio, > > OK - tried that. I get the same message about not finding a DOS drive followed by: > > wine: could not load L"C:\\windows\\system32\\bksetupE.EXE": Module not found > > But it is there!!!!!!How are you running it? Have you removed your ~/.wine directory since you had some root contamination?
Yes, I have removed the .wine folder in root and there seems to be no evidence of it in the root directory. It still refuses resolutely to install the program from the folder and claims that it cannot find the module as previously. Any other ideas? Thanks. Stephen Carter
stevecarter wrote:> Yes, I have removed the .wine folder in root and there seems to be no evidence of it in the root directory.Are you logged in as root?
I ran the rm as root to remove the .wine on root. I have since run the rm as myself to remove my local .wine and then, also as myself, ran winecfg to rebuild it. Sadly it has made no difference. Stephen Carter
Steve, try copying/moving the installation "into" wine bottle i.e. /home/user/.wine/drive_c/ I usually make a directory named install under /home/user/.wine/drive_c/ and then run installation from there. Such as: cd /home/user/.wine/drive_c/install/some_program/ wine setup.exe I hope this helps you. -Plamen
Thanks for your message Vassilev, I tried what you suggested, but still no good. :( If I install it from root it will make the directory .wine under root and install. If I install it from my local directory it just tells me that it cannot locate the module as in my previous messages. I am about to give it all up as a bad job! Best regards, Stephen Carter
Where exactly is the setup file located on your computer--the full unix path? What is the syntax you are using at the command line to try and run it when logged in as a normal user?
On Mon, Jun 2, 2008 at 9:34 AM, dimesio <wineforum-user at winehq.org> wrote:> Where exactly is the setup file located on your computer--the full unix path? > What is the syntax you are using at the command line to try and run it when logged in as a normal user? >Perhaps the dosdevices on the ~/.wine is messed up? John
John Drescher wrote:> > Perhaps the dosdevices on the ~/.wine is messed up? >Possibly, though I was thinking that he may simply be getting the syntax wrong. But I did have another thought: Steve, I know in your original post you said you downloaded the setup file to your local desktop, but were you logged in as root when you did that? If you were, then root owns that file and you need to change the ownership before you can access it as a normal user.