DOS SCSI ASPI FILES READ.ME FILE
--------------------------------
Copy All files to a directory called C:\BUSLOGIC.
Sample CONFIG.SYS
DEVICE=C:\BUSLOGIC\BTDOSM.SYS /D /M - ASPI Manager
DEVICE=C:\BUSLOGIC\BTCDROM.SYS /D:MSCD001 - If CD-ROM is Present
(Place CD-ROM on ID
2-6)
DEVICE=C:\BUSLOGIC\BTMDISK.SYS - DASD Support
(>2 Drives, Drives on ID 2-6,
Removable Media Drives)
Sample AUTOEXEC.BAT
C:\DOS\MSCDEX /D:MSCD001 /M:10 - Mounts CD as next Avalible
Drive.
ASPI MANAGER DOCUMENTATION 08/15/94
The Revision 4.xx DOS ASPI manager has several new features along
with the WIN-ASPI interface module. Most of these features are related
to command line switches at install (boot) time. Along with improvements
in the existing switches, additional switches are present.
** First a quick look at existing switches and their effects:
The /X, /N, /F, /I, /D switches work the same as before.
The port specifier /P now is NOT required on multiple card
installations or if the card is not on the primary port (330h). Prior
manager revisions only searched one card on the primary port. Now, all
cards are located and are logged in. If the user wants to skip a port
that may be found, any /P switch will defeat the port scans and only log
the implicit port(s) entered.
The /M, disable mailbox in the prior design had no qualification
by system configuration. The disable of the mailbox I/O works only if
certain system configurations are met. For example, if EMM386 is loaded
the /M will cause I/O errors as the non-mailbox I/O will not handle
scatter-gather I/O. When the /M is requested, if the system config is
not stable, the DOS Manager will not observe the request and will inform
the user. Also if Windows is started with the /M request, the DOS Manager
will inform the user and "freeze" windows at the init screen.
** Next a look at the new switches and their effects:
The /L switch allows /L for luns=8, and may be set to /L16, /L32
and /L64 to set the LUN support on WIDE SCSI cards.
The /E, rescan SCSI bus on ASPI "Request Device ID" (cmd=01), will
allow dynamic rescan of the bus. Prior manager revisions maintained the
code in memory for this function requested or not. The new manager will
discard the code if /E is not requested and thus saving about 1.6k of
memory requirements.
The /C switch clears the 486 or better system processor cache on
mailbox writes if so requested.
The /B switch allows the user to specify how many active mailboxes
and associated ccbs are allocated. Default is 4, the user may specify
between 4 to 8. Increasing the count from 4 to 8 will require about
1.5k of additional memory per card.
The /R switch stops the ASPI manager from "hard" resetting the
SCSI adapter if not under BIOS control. This will be useful in multi
initiator configurations.
The /S switch enables the SEEK command to operate. Default is not
enabled.
The /A switch enables WINASPI DLL full Adaptec emulation. Default
is not enabled.
The /J switch forces the DOS Manager to only scan 8 SCSI ID's on
WIDE SCSI cards.
The /W switch is active only with /D, and allows the screen display
to pause when each card is scanned. This is to prevent the displayed
information from scrolling off the screen so it may be analyzed.
WINASPI Description 08/15/94
Windows ASPI, or WINASPI, is a windows device driver layer used
for re-entrant, multi-threaded SCSI bus access for windows 3.00 or
higher. The WINASPI layer, provides an easy access method for windows
applications for SCSI I/O. This method is provided in the form of a DLL
program (dynamic link library). The name of the program is WINASPI.DLL.
The DLL functions are imported by an windows application during it's
operation. The DOS Manager v4.xx will have the ability to run in the
windows protected mode environment.
Also included for the WINASPI layer is a VxD, or Virtual Device
Driver. The VxD is named VaspiD.386. This code handles the locking and
unlocking of the data buffers for Virtual Dma Requests during SCSI I/O.
To use the WINASPI layer, the user copies the WINASPI.DLL and
the VASPID.386 files to the windows sub-directory. The DOS MANAGER
may be located anywhere on the disk as long as the user specifies the
appropriate path.
To activate the WINASPI layer, the installed windows application
must be configured to select the "Windows ASPI" method of access.
***** INSTALLATION *****
First, copy VaspiD.386 to the windows directory. The Winaspi.dll should
go into the system directory.
Next, modify the SYSTEM.INI file to include the statment:
"DEVICE=VASPID.386". This statement MUST be entered in the [386Enh]
section.
If windows is in standard mode WITH a memory manager, such as
EMM386, loaded WINASPI will not initialize. This mode is not
recomended by Windows. This error is returned as SS_ILLEGAL_MODE.
If the SCSI adapter is the primary adapter, and the SCSI IRQ
is set at 14, then the SYSTEM.INI file MUST include the statment
"VirtualHDIRQ=OFF". This statement MUST be entered in the [386Enh]
section.
BTMDRV MANAGER DOCUMENTATION 10/26/94
The Revision 4.xx DOS BTMDRV DISK manager has several new features
along new device support. Most of these features are related to command
line switches at install (boot) time. Along with improvements in the
existing switches, additional switches are present.
The /D switch enables verbose mode. This permits the user to see
the details of the device(s) being attached to the operating system.
The /L switch allows /L for luns=8, and may be set to /L8 /L16,
/L32, and /L64 to set the LUN support on WIDE SCSI cards. Cards not
able to operate in the WIDE SCSI mode will be limited to 8 luns.
The /T switch allows the removable drive-to-ready maximum time
on cartridge insertion to be set. The valid values range from 0 to 9
where the time-out is the value multiplied by 5 seconds. Thus /T2
allows about 10 seconds before the O/S is informed of a not ready
condition.
The /R switch allows for reserving partitions for removable drives.
This is used for the situation where a particular piece of media may
have more than one DOS partition.
The /J switch forces the DOS Manager to only scan 8 SCSI ID's on
WIDE SCSI cards.
The /W switch is active only with /D, and allows the screen display
to pause when each card is scanned. This is to prevent the displayed
information from scrolling off the screen so it may be analyzed.
BusLogic On-Line Technical Support Document
============================================
Document Date Code : 02/21/95
Q. I have a SCSI Adapter or an IDE adapter and I am moving
my drive from another controller, It is not booting but
if I boot from a Diskette, I can see my drive.
A. Boot with a disk with FDISK on it and type:
A:>FDISK /MBR
Q. How can I improve on the Performance of my SCSI Chain?
A. The performance of the SCSI Chain is effected by
many Elements of the SCSI Chain including a
system component, a controller component, and a
system component. Let's explore each of the
system components:
1) System Component
Setting up the system bus to properly accept a BusLogic
controller is critical to the speed of the SCSI Chain.
If you are using an ISA board make sure you are using the
maximum allowable bus speed that will work with your system.
The normal bus rate is 5.0Mhz but some systems permit up
to 8MHZ. This setting will be set in your Main Board's
BIOS and in the toggle of BTDOSM.SYS in your CONFIG.SYS.
If you are using PCI or VL-BUS controller, make sure that
your controller is plugged into a Bus Master Slot, not all are.
Also, make sure that the Bus-Speed is correct.
2) Controller Component
For each of your high performance devices, make sure that
Synchronous Support, FAST Support are turned on in AUTOSCSI
or by DIP switches. Make sure you load BTDOSM.SYS if under
DOS. Use the shortest cable possible and use active terminators.
Use high quality cables, shielded if external. Enable Disconnection
in AUTOSCSI. Verify that the system attributes (INT, PORT
address, BIOS) have UNIQUE values and are NOT shared. If a
drive was formatted on another brand of controller, back it up
and then delete the partition, recreate the partition, and restore
the data.
3) SCSI Device Component
The performance of the slowest device on your SCSI Chain
will determine the speed of the chain. Do not mix SCSI-I
and SCSI-II devices if speed is an issue. Make sure that
each of your SCSI Devices is set properly, has updated
firmware, can support FAST and SYNCHRONOUS Mode,
and if it uses an ASPI Driver, the current Driver as well
as current Firmware, BIOS, and Drivers for your BusLogic
adapter.
Q. I am running Netware and I receive a Lost Hardware Interrupt
Error?
A. This a passive error and can be corrected by adding the line:
SET DISPLAY LOST HDW INT ALEARTS=OFF
to your AUTOEXEC.NCF file.
Q. I have a Sound Board and a SCSI Controller and I am experiencing
Problems?
A. The MIDI Port Address is in conflict with your SCSI Card (Port
address 330h), so you need to change the port address on the
sound board to 330h or lower. There may also be DMA conflicts
and Interrupt conflicts.
Q. I have a 946C PCI SCSI Controller, and every time I load BTDOSM.SYS
my system hangs.
A. Verify the following:
1) The motherboard is a PCI 2.0 compliant
motherboard and the jumpers on my card
are not jumped. Or, my motherboard is not
PCI 2.0 compliant and I have set the jumpers
to a free BIOS Address. Then, I try plugging
my PCI Card into the slot closest to the
power supply, go into AUTOSCSI and change
the Interrupt to 15, and PIN Level to C.
2) My card is plugged into a PCI BusMastering Slot
3) I have Updated F/W and BIOS
4) I have downloaded the current version of my drivers
from the BusLogic BBS.
Q. Why does the "NO ROM BASIC" Message appear when Booting Up?
A. The Following reasons would account for the "NO ROM BASIC"
include:
1) The SCSI Boot Drive is not on SCSI ID 0 or 1.
2) The Termination in the SCSI Bus is not proper and/or
an Active Terminator is needed.
3) The Boot Partition is not set to ACTIVE.
4) The SCSI BIOS is not active, or in multiple controller
configurations, more than one BIOS is active.
5) Interrupt, Base Address, BIOS, or DMA conflict with another
controller in your system.
Q. Why is the Message "Missing Operating System" displayed during
boot, but the hard drive is still seen by the controller.
A. You want to make sure that the Drive has an Operating System on the
Boot Drive. If under DOS, make sure the Drive is properly FDISKed
and FORMAT C:/S has been issued. If the OS is on the drive, you may
need to backup your data and delete all partitions on the disk and
recreate them.
Q. My System displays a HARD DISK FAILURE Message, what's wrong?
A. If you are using only SCSI, set CMOS Drive type to "NOT INSTALLED",
if you are mixing Drive types, set the SCSI Drive to NOT INSTALLED.
If you are using an BusLogic IDE Controller, set the drive type to 1 for
each of your IDE drives. If the message proceeded, check all controller
settings as described in your manual. Then, replace the data cable and
the power supply voltage Levels. Lastly, the drive make be defective
or in the case of IDE, the Master & Slave settings may be wrong.
Q. My SCSI Bus Scan shows 6 Devices and I only have one, what's wrong?
A. The termination on the bus is not proper or the data cable is defective or
too long or the device is on ID 7 ( The default for the controller).
Q. What do I need to use a SCSI CD-ROM under DOS:
A. Make sure your CD-ROM is on SCSI ID 2-6 and add the following to the
beginning of your CONFIG.SYS:
DEVICE=C:\BUSLOGIC\BTDOSM.SYS /D /M
DEVICE=C:\BUSLOGIC\BTCDROM.SYS /D:MSCD002
Add the following to your AUTOEXEC.BAT:
C:\DOS\MSCDEX /D:MSCD002 /M:10
Q. How do I get non-Hard Drive SCSI Device to work with my system?
A. Remember 0,1, and 7 are reserved, so place your device on 2-6.
The Load the Following at the beginning of your CONFIG.SYS:
DEVICE=C:\BUSLOGIC\BTDOSM.SYS /D /M
Then after BTDOSM.SYS, the ASPI Manager, loads, you will need an ASPI
Device Driver for your Device. This is provided by the device Mfg. or
in third party drivers kits such as Corel SCSI.
Q. I have more than 2 Disks on my SCSI Controller or my SCSI BIOS is
Disabled or I have more than one BusLogic SCSI Controller or my device
is a Removable Media Device (Like SYQUEST), how do I Access them?
A. In your CONFIG.SYS, load the following:
DEVICE=C:\BUSLOGIC\BTDOSM.SYS /D /M
DEVICE=C:\BUSLOGIC\BTMDISK.SYS
Then use BTFDISK to Partition the disk and DOS FORMAT to high level
format the Disk(s). (You will not be able to boot off of these drives if your
BIOS is disabled)
Q. Can I connect SCSI-I, SCSI-I C.C.S, and SCSI-II devices to my BusLogic
Controller?
A. Yes.
Q. How can I Maximize my Disk throughput?
A. 1) Use a Short, High Quality Cable.
2) If using an external unit, use an ACTIVE TERMINATOR
3) Enable Synchronous Mode on controller and device.
4) Enable FAST Mode on controller and device.
5) Remove SCSI-I devices.
6) Load BTDOSM.SYS if Under DOS.
Q. I can Only See 528 MB on my IDE Controller and my drive is >528MB.
A. In Disk Parameter Setup in AutoIDE (F2 or F6 on bootup), go to TRK REMAP
on the >528MB Disk Drive and enable it. Then, delete and recreate the
partition table using FDISK.
Q. Can I use DISK MANAGER with my BusLogic IDE Drive?
A. No, you simply turn TREK REAM in AutoIDE to ENABLED
to access >528MB.
Q. I am using DOS and a BusLogic Adapter, what device drivers do I
need to Load?
A. You need to put the following at the beginning of your CONFIG.SYS:
DEVICE=C:\BUSLOGIC\BTDOSM.SYS /D /M
No other drivers are needed, you will need APSI-aware tape
backup software to access the tape drive.
Q. Under Which operating systems do I enable >1GB Option on my
BusLogic Adapter.
A. Operating System Enabled?
DOS Yes
Netware No
UNIX No
NT Yes
Q. I am connecting a Floppy Tape Drive to my SCSI Adapter,
and the Performance is slow. How do I speed this up?
A. Add the toggle /n04 to BTDOSM.SYS
Q. How do I find the current version of Firmware and BIOS in my Adapter?
A. Call BusLogic Tech Support and ask the operator what the
current BIOS and F/W Level is current. You will need to know
the BusLogic Controller Model # and Board REV Level.
Q. I have a Sound Board and a BusLogic SCSI Adapter in my system, are
there any conflicts.
A. Yes. Interrupt Conflict (Card Default is 11)
MIDI Port Address Conflict (Default is 330)
DMA Conflict (Default is 5)
Q. What kind of Memory do I need for my BusLogic IDE Controller?
A. You need 80ns or Faster, 1x9 SIMMS (9 Chip).
Q. I have a BusLogic SCSI Controller and a Hard Disk on not on
ID 0 or 1 and I cant see it.
A. To see the drive without driver or to boot on the drive, the drive
must be on ID 0 or 1, else you must load BTDOSM.SYS and
BTMDISK.SYS, and use BTFDISK to partition the drive.
Q. I am using ARCSERVE/ARCSOLO and Netware and my system is
locking up?
A. Specify the NOSCAN option in the Netware Driver.
Q. I am trying to partition my Hard Drive with >2GB and FDSIK
and it doesn't work?
A. DOS FDISK has a partition size limit of 4 drives by 2GB each drive.
To get larger partition sizes, load BTDOSM.SYS and use BTFDISK
to partition the drive and DOS' FORMAT to high level format the
Partition.
Q. I am using BSD UNIX and I have a driver problem.
A. Please contact Berkeley Systems Directly for Driver
Support.
