Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

wine cannot find dlls

17 views
Skip to first unread message

CrashedAgain

unread,
Nov 16, 2005, 11:10:34 AM11/16/05
to
I am trying to get Turbocad v7 to run in wine, however it is unable to
import the required dll's:

(typical error, there is a whole page of them)
err:module:import_dll Library GLU32.dll (which is needed by
L"C:\\Program Files\\IMSI\\TCW70\\Program\\RCore70.dll") not found

The required dlls ARE present in the same directory as the main
program .exe; wine documentation says this is where it searches first
so what is wrong?

I have also tried copying the dll's to ~drive_c/windows/system and
have also tried providing the dll path thus:

wine /home/crashedagain/.wine/drive_c/Program\
Files/IMSI/TCW70/Program/Tcw70.exe winedllpath
home/crashedagain/.wine/drive_c/Program\ Files/IMSI/TCW70/Program/

Daniel Skorka

unread,
Nov 17, 2005, 8:45:16 AM11/17/05
to
CrashedAgain <tedh...@sasktel.net> wrote:
> (typical error, there is a whole page of them)
> err:module:import_dll Library GLU32.dll (which is needed by
> L"C:\\Program Files\\IMSI\\TCW70\\Program\\RCore70.dll") not found
>
> The required dlls ARE present in the same directory as the main
> program .exe; wine documentation says this is where it searches first
> so what is wrong?

Actually, glu32.dll is something that comes along with wine. If your
program has its own version, that might be the problem. Try removing
this file and see where this goes. Also, if a.dll needs b.dll which in
turn needs c.dll, but c.dll isn't found, you'll get errors about b.dll
and a.dll not being found too. So check wether it really is glu32.dll
that is missing.

>
> I have also tried copying the dll's to ~drive_c/windows/system and
> have also tried providing the dll path thus:
>
> wine /home/crashedagain/.wine/drive_c/Program\
> Files/IMSI/TCW70/Program/Tcw70.exe winedllpath
> home/crashedagain/.wine/drive_c/Program\ Files/IMSI/TCW70/Program/

1. Always, always, _always_ run a .exe from the dir it is in.
2. What the hell does the winedllpath in there mean?
3. You forgot the magic numbers.

Daniel

CrashedAgain

unread,
Nov 17, 2005, 11:41:28 AM11/17/05
to

> Actually, glu32.dll is something that comes along with wine.

Thank You very much! That was the key...I had assumed all the missing
dll's were from the turbocad install and I hadn't checked them all. It
was missing glu32.dll and opengl32.dll. Copied them over from my winME
side & now it's at least TRYING to start. It's still not working, it
freezes at the opening screen which then has to be killed & wine is
left screwed up & won't restart but at least it got that far.

>1. Always, always, _always_ run a .exe from the dir it is in.

Actually, I think when the command is entered as I did (wine <path>
foo.exe), what the system does is cd-cd-cd down the path to the .exe
and then start from there. At any rate, I have never had any problems
doing it this way.

>2. What the hell does the winedllpath in there mean?

from man wine:
WINEDLLPATH
Specifies the path(s) in which to search for builtin dlls
and Winelib applications. This is a
list of directories separated by ":". In addition to any
directory specified in WINEDLLPATH,
Wine will also look in /usr/lib/wine.

>3. You forgot the magic numbers.

????

CrashedAgain

unread,
Nov 17, 2005, 3:23:03 PM11/17/05
to
As I said in my last post, wine appears to have damaged itself trying
to start Turbocad.
Now trying to run ANYTHING in wine results in this error:

