NP600 Installation and Configuration Readme File The new NP600 server drivers version 3.04EC for Netware 286 are included on the enclosed diskette. The files should match the following for size, time, and date. ANP600.OBJ 7971 7-16-90 5:07p BNP600.OBJ 7971 7-16-90 5:07p CNP600.OBJ 7971 7-16-90 5:07p DNP600.OBJ 7971 7-16-90 5:08p NP600.LAN 606 7-16-90 5:08p i. Copy the Operating System driver description file "NP600.LAN" to the AUXGEN diskette for "floppy disk" method or to the AUXGEN sub-directory if you are using "harddisk" or "network" method. For generating an External Bridge, the "NP600.LAN" file should be copied to the BRGEN-1 diskette or the BRGEN-1 sub-directory. ii. For the "floppy disk" method a blank disk needs to be formatted and labeled. Use the DOS LABEL command to label the diskette as "LAN_DRV_003". If the "harddisk" or "network" method is being used a subdirectory under a NetWare generation or work directory must be created. Under this generation directory use the DOS MKDIR command to create the "LAN_DRV_.003" subdirectory . Copy the *.OBJ files to either the labeled diskette or subdirectory depending on which method is being used. iii. Run NETGEN and select the correct driver from the list of driver options to generate the file server operating system. iv. Run BRGEN and select the correct driver from the list of LAN adapter options to generate the external bridge software. Before installing your NP600 boards in your server, you need to pick a configuration for each of the NP600s. The following is the configuration table for the NP600 drivers. 0 : I/O Address = 300h, IRQ = 9, DMA = 7 1 : I/O Address = 308h, IRQ = 11, DMA = 5 2 : I/O Address = 310h, IRQ = 15, DMA = 3 3 : I/O Address = 318h, IRQ = 5, DMA = 7 4 : I/O Address = 320h, IRQ = 9, DMA = 7 5 : I/O Address = 318h, IRQ = 5, DMA = 1 6 : I/O Address = 340h, IRQ = 5, DMA = 7 7 : I/O Address = 350h, IRQ = 11, DMA = 5 8 : I/O Address = 360h, IRQ = 3, DMA = 1 The IRQ selection jumper and the DMA selection jumpers are along the bottom edge of the PCB and should be clearly marked. Allowable IRQ selections are 3, 5, 9, 11, and 15 from left to right. There is a single jumper to select this. The DMA jumpers are a pair of jumpers that must be matched, and moved as a set. The DMA pins are groups of 4, two groups to the left of the IRQ pins, and two to the right. They are numbered 7, 5, 1, and 3, reading left to right. All jumpers, including the IRQ and the pair of DMA jumpers, should be installed in a vertical orientation. That is, positioned so that the jumper connects pins in a line from the top edge of the board to the bottom or card connector edge. The I/O address jumpers are in the middle/top of the PCB. Depending on your silkscreen, they may be easily readable, but for the table below, the jumpers are listed as reading LEFT TO RIGHT, and an "A" means the jumper installed from the middle pin to the pin towards the bottom or card edge connector, a "B" means the jumper installed between the middle pin and the pin towards the top or the 80186 chip. The jumpers represent address lines A9 through A3, reading from left to right, and "A" matches a binary 0 and "B" matches a binary 1. 300 B B A A A A A 308 B B A A A A B 310 B B A A A B A 318 B B A A A B B 320 B B A A B A A 340 B B A B A A A 350 B B A B A B A 360 B B A B B A A Finally, before installation in your server, select the interface type. This is the jumper that looks like a chip in the 4-row socket setup near top of the back panel. If you want to use the onboard thin-net interface with the BNC connector, the jumper-chip (also called a DIP-SHUNT) should be installed between the top and 3rd row of holes. If you want to use the DB-15 interface for thick-net or to external interfaces, then the chip should be installed between the 2nd and bottom row of holes. When you install the NP600 into a server, make sure you pick a slot with the extra connector for 16 bit operations. The NP600 cannot operate in an 8-bit slot. Once the 600 is installed and operational, there are a couple things that should be brought to the attention of the individual responsible for the system. There is a lot of discussion of routing buffers and percentages used in various documents and on various BBS systems. With the NP600 (and any other card that prefetches buffers) you first get a buffer for receive, then it hangs around assigned to the card until a packet is actually received from the wire. With most cards, you receive a packet, then go get a buffer and put it there. The problem is that when you run multiple LANs with cards that need buffers 'prefetched' you tie up a buffer for each LAN, when FSPs might be at a premium. They are just sitting there assigned to the cards doing nothing tying up resources and system performance suffers. Fortunately, Novell has an option, called 'turbo' buffers. These are the communication buffers you specify when you 'gen' your server. These are referenced as 'routing' buffers in the statistics. There is a caveat here that if routing buffers are used they will show up as 100% routing when you look at the statistics. This is not a problem except when trying to interpret the statistics and you do not realize how the NP600 operates. Just keep in mind that the results will not be as described in the Novell document "The Final Word". Using routing buffers directly means that you can have 4 NP600s in a server, and NOT tie up all the FSPs by assigning buffers to cards that just sit there waiting for received packets. Finally, previous users of NP600s have always been told that the red LED on the back is an error condition. With the current NP600 driver, the red LED indicates transmit activity, and the green LED indicates received activity. Received packets 'toggle' the green LED and turn the red LED off. Transmit packets 'toggle' the red LED. The timer tick also 'toggles' the green LED. This way the RED appears mostly off, but shows transmit activity. If it locks on, it is an error condition. The green LED shows receive activity, and in the absence of activity, flashes to show the NP600 is alive and well. Racal Bulletin Board Service - I.B.B.S The I.B.B.S. is a dial up service that provides subscribers with up-to-date marketing and technical information about Racal Interlan products. In addition, up-to-date DOS, Novell, LAN Manager, Banyan, 3COM and other device drivers are available. The service is available 23 hours a day. Individual dial up service is also available. Contact Racal Interlan at 1-800-LAN-TALK or 508-263-9929 for complete details. Racal InterLan Customer Service Your first line of Assistance and service for this product is available from your dealer or distributor that sold you the product. If you are unable to obtain the needed assistance, please contact Racal Interlan at: 1-800-LAN-TALK or outside the United States 1-508-263-9929. Please have your product name and serial number ready when you call us.