                        Installation Tips:
                        Operating Systems

* NOTE *
These TIPS are mainly for the PM3011 series controllers or the
PM2001/PM2012 SCSI Host Adapters running in emulation mode.  If you
are installing a DPT driver such as SWNOV (for Novell 286/386) or
SWUNIX (for SCO Unix 3.2.2), please consult the installation
instructions in the accompaning manual.

1.  MS/PC DOS, CONCURRENT DOS, PCMOS
     a. DPT Format and Certify
     b. Select the appropriate operating system shown.  If the   
        expected capacity shown on the next screen does not match 
        what the drive should be, you may need to install a BE3011 
        BIOS Expansion Chip.  Call Technical Support for details. 
     c. Accept the disk type, and the system will reboot. 
     d. Run FDISK (HDSETUP for PCMOS) and do the high level format
        (FORMAT C: /S).

2.  NOVELL NETWARE
     a. DPT Format and Certify.
     b. Select the appropriate version of Novell from the operating
        systems shown.  If the expected capacity shown on the next 
        screen does not match what the drive should be, you may  
        need to install a BE3011 BIOS Expansion Chip.  Call      
        Technical Support for details.
     c. Accept the disk type, and the system will reboot.
     d. For Netware 386, proceed with standard installation.  For 
        version 2.1x, proceed with steps e. and f.  For version
        2.0x, call DPT Technical Support.
     e. Run COMPSURF. 
     f. Answer "NO" to reformat the disk, "NO" to clear bad block
        table, and "NO" to enter in any further defects.  Select
        0 Sequential Passes, and 1000 Random I/O's.  Proceed with
        standard installation.

3.  XENIX
     a. DPT Format and Certify.
     b. Select XENIX from the list of operating systems shown.
     c. Accept disk type.
     d. Write down the BEST CONFIGURATION parameters on the next
        screen.  The system will then reboot. 
     e. Load XENIX from the floppy disk.
     f. Display Disk Parameters.  If the parameters displayed
        match the BEST CONFIGURATION that was written down, proceed
        with standard installation.  If the parameters do not    
        match, select Modify Parameters and change the disk      
        parameters to what the BEST CONFIGURATION is.  Proceed with
        standard installation.

4.  UNIX, INTERACTIVE, AT&T UNIX, MICROPORT, QNX
All of these variations of UNIX load in the same manner as XENIX. 
Follow the examples shown in the XENIX installation.

            Supplemental Information for SmartDrivers


SWNOV Drivers:

Commonly asked SWNOV Questions:

1. Why use SWNOV?
   To add multiple drive and controller support and, in the case
   of EISA, add system performance.  SWNOV also allows the use of
   large drives to be use (ie 1.5G) that is not normally
   supported by CMOS or other BIOS Expansion ROMs.

2. If my system is already setup with ISADISK, will I have to
   reinstall Netware?
   Yes.  SWNOV will logically change the parameters of your disk
   drive thereby destroying any FAT and Volume information.

3. When I load PM12NW31.DSK for my second controller, Netware
   says "MODULE USED REENTRANTLY".  Why am I getting this error
   message?
   This is NOT an error message.  Netware is simply stating that
   it knows it loaded the same module twice, one for each
   controller.

4. Can I use SWNOV on a DPT secondary controller and ISADISK on
   my primary Adaptec controller?
   Yes.  This configuration has been tested by DPT Technical
   Support.


Use of SmartROM:

Although SmartROM has been found to work with Netware 286 and
Netware 386 in most cases with or without a CMOS entry, I almost
always advise my customers to disable SmartROM if I am talking
through an installation at that time or if they have not yet
started the installation.  The reason I recommend this is because:

1.  I have seen some customers have NO CMOS ENTRY in setup (using
    SmartROM parameters) and have major problems trying to load
    up Netware.  This occurs when the customer selects DOS as the
    OS (for a boot partition to load Netware 386) in DPTFMT, and
    the DPTFMT sets CMOS to NO DRIVES INSTALLED.

2.  SmartROM buys you nothing when SWNOV is being used.  SmartROM
    is occupying an 8k bit address range and offering nothing in
    return as far as performance (SWNOV takes care of that).
    Disabling SmartROM frees up that address and allows for
    easier installation of Netware Interface Cards, Tape Cards,
    VGA, etc. and a "cleaner" disk subsystem.

