Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
User has wrong Ctl3d32.dll
Message
From
05/04/2000 08:23:08
 
 
To
04/04/2000 09:00:56
Jerry Tovar
Dana Corporation Dana It
Maumee, Ohio, United States
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00354275
Message ID:
00355600
Views:
17
Jerry,

This makes a little more sense now. You are including the NT version with your program even though it is apparently not needed.

Another program on this users Win9x computer recognizes the ctl3d32.dll and tries to use it, but, it is the NT version. Your other users are not failing because they do not have a program on their computers that recognized and tried to use the dll.

If the renaming suggestion doesn't work, you might have to send him the Win9x version (it should be on your MSDN CD, remember there are two). The original on his computer should be deleted before he copies the new one. This should fix his problem.

Apparently, your program does not need the dll, so it should be removed from your setup disk(s). Or, include the Win9x version. Of course, if some of your users are running your program under NT, then you have another problem don't you? ....NT trying to use the Win9x version!

I think you have entered into a world called "dll hell". Good Luck.

>Thanks for the response. This helps a lot. I'm not sure if they are on a network. We'll try renaming the file. The user is in another part of the conutry and we'll try to walk them through this.
>
>We have hundereds of installations but only seen this problem at this location.
>
>We use Wise7 to create the setup.exe. I see that Wise does include Ctl3d32.dll in our setup.exe but we haven't had any other reported problems of sending the wrong version of this file.
>
>Thanks
>
>
>
>
>>There are two versions of this file. One for NT and one for win95/98 (same name, different folders). It's used to give buttons, etc. a 3D appearance.
>>
>>Possibly another program installed on this persons computer is responsible. If it's a Novell network, I think this could be the cause.
>>
>>I would suggest backing the file up to a floppy and then delete it....or, rename it to something like ctl3d32.bak.
>>
>>Try rebooting the computer and running the program and see what happens.
>>
>>If it is a Netware workstation, I'm not sure what the fix would be.
>>
>>Are there other users in his organization running the same program without error?
>>
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform