|
Posted by =?Utf-8?B?RXRpZW5uZSBCb3VjaGVy on March 16, 2006, 10:47 am
If you were Registered and logged in, you could reply and use other advanced thread options I'll be damned. That's what it was. I have other machines with other security
products and OneCare is the only one to affect that functionality. I should I
tried without of course. Thanks for making me do it.
I'll have to see if I can report that as a bug for OneCare. I still don't
see why or how it affects renaming of running executables.
--
Etienne Boucher
"Shenan Stanley" wrote:
> Etienne Boucher wrote:
> > I posted this on the XP general newsgroup, but I'm not sure that
> > was the right place, this might not be either.
> >
> > On all my computers, with Windows 2000 and up (apparently it should
> > work lower NT versions as well) I can rename an executable that is
> > currently running with either a MoveFile inside the program, or
> > manually in the shell. On one of my machines I can't, and I get a
> > sharing mode (code 32) error. Does anyone know what could influence
> > this functionallity and make it impossible to do this on that
> > particular machine?
> >
> > The machine is close to a fresh install, mostly there's just
> > Windows OneCare on it.
> >
> > I only found one post about not being able to do this, back in
> > 2003, with no real anwser.
> >
http://groups.google.ca/group/microsoft.public.win2000.file_system/browse_thread/thread/d061625492aababe/5613724362886a6d?tvc=2&q=group%3Amicrosoft.*+rename+running+process
>
> Tried doing it without the Beta Software running on it?
>
> --
> Shenan Stanley
> MS-MVP
> --
> How To Ask Questions The Smart Way
> http://www.catb.org/~esr/faqs/smart-questions.html
>
>
>
|