code:
Invoking /usr/lib/wine/wine.bin
/home/crashedagain/.wine/drive_c/Program
Files/IMSI/TCW70/Program/Tcw70.exe ...
Line 173: Key is too long
'[Software\\Classes\\CLSID\\6A481801-E531-11CF-A115-00A024158DAF}\\6A481802-E531-11CF-A115-00A024158DAF}\\6A481803-E531-11CF-A115-00A024158DAF}\\6A481804-E531-11CF-A115-00A024158DAF}\\6A481805-E531-11CF-A115-00A024158DAF}\\Implemented
Categories\\7DD95801-9882-11CF-9FA9-00AA006C42C4}\\7DD95802-9882-11CF-9FA9-00AA006C42C4}]
1132244393'
Line 173: Error creating key
'[Software\\Classes\\CLSID\\6A481801-E531-11CF-A115-00A024158DAF}\\6A481802-E531-11CF-A115-00A024158DAF}\\6A481803-E531-11CF-A115-00A024158DAF}\\6A481804-E531-11CF-A115-00A024158DAF}\\6A481805-E531-11CF-A115-00A024158DAF}\\Implemented
Categories\\7DD95801-9882-11CF-9FA9-00AA006C42C4}\\7DD95802-9882-11CF-9FA9-00AA006C42C4}]
1132244393'
Line 190: Key is too long
'[Software\\Classes\\CLSID\\6A481801-E531-11CF-A115-00A024158DAF}\\6A481802-E531-11CF-A115-00A024158DAF}\\6A481803-E531-11CF-A115-00A024158DAF}\\6A481804-E531-11CF-A115-00A024158DAF}\\Implemented
Categories\\7DD95801-9882-11CF-9FA9-00AA006C42C4}\\7DD95802-9882-11CF-9FA9-00AA006C42C4}]
1132244393'
Line 190: Error creating key
'[Software\\Classes\\CLSID\\6A481801-E531-11CF-A115-00A024158DAF}\\6A481802-E531-11CF-A115-00A024158DAF}\\6A481803-E531-11CF-A115-00A024158DAF}\\6A481804-E531-11CF-A115-00A024158DAF}\\Implemented
Categories\\7DD95801-9882-11CF-9FA9-00AA006C42C4}\\7DD95802-9882-11CF-9FA9-00AA006C42C4}]
1132244393'
wineserver: loading /home/crashedagain/.wine/system.reg failed with
error 80000005
wine client error:0: recvmsg: Connection reset by peer
Wine exited with a successful status


although the last line usually is:

code:
wineserver: loading /home/crashedagain/.wine/system.reg failed with
error 80000005
wine: for some mysterious reason, the wine server failed to run.
Wine failed with return code 1

instead of the above.

I tried with removing/reinstalling wine (wine 20050725 from debian
unstable) but it still crashes. I then tried logging on & installling
wine as root, copying the missng dll's & installing turbocad (all to a
new install in /root directory). Tubocad froze as expected but the
konsole from which it was started closed OK. Here is all I got for
error message:

Invoking /usr/lib/wine/wine.bin /root/.wine/drive_c/Program
Files/IMSI/TCW70/Program/Tcw70.exe ...
fixme:ole:CoRegisterMessageFilter stub
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects

Any ideas anyone?

Daniel Skorka

unread,
Nov 17, 2005, 5:52:33 PM11/17/05
to
CrashedAgain <tedh...@sasktel.net> wrote:
> Thank You very much! That was the key...I had assumed all the missing
> dll's were from the turbocad install and I hadn't checked them all. It
> was missing glu32.dll and opengl32.dll. Copied them over from my winME
> side & now it's at least TRYING to start. It's still not working, it
> freezes at the opening screen which then has to be killed & wine is
> left screwed up & won't restart but at least it got that far.

It seems you don't understand me. wine _already has_ glu32.dll and
opengl32.dll. Don't copy them over from another windows, or from
anywhere else. If turbocad comes with its own glu32.dll, _delete it_.

>>1. Always, always, _always_ run a .exe from the dir it is in.
> Actually, I think when the command is entered as I did (wine <path>
> foo.exe), what the system does is cd-cd-cd down the path to the .exe

No, it doesn't. wine could do so, but I don't think i does either.

> and then start from there. At any rate, I have never had any problems
> doing it this way.

Some programs don't mind, some do.

>>2. What the hell does the winedllpath in there mean?
> from man wine:
> WINEDLLPATH
> Specifies the path(s) in which to search for builtin dlls
> and Winelib applications. This is a
> list of directories separated by ":". In addition to any
> directory specified in WINEDLLPATH,
> Wine will also look in /usr/lib/wine.

You have obviously never come before come across an environment
variable. It works like this:
WINEDLLPATH="foo:bar:blah" wine program.exe

>>3. You forgot the magic numbers.
> ????

The wine version number.

Daniel

Daniel Skorka

unread,
Nov 17, 2005, 5:57:33 PM11/17/05
to
CrashedAgain <tedh...@sasktel.net> wrote:
> As I said in my last post, wine appears to have damaged itself trying
> to start Turbocad.
> Now trying to run ANYTHING in wine results in this error:
> wineserver: loading /home/crashedagain/.wine/system.reg failed with
[...]

> error 80000005
> wine client error:0: recvmsg: Connection reset by peer
> Wine exited with a successful status

Your registry has somehow become damaged. Delete ~/.wine and install
turbocad again.

