"Reboot to Access Restore" Fix Does Not Work

Per your instructions I verified that although System
Restore creates a Checkpoint manually & by itself, IT IS
UNABLE TO RESTORE TO AN EARLIER POINT. NOTHING CHANGES.
"wininit.ini" continues to appear and I continue to rename
it. "tgcmd.exe" IS NOT checked in Startup and I can't find
Access Denied ( both r Mike M hints for a source of
wininit.ini) Can't find a KBase article exactly like my
issue (about a manual or system created checkpoint not
working.) I re-installed Win Me over itself about a month
ago per Dell Warranty Support because I had the Dec 1899
screen on Sys Restore- The "Reboot to Access Restore" is
another Chapter that has occurred when I DID and DID NOT
find wininit.ini via Search. Have run scanreg /fix several
times and am looking for another suggestion to get Sys
Restore Working; the Reboot to Use Sys Restore is now 2nd
priority. many Thanks!
-----Original Message-----
Make sure you're OK - test System Restore using the regime
on my web
site.....

http://www.btinternet.com/~winnoel/quiktipsr.htm

Good Luck - and let us know the EXACT error messages you
get (if any -
hopefully none!)


--
Noel Paton (MS-MVP 2002-2004, Win9x)

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

"Craig S" wrote in
message
...
I've had two daily Restore Points work correctly so I
presume I'm OK. Thanks to both of you for your interest! I
hope I don't post you back a recurrance.
-----Original Message-----
Umm - thanks, Mike! - I think!g

Unfortunately, I've never had the problem, either, so
have never had the
opportunity to bugchase it.


Craig,,,,,
Now - where to go from here, if Scanreg /fix doesn't
work????
thinking aloud, so this could ramble on a bit!g

I ASSume that you've checked for the presence of a
WININIT.INI file? - and
for the presence of any malware?

What's in the startup list in MSCONFIG?

from the sound of it, you change the system fairly
frequently - what was the
reason for the manual restore point you created just
before the problem
hit? - what was the system point created for (it
shouldn't have created one
automatically as the clock would have been reset after
the manual point,
AIUI).

Have you run any registry cleaners recently (specifically
in the relevant
period?) - have you got Spybot S&D set to Immunise? -
did you run it in the
relevant period? - what registry entries did you
remove/lock/restore with
it?


Probably best if I sleep on it - it's been a long week! -
if you can answer
the above before I wake up again, then I'll see what I
can find in the
morning.


G'night all!

--
Noel Paton (MS-MVP 2002-2004, Win9x)

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

"Mike M" wrote in message
...
There is no KB article that mentions SCANREG /FIX but
there is one that
IMO erroneously suggests SCANREG /RESTORE.
Erroneously because SCANREG
/RESTORE can only fix the error if it has happened in
the last five days
by replacing the faulty registry with a backup copy.
SCANREG /FIX
however fixes the problem 99.9% of the time regardless
of how long ago the
damage was caused by repairing the damaged entry
however what that entry
might be I have never managed to establish. I don't
feel this particular
problem is necessarily related to the use of (faulty)
software from
Symantec.

I'll leave Noel to follow up the problem.
--
Mike Maltby MS-MVP



"Craig S"
wrote ...

Thanks, Noel. Junked Norton last year system lock-
ups
(use NOD32-Spyware Blaster-Spybot S&D-AdAware 6 )& I
ran
scanreg /fix twice. Don't see other K-Base articles
this issue.



.



.