NOVELL TECHNICAL INFORMATION DOCUMENT TITLE: NWPA.NLM and CDROM.NLM updates. TID #: 2951606 README FOR: NWPAUP1A.EXE SUPERSEDES: NWPAUP1.EXE NOVELL PRODUCTS and VERSIONS: NLMs 3.12 NLMs IW 4.11 NLMs - NW42SV ABSTRACT: This file contains the latest NWPA (NetWare Peripheral Architecture) files, including the latest HAMs, CDMs, CDROM.NLM for v3.12, v3.2 and v4.x. ----------------------------------------------------------------- DISCLAIMER THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL. NOVELL MAKES ALL REASONABLE EFFORTS TO VERIFY THIS INFORMATION. HOWEVER, THE INFORMATION PROVIDED IN THIS DOCUMENT IS FOR YOUR INFORMATION ONLY. NOVELL MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS INFORMATION. ----------------------------------------------------------------- INSTALLATION INSTRUCTIONS: INSTALLING ON NETWARE VERSIONS 3.12/3.2 (This software kit will help you to upgrade a NetWare 3.12 server to support HAMs and CDMs. ) Before beginning the upgrade process, verify that the server to be upgraded is a fully functional NetWare 3.12 server which has been patched with the latest NetWare 3.12 OS patch kit. (The current minimum patch kit that should be installed, is 312PTD.exe.) After verifying that the patches have been properly installed, perform the following steps: 1. Copy all the files included in this download's "\COMMON" and "\3X" directories to the DOS directory from which NetWare is initially started. 2. Replace the CDROM.NLM that resides in the SYS:SYSTEM directory with the CDROM.NLM that is included in this download's \3x directory. 3. Edit the STARTUP.NCF to include the loading of the MMATTRFX.NLM patch, NWPALOAD.NLM and any required HAMs and CDMs. (Note that the NWPALOAD.NLM auto-loads NWPA.NLM and NBI.NLM. These files must be loaded prior to the loading of the .HAM and .CDM drivers.) For example the startup.ncf should look something like this: load c:patches\312ptd\pm312 pmload c:patches \312ptd load c:mmattrfx.nlm load c:nwpaload.nlm load c:scsi154x.ham port=330 load c:scsihd.cdm 4. If the CDROM.NLM is being used, modify the AUTOEXEC.NCF file to include the loading of AFTER311.NLM prior to the loading of CDROM.NLM. For example: load after311 load cdrom.nlm 5. "DOWN" the server, then enter "RESTART SERVER" at the console prompt. *************************** NWPA-SBACKUP SUPPORT ON NETWARE 3.12/3.2 -------------- DIBIMM.NLM serves as an additional driver shim for use with SBACKUP under Netware 3.12. DIBIMM allows SBACKUP to use the new Media Manager interface instead of the old DAI interface. This new interface allows for better error-handling as well as the use of NWPA drivers. DIBIMM.NLM is not meant as a replacement for DIBIDAI.NLM. DIBIMM.NLM only supports devices which are controlled by NWPA drivers (a HAM and CDM combination). DIBIDAI.NLM must be used for devices which are controlled by DAI drivers (most notably TAPEDAI.DSK). Supported Devices --------------- Currently, any tape device which is controlled by NWPA drivers and has at least single and multiple file mark capability is supported. Devices which do not have the minimum functionality will not appear on the list of devices when SBACKUP is first loaded. Installation --------------- Support for the DIBI2MM interface comes in the the form of 2 files: DIBIMM.NLM ~ This file resides in SYS:SYSTEM\ and is loaded by SBACKUP when the user selects the DIBI2MM interface. DIBI2$DV.DAT ~ This file resides in SYS:SYSTEM\DIBI\ and is used by SBACKUP to determine the DIBI drivers which are supported on the server. Simply replace the old DIBI2$DV.DAT with the new copy. Running Sbackup.nlm using NWPA drivers. --------------- After the files have been installed correctly, type "load sbackup" on the console. After SBACKUP loads and the user enters a proper login ID and password, SBACKUP will present the user with a list of DIBI drivers."DIBI2MM" should appear at the top of the list. After selecting DIBI2MM, a list of Media Manager tape devices which are controlled by NWPA drivers should appear. After the user selects a specific tape device, the user will be be asked if he or she wishes to change the block size. Normally, this block size can be left the same. After selecting "No" or choosing a new block size, SBACKUP's main menu should appear. From this point, the behavior of SBACKUP should be the same as with other DIBI drivers. ******************************* INSTALLING ON NETWARE VERSIONS 4.10/4.11 (Note these files have only been tested and certified for use on the NetWare 4.11 platform. They have not been tested on a NetWare 4.10 system.) 1. Create the directory C:\UPDATE. 2. Copy the files contained in this download's "\COMMON" and "\4X" directories to C:\UPDATE. 3. Edit the STARTUP.NCF file by entering the following two lines: load c:\update\nwpaload.nlm load c:\update\scsi154x.ham port=330 load c:\update\scsihd.cdm These should be added after any "set" parameters but before any "load" statements, then save the file. (NOTE: A current version NBI is included in this download file. You may need to use the NBI.NLM that is currently being used with your lan driver as it is more likely to experience a compatibility issue.) 4. Boot the server, dismount any CD-ROM volumes if mounted, unload CDROM.NLM if already loaded, and load INSTALL.NLM. 5. Edit AUTOEXEC.NCF and replace the line to load the CDROM.NLM file with the line "load c:\update\cdrom", then save the file. 6. DOWN the server, then enter "RESTART SERVER" at the console prompt. ISSUE: The NWPA.NLM, NWPAIO.NLM, NWPAMS.NLM, NBI.NLM and CDROM.NLM files are the same revisions as what are found in Support Pack 6a for NetWare 4.11. The HAMs and CDMs included in this download are the latest certified and release versions available at this time. They may or may not be newer that what is found in the IWSP6a.EXE update. This download kit is provided so that 4.10 and 3.x customers can take advantage of the NWPA architecture. Listed are some of the higher profile issues fixed by this update. Issue: Changes were made to front end the NEB calls for NWPAMS and NWPAIO. The APIs are just stubbed in the SFT3 modules because NEB is not supported in SFT3. This, however, allows drivers to load. The command line parser was also fixed to allow more than 256 chars in the command line string. Issue: Fixed SCSIHD.CDM, SCSICD.CDM, SCSICHGR.CDM and SCSIMO.CDM to pick appropriate disk geometry and capacity on media with unit sizes greater than 512Bytes/Sector and not initialized with any partitions. Issue: This new IDEATA.HAM fixes an issue where some Quantum drives sporadically are not being reported during ReturnDeviceInfo. In turn, that caused the Media Manager to assume that the device had gone away. Issue: The addition of the DIBIMM.NLM. DIBIMM allows SBACKUP to use the new Media Manager interface instead of the old DAI interface. This new interface allows for better error-handling as well as the use of NWPA drivers. ******************* BACKGROUND INFORMATION ON NWPA (NetWare Peripheral Architecture): The use of HAM's and CDM's on NetWare 4.1 SFTIII is not currently supported. If you need to mount CD's on a NetWare 4.1 SFTIII server, we suggest that you attempt this only with SCSI devices. IDE CDROM devices are supported under NetWare 4.1 and 3.12 using the NWPA (NetWare Peripheral Architecture) layer of support. The files NWPA.NLM, NWPALOAD.NLM, and NPAPATCH (3.12 specific) provide this layer of support. NWPA.NLM, NWPALOAD.NLM, IDECD.CDM, IDEHD.CDM, IDEATA.HAM, and CDROM.NLM are now universal files meaning that they are not NetWare version specific. They can be loaded on either 3.12 or 4.10. The NWPA layer uses *.HAM and *.CDM files instead of the normal *.DSK files. Breaking the monolithic *.DSK drivers out into *.HAM and *.CDM files makes them much easier to support and much easier to maintain from a development standpoint. The HAM (Host Adapter Module) extension refers to the driver that would be loaded to support a specific HBA (HostBus Adapter). The CDM (Custom Device Module) extension refers to the driver that would be loaded to support specific types of devices attached tothe HBA. Features and Functions of NWPA: Under the new NWPA the devices appear slightly differently than they did under the old *.DSK regime. Issuing a "List Devices" command from the server console could yield the following information: (this is for illustration only and most likely will not be exactly what you will see): 1. Device # 0 Quantum LPS540S (5E000000) (A SCSI hard drive attached). 19. [V025-A0-D1:1] NEC CD-ROM DRIVE:260 FW:1.01. (An IDE CDROM player). The numbers to the far left of the above example are the Media Manager object numbers. These numbers are used internally in the OS and are simply reported here. Basically it is the order in which these devices registered themselves with the Media Manager. DOS partitions, NetWare partitions, logical partitions, physical partitions, Hot Fix areas, etc. are all examples of objects that the Media Manager has to manage. Consecutive numbers are very rare and usually found in the most basic server setups, sometimes not even then. Do not be alarmed if your server does not have consecutive numbers! The NWPA also introduces an enhanced numbering sequence. In the above example you see a number within the []'s. This number is defined as follows [Sx-Vxxx-Ax-Dxx:x]: Sx - denotes the server number. In non-SFTIII environments the "S" and it's following number will not appear. In a SFTIII environment you will see either a "0" (Primary Server) or "1" (Secondary Server) following the "S". Vxxx - denotes the manufacturer ID. This was a two position number under the *.DSK drivers. The number has been expanded to 3 hexadecimal characters for use under NWPA. Numbers less than 100 have been assigned to Novell drivers. Ax - denotes the NWPA assigned unique adapter number. This number increments by one for each load of a HAM. Dxx:x - denotes the device number. This number has been expanded to handle the need to report more and more devices as technology advances. For IDE devices the first digit will be 1 if the port is 1F0, 2 if the port is 170, 3 if the port is 1E8 and 4 if the port is 168. In the case of SCSI the first digit denotes the SCSI id set on the device. For IDE the digit following the ":" denotes either Master (0) or slave (1). Under SCSI the digit following the ":" denotes the LUN (Logical Unit Number). By default the HAM's will try and load any needed CDM's for devices that are attached to the HAM. If you do not want the HAM's to autoload all of the required CDM's then instead of loading the HAM's first, which then autoloads the NWPA layers, we suggest that you explicitly load the NWPA.NLM with the /naload flag before any HAM's are loaded in the Startup.ncf. This will tell the NWPA.NLM NOT to autoload the HAM's and CDM's that it normally would. You will then need to load the HAM's and CDM's manually. For example: Startup.ncf where the CDM's are NOT autoloaded load NWPA /naload load ideata port=1f0 int=14 load idecd NWPAUP1.EXE was revised to correct readme and file compatibility issues. No new issues were resolved with this new version of the download. Self-Extracting File Name: NWPAUP1A.EXE Files Included Size Date Time ..\ NWPAUP1A.TXT (This file) ..\3RDPARTY\ AHA154X.DDI 13260 5-11-1998 12:57:22 pm AHA154X.HAM 29335 7-20-1998 4:55:16 pm AHA2740.DDI 4319 3-26-1998 11:16:38 am AHA2740.HAM 60826 3-25-1998 3:07:38 pm AHA2920A.DDI 6048 5-19-1998 2:59:08 pm AHA2920A.HAM 30170 4-21-1998 4:54:10 pm AHA2940.DDI 9887 6-2-1998 6:17:52 pm AHA2940.HAM 98815 7-20-1998 12:36:34 pm AIC63XX.DDI 11764 7-28-1998 1:32:30 pm AIC63XX.HAM 38676 7-20-1998 4:52:44 pm AIC78U2.DDI 2932 10-20-1998 5:25:20 pm AIC78U2.HAM 108310 11-30-1998 11:15:50 am BLFP3.DDI 22042 5-14-1998 12:33:06 pm BLFP3.HAM 101586 3-25-1998 12:46:42 am BLMM3.DDI 20766 5-14-1998 12:53:56 pm BLMM3.HAM 59900 3-25-1998 12:47:16 am CPQARRAY.DDI 8476 12-10-1998 5:02:00 am CPQARRAY.HAM 64465 12-17-1998 1:23:00 am CPQFC.DDI 5696 8-6-1998 6:00:00 am CPQFC.HAM 112120 12-17-1998 1:20:00 am CPQSCSI.DDI 6800 1-6-1999 5:03:00 am CPQSCSI.HAM 123352 1-14-1999 1:32:00 am CPQSHD.CDM 60421 12-2-1998 1:25:00 am CPQSHD.DDI 7769 12-16-1998 5:03:00 am DLTTAPE.CDM 44205 6-4-1998 2:50:12 pm DLTTAPE.DDI 5950 6-8-1998 4:06:10 pm EXATAPE.CDM 44716 5-5-1999 2:00:38 pm EXATAPE.DDI 7366 3-31-1998 11:51:08 pm INI9100.DDI 3557 4-29-1998 12:34:20 pm INI9100.HAM 60632 3-16-1998 2:17:00 pm IPSRAID.DDI 8848 5-27-1998 5:42:20 pm IPSRAID.HAM 23458 5-18-1998 12:29:00 pm LP6000.DDI 1357 3-4-1998 11:01:16 am LP6000.HAM 45701 4-14-1998 4:03:30 pm MDAC.DDI 4702 6-17-1998 3:26:16 pm MDAC.HAM 136571 7-29-1998 8:36:12 pm MEGA4_XX.DDI 16348 1-8-1999 2:27:08 pm MEGA4_XX.HAM 27201 10-27-1998 1:13:44 pm QL1000.DDI 3063 10-30-1997 2:52:24 am QL1000.HAM 54142 10-30-1997 2:52:32 am QL1080.DDI 3408 6-22-1998 4:54:26 pm QL1080.HAM 61744 6-22-1998 4:51:58 pm QL1240.DDI 3062 10-30-1997 2:52:56 am QL1240.HAM 56546 10-30-1997 2:53:04 am QL1280.DDI 3504 2-5-1999 8:44:00 pm QL1280.HAM 61436 4-16-1999 5:00:00 pm QL2100.DDI 3454 12-16-1998 10:40:26 am QL2100.HAM 77580 10-21-1998 2:22:14 pm SCSIDPT.DDI 26320 7-21-1998 10:04:32 am SCSIDPT.HAM 65691 6-17-1998 11:29:10 am SYM8XXNW.DDI 45884 6-23-1998 5:03:00 am SYM8XXNW.HAM 129045 6-23-1998 5:03:00 am SYMHINW.DDI 41488 6-23-1998 5:03:00 am SYMHINW.HAM 127050 6-23-1998 5:03:00 am UDMA.DDI 15501 10-15-1998 5:34:48 pm UDMA.HAM 25199 7-21-1998 5:51:58 pm ..\3X\ CDROM.NLM 134819 10-29-1997 3:44:00 pm DIBI2$DV.DAT 231 7-22-1996 11:49:40 am DIBIMM.NLM 16956 5-6-1997 2:17:10 pm MMATTRFX.NLM 1406 2-24-1997 2:27:20 pm NBI31X.NLM 45581 10-20-1998 5:08:20 pm TAPEDAI.DSK 37303 5-8-1997 11:19:58 am ..\4X\ CDROM.NLM 135214 9-24-1998 3:37:00 pm NBI.NLM 20338 8-29-1997 3:08:36 pm ..\COMMON\ DLTTAPE.CDM 45071 2-26-1999 11:31:10 am DLTTAPE.DDI 7157 2-26-1999 2:44:56 pm IDEATA.DDI 15534 8-17-1998 12:49:24 pm IDEATA.HAM 23318 8-25-1998 6:48:52 pm IDECD.CDM 9342 10-30-1998 1:50:34 pm IDECD.DDI 11933 10-28-1998 10:45:24 am IDEHD.CDM 11094 10-27-1998 5:39:06 pm IDEHD.DDI 12886 5-19-1998 3:09:46 pm IPSRADM.NLM 115027 4-16-1998 11:45:10 am IPSRAID.DDI 8848 5-27-1998 5:42:20 pm IPSRAID.HAM 23458 5-18-1998 12:29:00 pm NWASPI.CDM 15734 5-14-1998 3:41:10 pm NWASPI.DDI 6741 6-12-1998 12:07:00 pm NWPA.NLM 94727 2-1-1999 9:26:00 am NWPAIO.NLM 34491 2-1-1999 9:25:00 am NWPALOAD.NLM 3304 7-22-1998 4:45:08 pm NWPAMS.NLM 73905 2-1-1999 9:25:00 am NWTAPE.CDM 58657 11-19-1998 8:34:58 am NWTAPE.DDI 6787 5-7-1998 3:17:14 pm SCSI2TP.CDM 40564 7-14-1997 9:20:50 am SCSI2TP.DDI 3601 8-21-1996 11:55:14 am SCSICHGR.CDM 11492 3-11-1999 1:24:18 pm SCSICHGR.DDI 11097 7-23-1998 11:28:08 am SCSIHD.CDM 14683 3-11-1999 11:15:56 am SCSIHD.DDI 7548 7-23-1998 10:23:14 am SCSIMO.CDM 14927 4-27-1999 2:48:26 pm SCSIMO.DDI 7587 7-23-1998 11:25:58 am SCSIOSM.DDI 2463 10-26-1998 7:12:36 pm SCSIOSM.HAM 16076 3-5-1999 6:02:02 pm ----------------------------------------------------------------- Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information. -----------------------------------------------------------------