VOGONS


Shutdown issue on P5A-B

Topic actions

First post, by F2bnp

User metadata
Rank l33t
Rank
l33t

Greetings! I've had this issue for a while, but was too lazy to bother to be honest. I've got a P5A-B with a K6-III+ and Windows 98 installed. I'm using an AT power supply, which means that whenever I am to shutdown the computer, I should be getting the classic "It's now safe to turn off your PC" screen. Unfortunately, it always hangs right before that screen, showing the Win98 logo and a text that reads "Windows is shutting down".

Having read this discussion leads me to believe that this is ACPI related, but I can't really say the solution that was given there is optimal. I'm running the latest bios (1011) and the system is completely stable otherwise.

Any suggestions welcome!

Reply 1 of 7, by alexanrs

User metadata
Rank l33t
Rank
l33t

Isn't there a small TSR that disables the ATX OFF command so you can drop to DOS by performing a shutdown? If that works, it shouldn't be hard to make a TSR to fix it.

Reply 2 of 7, by tayyare

User metadata
Rank Oldbie
Rank
Oldbie

This problem frequently occurs and even according to Microsoft support, it has too many possible reasons.

https://support.microsoft.com/en-us/kb/238096

Copied from a post I just made for a user that is experiencing a similar problem: (second time in a week) 🤣

I know it's annoying but I also know it's not deadly. When you stuck with "Windows shutting down...blah..." window, just wait for a couple of minutes and shut down your computer. Nothing bad will happen. I had many rigs that do that to me, and even during the days, when you make one last update or install that one last utility, this was happening, sooner or later. The matter was not if, but when. We used 98 machines like this forever during the times without anything bad happening.

GA-6VTXE PIII 1.4+512MB
Geforce4 Ti 4200 64MB
Diamond Monster 3D 12MB SLI
SB AWE64 PNP+32MB
120GB IDE Samsung/80GB IDE Seagate/146GB SCSI Compaq/73GB SCSI IBM
Adaptec AHA29160
3com 3C905B-TX
Gotek+CF Reader
MSDOS 6.22+Win 3.11/95 OSR2.1/98SE/ME/2000

Reply 3 of 7, by meljor

User metadata
Rank Oldbie
Rank
Oldbie

It is a very well known issue, some of my systems do this, some don't. It never happens with a clean installation but often after installing drivers. I don't care, otherwise it runs fine.

asus tx97-e, 233mmx, voodoo1, s3 virge ,sb16
asus p5a, k6-3+ @ 550mhz, voodoo2 12mb sli, gf2 gts, awe32
asus p3b-f, p3-700, voodoo3 3500TV agp, awe64
asus tusl2-c, p3-S 1,4ghz, voodoo5 5500, live!
asus a7n8x DL, barton cpu, 6800ultra, Voodoo3 pci, audigy1

Reply 4 of 7, by F2bnp

User metadata
Rank l33t
Rank
l33t

I figured it wasn't a real issue, but just wanted to make sure. Thanks for the answers!

Reply 5 of 7, by F2bnp

User metadata
Rank l33t
Rank
l33t

Bumping this thread just in case anyone is interested. I found that the shutdown issue doesn't appear on other Windows versions. Windows 95 OSR2.5, Windows ME and Windows 2000 shutdown properly. This is somewhat puzzling to me, that Windows 98 SE would have such an issue. Could it be related to APM or ACPI?

Reply 6 of 7, by alexanrs

User metadata
Rank l33t
Rank
l33t

Have you installed ACPI support? One of my machines had shutdown issues with Windows 98 (froze at the Shutting Down Windows screen as soon as I installed the latest official Voodoo drivers), and installing ACPI support like described here seems to have solved everything.

Reply 7 of 7, by F2bnp

User metadata
Rank l33t
Rank
l33t

I'm pretty sure I tried this once, but it was after applying mainboard + 3dfx drivers, as well as the Unofficial Service Pack 2.1a. I'll give it another go with a clean install and see what happens.

UPDATE:

Turns out Windows 98SE installed ACPI by default on the board, so I did a clean install with APM instead (you just have to type "setup /p i) and now the system shuts down properly (displays "It is now safe to turn off your computer"). I'm guessing Win95 uses APM and WinME uses an updated ACPI? It would seem weird for ME to install APM by default, if 98SE installs ACPI, unless they figured out the bug later on and had no solution other than to install APM instead.