BUSLOGIC WINASPI IMPLEMENTATION UNDER NT:----------------------------------------Winaspi is the interface for windows applications to access the devicesattached to a scsi controller. It is basically a set of two DLLs,WINASPI.DLL and WNASPI32.DLL for 16 bit windows and 32 bit windowsrespectively. As NT runs on non-intel platforms also like alpha, the16 bit winaspi does not make any sense as 16 bit winaspi has a conceptof segment:offset pair for the data buffer and the post routine. SeeWINASPI documentation about programming specifications.

Some old winaspi applications do not run okay on NT. 16 Bit WINASPIapplications written for windows 3.1 environment might cause someproblems as some of windows 3.1 apis are not supported on win nt.One known application to test winaspi (16 bit) is central pointbackup. It also occasionally fails and might continue by hitting if any error message pops up. The adaptec EZ-SCSI versionof SCSI Explorer uses wnaspi32.dll and is a good way to test.

As microsoft is strongly against using ASPI, this can be given tocustomers who need winaspi for some backups etc.NOTE: These binaries are only for Intel platform.

This README file contains compressed installation instruction, updateinstructions and notes on configuring tunable paramenters for the BusLogic MultiMaster device driver. For more detailed installation instructions and other information, please refer to the manual included with the software package.

II. Installation ================NT 3.5, NT 3.51 and NT 4.0 include MultiMaster support on the distribution CD-ROM. The following steps are needed only if you cannot install with the built in driver.

9. The system will load the MultiMaster device driver and indicate that it has recognized a MultiMaster PCI SCSI Host Adapter in your computer. Press enter to continue with the rest of Windows NT 3.5x installation.

III. Upgrading an existing system================================NT 3.5, NT 3.51 and NT 4.0 include MultiMaster support on the distribution CD-ROM. The following steps are needed only if you have a problem with the built in driver.

This procedure does is a very wordy way of getting Buslogic.sys to (Boot device):\WINNT35\SYSTEM32\DRIVERS for NT 3.51 or (Boot device):\WINNT\SYSTEM32\DRIVERS for NT 4.0Making a backup of the Original buslogic.sys would be the safest thing to do since this procedure over writes the original file.