From: gregw@.hspice.portal.com (Greg Widdicombe)
Subject: Novell drivers for Adaptec SCSI boards (LONG)
Organization: Meta - Software
Date: Thu, 30 Jul 1992 18:29:39 GMT

 
Here is the file NOVELL.DOC downloaded from the Adaptec BBS.
It gives answers to some of the recent questions asked about
their cards/drivers and NetWare servers.  It is reproduced
without permission - but then, who cares :-).

============================================================
     Novell Netware Information
     for Adaptec SCSI host adapters and hard disk controllers

                                                       DATE: Jan, 1992



 SCSI Host Adapters:

     This file will list some of the most common problems, and give some
     helpful hints on how to solve them.

     General Information:

 1)  How to identify the Adaptec hardware product that you have.

         Adaptec hardware products, such as SCSI host adapters and hard disk
         controllers can be identified by a white sticker on a chip on the
         board.  The silkscreening on the board, including stickers on the
         FAB, should NOT be used to identify the board.

         The white sticker with the information on it has three lines.  Here
         is an example:

             AHA-1542B  :Product name
              429300 E  :Product number and revision
              9132      :Date code e.g. 32nd week of 1991

        Some controllers/host adapters have both a BIOS EPROM and a Microcode
         EPROM on it, some have only a BIOS EPROM.  These look similar to:

              ADAPTEC INC      ADAPTEC INC
              434101-00 C  or  420412-00 A
              MCODE F3F7       BIOS BB00
               @1990            @1988

 2)  How to identify the Adaptec software product that you have.

      The device driver being used should be identified by the ASW software
        package that it came with.  This would either be on the original
        floppy diskette, or on the cardboard software package.  Some examples
        are:

     ASW-1440 v3.0      Novell drivers for bus masters
     ASW-1240 v1.1      Novell drivers for non bus masters

     ASW-1440:  Novell NetWare drivers for Adaptec SCSI host adapters:

     These drivers are value added drivers that are fully Novell certified
     and NetWare ready.  Consequently, they are not free, but must be
     purchased from any Adaptec reseller or distributor.  However, if the
     SCSI host adapter is purchased in a kit form (e.g. The SCSI Master,
     kit for the AHA-1542B), the ASW-1440 Novell driver is included.

     Many times people here that a newer ASW-1440 software package is avail-
     able and want it, thinking that the previous driver must have had a bug.
     This is not the case.  The ASW-1440 driver is revised to add support for
     newer versions of NetWare and add support for new Adaptec SCSI host
     adapters. The newer ASW-1440 versions include the previously released
     drivers, along with the additions.

 NOTES:
        - 1540 refers to the AHA-1540/1540A/1542A/1540B/1542B
        - If a <number> is listed under description, that means that this
          version of the ASW-1440 includes the driver that was listed by the
          <number>.
        - 286 refers to Novell NetWare 286 v2.15 (SFT and Advanced)
            revs a, b, and c, and v2.2.
        - 386 refers to Novell NetWare 386
        - Adaptec SCSI host adapters are not supported with ELS versions of
            NetWare
        - All of the drivers listed below are Novell certified, except if
            marked with a *.
        - If the 'verbose=y' command line switch is used with
            NetWare 386 v3.11, the following text may appear:

                 !!! NO SCSI DEVICES FOUND TO REGISTER !!!

            Do not be concerned that SCSI devices are attached and are not
            being found by the driver.  The reason that this message occurs
            is because NetWare 386 v3.11 does not allow the host adapter to
            scan the SCSI bus to search for and display devices.  386 v3.1
            did allow this.  Simply ignore this, and proceed by loading
            the INSTALL.NLM, which is used to partition and add volumes to
            disk drives.  INSTALL will see all attached SCSI drives.

            The ASW-1440 revision history is shown below:


        Software Package:       Description:

        1) ASW-1140 v3.1        Driver for the 1540/1640 for 286

        2) ASW-1140 v3.2*       Driver for the 1540/1640 for 286

        3) ASW-1440 v1.0        Driver for the 1540/1640 for 386 v3.0

        4) ASW-1440 v2.0        Driver for the 1540/1640 for 286/386 v3.0/
                                 386 v3.1.  Includes 1), 2), and  3).
                                 (This version will support 386 v3.11 if
                                 patched with DSKPATCH.EXE)

        5) ASW-1440 v3.0        Driver for the 1540/1640/1740 for 286
                                 /386 v3.0/386 v3.1.  Includes 4).
                                 (This version will support 386 v3.11 if
                                  patched with DSKPATCH.EXE)

        6) ASW-1440 v3.1        Exactly the same as 5), except the drivers
                                 are provided already patched by DSKPATCH.EXE
                                 for use with 386 v3.11.

        7) ASW-1440 v3.2        Never released.

        8) ASW-1440 v3.3        Same as 6), except a new feature was added
                                 in the AHA1540.DSK and AHA1640.DSK to add
                                 support for more than 16 Megabytes of RAM
                                 with NetWare 386 v3.11 ONLY. (other versions
                                 still limited to 16 MBytes or less).  Also,
                                 the 'verbose=y' command line switch no longer
                                 displays the message:
                                 !!! NO SCSI DEVICES FOUND TO REGISTER !!!
                                 with 386 v3.11.

 AHA-1540B/AHA-1542B (AT to SCSI bus master host adapter):

  This includes the AHA-1540/1540A/1542A.

      1)  Bus master data transfer support problems

    The most common issue dealing with this host adapter is using it in a
    computer system that does not support bus master DMA data transfers at
    the speed selected on the host adapter.  The speed of the DMA transfer
    is set with either jumpers on the host adapter or command line switches
    on the Novell driver.

    The first step in troubleshooting an AHA-1540 series host adapter
    problem is to remove any jumpers at J5, positions 12 and 13 (by default,
    a jumper is installed at J12).  When these jumpers are removed, the DMA
    speed is set to 5 MBytes/sec.  To make sure that this speed is compatible
    with your computer, run the BUS MASTER DMA TEST in the host adapter BIOS.
    The test is invoked using DOS DEBUG.  Type DEBUG, and at the <dash>
    prompt, type -g=dc00:9 (assuming the host adapter BIOS is jumpered to
    the default BIOS address of DC000).  The DMA test will be displayed on
    the screen.  Press any key to run the test.  The test should be run with
    no device drivers or TSRs (terminate and stay resident program).  If the
    test displays funny characters on the screen, or the displays "READ/
    WRITE FIFO ERROR", or just simply hangs, then the AHA-1540 series host
    adapter (or any bus master I/O cards) is not compatible in that system.
    The Adaptec AHA-1520/1522 host adapter does not use bus master transfers
    and can be used instead, if desired.

      2)  Using Adaptec device drivers.

     Use the following command line switches on Adaptec ASPI device drivers
     to make the host adapter as compatible as possible:

       For the Novell NetWare 386 operating system:

           :load AHA1540 speed=ff bus_on=4 bus_off=12 io_combine=1

 NOTE:  ASPITRAN.DSK must be in the same path.

     This sets the DMA transfer speed to 3.3 MBytes/sec, the bus on time to
     4 microseconds, and the bus off time to 12 microseconds.

      In addition, if your file server has more than 16 Megs of RAM, add the
      following command line switch:

 :load AHA1540 above16=y (NOTE: This is only supported with version
                                          ASW-1440 v3.3)

       If you are using NetWare 386 v3.1 or v3.0, or have a version of the
       ASW-1440 older than v3.3, than the system is limited to 16 Megs of
       RAM or less.  If more than 16 Megs of RAM are in the system, add the
       following line to your STARTUP.NCF:

           :set Auto Register Memory Above 16 Megabytes = OFF

       Use the following STARTUP.NCF and AUTOEXEC.NCF files when more than
       16 Megabytes are in the system:

              STARTUP.NCF:
                 :set Auto Register Memory Above 16 Megabytes = OFF
                 :load AHA1540 above16=y

              AUTOEXEC.NCF:
                 :register memory 1000000 400000 (This is an example)

       The 'register memory' command is documented by Novell.  The first
       number is the starting address of the memory above 16 meg, and
       second number is the amount of extended memory.  Both numbers are in
       Hex.  The example above is for 4 Megs above 16 Meg.

       If you encounter a problem loading the driver with that switch, you
       may have to increase the reserved buffers below 16 meg with the
       following SET command:

             SET Reserved Buffers Below 16 Meg = 32

 3)  EISA configuration file

       An EISA configuration file is available to aid in the installation of
       the AHA-1540B/42B into an EISA system (note that the AHA-1740 EISA to
       SCSI host adapter is available as well).  The file is called
       !ADP0100.CFG and is available on the Adaptec BBS.  Keep in mind that
       the host adapter must be jumpered to however the EISA software is set.

 4)  Multiple host adapter support

       Up to four AHA-1540/42B host adapters can be put into each system.
       Only one host adapter can have its BIOS enabled (and must be at port
       330H), and all the other host adapters must have the BIOS disabled
       (remove the jumper at J6, position 1).  The host adapters must be
       jumpered to unique DMA channels, port addresses, and Interrupt
       channels (the manuals and jumper settings are on this BBS).

    AHA-1640 (microchannel to SCSI bus master host adapter)

     1)  Systems supported:
          The IBM models 50, 60, 70, and 80 have been certified on the
          AHA-1640.  Microchannel systems other than these have not been
          tested and may or may not work properly.

     2)  There are no bus mastering support issues with microchannel systems.

     3)  Using Adaptec device drivers.

 Use the following command line switches on Adaptec ASPI device drivers
      to make the host adapter as compatible as possible:

       For the Novell NetWare 386 operating system:

           :load AHA1640 bus_on=4 bus_off=12 io_combine=1

       NOTE:  ASPITRAN.DSK must be in the same path.

       This sets the bus on time to 4 microseconds,
       and the bus off time to 12 microseconds.

      In addition, if your file server has more than 16 Megs of RAM, add the
      following command line switch:

 :load AHA1640 above16=y (NOTE: This is only supported with version
                                          ASW-1440 v3.3)

      If you are using NetWare 386 v3.1 or v3.0, or have a version of the
      ASW-1440 older than v3.3, than the system is limited to 16 Megs of
      RAM or less.  If more than 16 Megs of RAM are in the system, add the
      following line to your STARTUP.NCF:

           :set Auto Register Memory Above 16 Megabytes = OFF

 4)  Multiple host adapter support

       Up to six AHA-1640 host adapters can be put into each system.
       Only one host adapter can have its BIOS enabled (and must be at port
       330H), and all the other host adapters must have the BIOS disabled
       (use the reference diskette software).  The host adapters must be
       set to unique arbitration levels, port addresses, and Interrupt
       levels (done with the reference diskette software).


     AHA-1740 (EISA to SCSI bus master host adapter)

   This includes the AHA-1740A/1742A/1744.

 General Information:

 1)  Systems supported:

       The AHA-1740 is designed to work in standard EISA bus systems.  The
       key issue is whether or not the motherboard BIOS used in that system
       supports a parameter known as "FREE FORM DATA".  Some versions of
       Award, Phoenix, and AMI BIOS do support Free Form Data, and other
       versions do not.  The symptom of non Free Form Data support shows up
       when the SCSI Device Configuration options during the EISA
       configuration setup.  For example, options may be changed such as
       "BIOS search for device" or "Send Start Unit" (and others).  If Free
       Form Data is not supported by the motherboard BIOS, then these options
       will change from what was just set to the defaults.

       Even if Free Form Data is not supported, the AHA-1740 can still be
       used, but the default values for SCSI Device Configuration will have
       to suffice.  (Note: if multiple AHA-1740s are in the system, then all
       the 1740 BIOS should be enabled if any options are changed from the
       SCSI Device Configuration menu).

 2) Bus mastering issues:

       Some EISA systems have slots that do not support bus mastering.  If
       this is the case, then during software installation you will be
       formed that the slot does not support bus mastering, and that it
       should be moved to another slot.

 3) Operating Modes:

      The AHA-1740 has two operating modes:  standard mode and enhanced mode.
      Both modes support high performance DMA data transfers and 32 bit host
      transfers.  The main difference between the two modes is the internal
      mailbox structure used by the AHA-1740.  The enhanced mode features a
      new enhanced mailbox interface, thus allowing access to up to 4 gig.
      of host RAM. Some of the other differences are listed below:

         Standard Mode:                 Enhanced Mode:

         Fast SCSI disk support up      Fast SCSI disk support up
         to 5 MB/sec.                   to 10 MB/sec.

         Up to 16 Meg memory            Up to 4 Gig memory on motherboard
         on the motherboard*.

         Uses DMA, IRQ, and port        Does not use DMA/IRQ/Ports
         addresses

         Uses AHA1540.DSK               Uses AHA1740.DSK

         Does not support               Tagged Queuing is supported
         Tagged Queuing

         *Can be overcome with NetWare v3.11 and ASW-1440 v3.3

 4)  Using Adaptec device drivers.

 Standard Mode:

 Use the following command line switches on Adaptec ASPI device drivers
      to make the host adapter as compatible as possible:

       For the Novell NetWare 386 operating system:

           :load AHA1540 io_combine=1

        NOTE:  ASPITRAN.DSK must be in the same path.

      In addition, if your file server has more than 16 Megs of RAM, add the
      following command line switch:

 :load AHA1540 above16=y (NOTE: This is only supported with version
                                   ASW-1440 v3.3)

       Use the following STARTUP.NCF and AUTOEXEC.NCF files when more than
       16 Megabytes are in the system:

              STARTUP.NCF:
                 :set Auto Register Memory Above 16 Megabytes = OFF
                 :load AHA1540 above16=y

              AUTOEXEC.NCF:
                 :register memory 1000000 400000 (This is an example)

      The 'register memory' command is documented by Novell.  The first
      number is the starting address of the memory above 16 meg, and
      second number is the amount of extended memory.  Both numbers are in
      Hex.  The example above is for 4 Megs above 16 Meg.

       If you encounter a problem loading the driver with that switch, you
       may have to increase the reserved buffers below 16 meg with the
       following SET command:

             SET Reserved Buffers Below 16 Meg = 32

       If you are using NetWare 386 v3.1 or v3.0, or have a version of the
       ASW-1440 older than v3.3, than the system is limited to 16 Megs of
       RAM or less.  If more than 16 Megs of RAM are in the system, add the
       following line to your STARTUP.NCF:

           :set Auto Register Memory Above 16 Megabytes = OFF

    Enhanced Mode:

     Use the following command line switches on Adaptec ASPI device drivers
     to make the host adapter as compatible as possible:

       For the Novell NetWare 386 operating system:

           :load AHA1740 io_combine=1

  NOTE:  ASPITRAN.DSK must be in the same path.

       To disable Tagged Queuing on those disk drives that support it,
       add the following switch:

           :load AHA1740 max_tags=1

 5)  Multiple host adapter support

       Up to four AHA-1740s (standard mode) can be put into each system.
       All of the host adapters should have their BIOS enabled,
       The host adapters must be set to unique arbitration levels, port
       addresses, and Interrupt levels (done with the system EISA config
       software).

       Up to twelve AHA-1740s (enhanced mode) can be put into each system.
       All the host adapter BIOS should be enabled.  IRQ, DMA, and port
       addresses are not used.  The AHA-1740 in enhanced mode still uses
       IRQ 11, so this interrupt should be changed any AHA-1540/1520/1510
       host adapters in the same system, to avoid a hardware conflict.
       All AHA-1740s in enhanced mode can share IRQ 11 with other AHA-1740s,
       however.

 AHA-1520/1522:  AT to SCSI non bus master host adapter

      1) Description and Systems supported:

 The AHA-1520 and AHA-1522 use Programmed Input/Output as the method
      of host data transfer.  This type of data transfer is very compatible
      with the vast majority of AT class compatible systems.  Thus,
        virtually every AT compatible on the market will work with the
        AHA-1520/1522 host adapters.

 There are no limitations on the amount of host memory that can be in
        the system.  The AHA-1520/1522 supports up to 4 gigabytes of
        motherboard memory installed in the system.

 2)  Using Adaptec device drivers.


       The software package that supports the AHA-1520 family of host
       adapters is the ASW-1240.  The revision history is shown below.
       The AHA-1520 family of host adapters includes the AHA-1520,
       the AHA-1522, AHA-1510, and AIC-6260.

