win98se shutdown problem

saimike

Senior member
Oct 30, 2000
393
0
0
hi guys,

i cant seem to shutdown win98se without it hanging on the "shutting down ... " screen with the win logo. when i try to restart, sometimes it reboots successfully and sometimes it doesnt. how do i correct this? pls dont tell me to reinstall win98se ... that would majorly suck ... thanks
 

SaturnX

Diamond Member
Jul 16, 2000
3,415
0
76
Hrmm... have you checked Windows Update and downloaded the Windows ShutDown Patch (it disables Fast Shut Down) or if you haven't, goto Start>Run>msconfig and I think check under the advanced button and uncheck fast shut down. (forget where it is exactly swtiched to Win2K). Also look for any hardware conflicts IRQs etc..

--Mark
 

yazz

Senior member
Oct 9, 1999
702
0
0


if that does not work try going into the Device Manager and find PCI BUS. disable IRQ steering and click the USE BIOS button.

have fun...
 

saimike

Senior member
Oct 30, 2000
393
0
0
i think i downloaded the ms shutdown thing, but i'll try the rest of the stuff. what does the pci irq steering thing do? what's the effect of using bios for that? thanks!
 

aUt0eXebat

Banned
Oct 9, 2000
2,353
0
0
if you do d/l the patch and that dosnt work, do what yazz said. all that does is the BIOS controls the IRQ settings for everything, instead of windows doing it. THat should work.
 

badtz42

Member
Oct 20, 2000
79
0
0
I had the same problem. I would have to click reboot and then shut the computer down manually when it started to reboot. Even reinstalling Win98SE didn't fix it. I was never able to fix it :frown: I've upgraded to Win2k since though :D
 

snoogans

Banned
Sep 14, 2000
248
0
0
There was a patch for that problem with ATA-100 Hard Drives with 2MB of cache. I'm at work so I can't try it yet but I'll see if disabling PCI steering works. If not (or just because you wanna be nice) could anyone direct me to the said ATA-100 fix? Searched MS, no luck...searched some tech sites and still no luck. Thanks
 

Cnuke

Member
Nov 7, 2000
186
0
0
Just as a side note, going into msconfig and cleaning helps to. Found on an issue with my network a client of AS/400 was causing it and a patch was aqired from them to fix problem.