I have tried everything I can think of to get Windows 98 Second edition installed on my system. However, everytime, after a seemingly good install to a freshly formatted partition and detecting my hardware and installing the drivers, when it finally goes into its "normal" mode (non-safe mode), it hangs for a long time (with the select light on the controller card and the hard drive lit), then eventually gives a blue screen saying:
Unable to write to drive C:
Data or files may be lost.
I can get it to boot in safe mode and remove the Adaptec AHA-2940UW SCSI controller device, then it will restart in "normal" mode and detect the "new" device and install the driver (I have tried the driver from the Win98SE, my old AIC78xx driver that came with the controller, and a "new" (older than Win98SE) driver downloaded from the Adaptec site). However the same thing happens. If I allow it to just reboot normally after the hang, Win98 will start, but I do not have access to my CD-ROM because the device was not started due to ASD:
"Windows stoppped responding while attempting to start this device, and therefore will never attempt to start this device again (Code 11.)"
I have scanned the disk under both Windows (safe-mode) and the Adaptec SCSI-Select Utilities, but no errors were found.
The PCI assigned IRQ's are all unique, with no conflicts or sharing. I am using a Tyan motherboard with Diamond S2000 Pro video, Adaptec AHA2940UW SCSI, LinkSys LNE100TX NIC, and WinTV PCI cards, and SB-AWE32 and USR 56000 Voice ISA cards. I have tried running without the WinTV card and even without the ISA cards. All Award BIOS (v4.51PG) settings are at their most conservative. The SCSI hard drive is a Samsung 2.1GB (model WN312162U).
My Caldera Open Linux 2.2 on the same drive seems to work just fine. I have tried installing another drive (IBM 309170U2) and have had similar problems with Win98SE, although I have reinstalled Windows 95a and RedHat Linux 6.1 on that drive without problems. I would really like to get my new 9GB drive working with FAT32!
What else can I try? I can't find any reports of a similar problem in Microsoft's Knowledge Base, Adaptec's Web site, or several other support sites.