Problems restarting my computer in win98se, please help!

[divinemartyr]

Just bought the following set up:

Pentium III 866 @ 936mhz
256 mb Crucial @ 144fsb cas2-2-2
Asus CUSL2-C motherboard (BIOS revision 1003)
30 gig Quantum Fireball LM 7200 rpm ata/66 HDD
Yamaha DS2416 Professional Audio Card
32 mb Leadtek Winfast GEForce2 GTS Video card
72x Kenwood TrueX CD-ROM
12x10x32 TDK VeloCD CD-R/CD-RW
1.44mb Teac Floppy
Black Hydraulic Case with 300w power supply
Microsoft Natural Pro Keyboard
Microsoft IntelliMouse Explorer
17" Mitsubishi Diamond Pro 710 Monitor

and i have my own home theatre connected to the PC eheh =) no BA's here. Anyway

THIS is my problem:

I installed all my software last night, everything was running smoothly. I installed windows 98 as my OS. Then I upgraded to win98SE and after I did this, the system hangs on the "Windows is shutting down" screen every time I restart (or it needs to restart after installing drivers etc) and it won't restart. I did this 2 nights ago (upgraded from win98 to win98se) and the same thing happened as soon as I installed SE. The strange thing is, it restarted fine before installing SE. Are there any known issues with win98se not restarting? Any help would be appreciated.

divinemartyr

 

[MGMorden]

There are known issues with all versions Windows 9x restarting/shutting down. It's a problem that's been around since 95, and they've never seemed to figure out how to fix it. I work as a technician at the University I attend and in my department 80-90% of the Windows 9x machines don't normally shut down properly. As far as the 98SE upgrade is concerned, it's likely that this did cause it, but simply because you upgraded it, not b/c you upgraded to 98SE (MS's upgrades usually don't do very well, I would always recommend a clean install, but seems like your choices were limited). As for a solution, I'm pretty sure MS has a page up on their support site dedicated to this exact issue. You might want to check there.

Good luck to ya.

 

[divinemartyr]

Yes actually someone over in the General hardware forum posted a response to my thread on the same subject, and it was exactly what I needed. It addressed this exact issue along with a patch from MS!


divinemartyr