3.  Disabling the SmartROM gets rid of the WAITING FOR DEVICE
    SPINUP message that 3 out of 5 people complain about.


Using Netware's ISADISK:

All DPT controllers are compatible with the ISADISK driver for both
Netware 286 and Netware 386.  There is, however, one anomaly.  The
ISADISK.DSK that is currently shipping with Netware 386 3.11 is
freaking out on a great deal of controllers.  If you experience the
error message FAT TABLE ERROR MISMATCH when trying to mount
volumes, use an older version of ISADISK.DSK (from Netware 386 3.1
or 3.0).  This is the advice I received from Novell.  This still is
not fix for it on Netwire.  More and more customers are aware of
this now and are not very upset.  The older version of ISADISK.DSK
can be downloaded from the BBS as ISADISK.ZIP.

ISADISK.DSK for Netware 386 can be loaded twice (reentrantly) for
duplexing emulating controllers (like PM3011 and PM2001). 
Unfortunately, ISADISK.DSK does not provide disk drive parameters
(like SWNOV) and relies on CMOS entries.  If your motherboard has
CMOS support for a secondary controller at base I/O 170, then
ISADISK.DSK can be used to duplex PM3011's and PM2001's under
Netware 386.  So far the only machine I've seen with this feature
is a Compaq Deskpro.  However, ISADISK.DSK can be loaded with a /B
switch which forces ISADISK.DSK to look for drive parameters at
C800.  Theoretically, a DPT primary controller with a BE3011 at
D800 and ISADISK should co-exist with a DPT secondary controller
with a BE3011 at C800 and ISADISK /B.  This is yet to be tested.


User Definable Disk Parameters:

UDP's will not work on any version of Netware.  Sometimes we get
asked why....here it is in a nutshell:

ISADISK for Netware 286 and Netware 386 is tied to BIOS for disk
parameters...it does not provide it's own as does SWNOV.  ISADISK
is looking a specific address in BIOS for disk parameters, and that
address is F000:E671.  F000:E671 is the location in system BIOS
where the Types 1-46 table is stored.  All types above 46,
including UDP's, get stored at a different offset.  ISADISK freaks
out as it cannot find that offset.  A similar "failure" is when
DPTFMT says "NO DRIVE TYPE SMALL ENOUGH".  That error message
occurs when CMOS is set to a UDP or a drive to higher than 46. 
DPTFMT is trying to look for the standard drive table at F000:E671
when you are selecting the operating system.


Maximum Drives Supported

Not much to say here....we all know how to hook up drives observing
termination, etc.  For specific supported device information,
please consult the NETWARE/DPT CONTROLLER CROSS REFERENCE CHART. 
Largest example I can think of:  I talked to a customer about 2
weeks ago who has 3 PM2012B controllers in a Wyse 486/33 using
SWNOV and Netware 386.  He has 18 1.5G Micropolis drives on line
and running.  He is anxiously awaiting SWNOV to support LEVEL IRQ's
so he can add a fourth controller.


Maximum Controllers Supported

To be on the safe side, when using ISADISK specify 1 controller per
system.  Two controller support can be obtained with SWNOV in both
ISA and EISA environments.  Three controller support can be
obtained with SWNOV in EISA only.  Four controller support can be
obtained with SWNOV in EISA only as soon as we verify that DK's new
PM12NW31.DSK is supporting LEVEL IRQ's ok.


Support for devices other than hard disks

The is currently no support for tape drives or CDROMs, however DK
says they will be supported in the near future.  Rumor has it that
the PM12NW31.DSK driver that DK modded to support LEVEL IRQ's is
also working with Cheyenne TBU software.


Netware's Software Mirroring

Novell's mirroring can be invoked with or without SWNOV.  It should
be noted that Netware's mirroring will only mirror a Netware
partition (no DOS partitions are mirrored) and Netware cannot boot
from a secondary drive as does DPT's mirroring.  Netware's
mirroring is also slower because it is done thru software (OS has
to write to each drive before the operation is complete, as opposed
to DPT's hardware mirroring where one write to the primary is
executed, and the secondary is then updated in the background
transparent to Netware).  Hardware mirroring for the PM2011 and
PM2012B will definitely be hot.


