Installing in wrong place

stevecarter · Post by **stevecarter** » Sun Jun 01, 2008 9:40 am

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

John Drescher · Post by **John Drescher** » Sun Jun 01, 2008 9:53 am

On Sun, Jun 1, 2008 at 10:40 AM, stevecarter <[email protected]> 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

stevecarter · Post by **stevecarter** » Sun Jun 01, 2008 10:00 am

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

vitamin · Post by **vitamin** » Sun Jun 01, 2008 10:05 am

stevecarter wrote:I right-clicked on the desktop icon and followed the "Action" menu.

It was as the install started that I noticed it forming a new .wine directory at root and then installed into it.

That means you are logged in as a root. To verify - open terminal and run 'whoami'.

stevecarter · Post by **stevecarter** » Sun Jun 01, 2008 10:19 am

OK - I can see how that has happened, but when I try it logged is as myself, I get a complete fail to install.

The message being:

Warning: could not find DOS drive for current working directory '/home/Stephen', starting in the Windows directory.
wine: cannot find '/home/Stephen/Desktop/bksetupE.EXE'

(The capitalisation in the file name is as it was received from the website.)

I have checked that the setup file is indeed in the directory, so why cannot wine find it?

Best regards,

Stephen Carter

Post by **dimesio** » Sun Jun 01, 2008 11:10 am

Open a terminal, cd to the directory where the executable is, and try running it from there. (All as a normal user.)

stevecarter · Post by **stevecarter** » Sun Jun 01, 2008 11:16 am

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

vitamin · Post by **vitamin** » Sun Jun 01, 2008 12:12 pm

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?

stevecarter · Post by **stevecarter** » Sun Jun 01, 2008 2:30 pm

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

vitamin · Post by **vitamin** » Sun Jun 01, 2008 2:37 pm

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?

stevecarter · Post by **stevecarter** » Sun Jun 01, 2008 3:09 pm

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

Plamen.Vassilev · Post by **Plamen.Vassilev** » Sun Jun 01, 2008 5:21 pm

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

stevecarter · Post by **stevecarter** » Mon Jun 02, 2008 2:49 am

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

Post by **dimesio** » Mon Jun 02, 2008 8:34 am

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?

John Drescher · Post by **John Drescher** » Mon Jun 02, 2008 8:55 am

On Mon, Jun 2, 2008 at 9:34 AM, dimesio <[email protected]> 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

Post by **dimesio** » Mon Jun 02, 2008 11:22 am

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.