replacement file "ctl3d32.dll" ?

  • Thread starter Thread starter *Prot3anThr3ad*
  • Start date Start date
P

*Prot3anThr3ad*

somehow the one on my machine got mixed up with a win95/98 version.
where can i d/l just the version of ctl3d32.dll for windows 2000
without running sfc ?
 
somehow the one on my machine got mixed up with a win95/98 version.
where can i d/l just the version of ctl3d32.dll for windows 2000
without running sfc ?

Hi PT...

Already looked in the "Driver Cache" in the WINNT folder?

If it isn't there, and your addy is true, I can mail you mine! Just "ping"
me! I have SP4 installed, and you?

You will have to put it in place from an floppy (DOS) though, as it may be
"in use" when W2K is running.
 
somehow the one on my machine got mixed up with a win95/98 version.
where can i d/l just the version of ctl3d32.dll for windows 2000
without running sfc ?

Did you do a search of your system to see if you have a copy of the
original someplace?? Sometimes there will be morw then one copy of
the same file on a system.

If there is just replace the ruined one with the good one.
 
try proteanthread at yahoo; thanks btw.


In_Parentheses said:
Hi PT...

Already looked in the "Driver Cache" in the WINNT folder?

If it isn't there, and your addy is true, I can mail you mine! Just "ping"
me! I have SP4 installed, and you?

You will have to put it in place from an floppy (DOS) though, as it may be
"in use" when W2K is running.
 
there is absolutely not one copy on my hd except in the app directory
from which i am trying to run the app.

not even in the dll cache directory.
 
*Prot3anThr3ad* said:
it worked.



In_Parentheses said:
@m79g2000cwm.googlegroups.com:


You're welcome! I'd be interested to learn whether this worked as it
should.

There was a version infected with trojan don't use anything someone mails to
you

Safest way is just rename ctl3d16.dll to ctl3d32.dll its mostly same
functionality
 
*Prot3anThr3ad* said:
it worked.





There was a version infected with trojan don't use anything someone
mails to you

Safest way is just rename ctl3d16.dll to ctl3d32.dll its mostly same
functionality

Joe User, although your advise may sound sane enough to follow, let me
assure you that this file is clean!

Renaming 16-bits files to perform 32-bits operations is just as hazardous
as running files from an unknow source... the stability of the OS may be
inflicted quite seriously.
 
Back
Top