I tried microsofts solution to restarting found ->
http://support.microsoft.com/default.aspx?scid=kb;en-
us;250323
but it doesnt work. Any help would greatly be appreciated
Insert your bootdisk
(http://home.earthlink.net/~montybarker/bootdisk.com) and type
SCANREG /FIX
at the A:\> prompt.
--
Monty Barker
Visit my site @ http://home.earthlink.net/~montybarker like 5500 others
have!
Be sure to sign my Guestbook while you're there!
Please help me name my future email newsletter at
http://home.earthlink.net/~montybarker/newspoll.html! Thank you!!!
Please post replies to the newsgroup so that all other readers may
benefit.
But, if you *must* email me, my email address is on my web site above.
"Come to the newsgroup before throwing Windows out the window."
When Windows starts, it checks the Registry. If it passes this first test,
two things happen: a copy is made of that Registry for future use, and
Windows starts.
When a damaged Registry is found, Windows goes to one of the backup copies
and tries to use it instead. The most common cause of the problem you have
is when the backup copy has become damaged also, so you keep replacing your
most current with one that won't pass the startup test.
One way around this is to manually load an earlier version of the Registry.
Your last 5 are backed up. Your worst problem would be if this has been
going on for at least 5 days because, in that case, all backed up copies
will be corrupted. But you can try SCANREG /RESTORE and see if there is an
older one that makes this problem go away.
If that doesn't work, try repairing the current one with SCANREG /OPT /FIX.
One major cause of ongoing Registry damage is physical RAM that is damaged.
It will cause writes to the Registry to be wrong.
--
Jim Eshelman
MS-MVP, Windows Shell/User
http://aumha.org/
http://WinSupportCenter.com/