Help with Win2000 box...

[ZeroEffect]

i know this isn't strictly on topic, but this box crunches seti, and that's about
it. Anyways, OS is Win2000. Was checking SetiQ and noticed it was overdue
so i turned the monitor on and it had hung up on reboot. The status bar on
the bottom of the page gets to about 90% and then just hangs. I tried
Safe Mode reboot, same thing. Tried reinstalling the OS, it loads the startup
files and then win it reads "Starting Windows 2000" it hangs.

I'm not sure of what to try next, short of FDisk ing it and putting a fresh install
on it. Is there any way i can save the two units it was working on? I took the
HDD out and put it in another system and backed up some misc. files and mp3s,
so the HDD is working fine.

Any ideas from you guys would be great, if not it's getting FDISKed tonight... i can't
stand it not crunching! (Win2K = Stable?)

System info:
Nothing new installed for over a month.
Tyan Tiger MP S240 motherboard
IBM 60GB HDD

thanks guys.

 

[EvilWobbles]

I had a similar problem with a Win 2000 box several months ago. The system would load the Windows 2000 logo screen and then hang. I tried safe mode and also got no result.

Luckily I was able to use the option to Load Last Known Good Configuration. This loaded Windows 2000 just fine. You might want to give that a try. I was able to get to the data I needed and I promptly FDISK'd and formatted the drive and loaded a Windows 2000 Ghost image.

Good Luck...

 

[ZeroEffect]

...it hangs on Last Known Good Configuration too.
it's not even getting to the windows logo screen.

thanks for the info though.

 

[RaySun2Be]

<I took the HDD out and put it in another system and backed up some misc. files and mp3s,
so the HDD is working fine. >

Do the same for the SETI folder. Hook up the hard drive, and copy the entire SETI folder & subfolders (if using SETIDRIVER) to another PC.

If you have to FDISk and start over, you can then copy the SETI folder back over, start it up, and it should start crunching from where it left off.

As far as Win2K, try the Last Known Good configuration as suggested. If that doesn't work, you can try to repair Win2K running setup off of the Win2K cd, I think there are some repair options. Only repair the registries as a last resort.

If that doesn't work, try creating install floppies (it takes 4) from the Win2K CD, then boot up and run through the install, there is a repair option on there that might work.

It worked for me when I changed out my BH6 for a KT7 board, and Win2K choked on the chipset change and hung up at about the same place, then wouldn't recognize the hard drive or CD-ROM.

Good luck!

 

[Robor]

I've never had much luck with the repair option myself. Anymore if I run into one of those problems I put a new HD in the box, load Win2K from scratch, and copy any needed data over from the old drive. Sometimes it's quicker to just reload the system than waste the time troubleshooting. Pretty often you have to reload anyway.

Good luck dude. Oh, check you PM...