Duplexing

Duplexing is just mirroring two hard disks on different
controllers.  Currently, duplexing can only be achieved with SWNOV,
pending testing with ISADISK /B on the PM3011 and PM2001. 
Duplexing does offer a slight performance increase over Netware's
software mirroring as the OS can read both channels at the same
time.



INSTALLATION NOTES/COMMON QUESTIONS
SCO UNIX 3.2.2 & ODT 1.1.X

DISK CAPACITIES
     W/O SWUNIX - 2048 X 16 X 63 (1.057Gb)
     W/SWUNIX   - SWUNIX 1E1 - Primary 2048 X 16 X 63 (1.057Gb)
                               Secondary - Hardware limitation only
                  SWUNIX 1E  - 2048 X 16 X 63 (1.057Gb)

     The current shipping version of the SWUNIX is V1E.  Version
     1E1 is currently available on the BBS (UNIX1E1.ZIP).

SMARTROM & BTE
     Neither chip is required, although both will work.  With the
     BTE you should still get a BC that will have to be manually
     entered during the SCO install.  The smartrom will pass the BC
     on to UNIX during the install, so you should not have to
     manually enter the BC when smartrom is used.

DEVICE SUPPORT
     MAX Controllers - 2
     MAX hard drives - 4/system (even when SWUNIX installed)
     MAX drives/Controller - 4
     Removable & MO drives - most should work as long as the
     512 byte/sector is used.
     Tape drives - All those supported by SCO.
     Backup Software - TAR, CPIO, and 3rd party software not
     bundled with a specific tape drive.
     CDROM - Sony & Toshiba are supported.

SWUNIX files & directories
     /etc/conf/cf.d - Directory where most of the Applicable SCSI
                      device set up files are.  Those files are:

          MSCSI - This is the master SCSI device table.  In this
                  file is where SCO Unix stores the HA/ID/LUN info
                  for every SCSI device attached.

          MDEVICE - This file contains DMA information,
                    configuration information & features for all
                    drivers.

          SDEVICE - This file contains I/O address & Interrupt #
                    and whether a driver is installed or not.  This
                    file is created using all the information
                    stored in the files from the sdevice.d
                    subdirectory.  This is the file that is used to
                    supply the kernel with parameters when a relink
                    is done.  The information in this file should
                    match the information in the files from the
                    sdevice.d subdirectory.


     /etc/conf/sdevice.d - Directory where Interrupt & I/O address
                           info is stored.  Applicable files are:

               dptH - DPT controller info file.
               Sdsk - SCSI disk info file. 
               Stp  - SCSI tape info file.
               Srom - SCSI CDROM info file.



     /etc/conf/bin - Directory where the idbuild program is
                     located.  This is the program you run to
                     relink the kernel when parameters have
                     been changed. ie - "AD" driver has been
                     removed to facilitate addition DPT tape.


