cannot run norton utilities?

[rob f.]

when i try to run norton disk doctor i get the same
message, norton disk doctoris unable correctly identify
the version of this operating system due to another
application hooking and modifying the win 32 version
functions. norton disk doctor will now terminate. this
happens with disk doctor,norton windoctor. does anybody
have any advice?

 

[Carey Frisch [MVP]]

What version of Norton are you trying to use?

--
Carey Frisch
Microsoft MVP
Windows XP - Shell/User

Be Smart! Protect your PC!
http://www.microsoft.com/security/protect/

----------------------------------------------------------------------------------


| when i try to run norton disk doctor i get the same
| message, norton disk doctoris unable correctly identify
| the version of this operating system due to another
| application hooking and modifying the win 32 version
| functions. norton disk doctor will now terminate. this
| happens with disk doctor,norton windoctor. does anybody
| have any advice?

 

[Guest]

Rob
I have the same problem with mine....Norton utilities can't identify my operating system because another application has hooked or modified the WIN32 version....etc. I've been working on it all day. Please let me know if you find a solution, as I am getting the same dialogue box and it's frustrating...just bought Norton Systemworks 2004 thinking it would take care of my computer problems.

 

[Guest]

I don't know if you were replying to Rob, or myself....but as for myself, I am using Norton Systemworks 2004 (home version)....do you have any suggestions?

 

[Guest]

having exact same prob, were you able to find a solution?

 

[Guest]

when i try to run norton disk doctor i get the same
message, norton disk doctoris unable correctly identify
the version of this operating system due to another
application hooking and modifying the win 32 version
functions. norton disk doctor will now terminate. this
happens with disk doctor,norton windoctor. does anybody
have any advice?

 

[bullwinkel J. Moose]

you might want to post this on a symantec newsgroup.