NOTES:
        - 1520 refers to the AHA-1520/1522
        - If a <number> is listed under description, that means that this
          version of the ASW-1240 includes the driver that was listed by the
          <number>.
        - 286 refers to Novell NetWare 286 v2.15 (SFT and Advanced)
            revs a, b, and c, and v2.2.
        - 386 refers to Novell NetWare 386
        - Adaptec SCSI host adapters are not supported with ELS versions of
            NetWare
        - All of the drivers listed below are Novell certified, except if
            marked with a *.
        - If the 'verbose=y' command line switch is used with
            NetWare 386 v3.11, the following text may appear:

                 !!! NO SCSI DEVICES FOUND TO REGISTER !!!

            Do not be concerned that SCSI devices are attached and are not
            being found by the driver.  The reason that this message occurs
            is because NetWare 386 v3.11 does not allow the host adapter to
            scan the SCSI bus to search for and display devices.  386 v3.1
            did allow this.  Simply ignore this, and proceed by loading
            the INSTALL.NLM, which is used to partition and add volumes to
            disk drives.  INSTALL will see all attached SCSI drives.

              Software Package:       Description:

        1)    ASW-1240 v1.0           Support for AHA-1520/1522 for NetWare
                                      286 v2.15 and NetWare 386 v3.1.  It
                                      also works with NetWare 286 v2.2,
                                      NetWare 386 v3.11 if patched with
                                      DSKPATCH.EXE.

        2)    ASW-1240 v1.1           Same as 1) above, except supported is
                                      added for the AHA-1510 and AIC-6260.

        3)    ASW-1240 v1.2           Same as 2) above, except the driver for
                                      NetWare 286 v2.2 is now certified and
                                      the driver for NetWare 386 v3.11 does
                                      not need to be patched.


 Use the following command line switches on Adaptec ASPI device drivers
        to make the host adapter as compatible as possible:

       For the Novell NetWare 386 operating system:

           :load AHA1520

 NOTE:  ASPITRAN.DSK must be in the same path.

 3)  Multiple host adapter support

       Up to two AHA-1520/1522 host adapters can be put into each system.
       Only one host adapter can have its BIOS enabled (and must be at port
       340H), and the other host adapter must have the BIOS disabled
       (remove the jumper labeled BE at jumper block J9).  The host adapters
       must be set to port addresses and Interrupt channels.  Only the
       PIO method of data transfer can be used, and must be used for each
       host adapter.


     ADAPTEC DISK CONTROLLER / NETWARE COMPATIBILITY

  This section includes a discussion of Adaptec hard disk controllers
  (not SCSI host adapters).

  I will summarize the below discussion here:

  The Adaptec ACB-2320D/2322D ESDI disk controller is completely compatible
  with all versions of Novell NetWare 286 and 386.  NetWare 286 has a 1024
  cylinder limit, so 63 sector translation or drive splitting should be used
  if the disk drive has greater than 1024 cylinders.

 There are no special considerations for NetWare 386.

 Adaptec MFM controllers are completely compatible with NetWare 286 and 386.

    The following hard disk controllers have compatibility issues with
    NetWare 286:

    ACB-2370/2372, 2370A/2372A, 2370B/2372B, 2372C, 2320/22, 2320A/2322A,
    2320B/2322B/2322B-8/2322B-16

  When using these disk controllers with NetWare 286 2.15 or 2.2, the
  disk driver provided with Novell NetWare must be patched in order to
  work with Adaptec controllers.  Patched versions of these drivers are
  available on the Adaptec BBS.  The disk driver is called ATDISK.OBJ or
  ISADISK.OBJ, and can be found on the DSK_DRV_.001 floppy diskette.

 These disk controllers are fully compatible with NetWare 386, however.

    The Novell disk driver for standard disk controller on supports one hard
    disk controller, so disk duplexing (two AT controllers in the same system)
    is not possible.  For disk duplexing applications, use SCSI host adapters
    (preferably Adaptec SCSI host adapters).


 All of the issues we have seen with different generations of Adaptec
 AT controllers and different generations of Novell Netware can be
 determined by the following list of problems.  Most of these
 problems existed only with old revisions of Netware.  On the
 current revisions of Netware available from Novell, only three
 problems are still an issue.

 Novell 2.OA advanced Netware 286
  1) Set up to use 17 sectors/per track only
  2) Doesn't wait very long for a hard disk controller to respond
   with data request after initiating write command.
  3) Not compatible with Adaptec autoconfiguration.
  4) Incompatiable with the Adaptec controller older version of
   firmware with effected the busy flag before setting IRQ14.

 Novell 2.OA Advanced             OBSOLETE
   Problems 1,2,3 and 4

 Novell 2.OA SFT versions         OBSOLETE
   Problems 1,2, and 3


 Novell 2.1O et al                OBSOLETE
   Problems 2 and 3

 Novell 2.11 et al                OBSOLETE
   Problems 2 and 3

 Novell 2.12 et al
   Problem 3

 Novell 2.15 et al
   Problem 3

 Implementations with Adaptec AT controller.

