I just built my own PC, and everything is working fine for me, with one exception. I am running Windows 98 SE, and when I go to shut down, instead of seeing the usual "Windows is Shutting Down" screen (with the clouds, etc) and then the "It is now safe to shut off your computer" message, all I get is a cursor at the top of a black screen. Usually I can hear the hard drive spin down, and I end up pushing the power switch on the case then. But sometimes after the hard drive spins down, it starts up again, and the computer restarts. I have read other similar questions and tried all sorts of solutions posted on this forum (including downloading a couple different patches from Microsoft, mentioned in other posts, and I've also tried the troubleshooter on the Microsoft Windows98SE website,) but I've had no luck so far. I have also downloaded and installed the latest "Critical Updates" from Microsoft. About my computer: As I said above I built it myself, so there is no brand. I have an "FIC 1st Mainboard, VA503+" motherboard, a 500mhz AMD K6-2 processor, and 128MB RAM. I have a 20GB hard drive, a 3.5" floppy drive and a 50x CD ROM drive. I have a Visiontek RIVA TNT2 32MB AGP video card, ASOUND Gold ISA sound card, DSI 56K PCI modem, Xircom PCI usb card, and a Kouwell PCI SCSI card. If you have any ideas, please reply! The only thing I can think of is trying downloading the latest BIOS settings (currently, the website where I would do this is temporarily unavailable).

I don't have a quick answer, but here is a site with oodles of information. http://www.aumha.org/a/shutdown.htm HTH

http://216.167.71.32/windows98/troub-51.shtml more 98se shutdown help.

have you enabled usb in bios/setup this will solve that sometimes.

Andrew, if you have an AT case, that is the problem. I experienced this building my pc a few months ago using the VA-503+ and a K6-3 333. Download the patch in the support area of FIC's website, that should work. Its question 25 in the VA-503+ support/faq area. Good luck.

microsoft.com look for support.goood luck :)

Problem Solved! Thanks to everyone who replied. Vince had the magic solution that worked: it was because I'm using an AT case and pwr supply, I needed to download a newer version of BIOS that had the fix for this very problem.