STANDARD MICROSYSTEMS CORPORATION Novell NetWare 386 3.1 Server driver For EtherCard PLUS Family LAN Adapters INSTALLATION GUIDE This software is licensed by SMC for use by its customers only. Copyright (c) 1992 Standard Microsystems Corporation. All rights reserved. The purpose of this document is to briefly explain the installation of the NetWare 386 LAN drivers that are used with the Standard Microsystems EtherCard PLUS Family LAN adapters. The files in the release diskette are: INSTALL.DOC This file. RELEASE.DOC Version number and specific release information. SMCPLUSS.LAN NetWare 386 3.1 Server driver. 1. Refer to the NetWare 386 Installation manual and follow the instructions to partition the hard disk and to copy the necessary system files to drive C:. 2. Copy SMCPLUSS.LAN from this diskette to drive C:. 3. Follow the "Run SERVER" and the "Load loadable modules" sections of Novell's Installation Manual to Step (3) - Load LAN driver module. load c:smcpluss 4. Answer the prompts for the hardware attributes of each adapter. Depending on the type of adapter you have, there are up to four adapter specific configuration parameters the driver may ask you to supply: 1) I/O Base Address. 2) Interrupt Request (IRQ) Level. 3) RAM Buffer Base Address. 4) Size of RAM Buffer - Enter 200 for 8K bytes 800 for 32K bytes. 5) MCA Bus Slot number (Micro Channel Only). For the SMC8003EP, WD8003EB, SMC8003W, SMC8013EP, SMC8013W, SMC8013EW, SMC8003WC, SMC8013WC, SMC8013EPC, and SMC8013EWC, the driver will only prompt you for the I/O Base Address. For the WD8003E, WD8003WT, WD8003EBT, WD8003S, and WD8003SH, the first four parameters listed above are required. For the WD8013EBT adapter, the first three parameters listed above are required. For all Micro Channel adapters, only the bus slot number is required. If you do not want the prompts to appear, you can include the required configuration parameters in a command line. Refer to the NetWare 386 3.1 System Administration manual under LOAD LAN drivers. For the SMC8003EP, 8003EB, 8003W, 8013EP, 8013W, 8013EW, 8003WC, 8013WC, 8013EPC, and 8013EWC: load c:smcpluss port=280 For the 8003E, 8003WT, 8003EBT, 8003S, and 8003SH: load c:smcpluss port=280 int=3 mem=d0000:200 For 8013EBT adapters: load c:smcpluss port=280 int=3 mem=d0000 For all Micro Channel adapters. load c:smcpluss slot=1 5. Proceed with Step (4) - Load other loadable modules - to continue the installation of NetWare 386 3.1. NOTE: The driver has to be bound to start working (refer to the section "Bind the protocol to the LAN driver"). Novell NetWare 386 3.1 Server driver Custom Variables 1. CollisionsCount This counter contains the total number of collisions that have been detected by the hardware when this driver has attempted to transmit a packet accross the network. 2. ExcessCollisionsCount This counter contains the total number of times that the hardware has not been able to transmit a packet because of collisions. The hardware will automatically re-attempt to transmit a packet up to 16 times if it detects that a collision has occured. On the 16th consective collision for a given packet, this variable is incremented. 3. TxTimeOutCount The number of times a Transmit complete interrupt did not occur within 2 seconds of starting a packet transmission. When this occurs, the NIC is reset and an atttempt is made to re-transmit the packet. 4. BadNetworkErrorCount This count contains the number of times that a packet was not transmited. If a Transmit Timeout occurs 10 times in a row for a given packet, the packet is discarded, this variable is incremented and an attempt to send the next packet is begun. 5. UnderrunErrorCount This variable counts the total number of times that the transmision FIFO has been underrun by the DMA controller. The NIC contains a 16-byte FIFO. During transmission the Transmit Serializer reads data from the FIFO and the DMA writs data into the FIFO from memory. If the FIFO becomes empty because the DMA does not write to it and the transmision byte count register on the NIC indicates that the packet has not been completely transmitted, a FIFO Underrun occurs. Transmission of the packet is aborted when this event happens. 6. RxCRCErrorCount This count contains the total number packets received with CRC errors. During transmission, CRC logic in the hardware generates a 32 bit CRC for the transmitted bit sequence and appends these four bytes as the last four bytes of a transmited packet. During reception, CRC logic grenerates a CRC field from the incoming packet and compares it to the last to four bytes of the packet. If the values do not match, a CRC Error is generated. This count is also incremented when Frame Alignment errors occur. A Frame Aligment error indicates that the incoming packet did not end on a byte boundary and consequently the CRC did not match at the last byte boundary. 7. RxFrameCRCErrorCount This count contains the total number packets received with a Frame Aligment error. This error indicates that the incoming packet did not end on a byte boundary and the CRC did not match at the last byte boundary. 8. RxFIFOOverrunErrorCount This countains the total number of times that the FIFO has been overrun when receiving a packet. The NIC contains a 16-byte FIFO. During reception the Receive Deserializer writes data into the FIFO and the DMA reads data from the FIFO. If the DMA cannot begin a bus access to write a byte of the received packet within the time it takes to fill the FIFO, a FIFO Overrun occurs. Reception of the packet is aborted when this event happens. 9. RxMissedPacketCount This count contains the total number to times that packets have not been received because the packet receive buffer queue is full. 10. GotNothingCount The number of times a receive packet interrupt occured without the NIC having placed any data in a recieve buffer. 11. NICResetCount Whenever the NIC is reset, this variable is incremented. This counter is incremented when the board is initialized for the first time, the board was in a SHUTDOWN state and then restarted, or a Transmit Timeout occured. 12. UnsupportedMediaCount The number of packets that have been received of a frame type that the driver has not been configured for (ETHERNET_802.2, ETHERNET_802.3, ETHERNET_SNAP, ETHERNET_SNAP) or does not support. 13. EnqueueSendCount The number of times the driver had a packet ready to transmit while the NIC was still transmitting the previous packet. 14. DequeueSendCount The number of times packets have been removed from the transmission queue where they have had there transmision delayed. EnqueueSendCount minus DequeueSendCount will be the current number of packets queued for transmission. On a properly operating network this number should be zero. 15. E8023PacketsAcceptedCount Number of ethernet 802.3 packets that have been received by this network node. 16. EiiPacketsAcceptedCount Number of Ethernet II packets that have been received by this network node. 17. E8022PacketsAcceptedCount Number of Ethernet 802.2 packets that have been received by this network node. 18. ESNAPPacketsAcceptedCount Number of Ethernet SNAP packets that have been received by this network node. 19. BackToBackTxCount Indicates the number of times a Transmit Complete, Transmit Abort or Transmit Timeout interrupt occured, and, there was another transmit packet already buffered to the LAN Adapter's RAM ready for immediate tranmission. 20. NICBusyCount Indicates the number of times that a transmit packet was moved to the LAN Adapter's RAM and transmission was not started because the NIC was currently transmitting another packet. 21. NICNeedsServiceCount The number of times that a transmit packet was moved to the LAN Adapter's RAM, and, the NIC was not busy transmitting a packet, and, the NIC had a Transmit Complete or Transmit Abort interrupt that needed servicing before the next packet could be transmitted. Novell NetWare 386 3.1 Server driver Error Messages 1. Error: Verifying LAN Adapter at Specified I/O Port. The driver was unable to find a lan card signature id at the spcified base I/O port. 2. Error: Verifying LAN Adapter in Specified Slot. The driver was unable to find a matching lan card Adapter Id byte in a Micro Channel system. 3. Error: Maximum LAN boards loaded for this driver. This error message indicates that the maximum number of lan cards that a single driver can support has been exceded. The current limit is eight lan adapter cards. 4. Error: Could not find matching virtual adapter. This message is displayed when attempting to load a new frame type for an adapter that has already been loaded, and the parameters describing the adapter do not match any of the currently running adapters. 5. Error: Unable to get resource tag. This is an internal OS error that should occur only when the system is out of memory. 6. Error: Unable to get memory. This is an internal OS error that occurs when the driver is unable to allocate memory needed for its local data. 7. Error: Unable to set hardware interrupt. This is an internal OS error that should occur only when the system is out of memory or, an attempt was made to share an un-sharable interrupt, or an invalid interrupt was specified. 8. Error: Hardware configuration conflict. This is an internal OS error that is displayed when the hardware configuration of a lan adapter has conflicts and does not match completely a previously configured adapter, or an invalid hardware parameter was specified. 9. Hardware Error: Node entered matches a multicast address. A node address was given on the command line or the board is configured for a node address that is reserved for multicast address. This can be fixed by zeroing the Least Significant Bit of the Most Significant Byte of the node address. 10. Hardware Error: Unable to initialize ethernet card. The driver is unable to read the base port register of the NIC. 11. Hardware Error: Ethernet buffer memory failure. A write/read of the the last word of memory on the Lan Adapter failed. This usually indicates a problem with the size of memory that the adapter is configured for, or a conflict with other memory in the system. 12. Error: Unable to register MLID with the LSL. This is an Internal OS error message that is displayed when registering a new board with the OS. This message usually indicates that the OS is out of memory. 13. Possible cable disconnect detected on LAN adapter. This message is displayed whenever the driver is unable to transmit a packet after 10 Transmit Timeouts have occured. Novell NetWare 386 3.1 Server driver Warning Messages 1. Unneeded Memory Address ignored The user specified a memory address parameter when loading the driver that was un-needed. A sofware specified memory address will be used instead. 2. Unneeded Memory Length ignored The user specified a memory length parameter when loading the driver that was un-needed. A sofware specified memory length will be used instead. 3. Unneeded Interrupt number ignored The user specified a interrupt number parameter when loading the driver that was un-needed. A sofware specified interrupt number will be used instead. EtherCard PLUS, TokenCard, and SuperDisk are trademarks, and SMC and Standard Microsystems are registered trademarks of Standard Microsystems Corporation. Other trademarks mentioned herein belong to their respective companies.