IWETHEY v. 0.3.0 | TODO
1,095 registered users | 0 active users | 0 LpH | Statistics
Login | Create New User
IWETHEY Banner

Welcome to IWETHEY!

New Oh man that is hosed
SOFTWARE is everything installed, including Windows itself.

You can do a "last known good" - dance on F8 while it's trying to boot.
-drl
New ICLRPD
You can do a "last known good" - dance on F8 while it's trying to boot.
===

Implicitly condoning stupidity since 2001.
New Nah
"Last Known Good" is nothing to do with the registry, or the drivers. It's simply the last time you managed to log in. The best you can do with that is to recover your own user registry hive, which won't help here.


Peter
[link|http://www.debian.org|Shill For Hire]
[link|http://www.kuro5hin.org|There is no K5 Cabal]
[link|http://guildenstern.dyndns.org|Home Page - Now with added Zing!]
New Nah
I thought - well I know - a successful shutdown will by default make a backup copy of the registry (that's what all the disk activity is), which can be reloaded with a "last known good". Usually the backup has the same issues as the primary, because by the time you know a real problem is afoot it has propagated to all 4 backup copies. The only real use is for an install of something that completely prevents booting.

I remember well when this facility was added to Windows NT - the first release (3.1) did not have such a facility, so if you installed a driver that would not work (very easy to do in the early days - wow this was 10 years ago now), you were dead, the whole thing had to be reinstalled. 3.5 allowed the "Last Known Good" choice to roll back to the previous configuration.

The backups are somewhere below system32 and are compressed.
-drl
New My bad
Anyway, I never bother "fixing" Windows boxes.

There's no point (it'll only break again anyway) and it's far more cost-effective to reload the operating system.


Peter
[link|http://www.debian.org|Shill For Hire]
[link|http://www.kuro5hin.org|There is no K5 Cabal]
[link|http://guildenstern.dyndns.org|Home Page - Now with added Zing!]
     Windows 2000 Pro Bluescreen on boot - (broomberg) - (16)
         to recover data - (boxley) - (2)
             Toss it - (broomberg) - (1)
                 Are you sure? - (orion)
         Pull the drive - (inthane-chan)
         Oh man that is hosed - (deSitter) - (4)
             ICLRPD - (drewk)
             Nah - (pwhysall) - (2)
                 Nah - (deSitter) - (1)
                     My bad - (pwhysall)
         I got that yesterday... - (hnick) - (5)
             That is weird - (deSitter) - (4)
                 Sure is. - (hnick) - (2)
                     Re: Sure is. - (deSitter) - (1)
                         Yeah, brain fart - (hnick)
                 True hardware error in my case - (broomberg)
         Hard drive errors - (orion)

Thank you, drive through.
61 ms