View Single Post
  #10  
Old October 14th 04, 07:26 PM
arvind
external usenet poster
 
Posts: n/a
Default

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




.