ÿMKMSGFLXCB£¦©¬¯²µ¸»çz}€º½‚…ˆ‹Ž‘”—šåª Î j m / `mP4õÍÐŒ"p#@$¹%' ((((((( (#(&()(,(y)‰*Œ**? ? ? ? ? ? ? ? ECause: The value specified for the parameter in the MPC module in PROTOCOL.INI is not the correct type. User Action: Change the value in PROTOCOL.INI to the correct type for the parameter. ECause: An internal software error occurred. User Action: Contact your customer service center. ECause: One or more Auto Busmaster Family adapters are set to a different interrupt level. To function properly, these adapters must all be set to the same interrupt level. User Action: Use the reference diskette that came with your computer to ensure that all Auto Busmaster Family adapters are set to the same interrupt level. For ISA adapters, use the appropriate configuration program. ? ? ECause: The NDIS MAC driver (MPC) has detected an invalid interrupt level assigned to the Auto Busmaster Family adapter located in Slot n. The interrupt level is assigned by the system. User Action: Reconfigure your system slot which contain the Auto Busmaster Family adapter, to a valid interrupt level. ECause: The parameters specified require more space for processing than can be handled. The maximum allowable control-block size is 64KB. User Action: Reduce the value specified for the MAXTRANSMITS, MINRCVBUFFS, or MULTICASTNUM parameters to reduce the amount of storage required for the control-blocks. The control-block area can be computed using the following formula: 1698 + (192 * MAXTRANSMITS) + (256 * MINRCVBUFFS) + (16 * MULTICASTNUM) The control-block work area must be less than 64KB. ECause: The adapter is not responding to a request to initialize. User Action: Run the hardware diagnostics for the Auto Busmaster Family adapter. Contact your customer service center. ? ? ? ? ? ? ? ? ? WCause: Only one occurrence of the device driver statement for the Auto Busmaster Family adapter NDIS MAC device driver is required to support multiple adapters. Additional instances of the device driver statement in CONFIG.SYS will be ignored. User Action: Remove the duplicate device driver statements from CONFIG.SYS. ECause: The parameter specifying the driver name (DRIVERNAME) was not found in PROTOCOL.INI. This parameter is required. User Action: Change PROTOCOL.INI to specify the proper information. ECause: An unexpected error occurred when the program attempted to open the Protocol Manager. The Auto Busmaster Family adapter NDIS MAC device driver has been removed. User Action: Check the drive and directory to ensure that the protocol manager is located in the specified path. ECause: The device driver was unable to register with the Protocol Manager. User Action: Reinstall the Protocol Manager and try the operation again. ECause: There was no adapter found in this system. Auto Busmaster Family adapters are required to run the MAC device driver. User Action: Install an Auto Busmaster Family adapter in the computer, or remove the device driver statement from CONFIG.SYS. WCause: An unrecognized parameter was found while processing the Auto Busmaster Family adapter section of PROTOCOL.INI. User Action: Correct the parameter or remove it from PROTOCOL.INI. WCause: The value specified for the network address parameter in PROTOCOL.INI is not valid for one of the following reasons: - Invalid local station address - Too long - Too short - Contains non-hexadecimal characters - Not enclosed in double quotes User Action: Remove or correct the network address parameter (NETADDRESS). A valid value for this parameter is 12 characters long and is enclosed in double quotes. For Token Ring adapters, the locally administered address must be within the hex range 400000000000 through 7FFFFFFFFFFF. For Ethernet adapters, the locally administered address must be entered in CANONICAL format, such as 020000000000. Do not set the corresponding group address bit. ? ECause: The address specified for the NETADDRESS parameter is being used by another adapter on the network. User Action: Either modify PROTOCOL.INI to provide a different value for the network address (NETADDRESS) parameter, use the default burned-in address, or remove the other adapter that is using this network address from the ring. ECause: The token ring network is not functioning, or is currently in a beaconing state. Another possibility is that the token ring cable is not connected to the adapter card, or the adapter is configured for the wrong speed. User Action: Make sure the token ring cable is attached to the appropriate connector on the adapter. Verify that the adapter is properly configured for the ring speed (data rate) and media type. Reboot your computer. If this problem still exists, contact your network administrator. ECause: When the adapter tried to open onto the network, a hardware error occurred on the adapter. User Action: Run the hardware diagnostics for the Auto Busmaster Family adapter. Contact your customer service center. ECause: While attempting to open the adapter, an indication was received that the adapter is not properly connected to the Token Ring. User Action: Ensure that the Token Ring cable is connected to the adapter and to the Token Ring multistation access unit (MAU). If the error persists, use a different Token Ring cable and check to ensure that the connection to the MAU is functioning properly. Then, run the hardware diagnostics for the Auto Busmaster Family adapter. ECause: The ring speed is different from the speed of the adapter attempting to insert into the ring. User Action: For MCA adapters, use the reference diskette that came with your computer to ensure that the adapter is configured at the same speed as the Token Ring, or is configured for autosense mode. For ISA adapters, use the appropriate configuration program. For PCI adapters, add or modify the DataRate paramenter in PROTOCOL.INI. ECause: While attempting to open a new adapter in Token Ring mode using the autosense configuration option, it was determined that the adapter was the only station on the ring. The adapter will not be allowed to open in order to prevent possible network disruptions. User Action: Reboot the computer at a later time, when at least one other station is on the ring. As an alternative, reconfigure the adapter for manual mode, specifying the correct speed of the Token Ring to which the adapter is connected, then restart the computer. ? ? WCause: The amount of local memory needed to hold all possible queued transmit frames, MAXTRANSMITS * MAXTXFRAMESIZE, is greater than 128 kilobytes. The device driver has reduced the MAXTRANSMITS value to allow the maximum number of transmit frames to fit within 128 kilobytes so that any transmit frame data located above the 16 megabyte address boundary can be copied down by the device driver for transmission by the adapter. User Action: Ensure that the values specified for MAXTRANSMITS and MAXTXFRAMESIZE are accurately specified in PROTOCOL.INI. If not specified, they should both be added with appropriate values. The default values for these parameters in OS/2 are MAXTRANSMITS = 31 and MAXTXFRAMESIZE = 18000, which exceeds the 128 kilobytes allocated by the device driver for the local transmit buffer space. These local transmit buffers are needed when more than 16 megabytes of system memory is detected, and this Auto Busmaster Family adapter is unable to access above 16 megabytes. ECause: The Auto Busmaster Family adapter device driver was unable to determine the amount of system RAM in the computer. User Action: Contact your customer service center. ? ECause: The configuration parameters specified require more space for processing than can be handled with the available system memory. User Action: Reduce the value specified for the MAXTRANSMITS, MINRCVBUFFS, or MULTICASTNUM parameters to change the amount of storage required. The following formula can be used to compute the maximum value: H(i) = RCVAREA(i) + ALLOCSIZECB(i) A H(i) value should be computed for each Auto Busmaster Family adapter, and the sum of all H(i) values must be less than 1 MB. The receive area for each adapter can be computed: RCVAREA = MINRCVBUFFS x SIZWORKBUF The approximate control block area for each adapter can be computed using the following formula, and must be less than 64KB: ALLOCSIZECB = 1698 + (192 * MAXTRANSMITS) + (256 * MINRCVBUFFS) + (16 * MULTICASTNUM) If the high priority transmit channel is enabled, you must double the number of MAXTRANSMITS in the preceding formula. ECause: The adapter is not responding to a request to configure the high priority transmit channel. User Action: Run the hardware diagnostics for the Auto Busmaster Family adapter. Contact your customer service center. ECause: The adapter was unable to configure the high priority transmit channel. User Action: Run the hardware diagnostics for the Auto Busmaster Family adapter. Contact your customer service center. ECause: The Auto Busmaster Family adapter NDIS MAC device driver was unable to determine the type of I/O bus designed into the computer system. It was looking for either a Micro Channel, EISA, ISA or PCI bus. User Action: Make sure your system is based on one of these four I/O bus types and contains an industry-standard BIOS. Contact your customer service center. ECause: The Auto Busmaster Family adapter is configured to use I/O mode, but it is installed in a 10-bit ISA system. User Action: Change the adapter card configuration setting to use Memory Mapped I/O (MMIO) mode instead of I/O mode, then re-boot the computer. If the error persists, contact your customer service center. ECause: The Auto Busmaster Family adapter NDIS device driver timed-out waiting for a setup completion indication from the adapter card. User Action: Run the hardware diagnostics for the Auto Busmaster Family adapter. Contact your customer service center. ? ? ? ? ? ? ? ? ? ? ? ECause: The Ethernet cable is not properly connected between the adapter card and the local area network. User Action: Check that your Ethernet cable is: - Connected to the proper UTP, COAX, or AUI port on the adapter card. - Connected to the Ethernet network. - Properly terminated (if using an AUI or COAX connection). ECause: This is most likely due to an Ethernet COAX or AUI connection that has been broken or is improperly terminated. User Action: Check your network connection. If your network connection is good and this problem persists, contact your customer service center. ? ? ?