NOVELL TECHNICAL INFORMATION DOCUMENT TITLE: Latest CDROM.NLM and supporting files. README FOR: CDUP4.EXE NOVELL PRODUCTS and VERSIONS: NetWare 3.12 NetWare 4.01 NetWare 4.02 NetWare 4.1 ABSTRACT: This file contains the latest CDROM.NLM and support files for v3.12 and v4.x. ----------------------------------------------------------------- DISCLAIMER THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL. NOVELL MAKES EVERY EFFORT WITHIN ITS MEANS 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. ----------------------------------------------------------------- ISSUE: New features and fixes: - the command CD DIR would provide incorrect file and directory names - the key did not escape from the CD DIR command as prompted - lowers CPU utilization during indexing and subsequent IO activity - provides faster volume mounts - corrects a problem during large file copies where the copy would slow down dramatically Self-Extracting File Name: cdup4.exe Files Included Size Date Time ..\ CDUP4.TXT (This file) CDCMMNDS.TXT 7391 7-26-95 3:25:06 pm CDROM.NLM 134252 5-7-96 4:28:38 pm IDEATA.DDI 8512 6-12-95 10:21:16 am IDEATA.HAM 14441 6-13-95 1:29:56 pm IDECD.CDM 9372 6-26-95 12:44:28 pm IDECD.DDI 3818 2-14-95 12:24:40 pm IDEHD.CDM 9494 9-19-94 2:03:54 pm IDEHD.DDI 5855 5-8-95 2:56:48 pm NWPA.NLM 69012 7-13-95 7:46:36 am NWPALOAD.NLM 2719 6-13-95 1:37:54 pm ..\NETWARE.312\ NPAPATCH.NLM 1985 6-26-95 10:27:20 am PM312.NLM 8603 3-27-95 12:38:26 pm Installation Instructions: Installation Instructions for all versions of NetWare 3.12 and 4.10: Copy all of the files from the root directory of this kit to both the boot partition of your server and the SYS:SYSTEM directory. NetWare 3.12 specific instructions: Copy the NPAPATCH.NLM and PM312.NLM from the 3.12 subdirectory of the kit to the boot partition of the server. ******************************************************************************- ************************************* NOTE: These new patch files supersede any previous versions.The old NPA312 module is no longer needed. ******************************************************************************- ************************************* Modify your Startup.ncf file so that the VERY FIRST item loaded is the NPAPATCH.NLM. NPAPATCH.NLM is dependent on PM312.NLM and will attempt to auto-load the PM312.NLM file. This patch fixes a couple of known issues with the media manager and in as much as the Media Manager manages all communication with devices this patch must be loaded first. Failure to load this patch before any drivers establish communication with the hardware may cause your server to ABEND. This patch, like all other dynamic patches should not be unloaded once the server is up. Unloading any patch while the server is running can and most likely will cause unpredictable results. The current version of the CDROM.NLM needs to have AFTER311.NLM, STREAMS.NLM and CLIB.NLM files loaded before it will load. You can accomplish this by loading the AFTER311.NLM file at the server console. The CLIB.NLM and STREAMS.NLM files will be automatically loaded. Because the latest CDROM.NLM is message enabled it must be loaded from the SYS volume and you MUST follow the instructions below carefully for your 3.12 server: 1. Search the SYS volume for files named CDROM.MSG and delete them. Using the NDIR command from the root is suggested. For example "NDIR CDROM.MSG /s". Note: If you experience problems with the server after loading this new NLM make sure that the first search path is set to the location where the CDROM.NLM was loaded from. If you are still experiencing problems then log a call with Novell Technical Support. IDE specific driver Load Order: NetWare 3.12 startup.ncf: Load NPAPATCH Load IDEATA port=1f0 int=14 NetWare 3.12 autoexec.ncf Load After311 Load CDROM NetWare 4.10 startup.ncf: Load IDEATA port=1f0 int=14 NetWare 4.10 autoexec.ncf Load CDROM When IDEATA.HAM is loaded, it will scan for any attached devices. If a CD-ROM device is discovered, IDECD.CDM will be loaded. For hard drives, IDEHD.CDM is loaded. The new CDROM.NLM will autoload the NWPALOAD.NLM which will in turn autoload the NWPA.NLM. After the NWPA.NLM loads the NWPALOAD.NLM will unload itself.Mount your CD's as NetWare volumes as you normally would. For a list of available CDROM.NLM commands, type CD HELP at the SYSTEM CONSOLEprompt after the CDROM.NLM has been loaded. Additional information about CDROM.NLM commands can be obtained by looking at the CDCMMNDS.TXT file included in this kit or by studying the September 1994 AppNote. 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 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 ----------------------------------------------------------------- Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information. -----------------------------------------------------------------