This document (2951606) is provided subject to the disclaimer at the end of this document.
Click the filename to download: nwpaup1a.exe 1341903 bytes 09Jun1999 06:44PM
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.
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.
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 Version Checksum
\
NWPAUP1A.TXT 17979 09Jun1999 06:43PM
\3rdparty
AHA154X.DDI 13260 11May1998 12:57AM
AHA154X.HAM 29335 20Jul1998 04:55PM
AHA2740.DDI 4319 26Mar1998 11:16AM
AHA2740.HAM 60826 25Mar1998 03:07PM
AHA2920A.DDI 6048 19May1998 02:59PM
AHA2920A.HAM 30170 21Apr1998 04:54PM
AHA2940.DDI 9887 02Jun1998 06:17PM
AHA2940.HAM 98815 20Jul1998 12:36AM
AIC63XX.DDI 11764 28Jul1998 01:32PM
AIC63XX.HAM 38676 20Jul1998 04:52PM
AIC78U2.DDI 2932 20Oct1998 05:25PM
AIC78U2.HAM 108310 30Nov1998 11:15AM
BLFP3.DDI 22042 14May1998 12:33AM
BLFP3.HAM 101586 25Mar1998 00:46AM
BLMM3.DDI 20766 14May1998 12:53AM
BLMM3.HAM 59900 25Mar1998 00:47AM
CPQARRAY.DDI 8476 10Dec1998 05:02AM
CPQARRAY.HAM 64465 17Dec1998 01:23AM
CPQFC.DDI 5696 06Aug1998 06:00AM
CPQFC.HAM 112120 17Dec1998 01:20AM
CPQSCSI.DDI 6800 06Jan1999 05:03AM
CPQSCSI.HAM 123352 14Jan1999 01:32AM
CPQSHD.CDM 60421 02Dec1998 01:25AM
CPQSHD.DDI 7769 16Dec1998 05:03AM
DLTTAPE.CDM 44205 04Jun1998 02:50PM
DLTTAPE.DDI 5950 08Jun1998 04:06PM
EXATAPE.CDM 44716 05May1999 02:00PM
EXATAPE.DDI 7366 31Mar1998 11:51PM
INI9100.DDI 3557 29Apr1998 12:34AM
INI9100.HAM 60632 16Mar1998 02:17PM
IPSRAID.DDI 8848 27May1998 05:42PM
IPSRAID.HAM 23458 18May1998 12:29AM
LP6000.DDI 1357 04Mar1998 11:01AM
LP6000.HAM 45701 14Apr1998 04:03PM
MDAC.DDI 4702 17Jun1998 03:26PM
MDAC.HAM 136571 29Jul1998 08:36PM
MEGA4_XX.DDI 16348 08Jan1999 02:27PM
MEGA4_XX.HAM 27201 27Oct1998 01:13PM
QL1000.DDI 3063 30Oct1997 02:52AM
QL1000.HAM 54142 30Oct1997 02:52AM
QL1080.DDI 3408 22Jun1998 04:54PM
QL1080.HAM 61744 22Jun1998 04:51PM
QL1240.DDI 3062 30Oct1997 02:52AM
QL1240.HAM 56546 30Oct1997 02:53AM
QL1280.DDI 3504 05Feb1999 08:44PM
QL1280.HAM 61436 16Apr1999 05:00PM
QL2100.DDI 3454 16Dec1998 10:40AM
QL2100.HAM 77580 21Oct1998 02:22PM
SCSIDPT.DDI 26320 21Jul1998 10:04AM
SCSIDPT.HAM 65691 17Jun1998 11:29AM
SYM8XXNW.DDI 45884 23Jun1998 05:03AM
SYM8XXNW.HAM 129045 23Jun1998 05:03AM
SYMHINW.DDI 41488 23Jun1998 05:03AM
SYMHINW.HAM 127050 23Jun1998 05:03AM
UDMA.DDI 15501 15Oct1998 05:34PM
UDMA.HAM 25199 21Jul1998 05:51PM
\3x
CDROM.NLM 134819 29Oct1997 03:44PM
DIBI2$DV.DAT 231 22Jul1996 11:49AM
DIBIMM.NLM 16956 06May1997 02:17PM
MMATTRFX.NLM 1406 24Feb1997 02:27PM
NBI31X.NLM 45581 20Oct1998 05:08PM
TAPEDAI.DSK 37303 08May1997 11:19AM
\4x
CDROM.NLM 135214 24Sep1998 03:37PM
NBI.NLM 20338 29Aug1997 03:08PM
\common
DLTTAPE.CDM 45071 26Feb1999 11:31AM
DLTTAPE.DDI 7157 26Feb1999 02:44PM
IDEATA.DDI 15534 17Aug1998 12:49AM
IDEATA.HAM 23318 25Aug1998 06:48PM
IDECD.CDM 9342 30Oct1998 01:50PM
IDECD.DDI 11933 28Oct1998 10:45AM
IDEHD.CDM 11094 27Oct1998 05:39PM
IDEHD.DDI 12886 19May1998 03:09PM
IPSRADM.NLM 115027 16Apr1998 11:45AM
IPSRAID.DDI 8848 27May1998 05:42PM
IPSRAID.HAM 23458 18May1998 12:29AM
NWASPI.CDM 15734 14May1998 03:41PM
NWASPI.DDI 6741 12Jun1998 12:07AM
NWPA.NLM 94727 01Feb1999 09:26AM
NWPAIO.NLM 34491 01Feb1999 09:25AM
NWPALOAD.NLM 3304 22Jul1998 04:45PM
NWPAMS.NLM 73905 01Feb1999 09:25AM
NWTAPE.CDM 58657 19Nov1998 08:34AM
NWTAPE.DDI 6787 07May1998 03:17PM
SCSI2TP.CDM 40564 14Jul1997 09:20AM
SCSI2TP.DDI 3601 21Aug1996 11:55AM
SCSICHGR.CDM 11492 11Mar1999 01:24PM
SCSICHGR.DDI 11097 23Jul1998 11:28AM
SCSIHD.CDM 14683 11Mar1999 11:15AM
SCSIHD.DDI 7548 23Jul1998 10:23AM
SCSIMO.CDM 14927 27Apr1999 02:48PM
SCSIMO.DDI 7587 23Jul1998 11:25AM
SCSIOSM.DDI 2463 26Oct1998 07:12PM
SCSIOSM.HAM 16076 05Mar1999 06:02PM
| Document Title: | NWPA.NLM and CDROM.NLM updates. |
| Document ID: | 2951606 |
| Creation Date: | 08Jun1999 |
| Modified Date: | 30Mar2000 |
| Revision: | 2 |
| Novell Product Class: | NetWare |
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.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.