SPECIAL CONSIDERATIONS


     1) Primary bootable hard drive should be at ID 0, because when
        the driver is loaded, it assumes that the primary drive is
        at ID 0 (MSCSI File).  If the system has already been     
        installed on a primary device not set at ID 0, then do the
        following steps: 

          1) Use Custom to add the driver in, DO NOT relink the
             kernel with idbuild until step 2 is completed.

          2) Edit the MSCSI file to reflect the correct SCSI ID of
             the primary device (second field of MSCSI).  Change
             directory to /etc/conf/bin, run ./idbuild, and then
             reboot and all will work.

     2) The primary bootable hard drive is limited to 1.057Gb total
        capacity, even if the driver is going to be added.  This is
        because during the install, we have to input the BC to SCO,
        and at that point SCO's limitation is 2048 X 16 X 63      
        (1.057Gb).

     3) The root filesystem must occupy 1024 cylinders or less to
        insure that the kernel is on the bootable portion of the
        hard drive.  

     4) If DOS and UNIX are to be co-resident and the dual boot   
        feature utilized, then the DOS partition must be the first
        partition and must be created with DOS 3.3.  The dual boot
        feature only works with the 12-bit FAT system.  DOS4.01   
        uses 16-bit FAT and DOS5.0 uses 32-bit FAT.  You can     
        install either DOS4.01 or DOS5.0 as the DOS partition, but
        you would have to "activate" that partition to get it     
        to boot, then re-activate the unix partition when ready to
        go back into unix.

     5) When running DPTFMT on a controller that has a smartrom   
        installed, user will be asked if dos will be installed on
        the disk.  You must always answer no to that question,    
        because if you answer yes, the maximum BC will be 
        1024 X 16 X 63 (528Mb).

     6) Whenever a tape drive is going to be attached to a DPT    
        controller, after installing the DPT driver, you must use
        the following steps: 

          1) remove the existing Adaptec tape driver and the
             existing Cartridge driver using the MKDEV TAPE
             utility.

          2) Relink the kernel using the idbuild utility. 

          3) Run MKDEV TAPE to add the tape drive to the dpt
             controller.

     7) When running the SCO install procedure, you must always   
        pick "FULLY CONFIGURABLE INSTALLATION", because if you do
        not, "dkinit" will never run and you will not be able to
        input the BC.


     8) The MKDEV HD utility in Unix is how you attach SCSi disk 
        drives to the DPT driver.  This utility only has to be run
        once for the primary bootable disk drive.  On the second,
        third, and fourth disk drives the utility will have to be
        run twice.  The first run is when you identify the SCSI   
 HA/ID/LUN info that SCO will install into the MSCSI file.        
 The second time you run the utility is when Unix allows you      
 to create the partitions and the filesystems on the device.



COMMON PROBLEMS


     1) "SYMBOLIC REFERENCE ERROR" - This error occurs when you try
        to link the driver in to the kernel.  This error indicates
        that the version of UNIX is incorrect.  The version of UNIX
        we have seen this error with is 3.2.0.  I suspect you will
        see the same error with other non 3.2.2 versions of UNIX. 
        To verify the version of UNIX, the best method is to look
        at the N1 boot diskette to verify the version. 

     2) "PANIC SRMOUNT - CAN NOT MOUNT ROOT" - This infamous error 
        can be caused by several things.  The following is a list
        of the known causes of this error in the order of most    
        common causes to least common causes.  

          A) Incorrect HA/ID/LUN info entered during install of the
             driver.  The driver assumes that the primary drive
             will be at ID 0.  If the primary drive is at some
             other ID and even though it has been mapped correctly,
             you will get this error.  Check the MSCSI file and run
             DPTFMT to verify ID settings.

          B) Corrupted data read in busmastering mode.  This can be
             caused by a bad CM, or bad MM, or busmastering   
             problems on the motherboard.  Try a different slot,
             different motherboard, different controller, or the
             Y19/Y21/Y28 settings on the 2011.

          C) Adaptec driver still linked in to the kernel when
             adding the DPT driver.  I have seen removing the
             Adaptec driver resolve this problem, but I have also
             seen a system work with the Adaptec driver installed
             along with the DPT driver.  

     3) "CAN NOT OPEN /DEV/RDSK/XsX" - This error will occur on   
        secondary devices when running the mkdev hd script.  The
        causes are incorrect ID/HA/LUN info entered in MSCSI, or
        the controller does not correctly see the device, which can

        be caused by a bad cable, a bad device, or a bad          
        controller.  Run DPTFMT to verify ID setting and verify   
        cable connections.

     4) "ERROR - INIT SCRIPT FAILED" - This error is caused by not
        having the link kit installed.  Use the custom program to
        verify that the link kit is installed.

     5) "NO CONFIGURATION INFORMATION FOR SDISK UNIT X" - This    
        error can be caused by a couple of things.  If there has
        been a CMOS drive entry set for a secondary drive in      
        emulation mode, then when you try to run mkdev hd, you will
        get this error.  Also, if the Adaptec driver has not been
        removed, and in the MSCSI file the first field shows an   
        "ad" instead of a "dptH", this will cause this error.  You
        can just edit the MSCSI file and remove the"ad" and input
        the "dptH" and that will fix the problem.


