G
Guest
This is so frustrating - I've tried to work this out with Symantec but they
keep referring me to support.microsoft.com, so here goes.
I uninstalled my previous version of Norton AV before installing NAV 2005 in
XP Professional SP2, and after installing, I received a Found New Hardware
pop-up for the Symantec Settings Manager. (I still do every time I start my
computer up.) This is when I contacted Symantec Technical support and they
instructed me to uninstall NAV 2005, and I was also provided with
instructions to uninstall remnants of NAV 2003 and any earlier versions. I
was also instructed to use MSI and remove certain files that begin with cc,
Norton, Symantec, Sym, MSRedist. I did all of this and re-installed NAV
2005. This time I got TWO Found New Hardware pop-ups, for the Symantec
Settings Manager and for symlcbrd. When I run through the Hardware wizard
all possible ways, it basically tells me it cannot install the hardware
because it cannot find the specific software.
I still think this is Symantec's problem but perhaps something in my
registry is corrupted or... I have no clue... Any resolutions????
Thanking you in advance,
Jill
keep referring me to support.microsoft.com, so here goes.
I uninstalled my previous version of Norton AV before installing NAV 2005 in
XP Professional SP2, and after installing, I received a Found New Hardware
pop-up for the Symantec Settings Manager. (I still do every time I start my
computer up.) This is when I contacted Symantec Technical support and they
instructed me to uninstall NAV 2005, and I was also provided with
instructions to uninstall remnants of NAV 2003 and any earlier versions. I
was also instructed to use MSI and remove certain files that begin with cc,
Norton, Symantec, Sym, MSRedist. I did all of this and re-installed NAV
2005. This time I got TWO Found New Hardware pop-ups, for the Symantec
Settings Manager and for symlcbrd. When I run through the Hardware wizard
all possible ways, it basically tells me it cannot install the hardware
because it cannot find the specific software.
I still think this is Symantec's problem but perhaps something in my
registry is corrupted or... I have no clue... Any resolutions????
Thanking you in advance,
Jill