Heres the deal, I installed and played KOTOR2 yesterday, predictably it crashed...so I rebooted, it crashed again...tried to reboot....tried to reboot...cant reboot, it gets stuck at Mup.sys driver, a useless novell network interface driver, that I dont need, yet somehow fucks up my boot sequence.
I've tried multiple things, booting from windows CD, booting from boot disks, safe mode, network boots, repairing windows installation, recovery console...etc etc. To no avail.
To those of you that may be able to help, the most relevent piece of data about this problem seems to be the fact that the computer is unable to read my hardrive to go into the recovery cosole, it gets stuck at
"scanning 28640mb on id1 blah blah blah" endlessly, I even let it go over night, it simply wont scan my harddrive. This leads me to think its a hard drive issue somehow caused by installing a new game, though WHY it would get stuck on mup.sys is beyond me. SO, does anyone have any bright ideas about what might be happening? the mup.sys bug is very common, but its extremely UNcommon that I cant boot to the recovery cosole.
this is a shot in the dark, but I figure most of you fuck up your computers now and then, Im hoping this may ring a bell :/
EDIT: Im on my old 333mhz right now..Im surprised its still alive and working after all these years
2005-02-21, 11:19 PM
Threaded Mode