Talking about Norton.....
 

Meant to tell you..
I installed Norton 2005 on a VPC ME - and kept getting CFGWIZ errors on
booting.
Clearing all MSCONFIG entries for Norton allowed a clear boot, but running
Norton from the Start|Programs menu gives the same CFGWIZ error

I then gave up in disgust, and reverted to my prior imageg

--
Noel Paton (MS-MVP 2002-2005, Windows)

Nil Carborundum Illegitemi
http://www.btinternet.com/~winnoel/millsrpch.htm
http://tinyurl.com/6oztj

Please read http://dts-l.org/goodpost.htm on how to post messages to NG's

Oh - hell!
Sorry - that was meant to be an email, not a post!

--
Noel Paton (MS-MVP 2002-2005, Windows)

Nil Carborundum Illegitemi
http://www.btinternet.com/~winnoel/millsrpch.htm
http://tinyurl.com/6oztj

Please read http://dts-l.org/goodpost.htm on how to post messages to NG's

"Noel Paton" wrote in message
...
Meant to tell you..
I installed Norton 2005 on a VPC ME - and kept getting CFGWIZ errors on
booting.
Clearing all MSCONFIG entries for Norton allowed a clear boot, but running
Norton from the Start|Programs menu gives the same CFGWIZ error

I then gave up in disgust, and reverted to my prior imageg

--
Noel Paton (MS-MVP 2002-2005, Windows)

Nil Carborundum Illegitemi
http://www.btinternet.com/~winnoel/millsrpch.htm
http://tinyurl.com/6oztj

Please read http://dts-l.org/goodpost.htm on how to post messages to NG's

Noel Paton wrote:

Oh - hell!
Sorry - that was meant to be an email, not a post!

I suspect Noel that at east some of us realised that. :-)
--
Mike

In microsoft.public.windowsme.software, "Mike M"
wrote:

Noel Paton wrote:

Oh - hell!
Sorry - that was meant to be an email, not a post!

I suspect Noel that at east some of us realised that. :-)

....and some of us at west as well....

Alan Edwards wrote:

...and some of us at west as well....

least east west what's it matter? NAV doesn't work on Win Me regardless
of which direction you face. :-)
--
Mike

"Mike M" wrote:

Alan Edwards wrote:

...and some of us at west as well....

least east west what's it matter? NAV doesn't work on Win Me regardless
of which direction you face. :-)

NAV2002 and NAV2003 are okay with WindowsMe it appears, but certainly
not NAV2004. And it appears that NAV2005 is also not usable with
WindowsMe.


Ron Martell Duncan B.C. Canada
--
Microsoft MVP
On-Line Help Computer Service
http://onlinehelp.bc.ca

"The reason computer chips are so small is computers don't eat much."

Ron Martell wrote:

NAV2002 and NAV2003 are okay with WindowsMe it appears, but certainly
not NAV2004. And it appears that NAV2005 is also not usable with
WindowsMe.

Ron,

They may "work" but can they survive the use of system restore and what
about the damage that can be caused by LiveUpdate?
--
Mike

"Mike M" wrote:


Ron,

They may "work" but can they survive the use of system restore and what
about the damage that can be caused by LiveUpdate?

You are the resident guru for System Restore and I was not aware that
there were issues with WindowsMe and Live Update prior to NAV2004.

I have a client that ran several WindowsMe machines with NAV2002 for a
couple of years with no issues. We have recently upgraded these
machines by installing more RAM and going to XP Pro.


Ron Martell Duncan B.C. Canada
--
Microsoft MVP
On-Line Help Computer Service
http://onlinehelp.bc.ca

"The reason computer chips are so small is computers don't eat much."

Ron Martell wrote:

You are the resident guru for System Restore and I was not aware that
there were issues with WindowsMe and Live Update prior to NAV2004.

I have a client that ran several WindowsMe machines with NAV2002 for a
couple of years with no issues. We have recently upgraded these
machines by installing more RAM and going to XP Pro.

Ron,

Issues yes, but not everyone is affected. LiveUpdate seems to be one of
the vectors that can cause the C:\_RESTORE\TEMP folder to bloat and the
state manager to stop analysing and either cabbing or discarding the files
temporarily stored there but what the precise trigger is I have never
managed to determine.

One reason though why I have never recommended the use of any version of
NAV with Win Me is that if a user rolls their system back to before the
last NAV signature update NAV gets broken because for some inexplicable
reason NAV stores signature version details in the registry. I suspect
that using scanreg /restore could cause similar problems.

Cheers,
--
Mike

i've ME with NAV03, and i agree with mike in that i can't
restore my puter to a point before the last liveupdate
session with new signature files, without the NAV refusing
to boot the puter. so i make it a point to create a
restore point after every LU session. no other problems
otherwise. by the way, i don't seem to have any TEMP
folder in C:\_RESTORE. the only ones are- VxDMoN.cfg,
DISKCFG, SRDISKID, and VxDMoN. do i've to do something
about this or let it be. tia. arvind
-----Original Message-----
Ron Martell wrote:

You are the resident guru for System Restore and I was
not aware that
there were issues with WindowsMe and Live Update prior
to NAV2004.

I have a client that ran several WindowsMe machines
with NAV2002 for a
couple of years with no issues. We have recently
upgraded these
machines by installing more RAM and going to XP Pro.

Ron,

Issues yes, but not everyone is affected. LiveUpdate
seems to be one of
the vectors that can cause the C:\_RESTORE\TEMP folder to
bloat and the
state manager to stop analysing and either cabbing or
discarding the files
temporarily stored there but what the precise trigger is
I have never
managed to determine.

One reason though why I have never recommended the use of
any version of
NAV with Win Me is that if a user rolls their system back
to before the
last NAV signature update NAV gets broken because for
some inexplicable
reason NAV stores signature version details in the
registry. I suspect
that using scanreg /restore could cause similar problems.

Cheers,
--
Mike




.