Gateway 2910A/I SCSI PCIe DOS Drivers
First off, you've probably found this info NOWHERE else. This took me a while.
So consider a Paypal Donation!
Here's the info on the driver I used to be able to recognize hard drives. From some readme I found somewhere.
-----Pasted portion-----
So consider a Paypal Donation!
Here's the info on the driver I used to be able to recognize hard drives. From some readme I found somewhere.
-----Pasted portion-----
ASPI8DOS.SYS ------------ ASPI8DOS.SYS is Adaptec's ASPI manager for AIC-7850/7855/7870 based PCI SCSI host adapters. Running Adaptec EZ-SCSI will automatically detect which host adapter you have installed, which ASPI manager needs to be loaded, and what the correct command line switches are. o If you have an Adaptec PCI SCSI host adapter installed in your system, and you have EMM386.EXE loaded from MS-DOS versions up to 6.2, your system might hang if loading the ASPI manager after EMM386.EXE. This has been fixed in the EMM386.EXE that ships with MS-DOS 6.22 and later. If you experience this problem, you will either need to load ASPI8DOS.SYS before EMM386.EXE, or upgrade to MS-DOS 6.22 or later. If the ASPI manager detects a conflict, a message will be shown explaining how to work around the problem. Other ASPI modules (e.g. ASPICD.SYS) can continue to be loaded high. o There are several techniques for a driver to determine if its PCI SCSI host adapter is installed in your system. ASPI8DOS.SYS will determine which is the best method, and has been written to work around the EMM386.EXE problems discussed above. There are three command line switches you can use to force the ASPI manager to use a specific method. These are: /MB - This command line switch will force the driver to use the PCI BIOS calls (INT 1Ah) to scan for PCI SCSI host adapters. /M1 - This command line switch will force the driver to use the "Mechanism 1" method for scanning for PCI SCSI host adapters. /M2 - This command line switch will force the driver to use the "Mechanism 2" method for scanning for PCI SCSI host adapters. For example, if you want to force the ASPI manager to find your PCI SCSI host adapter using PCI motherboard BIOS calls, your CONFIG.SYS would be: DEVICE=C:\SCSI\ASPI8DOS.SYS /D /MB NOTE: Most PCI systems do not support all three methods for scanning for PCI cards. It is recommended that you let the ASPI manager determine which method is suitable. o If you would like ASPI8DOS.SYS NOT to reset the SCSI bus, during driver initialization, you can use the /NORST command line switch. For example: DEVICE=C:\SCSI\ASPI8DOS.SYS /D /NORST If you would like ASPI8DOS.SYS to always reset the SCSI bus, during driver initialization, you can use the /RESET command line switch. For example: DEVICE=C:\SCSI\ASPI8DOS.SYS /D /RESET o If there are more host adapters that ASPI8DOS can support, ASPI8DOS will display "Not enough memory for all host adapters". In this case, the user should manually add more lines of "DEVICE=ASPI8DOS.SYS" to CONFIG.SYS to support the extra host adapters. EZ-SCSI only installs one entry in config.sys for ASPI8DOS.SYS.
-----
--End Pasted Info--
I actually have a DOS FLOPPY (!!) of Adaptec EZ-SCSI 1.0 and I found some later drivers I upgraded.
Using INSTALL.BAT on EZ-SCSI 1.0 floppy DOES NOT recognize the Adapter. Probably because it's too new: it's a PCIe card.
Using INSTALL.BAT on EZ-SCSI 1.0 floppy DOES NOT recognize the Adapter. Probably because it's too new: it's a PCIe card.
As of this writing, the ASPI Manager for AIC-78xx/-75xx v1.32 recognizes this controller card and an attached SCS2SD device with 2 SCSI LUNs.
Comments