Jopa,
I use Adaptec SCSI host adapter with the exact same ASIC--the AIC-7880 with Windows NT 4.0. The specific model is the AHA-2940U2W. I bet you have either this model or some variation thereof, possibly the AHA-2940U.
You will need to go to Adaptec's Web and download the appropriate driver for Windows NT 4.0 and copy it to a floppy. While you’re there, you might also want to read up on your host adapter and make sure it’s properly configured for your system. Read their SCSI tutorials, the specs for your adapter, cable recommendations, and the installation guide for the adapter.
You can also download a BIOS update for the host adapter is you don’t happen to already have the latest version. I wouldn’t update the BIOS, though, unless it really looks like it’ll solve a specific problem *and* unless you’re sure that you’ve got a retail version of the host adapter--not an OEM version. Some OEMs like to do funky things with the hardware they use, others don’t. For what it’s worth, I’ve used the BIOS update on Dell OEM versions of the 2940U2W and never had a problem—Dell apparently doesn’t alter the card.
Make sure the host adapter is properly installed and properly jumpered.
Press - during the POST to run Adaptec’s SCSISelect BIOS setup utility and make sure everything's set up correctly. If you need some guide to using the SCSISelect utility or need to know what some of the settings mean, you can find all the information you need on Adaptec’s site. (This information is included in the host adapter’s manual.) You might try using default settings. Make sure the host adapter is set to provide termination. You’ll have three options: Termination enabled, termination disabled, and automatic. Also make sure the card is supplying termination power to the SCSI buss. If you're using passive termination, this will be unnecessary, but it won’t hurt. If you’re not using passive termination and some other device is already supplying termination power, that won’t hurt either because the terminators in the host adapter and hard drive will have protection against over voltage.
Make sure you’re using the correct sort of cables. The cables you need depend on the type of signalling you’re using and the interface transfer speed. Be aware that an unfortunate number of vendors have absolutely no clue whatsoever when it comes to SCSI cables. In fact, I have only been able to find *one* vendor who isn't clueless about these things and that's Adaptec. If a vendor tells you, "Yeah, that cable will work--it says ‘SCSI-III’ right here.", you might do well to get another opinion. I can't count the number of times I've ordered cables and gotten almost but not quite compatible parts no matter how clearly I specify the exact type of cable needed. One example: I ordered cables for my Ultra160 hardware. I got cables for Ultra2 hardware. The reason? Both types of cable are called “SCSI-III” cable. The term "SCSI-III” is quite broad and includes different types of incompatible hardware.
Anyway, make sure you're using the correct cables for your hardware.
Make sure the cable isn't wrapped around anything, coiled, or folded back on itself. I have personally seen cases in which a very knowledgeable, highly intelligent person (okay, so it was me!), carefully and gently folded up a ribbon cable to improve airflow and get it out of the way. This screwed up the signal across the buss just enough to get intermittent read/write errors. If the cable is wrapped around a power supply, you'll probably have some problems.
Make sure all connections are good.
Make sure the hard drive is correctly jumpered. If you don't have any other SCSI devices besides the host adapter and the hard drive, connect the host adapter card to one END of the cable and connect the hard drive to the other END, and jumper that drive to provide termination--assuming you don't have a SCSI cable that has a terminator built into the end. (All Ultra160 ribbon cables have a terminator built right into the end of the cable. Some really nice Ultra2 cables are also made this way. If this is case and the cable has a terminator built into the end--you'll know if it does--it'll be encased in a big rectangular housing on the end--do NOT configure your hard drive to provide termination, 'cause that end of the cable will already be terminated by the terminator built into the cable.)
Make sure all jumpers are making good contact and are snug. If a SCSI ID jumper isn't making a good connection, the SCSI ID reported by the drive or some other vital option might change during use. I've seen this happen and it took quite a while to find the cause of the problem.
If everything seems good so far, run the SCSISelect utility. See if the host adapter correctly detects and recognizes the hard drive. If not, you’ve got a hardware or configuration problem.
Using the SCSISelect utility, scan the disk for errors. If errors are found, you’ve got a hardware or configuration problem. Low-level format the drive and check for errors again. (Don't do a low-level format unless the drive is installed in the system and has reached a stable ambient running temperature.)
If the SCSISelect utility can detect the drive, format the drive, and finds no errors when checking the disk for errors, your hardware is good to go and you can safely assume that any problem you encounter after this point is some sort of software issue.
Install Windows NT. You WILL have to provide the host adapter driver during installation. Provide the driver during the installation phase when NT is setting up support for mass storage devices. You will need to specify a mass storage device and provide a disk (the disk with the host adapter driver on it) during installation. Select the correct model of host adapter you're using, and continue the installation. It should work fine.
I'm sorry to write such a long post, but if you get through all this you should be able to get it working.
I think it’s odd that Windows 98 ran into a problem. I know that Windows 98 Second Edition does include support for SCSI host adapters using the AIC-7880 ASIC. I bet the pre-Second Edition release does as well.
Try to determine whether you’ve got a hardware problem. The SCSISelect utility can be invaluable for this.
