On Tue, Dec 02, 2003 at 10:59:25AM +0100, Arend Lammertink wrote: > "In article: <[EMAIL PROTECTED]> [EMAIL PROTECTED] (Frode > Gill) writes: > > > > In article <[EMAIL PROTECTED]>, > [EMAIL PROTECTED] wrote: > > >> How can I copy a dll file to the system32 directory if the file is > > >> being used by Windows? > > > > > >The normal 'proceedure' is:- > > >rename the.dll the.old > > ^^^^^^ > > > > And this is not possible when the .dll is in use by windows... > > > > Another way of doing it, is to put the new <file>.dll in the directory > > as <file>.tmp, and have it renamed to .dll during startup. There is a > > way to set this in the registry - not sure how to do it though :-/ > > Since when?. You can rename a DLL in use, you just cannot move it.
Just out of curiosity, why is there a difference between renaming a file and moving it? Just how can Windows even tell the difference, unless the moving is between different filesystems? This sounds seriously brain-damaged, but then I always knew that might be the case. - Svein Ove Aas