Problem   ACB-231X     ACB-23XXA                ACB-23XXB
   1      No Problem   Patch Netware            Use 17 sectors,or patch

   2      No Problem   Fixed with current F/W   No Problem
                       ACB-2372A/rev B
                       ACB-232XA/rev A

   3      No Problem   Use MB type table,DMN     Use MB type table,DMN
                       DUB-14, or patch          DUB-14,17 secotrs,  or
                                                 patch.
   4      No Problem   Fixed with current F/W    No Problem

Following are some installation tips for Novell

The only obstacle to installing Netware wtih Adaptec 23XX controllers is
providing the correct drive type parameters.  Netware can be patched to
allow the Adaptec BIOS autoconfiguration to do the job, but this is
limited to one physical drive in the system and is not recommended.  The
following list describes our recommended solution to this problem in
order of preference.

1) If a drive type table with the correct heads, cyls, and sectors/track
   is available, or a user programmable drive type table is available,
   select that table with the AT setup program, disable the Adaptec
   BIOS, and install Novell, including COMPSURF format analysis.

2) Use the DUB-14 card from Golden Bow to provide the correct drive type
   table.  Select the rive table using the DUB-14 setup routine, disable
   the Adaptec BIOS, and install Netware , including COMPSURF format
   analysis.

3) Use Disk Manager N from Ontrack to initialize the disk and setup
   for non-standard parameters after disabling the Adaptec BIOS.
   Follow the Disk Manager N instructions for installing Novell in
   conjunction with their software.