INSTALLATION PROCEDURES

     These install procedures assume that basic hardware
     installation rules have been followed, meaning SCSI ID's are
     correct, ESDI drive has been low level formatted, termination
     rules applied, proper SCSI LUN map saved/entered in ECU, etc.
     
     3011/XX & 2001/9X
          1) Select SCO Unix from the OS selection screen in
             DPTFMT.
          2) Note drive type and BC displayed.  Make sure that the
             BC closely matches total drive capacity, and write it
             down for future reference.
          3) Reboot with the SCO N1 diskette, choosing fully
             configurable install.
          4) Manually enter the BC supplied by DPTFMT.
          5) Complete the SCO install.

     201X/9X
          1) Select SCO Unix from the OS selection screen in
             DPTFMT.
          2) Note drive type and BC displayed.  Make sure the BC
             closely matches total drive capacity, and write it
             down for future reference.
          3) Reboot with SCO N1 diskette, choosing fully          
             configurable install.
          4) Manually enter the BC supplied by DPTFMT (if SROM
             present, it should automatically supply the BC).
          5) Complete the SCO Install - making sure the link kit is
             installed.

          The following steps apply to the 201X/9X install
          procedure when using SWUNIX and there is to be a tape
          drive installed on the DPT controller.

          6) Run MKDEV TAPE to remove the existing Adaptec tape
             driver and the existing cartridge tape driver.
          7) Relink the kernel using /etc/conf/bin/idbuild.
          8) Run CUSTOM to install the SWUNIX.
          9) Run additional MKDEV HD's when secondary drives
             attached.  Relink with /etc/conf/bin/idbuild after
             every run.
         10) Run MKDEV TAPE to add in a SCSI tape drive to the DPT
             controller. Relink with /etc/conf/bin/idbuild.

          The following steps apply to the 201X/9X install
          procedure when using SWUNIX and there is to be no tape
          drive installed on the DPT controller.

          6) Run CUSTOM to install the SWUNIX.
          7) Run additional MKDEV HD's when secondary drives are
             attached.  Relink with /etc/conf/bin/idbuild after
             every run.



SW-OS2:

               OS/2 Installation Reference
               ---------------------------

OS/2 Versions
-------------
1.0, 1.1, and 1.2 -      WD emulation only
1.21 and 1.3 -           WD emulation or EATA mode (w/driver)

Non-LADDR versions of OS/2 do not allow more than 1 mass storage
driver to be loaded at a time.  Therefore, you cannot mix WD-type
and SW-OS2 controllers in the same system.

WD Emulation
------------
Uses standard DISK01.SYS that ships with OS/2.
(IBM OS/2 1.3)
--------------
DISK01.SYS     29067 bytes    Dated: 04-17-91

CMOS Entry:              Required
BTE Parameters:          Will work if necessary
SmartROM Parameters:     Incompatible
Drive Capacity:          1024 x 15 x 63 (528 Mb)
Max. Primary Partition:  528 Mb.
Max. Controllers:   2
Max. Hard Drives:   4
Max. Drives/Controller:  2
WD Drive Mappings:  Required for all drives

SW-OS2 Drivers
--------------
Version 1A
DISK01.SYS          44521 bytes    Dated: 04-02-91   5:51p

CMOS Entry:              Required
BTE Parameters:          Will work if necessary
SmartROM Parameters:     Incompatible
Drive Capacity:          1024 x 15 x 63 (528 Mb)
Max. Primary Partition   528 Mb*
Max. controllers:   2
Max. Hard Drives:   14
Max. Drives/Controller:  7
WD Drive Mappings:  Required for boot drive only

*If planning on having more than one partition,  the primary
partition should be less than 528Mb.

Version 1.C (OS2BETA.ZIP)
DISK01.SYS          42929 bytes    Dated: 09-13-91   4:00p

CMOS Entry:              Not Required
BTE Parameters:          Not Necessary
SmartROM Parameters:     Compatible
Drive Capacity:          2048 Gb. theoretical (HPFS)
Max. Primary Partition   2 Gb.
Max. controllers:   2
Max. Hard Drives:   14
Max. Drives/Controller:  7
WD Drive Mappings:  Required for boot drive only



