[Wine] Re: Wine and MS Access problem

Daniel Skorka skorka at gmx.net
Mon Mar 19 00:49:13 CDT 2007

Robert McLean <robert.mclean1 at sympatico.ca> wrote:
>> You haven't mentioned your wine version.
> 0.9.22 according to the wine config screen, I dont know how to tell if
> this is also the main wine program version.  In any event is what I
> downloaded through the Add/Remove Software menu on my system a few days
> ago.  One of the things I am trying to learn as a new Linux user is
> where the applications actually get installed to, or how to read their
> properties.  In other words I am just guessing that 0.9.22 is the wine
> version number.

Yep, that's it.

> I am not sure what you mean by native widows installation as my C drive
> In my Windows system I have C drive with various data, and D drive with
> data and the WindowsXP system.  These are physically distinct 10GB
> drives, not partitions.
> In my Linux system I have the C drive mounted as /mnt/windows/C, and
> the D drive mounted as /mnt/windows/D, and a 200GB drive with just
> Linux on it.
> In the Wine configuration screen under drive mappings I have
> C:   /mnt/windows/C/

Do _not_ do that. Unless you have important data in it, delete ~/.wine
Leave the mapping of C: alone (i.e. keep it at ~/.wine/drive_c. C is
where wine expects to find DLLs and stuff.

> D:   /mnt/windows/D/
> E:   /
> F:   /mnt/windows/C
> G:   /mnt/windows/D
> H:   /home/Bob
> I have no idea what is going on with the E, F and G drives.  Wine just
> seems to put them in there.  I do have a CD rom which Windows calls E,
> but I have not mounted it into linux yet.  I assume H is my linux hard
> drive.  When I fist started wine a few days ago, C was mapped to

I'm guessing that is some kind of autodetection that includes your
windows drives into your wine setup.

> something like /c_drive/ or something like that.  Is that what you mean
> a fake C drive ? The problem I ran into was that when I ran my scad


> spice program it worked basically, and found most data files, but it
> would not find any".include" files unless I manually changed all
> references to C drive to /mnt/windows/C,  And I decided that cant be
> right, So I went into config and mapped C into where it is actually
> mounted.

Well, you were wrong. What you never should do is something like 
$ wine /path/to/app.exe
Instead, do
$ cd /path/to && wine app.exe
This solves most file not found problems. If that doesn't help, well
have to keep looking.

> Ok, that makes sense.  But how do I tell wine where windows\system32 is
> ?  

You _could_ change the default setup and point it to
/mnt/windows/D/blah. Seeing how you are a novice, that is not a good
idea. The easiest solution is to copy DLL files that are not found from
your real windows installation to ~/.wine/drive_c/windows/system32

For general reference, you should read the Wine Users Guide:


More information about the wine-users mailing list