4) If the motherboard BIOS contains a 17 sector/track drive type
   table with the same approximate CAPACITY as the attached drive
   the 17-sector emulation capabilities of the ACB-23XXB may be used
   to allow the use of that drive type table.  First , format the
   disk drive using the Adaptec BIOS format utility, DO NOT mark
   defects on the manufacturer's defect list.  Disable the Adaptec
   BIOS. Use the AT setup utilites to select a drive table with the
   same capacity or LESS than the actual attached drive ( see equation
   below).

   (actual heads)(actual cyls)(actual sects\track)>(heads in table)
   (cyls. in table)(sects\track in table..17)

   Finally, install Netware, skipping the COMPSURF format, but still
   run COMPSURF disk analysis.


5) Use Adaptec Patch instruction to modify AT disk driver.  This allows
   Adaptec autoconfiguration to work, but is still only compatiable with
   installation of only 1 physical disk drive.

For an OEM customer who is designing in an AT RLL or ESDI disk
controller, the more desirable solution is to use option 1.  There
is no reason  why the motherboard BIOS does not support the correct
drive type table.  For system integrators and endusers's this is
typically not an option (except with the few BIOS'S that now support
programmable drive type tables).  Therefore options 2 through 4 are
generally recommended to those customers.


INSTALLATION INSTRUCTION FOR THE USING ADAPTEC AUTOCONFIGURATION
WITH NETWARE 2.12 AND 2.15