Installing Dual Boot
--------------------
Before installing OS/2.....

- Make sure the DOS partition setup is compatible with OS/2.
     - WD emulation - DOS must use CMOS parameters.
          (SmartROM "emulated" parameters are OK)
     - SW-OS2 1A - DOS must use CMOS parameters.
          (SmartROM "emulated" parameters are OK)
     - SW-OS2 1C - DOS can use SmartROM parameters.

- Make sure your DOS files are in a directory called "DOS".

- Make sure there is a copy of COMMAND.COM in the DOS directory.

- The CONFIG.SYS file must contain:
     SHELL = C:\DOS\COMMAND.COM /P

- The AUTOEXEC.BAT file must contain:
     SET COMSPEC=C:\DOS\COMMAND.COM
     PATH=C:\DOS;
     APPEND=C:\DOS;
     COPY C:\DOS\COMMAND.COM C:\  >NUL



Installing the driver
---------------------

- Make a working copy of the OS/2 Installation disk.

- Copy the DISK01.SYS from our drive disk to the working copy of
  the Installation disk.

- Install OS/2
     - Create Primary partition only!
     - If using CMOS entry and planning to have a second partition,
       make sure the primary partition is less than 528Mb.
     - If installing OS/2 - DOS dual boot, primary partition must
       be a FAT filesystem.

- Reboot - booting OS/2 from the hard drive

- Create extended partitions and logical drives with FDISKPM.
     - If using CMOS entry, this will make available extra
       cylinders beyond 1024.
     - FDISKPM may report inaccurate partition sizes.
     - If primary partition is FAT filesystem, the OS/2 install
       will not add the HPFS info to CONFIG.SYS.  It must be added
       before trying to create any HPFS partitions:

          IFS = C:\OS2\HPFS.IFS /c:64
          RUN = C:\OS2\CACHE.EXE /LAZY:ON

- Format newly created logical drives using the Format utility.
     FORMAT D: /FS:HPFS
     FORMAT D: /FS:FAT


OS/2 Anomalies
--------------
- OS/2 assigns drive letters to all the primary partitions on all
  physical drives first, then to the logical drives in extended
  partitions.

- If your primary partition takes up the whole physical drive (or
  528Mb if using CMOS parameters), the OS/2 installation procedure
  will not even copy FDISKPM over to your hard drive.  You must do
  it manually:

     UNPACK A:FDISKPM.EX@    C:\OS2
     UNPACK A:FDISKPMH.HL@ C:\OS2\HELP
     UNPACK A:FDISKPM.DL@    C:\OS2\DLL

    The program will have to be manually added to one of the
    Program Groups to be accessible from PM.  It can also be run
    from the OS/2 command line.

- Citrix is a multi-user version of OS/2.  It is compatible with
  our drivers.  It does not support PM.  Therefore, there is no
  FDISKPM.  It is rumored that they have their own fixed disk
  partitioning utility.  Also, since SYTOS PLUS runs under PM, it
  can't be run under Citrix.  In other words, SW-OS2 doesn't
  support tape drives under Citrix's OS/2.

- 3Com 3+ Open is a licensed version of Microsoft LAN Manager.  It
  is no longer being produced.  However, it is an old version of
  LANMAN that only runs on top of OS.2 1.1.  Therefore, it is not
  compatible with our driver.  Our controllers will work with 3+
  Open in emulation mode without any problems.  Just in case you
  were about to ask,  there is no way to get 3+ Open to run on top
  of OS/2 1.21 or 1.3.  However, I hear Microsoft has a very
  liberal upgrade policy to real LANMAN...



OS/2 Error Messages and Problems
--------------------------------
"SYS1728: The system does not have enough storage to enable disk
caching."

When: This message is encountered when OS/2 is booted from the hard
      drive.  It happens with large hard drives.

Why: This message is very poorly worded.  It really means that the
     amount of memory that has been specified for your OS/2
     software disk caching is inadequate for the size of your hard
     drive.

Fix: OS/2's installation defaults to a 64k software disk cache by
     putting the following line in your CONFIG.SYS:

     diskcache=64

     Changing the number of kilobytes to a higher value will get
     rid of the error message.  128k per gigabyte seems to be about
     right.  The message will also go away if you turn off software
     caching by deleting the above line all together.


