CTL3DV2.DLL 
Author Message
 CTL3DV2.DLL

Does anybody know the reason why CTL3DV2.DLL should be under \windows\system
directory. All dll/vbx for my developed application are located under
working directory and it's working well except CTL3DV2.DLL. Windows(WFW3.11)
returns ERROR msg "This application uses CTL3DV2.DLL, which has not been
correctoy installed." After ignored the msg, the application starts to work
correctly again. After I moved this dll to \windows\system directory.
The msg didn't appreared.




Sun, 19 Jul 1998 03:00:00 GMT  
 CTL3DV2.DLL

Quote:

>Does anybody know the reason why CTL3DV2.DLL should be under \windows\system
>directory. All dll/vbx for my developed application are located under
>working directory and it's working well except CTL3DV2.DLL. Windows(WFW3.11)
>returns ERROR msg "This application uses CTL3DV2.DLL, which has not been
>correctoy installed." After ignored the msg, the application starts to work
>correctly again. After I moved this dll to \windows\system directory.
>The msg didn't appreared.

One of the problems with CTL32.DLL was that it was getting installed
all over the place, so Microsoft made the V2 version aware of its
location and only able to run from Windows\System.  That is proper
behavior for a shared .DLL.

--
Don Bradner

author of WWPlus, ImgViewer/16, and BirdData
http://www.redshift.com/~arcatpet



Tue, 21 Jul 1998 03:00:00 GMT  
 CTL3DV2.DLL

o Does anybody know the reason why CTL3DV2.DLL should be under
o \windows\system directory. All dll/vbx for my developed application
o are located under working directory and it's working well except
o CTL3DV2.DLL. Windows(WFW3.11) returns ERROR msg "This application uses
o CTL3DV2.DLL, which has not been correctoy installed." After ignored the
o  msg, the application starts to work correctly again. After I moved this
o dll to \windows\system directory.  The msg didn't appreared.

CTL3DV2.DLL is *designed* to give this error message if it's not in the
Windows system directory. The intent is to stop people from keeping the dll
in the application directory. This reduces the chance of your program being
stuck with the in-memory module of a non-compatible version of the dll in
another app's directory.

All shared dll and vbx files should be kept in the Windows system
directory. Only keep private dll and vbx files in the app directory.

David
--

____D__a__v__i__d_____B__e__r__g__a__r__t___________________________________



Tue, 21 Jul 1998 03:00:00 GMT  
 CTL3DV2.DLL

That was/is MS's attempt to not have the dll scattered all over.  That
is, if you package/use it in your program, you have to install it --
properly -- in the user's \windows\system directory.

George


Quote:
>Does anybody know the reason why CTL3DV2.DLL should be under \windows\system
>directory. All dll/vbx for my developed application are located under
>working directory and it's working well except CTL3DV2.DLL. Windows(WFW3.11)
>returns ERROR msg "This application uses CTL3DV2.DLL, which has not been
>correctoy installed." After ignored the msg, the application starts to work
>correctly again. After I moved this dll to \windows\system directory.
>The msg didn't appreared.


===============================================================================
 George R. Torralba              xxxxxxxxxxxx                  Batang Cebu!!!
 Seattle, Washington             206.241.2801              MIME mail accepted
===============================================================================


Thu, 23 Jul 1998 03:00:00 GMT  
 
 [ 4 post ] 

 Relevant Pages 

1. CTL3D.DLL and CTL3DV2.DLL?

2. CTL3DV2.DLL disappearing from client's machine

3. CTL3DV2.DLL error message

4. "ctl3dv2.dll" usage question

5. CTL3DV2.DLL Won't Load - Arrgh!

6. CTL3DV2.DLL - crashing

7. CTL3dv2.dll usage

8. ctl3dv2.dll conflicts

9. ctl3dv2.dll

10. CTL3DV2.DLL causes STACK Fault

11. VB 3.0 and ctl3dv2.dll ?

12. ctl3dv2.dll * MS-Office = CRASH!!!

 

 
Powered by phpBB® Forum Software