Adaptec PC/AT controllers support a feature called "autoconfiguration"
which allows the controller to automatically generate a drive type table
for systems that don't have a correct drive type table supplied in their
motherbboard BIOS.  The Adaptec controller BIOS performs this function
when the machine is first powered up. Unfortunately, this feature is not
normally compatiable with Netware.  Netware can be modified to allow the
use of this feature, although this method only supports the use of one
physical disk drive attached to the ACB-23XX controller. PLEASE READ THIS
ENTIRE APPLICATION NOT BEFORE ATTEMPTING TO INSTALL NOVELL NETWARE 2.12
OR 2.15WITH THE ADAPTEC ACB-23XX CONTROLLER.  Be sure to make backup
copies of the original Novell Netware diskettes.  DO NOT ATTEMPT TO MAKE
MODIFICATIONS TO THE ORIGINAL COPIES OF YOUR NOVELL DISKETTES.

1.)    PATCHING NETWARE

The Netware package contains a PC/AT disk driver call ATDISK.OBJ.  This
drivers must be modified as follows to allow the use of Adaptec
autoconfiguration:

    1.) Boot your computer from a DOS diskette.  Insert a diskette in
        drive A, that contains the utility DEBUG.COM .  Invoke the
        utility by typing:

          - A>DEBUG                   <CR>

    2.) Insert a copy of the Netware DSK_DRV_001 diskette in drive A:
        load ATDISK.OBJ by typing:

          - A> N ATDISK.OBJ           <CR>
          - A> L                      <CR>

    3.) Search for the hexadecimal code sequence 3D 00 C8 72 by
        entering the command:

          - S CS:0 FFFF 3D 00 C8 72   <CR>

    4.) The debugger should find two occurances of that sequence and
        reports the address of the first byte of each sequence with a
        display of the following format:

           AAAA:BBBB   where BBBB and YYYY are the offsets of the
           XXXX:YYYY              first bytes of each occurence

     5.) The sequence 3D 00 C8 72 must be replaced by 3D 00 00 72
         Enter the command:

           -E CS:BBBB                <CR>

         This will display the value 3D: press the space bar twice
         and the debugger displays the value C8 Type 00 and press
         the return key.

    6.) To verify that the patch was done properly, you may now display
        the changed data by entering the command:

            -D CS;BBBB                <CR>

    7.) Repeat steps 5 and 6 for the second occurence of the sequence
           (CS:YYYY).

    8.) Save the patched file on the diskette by entering the command

          -W                         <CR>

    9.) End the DEBUG session by typing:

          -Q                         <CR>