"FDISK unsuccessful"

When: During installation.

Why: You are trying to use SmartROM parameters without our 1C
driver.

Fix: Use the 1C driver or go back through DPTFMT and set a CMOS
drive type.

"TRAP 000D"

When: While booting OS/2 from the hard drive.

Why: There could be a lot of causes.  I was able to produce this
error by setting up the hard drive with the 1C driver using
SmartROM parameters and then copying the WD DISK01.SYS into the
root directory and then rebooting.  The general cause is a
driver/drive type inconsistency.

Fix: Check to make sure there is still a CMOS type set.

"Internal Error #3"

When: On the LANMAN console under heavy disk I/O.

Why: A bug in the 1A driver

Fix: Use the 1C driver.  This was discovered by AST.  Their driver,
while not Version 1C, has this problem fixed also.


"SYS0540: Not formatted with HPFS"

When: When trying to format an HPFS partition.

Why: HPFS has not been loaded.  This is common if you only created
a FAT filesystem during installation.

Fix: Add the following two lines to the CONFIG.SYS file and reboot:
     IFS = C:\OS2\HPFS.IFS /c:64
     RUN = C:\OS2\CACHE.EXE /LAZY:ON


AST 486/33 EISA Tower hangs during install

When: During installation.

Why: Downlevel AST BIOS
Fix: Must have AST BIOS 1.12 or greater


Secondary PM2012B hangs at boot with LED 8 ON
(AST CPU, OS/2 1.2)

When: During boot, just as OS/2 is loading

Why: Bug in EISA CFG file

Fix: Get the new !DPTA401.CFG file - Version 003.B or change their
file:

     Change:   INIT = IOPORT(1) LOC(0) 1
     To:       INIT = IOPORT(1) LOC(0) 0


OS/2 Tape Drive Support
-----------------------

SCSI tape drives are supported by SW-OS2 in conjunction with SYSTOS
PLUS (OS/2 retail version or the version that ships with Microsoft
Lan Manager).

Installing Tape Support
- The tape drivers assume the presence of the PM201x disk driver.
- Install PM201x disk driver, hardware, and OS/2 (See 12. above.)
- Install Sytos Plus in the normal manner but use the DPT driver
  floppy in place of the Sytos Plus driver disk allowed during
  installation.
- Reboot OS/2 and note tape related message displayed as driver
  is loaded and initialized.

Supported Tape Drives
Each driver has 3 files on the driver disk .SYS, .DLL, and .TXT

Tape Drive               Driver Name    SCSI Inquiry ID*
Archive Viper 2150S DA2150.SYS      'ARCHIVE VIPER 150  21247'
Archive Viper 2525S DA2525.SYS     'ARCHIVE VIPER 2525'
Archive Python      DAPYTH.SYS     'ARCHIVE Python'
(jumpered for SCSI-2)
Tandberg 3660       DT3660.SYS     'TANDBERG TDC 3600   '
Tandberg 3800       DT3800.SYS     'TANDBERG TDC 3800   '
Wangtek 5150ES      DW5150.SYS     'WANGTEK 5150ES SCSI-36  '
Wangtek 6130HS      DW6130.SYS     'WANGTEK 6130HS          '
Wangtek 5525ES      DW5525.SYS     'WANGTEK 5525ES SCSI '
(jumpered for SCSI-1)
Exabyte 8200        DX8200.SYS     'EXABYTE EXB-8200'
(SW-OS2 version 1C only)

If a customer is trying to use an OEM'd drive that uses a modified
Vendor/Product ID but is otherwise functionally identical to a
supported model, a command line switch can be used in the
CONFIG.SYS file to override the default SCSI Inquiry ID.  This is
supported in the 1C versions of the tape drivers only.
The following entry would be for a Wangtek 6130HS that is
repackaged by GitchiGummi Inc. of Taiwan:

device = DW6130.SYS /VPID"GITCHI X15  "

The maximum string length is 24 characters.  If the quotes are
adjacent (i.e. ""), any SCSI Inquiry ID will be accepted by the
driver.

DPT cannot take responsibility for anything that results from using
this "trick".



