> I tried with removing/reinstalling wine (wine 20050725 from debian
> unstable) but it still crashes. I then tried logging on & installling
> wine as root, copying the missng dll's & installing turbocad (all to a
> new install in /root directory). Tubocad froze as expected but the
> konsole from which it was started closed OK. Here is all I got for
> error message:

Of course. root doesn't have the same damaged registry. Do I really need
to tell you that
a) being root has nothing to do with the problem and
b) you should never do such things as root?

Please try version 0.9.1 of wine (there's a debian unstable package) and
see if the error persists. And please, delete your ~/.wine before you do
so.

Daniel

CrashedAgain

unread,
Nov 17, 2005, 6:22:59 PM11/17/05
to
You are absolutely right, the problem was (is) in the system.reg. I'm
not very good at this, it took me a couple of hours to find it but I
did get that far.
I used root because it is the only other user on my system, not because
it was root. Yes you're not supposed to do things as root but I don't
see the harm provided you are aware of what you are doing.
Actually what I have now is wine 0.9 from debian unstable. And yes it
gives the same problem. The actual problem line in system.reg is :

(line177)[Software\\Classes\\CLSID\\6A481801-E531-11CF-A115-00A024158DAF}\\6A481802-E531-11CF-A115-00A024158DAF}\\6A481803-E531-11CF-A115-00A024158DAF}\\6A481804-E531-11CF-A115-00A024158DAF}\\6A481805-E531-11CF-A115-00A024158DAF}]
1132266855
(line178)
@="IMSIGX Matrix"

there may be more. It may just be an issue with the line length.

That is actually a secondary issue though...it is what is left in the
system.reg after turbocad tries to start.
The primary issue is why turbocad freezes instead of starting. I've got
no clue on how to track that one except for the bit of error message
quoted above.

CrashedAgain

unread,
Nov 17, 2005, 8:41:27 PM11/17/05
to
Oops.
I hadn't quoted the error message:

CrashedAgain

unread,
Nov 17, 2005, 10:28:30 PM11/17/05
to
Reply to your message posted at 4.57 pm. I missed reading this one,
probably I was writing/sending my next post at that time.


>It seems you don't understand me. wine _already has_ glu32.dll and
>opengl32.dll. Don't copy them over from another windows, or from
>anywhere else. If turbocad comes with its own glu32.dll, _delete it_.


Then I must be doing something wrong with the install because mine
doesn't. So, trying to make sure the install is correct, I did the
following:

-moved ~.wine to a bakup. ~.wine now gone
-apt-get --purge remove wine
-apt-get -t unstable install wine wine-utils
-winecfg. autodetected drives & autodetected sound. It only autodetects
OSS even though I have alsa & aRts but no matter. At this point it made
a new ~.wine which contained a ~windows/system directory but it is
empty. Where are the .dll files? There also used to be a fake_windows
directory but perhaps this is no longer used?
-Tested: wine~~~notepad.exe works OK.
-copied ~/Program\ Files/IMSI from the balup directory. This is the
Turbocad directory, it is a bit of a PITA to install from the turbocad
setup.exe because setup.exe will only run if root. It contains some
.dlls but NOT GLU32 or opengl32.
-tried to run it. Got a whole boatload of missing .dll errors
-copied GLU32.dll & Opengl32.dll from the bakup directory to
~/windows/system/. This folder now contained only these two files.
Tried to run, got more missing .dll errors so started to follow these,
eventually just copied the whole ~windows/system dir from bakup.
-tested Turbocad again. Same result...lockup, had to restore system.reg
file.
-restored the whole bakup directory as there were other apps in it.

SO, what am I doing wrong. With the old (pre 0.9) version, system
directory was populated with .dlls (these are the ones I was/am using)
when the very brief configure dialog created the fake_windows
directory. Even then there was no GLU32 nor opengl32.dll.

How do I get the dlls into system directory with 0.9? There doesn't
seem to be any way to do it from winecfg.

>You have obviously never come before come across an environment
>variable. It works like this:
>WINEDLLPATH="foo:bar:blah" wine program.exe

You are right, I have never used these before. I was going by man wine
which says :

SYNOPSIS
wine program [arguments ... ]
wine --help
wine --version

and then goes on to list WINEDDPATH under PROGRAM/ARGUEMENTS so I
figured it should go after the wine <program> entry.

Daniel Skorka

unread,
Nov 18, 2005, 6:06:43 AM11/18/05
to
CrashedAgain <tedh...@sasktel.net> wrote:
> Actually what I have now is wine 0.9 from debian unstable. And yes it
> gives the same problem. The actual problem line in system.reg is :
>
> (line177)[Software\\Classes\\CLSID\\6A481801-E531-11CF-A115-00A024158DAF}\\6A481802-E531-11CF-A115-00A024158DAF}\\6A481803-E531-11CF-A115-00A024158DAF}\\6A481804-E531-11CF-A115-00A024158DAF}\\6A481805-E531-11CF-A115-00A024158DAF}]
> 1132266855
> (line178)
> @="IMSIGX Matrix"
>
> there may be more. It may just be an issue with the line length.

Hmm. So this program creates an registry string that is too long for
wine to handle. I think you should tell the developes about it.

Daniel

Daniel Skorka

unread,
Nov 18, 2005, 6:24:36 AM11/18/05
to
CrashedAgain <tedh...@sasktel.net> wrote:
> Then I must be doing something wrong with the install because mine
> doesn't. So, trying to make sure the install is correct, I did the
> following:
>
[...]

>
> SO, what am I doing wrong. With the old (pre 0.9) version, system
> directory was populated with .dlls (these are the ones I was/am using)
> when the very brief configure dialog created the fake_windows
> directory. Even then there was no GLU32 nor opengl32.dll.
>
> How do I get the dlls into system directory with 0.9? There doesn't
> seem to be any way to do it from winecfg.

That's because you are not supposed to put them there. Look in
/usr/lib/wine, they're all here. You don't need them in
~/.wine/drive_c/windows/system, it's that simple. Now about those missing
DLLs: Have you tried fiddling with the windows version in winecfg? That
might help you.

> and then goes on to list WINEDDPATH under PROGRAM/ARGUEMENTS so I
> figured it should go after the wine <program> entry.

For me, it is listed under 'ENVIRONMENT VARIABLES' :)
>

CrashedAgain

unread,
Nov 18, 2005, 10:58:32 AM11/18/05
to
>Hmm. So this program creates an registry string that is too long for
> wine to handle. I think you should tell the developes about it.

Will do that.

>That's because you are not supposed to put them there. Look in
>/usr/lib/wine, they're all here. You don't need them in
>~/.wine/drive_c/windows/system, it's that simple. Now about those
missing
>DLLs: Have you tried fiddling with the windows version in winecfg?
That
>might help you.

crashedagain@desktop:~$ ls /usr/lib/wine---yes, it is full of .dll's
BUT
crashedagain@desktop:~$ ls /usr/lib/wine/opengl32.*
ls: /usr/lib/wine/opengl32.*: No such file or directory
crashedagain@desktop:~$ ls /usr/lib/wine/glu32.*
ls: /usr/lib/wine/glu32.*: No such file or directory
there were also others missing but I no longer have that error message.

>For me, it is listed under 'ENVIRONMENT VARIABLES' :)

Oh, I see what you mean, I didn't realize that was different from
Program/Arguements. and there is no indication of the syntax to use.

Anyway, I now know how. Thanks.

I also have another app I can't get to run in wine but that is a
different subject. will post it soon. Hope you can help.

Daniel Skorka

unread,
Nov 19, 2005, 7:02:21 AM11/19/05
to
CrashedAgain <tedh...@sasktel.net> wrote:
> crashedagain@desktop:~$ ls /usr/lib/wine---yes, it is full of .dll's
> BUT
> crashedagain@desktop:~$ ls /usr/lib/wine/opengl32.*
> ls: /usr/lib/wine/opengl32.*: No such file or directory
> crashedagain@desktop:~$ ls /usr/lib/wine/glu32.*
> ls: /usr/lib/wine/glu32.*: No such file or directory
> there were also others missing but I no longer have that error message.

So you are indeed missing those files, which is rather strange. I just
downloaded the debian unstable wine package version 0.9.1-winehq-3 and
it contains those dlls. Could it be that your filesysem is corrupt, or
that something went wrong during the install?

Daniel

CrashedAgain

unread,
Nov 20, 2005, 12:26:40 PM11/20/05
to
The answer was so obvious once I found it!
For Debian the .dll's are not part of the wine pkg, They are provided
by the libwine pkg and there is a separate libwine-gl (and
libwine-alsa, libwine-arts and several others) pkg which I did not
have. I have them now.

Daniel Skorka

unread,
Nov 21, 2005, 5:52:10 AM11/21/05
to

Ah, my fault. I thought you were using the winehq package, which is just
everything in one neat package. I could've told you debian splits them
up to about a dozen.

Daniel
>

0 new messages