Software Patch for Novell Netware 2.0A-ELS1

The following files must be patched:

Disk                                        File

INSTALL                                     COMPSURF.EXE
INSTALL                                     PREPARE.EXE
OS ARCNET                                   NET $OS.EXE
OS ETHERNET                                 NET $OS.EXE

INSTALL                                     LOADER.DAT
INSTALL                                     INSTALL.EXE

In the first 4 files, 2 strings must be patched:

B9 64 00 must be replaced with B9 00 02.

and

3D 00 C8 72 must be replaced with 3D 00 00 72.

To implement these modifications, the DOS debug program, or
another editor capable of modifying files such as Norton
Utilities, AT 86, etc can be used.

Note that .EXE files cannot be modified by the DOS debug program,
therefore, these files ust be first renamed, then patched, then
renamed back to their original name.

The example below shows how to patch the COMPSURF.EXE file using
the DOS debug program:

C>ren a:compsurf.exe compsurf.ada

C>debug a:compsurf.ada
-s cs:0000 ffff 3d 00 c8 72
1382:743C
1382:74A5
1382:8FEC
1382:9063
-e cs:743C
1382:743C  3D.   00.   C8.00
-e cs:74a5
1382:74A5  3D.   00.   C8.00
-e cs:8fec
1382:8FEC  3D.   00.   C8.00
-e cs:9063
1382:9063  3D.   00.   C8.00
-w
Writing 1B3A8 bytes
-q

C>ren a:compsurf.ada compsurf.exe

C>

-- 
     Greg Widdicombe     |  Meta-Software, Inc.  |    _--_|\
  * Up from Down Under * | 1300 White Oaks Road, |   /     *\
                         |  Campbell, CA 95008   |   \_.--._/
 gregw@hspice.portal.com |     (408)369-5451     |         v