And to add to that;
Looking in;
HKEY_LOCAL_MACHINE\SYSTEM\Select
you'll find the D-Word values for
"Current"=dword:00000001
"Default"=dword:00000001
"Failed"=dword:00000000
"LastKnownGood"=dword:00000002
CurrentControlSet is volatile and will always be an image (at boot) of
what's defined in ControlSetx where x = the value of "Current"
Choosing last known good boots the system with the control set that last
successfully booted your system. Control sets contain system configuration
information such as device drivers and services. Nothing to do with the
software hive.
--
Regards,
Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft MVP [Windows NT/2000 Operating Systems]
Microsoft Certified Professional [Windows 2000]
http://www.microsoft.com/protect.
:
The reason this isn't possible in Windows 2000 is because this operating
system came out before Microsoft developed the Restore functionality. The
first operating system that had that was Windows ME and I believe they
continue to this day with that functionality. In Windows 2000 we have what
is called "return to a prior good configuration." Arrived at by hitting F12
before the Windows 2000 spash screen comes up. This is akin to what Windows
98 had where it saved registry settings from the last 5 successful boots.
They are called rdb files something like that. When you had a bad boot in
Windows 98 we'd get .BAD files. Not a pretty thing to see n Windows
Explorer.
Anyway this is the crux of the issue. What may seem a successful boot to
the machine may not be a successful boot to you. So if you rebooted your
machine once in the time you have experienced this trouble and got to the
desktop well then that is the last known good configuration. It doesn't
work too well and so that is why the Restore functionality was developed.
About a year after Windows 2000 first seen in Windows ME. That was a
selling point at the time.