Boot Loop
I have a strange problem with my WIN2000 install. Windows will not complete the boot process, as the furthers that it gets is to the Logon screen/box. After logging on, the WIN 2000 sound comes on but the Windows screen stays blank with only the background color, no icons.
I have a strange problem with my WIN2000 install. Windows will not complete the boot process, as the furthers that it gets is to the "Logon" screen/box. After logging on, the WIN 2000 sound comes on but the Windows screen stays blank with only the background color, no icons. After about 28 seconds the "save settings" box appears and it stays on for about 13 seconds, then the "Logon" screen/box reappears.
I tried booting in various modes, including the "safe mode" but with stuck in a similar loop. Tried enabling the “bootlog” but can't seem to locate the file. The last time I encountered a similar problem, was after I updated with SP1. And, interesting enough on this particular WIN 2000 install I had recently installed Office 10 beta and then later uninstalled it. It was working fine after the uninstall, and reinstallation of Office 2000. The system was working flawlessly since the fresh installation in August 2000.
Any ideas?
Thanks!
I tried booting in various modes, including the "safe mode" but with stuck in a similar loop. Tried enabling the “bootlog” but can't seem to locate the file. The last time I encountered a similar problem, was after I updated with SP1. And, interesting enough on this particular WIN 2000 install I had recently installed Office 10 beta and then later uninstalled it. It was working fine after the uninstall, and reinstallation of Office 2000. The system was working flawlessly since the fresh installation in August 2000.
Any ideas?
Thanks!
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
Here a few suggestions to fix or pinpoint the trouble:
Pull the sound card and see if that helps.
Have you tried to revert to the last known good configuration (recovery console)?
Can you boot with an good old-fashioned DOS boot disk ?
Did you have the boot drive scanned just before this happened- do you find .chk files (saved from a fix of bad sectors/crosslinked files)In that case they contain data that isn't availabe anymore, possibly system files
As you cant't get to safe mode I'd also look for a hardware problem; testing memory chips one by one, possibly loose cards, etc.
Have you touched bios and perhaps, maybe, possibly switched something accidently?
Have you updated any drivers or installed anything just before this happened ? What was the last thing you did before thsi occured?
As a last try you could do a system file restore from the W2K cd.
Let us know whatever or whoever it was
H.
PS. Once long ago (W3.1 I think it was)I got myself in an endless loop by trying to make a batch file of proggies always starting when windows started. Worked fine but the file was called startup.bat and contained the command startup. Sometimes the weirdest things have the simplest causes.
Pull the sound card and see if that helps.
Have you tried to revert to the last known good configuration (recovery console)?
Can you boot with an good old-fashioned DOS boot disk ?
Did you have the boot drive scanned just before this happened- do you find .chk files (saved from a fix of bad sectors/crosslinked files)In that case they contain data that isn't availabe anymore, possibly system files
As you cant't get to safe mode I'd also look for a hardware problem; testing memory chips one by one, possibly loose cards, etc.
Have you touched bios and perhaps, maybe, possibly switched something accidently?
Have you updated any drivers or installed anything just before this happened ? What was the last thing you did before thsi occured?
As a last try you could do a system file restore from the W2K cd.
Let us know whatever or whoever it was
H.
PS. Once long ago (W3.1 I think it was)I got myself in an endless loop by trying to make a batch file of proggies always starting when windows started. Worked fine but the file was called startup.bat and contained the command startup. Sometimes the weirdest things have the simplest causes.
sounds
like tricks we use to play on each other.
although a rather nasty one to play.
sometimes ppl like to put in your startup or run or whatever ..
a shutdown command or loggof command.
OR the other heinous thing is
Office 10 beta had the subscription thing in testing?
and after all these months its kicked in ..realised you have a pirated copy of win2k and killed everything
Try to install the recovery console from the win2k cd...
see if a full resotre works ..otherwise its slash and burn.
like tricks we use to play on each other.
although a rather nasty one to play.
sometimes ppl like to put in your startup or run or whatever ..
a shutdown command or loggof command.
OR the other heinous thing is
Office 10 beta had the subscription thing in testing?
and after all these months its kicked in ..realised you have a pirated copy of win2k and killed everything
Try to install the recovery console from the win2k cd...
see if a full resotre works ..otherwise its slash and burn.
