NOVELL TECHNICAL INFORMATION DOCUMENT TITLE: Readme for CDUP2.EXE README FOR: CDUP2.EXE NOVELL PRODUCTS and VERSIONS: NetWare 3.12 NetWare 4.1 ABSTRACT: The files in this release kit are currently in test in Novell Labs and Test bulletins will be soon be issued. These files provide minor enhancements to the CDROM.NLM and most importantly they provide IDE CDROM support under NetWare 4.1 and now under 3.12. ----------------------------------------------------------------- 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. ----------------------------------------------------------------- IDE CDROM devices are supported under NetWare 4.1 and 3.12 using the NWPA (NetWare Peripheral Architecture) layer of support. The files of 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. 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 (Host Bus Adapter). The CDM (Custom Device Module) extension refers to the driver that would be loaded to support specific types of devices attached to the HBA. For example, if you were using an IDE HBA (either a paddleboard or a motherboard with built-in IDE support) and you had an IDE drive attached that was serving as a NetWare volume, instead of loading the IDE.DSK you would now load the IDEATA.HAM and IDEHD.CDM drivers. If you then wanted to add an IDE CDROM player you would simply add the CDROM player to the IDE bus and load the IDECD.CDM. SYMPTOM: 1. Mounting IDE CDROM devices under NetWare 3.12 was not supported. 2. Trying to mount CD's with an excessively large number of directories or files would sometimes fail with an error message indicating that there was not enough directory space to mount the volume. SOLUTION: 1. Apply the latest CDROM.NLM and supporting NWPA files included in this kit. 2. Using the latest CDROM.NLM included in this kit, mount the CD volume with the /rx flag. The /rx flag rebuilds the index file with an extended amount of space being allocated for the index file. Self-Extracting File Name: CDUP2.EXE Files Included Size Date Time ..\ CDUP2.TXT (This file) CDCMMNDS.TXT 7394 7-18-95 9:00 am CDROM.NLM 118915 4-13-95 4:33 pm NWPA.NLM 69012 7-13-95 7:46 am NWPALOAD.NLM 2719 6-13-95 1:37 pm IDEATA.DDI 8512 6-12-95 10:21 am IDEATA.HAM 14441 6-13-95 1:29 pm IDECD.DDI 3818 2-14-95 12:24 pm IDECD.CDM 9372 6-26-95 12:44 pm IDEHD.DDI 5855 5-08-95 2:56 pm IDEHD.CDM 9494 9-19-94 2:03 pm ..\NETWARE.312 NPAPATCH.NLM 1985 6-26-95 10:27 am PM312.NLM 8603 3-27-95 12:38 pm Installation Instructions: 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. You may have to rename the previous versions of duplicate files in order to accomplish this. Make any needed hardware changes. You may need to re-configure your original IDE hard drive so that it now knows that there is a slave device attached to the IDE bus. Also jumper the IDE CDROM device as a slave. Load the IDEATA.HAM in place of the IDE.DSK if required. Load the new CDROM.NLM. This will cause NWPALOAD.NLM to load which in turn loads the NWPA layer. This should be all that's required. Mount your CD's as NetWare volumes like you have done in the past. For a list of available CDROM.NLM commands, type CD HELP at the SYSTEM CONSOLE prompt 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. NetWare 3.12 specific instructions: Copy the NPAPATCH.NLM and PM312.NLM from the 3.12 subdirectory on the kit to the boot partition of the server. 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 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 that would establish communication with the hardware will cause your server to ABEND. This patch like all other 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. - 3.12 specific 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 you MUST follow the instructions carefully or the CDROM.NLM will not load or your server may possibly ABEND with a GPPE. 1. Search the SYS volume for files named CDROM.MSG and delete them. Using the NDIR command from the root is suggested. 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. Features and Functions of NWPA: NWPA works more closely with the Media Manager layer in the OS (Operating System) than the old *.DSK drivers did. Part of the specification of the NWPA layer states that whenever a *.HAM driver is loaded it must scan the bus to determine what type of devices are attached to the bus. Based on the devices found, the *.HAM then auto-loads the appropriate *.CDM drivers to support those devices. Another example. Let's assume that you had a server with one IDE drive being used as a boot device and your NetWare volumes were on a SCSI bus in the same box. Let's say that you wanted to add an IDE CDROM device to your existing IDE bus. You would configure the IDE CDROM device as a slave and if needed configure the IDE drive as a Master with Slave attached and attach the CDROM player to the IDE bus. You would copy all of the files from this kit to the boot partition of your server in addition to the SYS:SYSTEM partition. You would modify your Startup.ncf so that instead of loading the IDE.DSK you load the IDEATA.HAM driver which would then auto-load the IDECD.CDM device driver and IDEHD.CDM. The IDECD and IDEHD CDM's would be auto-loaded due to the requirements that the HAM's auto-load the needed CDM's for whatever devices they find. Issuing a "List Devices" command from the server console would 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. 20. [V025-A0-D1:0] WDC AC2200F Original IDE hard drive with NO NetWare partitions. The fact that the IDE hard drive with NO NetWare partitions is showing up under "List Devices" may concern you but the only reason that it shows up is due to the requirement that the HAM's report all devices and load all CDM's required to support those devices. 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. 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 and 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). Types of CDROM players: CDROM players come in two different flavors. Their identity can be partially established by looking at the connector on the player. If the connector has 50 pins then you know that this device is a SCSI based CD player. If the connector is of the 40 pin variety then you have a more difficult problem on your hands. We will call the 40 pin connector type "other". Of the "other" types of CD players, there are 4 possible interface types: Mitsumi Sony Panasonic ATAPI The Mitsumi, Sony, and Panasonic types of interfaces are pretty widely accepted in the industry. NetWare support for these interfaces though is non existent. These interfaces are proprietary and no drivers exist to provide any type of support for these players to make CD's mountable as NetWare volumes. Most of the players that have this type of interface are connected either directly to some type of proprietary bus card or to an audio card (sound blaster, soundwave, etc). Many sound cards have three separate 40 pin connectors on them in order to support all of the possible interfaces. The ATAPI type of player, on the other hand, is commonly referred to as the IDE CDROM player. NetWare does provide drivers to mount CD's in the ATAPI devices as NetWare volumes. The drivers are found in this kit. If you have a CD with the "other" type of connector and it is not clearly labeled as to what type of interface it has or supports, please call the manufacturer of the device and ask them. IDE vs. ENHANCED IDE We hear much talk these days of enhanced IDE or EIDE as it may be called. These discussions beg the question; What is the difference between IDE and EIDE? Seagate and Quantum have produced a white paper that defines what the differences are. There are four major points that are outlined. The four points that supposedly define an enhanced IDE device are as follows: 1. High capacity addressing of ATA hard drives over 528 MB. 2. Fast data transfer rates for ATA hard drives (support for PIO mode 3 at 11.1 MB per second). 3. Dual ATA host adapters supporting up to four hard disk drives per computer system. See the note on Support Tips for IDE devices later in this document. 4. Non-hard disk drive ATA peripherals (e.g., CD-ROMs). Unfortunately many manufacturers disagree as to whether their machines and devices need to meet all four requirements or just one or a combination thereof. These disagreements are largely what lead to the incompatibilities that we so often see when using IDE devices under NetWare. DOS & Windows don't really push the limits of the so called IDE SPECIFICATION. For many years the IDE SPEC was so loosely defined that you could pour water through it. NetWare on the other hand pushes the SPEC and tests all of its limitations. Quotes from the white paper: "Each of these features (referring to the four points mentioned earlier) supports improved functionality at a system level and they are felt to be positive for the industry and end users. However, as a package, Enhanced IDE is causing increased confusion in the industry and raising the risks of incompatibility and mismatched system integration because theses features require an extremely high degree of integration. To have a fully functional Enhanced IDE system, specific support is required not only for the storage peripherals but also for host adapters, core logic, system bus, BIOS and operating systems - virtually every major block of PC architecture. Adding to this complexity is the fact that there is no central industry supported standard that controls these features". "In our experiments with some of the first available Enhanced IDE products, we encountered a variety of problems that prevented us from tapping their full potential." PC Magazine, July 1994. "The Perfect Hard Disk," page 194. Support Tips for IDE devices: Novell Technical Support has seen several issues where motherboards with dual IDE ports are unable to support IDE hard drives on one port and IDE CDROM devices on the other port. The problem is due to the way that the dual IDE ports are implemented on the motherboard via the CMD chipset. You may try putting the CDROM and hard drive on the same port to see if that will help solve your problem. If you find that the CMD chipset is the source of your problem and moving the CDROM and hard drive to the same port did not solve your problem we suggest that you contact the manufacturer of your machine for a work-around or driver to solve the problem. If all else fails then we suggest that you try a different paddleboard or contact your third party hardware supplier to see what products they have that are Novell certified with perhaps a more stable bus such as SCSI! ----------------------------------------------------------------- Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information. -----------------------------------------------------------------