Madge LAN Support Software Error Messages

1002 * Hardware problem: failed to discover interrupt number.
The adapter's interrupt setting may conflict with that of another device installed in the computer. Check the interrupt and I/O location settings.

1003 * No adapter at specified I/O location.
No adapter has been found at the I/O location specified. Either no adapter is present at the I/O location or the adapter is present but is failing to respond correctly.

1004 * No adapter found.
No adapter has been found. Either no adapter is present or the adapter is failing to respond correctly.

1005 Invalid interrupt number specified.
Either an interrupt number override was specified and the adapter could not be set to that interrupt number, or an interrupt number was specified (without requesting override) and it did not match the interrupt number of the adapter.

1006 Invalid DMA channel specified.
Either a DMA channel override was specified and the adapter could not be set to that DMA channel, or a DMA channel was specified (without requesting override) and it did not match the DMA channel of the adapter.

1007 No interrupt number selected by configuration utility.
This applies to Smart 16/4 MC adapters and Smart 16/4 MC32 adapters only. The adapter cannot be accessed because MicroChannel interrupts are disabled. To select an interrupt number, run your computer's configuration program.

1009 No adapter with specified I/O location and slot.
An adapter was found at the specified I/O location, but it was not at the specified slot. Change or remove the specification of the slot number.

1016 Interrupt already in use.
The specified interrupt is in use by another device, and cannot by shared. Reconfigure the adapter, or change the interrupt being used by the other device. This error will only be reported by OS/2 drivers.

1017 No speed selected by configuration utility.
This applies to Smart 16/4 EISA, MC, and MC32 adapters only. The default ringspeed setting for these adapters is adapter disabled. To use the adapter, run your computer's configuration program and select a valid ring speed.

1018 Adapter not enabled by configuration utility.
This applies to Smart 16/4 EISA, Smart 16/4 MC, and Smart 16/4 MC32 adapters only. To enable the adapter, run your computer's configuration program.

1020 No adapter at specified slot.
No adapter has been found at the slot specified. Either no adapter is present at that slot or the adapter is present but is failing to respond correctly.

1022 Software already running on adapter.
The adapter is already in use by another Madge driver. If you wish to overload the existing driver unload the previous one, or use options to the new driver to force the load.

1027 PCMCIA Failed to get I/O range from Card Services.
PCMCIA adapters are allocated resources, such as I/O ranges, by a software entity referred to as Card Services. A given implementation of Card Services will have a list of I/O ranges available for use with PCMCIA adapters. The first resource that Madge software requests for PCMCIA adapters is an I/O range. This error indicates that Card Services has been unable to allocate an I/O range to the adapter. Either there is already software running on the adapter and it already has an I/O range, or Card Services has no suitable I/O ranges in its list (the adapter requires an I/O range which is 32 bytes long, and which is aligned on a 32 byte boundary). It may be possible to change the configuration of Card Services and allocate more I/O ranges to it (see the documentation associated with it). This error may also occur if a third party PCMCIA device has been removed and the software driving that device has not relinquished control of the socket to Card Services.

1028 PCMCIA Failed to get interrupt number from Card Services.
PCMCIA adapters are allocated resources, such as interrupt numbers, by a software entity referred to as Card Services. A given implementation of Card Services will have a list of available interrupt numbers for use with PCMCIA adapters. This error indicates that none of the interrupt numbers in this list are available for use with the adapter. If possible, allocate more interrupt numbers to Card Services, but bear in mind that certain PCMCIA socket controllers (such as the Intel, or any Intelcompatible controller) only support a limited set of interrupt numbers, and that those interrupt numbers allocated to Card Services should be ones which are not being used by any other devices in the system.

1029 PCMCIA Card Services failed to configure card.
The PCMCIA card could not be set up for the driver by Card Services. This strongly indicates that the adapter is faulty.

1030 PCMCIA Card Services out of memory.
Change your Card Services configuration to enable Card Services to access at least 4kbytes of DOS memory.

1034 Invalid IO location allocated by PCI BIOS.
There is a problem with the system BIOS in allocating the IO resource. This should not occur. If it does, check that you have the latest BIOS code.

1036 * Failed verifying downloaded code.
This error strongly indicates that some other device in the computer is using I/O locations which conflict with the I/O range of the adapter. Some devices do not look at all parts of I/O addresses (often using only the least significant ten bits) and hence respond to large numbers of I/O locations scattered throughout I/O space. For example, some sound cards at 0220h also appear at X220h, X620h, XA20h, and XE20h (where X is any hexadecimal digit). This would mean that Madge Smart 16/4 AT Ringnodes (which can be set to 0A20h, 1A20h, 2A20h or 3A20h) could not be used unless the I/O location of the sound card were changed to, say, 0240h. Alternatively, this error might indicate an adapter fault for example, a faulty memory chip.

1037 No adapter with specified burntin address.
No adapter has been found with the specified burntin address. Either no adapter is present with that burntin address, or the adapter is present but is failing to respond correctly.

1038 No adapter with specified I/O location and burntin address.
An adapter was found at the specified I/O location, but it did not have the specified burntin address. Change or remove the specification of the burnt-in address.

1041 Bad automatic configuration of PCMCIA card.
The PCMCIA adapter has been automatically configured some PCMCIA utility, but has not been assigned sufficient resources to function. Either it has not been assigned an interrupt number, or it has not been assigned an I/O range or has been assigned an I/O range that is too small. There is no need to automatically configure the adapter Madge software is capable of configuring the adapter itself by making use of Card Services.

1042 No adapter at specified slot with specified burnt-in address.
An adapter was found at the specified slot, but it did not have the specified burnt-in address. Change or remove the specification of the burnt-in address.

1043 Bad interrupt line trigger mode.
This applies to Smart 16/4 EISA Ringnodes only. The trigger mode (edge or level) set up by the BIOS at the programmable interrupt controller (PIC) does not match the trigger mode of the adapter. This indicates a fault in the BIOS or in the computer's EISA configuration program.

1044 DMA channel test failed.
The test of the adapter's DMA channel failed. This usually indicates that another card is using the same DMA channel.

1046 No adapter at specified subport.
No adapter has been found at the specified subport. A subport number identifies a particular adapter on a Multinode. Either no Multinode is present, or you have specified a subport which does not exist (Multinodes currently only have subport numbers ranging from 1 to 3), or that subport on the Multinode is faulty.

1047 No adapter at specified I/O location and subport.
An adapter was found at the specified I/O location, but it was not at the specified subport on a Multinode.

1048 No adapter at specified slot and subport.
An adapter or Multinode was found at the specified slot, but either it was not a Multinode, or it was a Multinode without an adapter at the given subport.

1107 Invalid DMA channel selected.
You have specified an incorrect DMA channel. Check the switch settings and commandline options.

1108 adapter failed to start up.
The adapter hardware could not be started. Run the Madge Diagnostics program for further information.

1110 Check cable is attached.
The cable is not connected. Check that the cable is connected to both the adapter and the hub.

1111 Error bringing up adapter.
The adapter hardware could not be started. Run the Madge Diagnostics program for further information.

1112 Hardware problem: DMA problem at initialize.
It is not possible to initialize the adapter because of a DMA error. There may be an incorrect DMA setting.

1113 * Hardware problem: initialize timed out.
The attempted Direct Memory Access, performed while initializing the adapter, timed out. There may be an incorrect DMA setting. If this message appears during remote booting of OS/2 from LAN Server, it may indicate an interrupt clash.

1114 * Hardware problem: check cable is attached.
Check that the cable is attached.

1115 Hardware problem: invalid initialize options.
It is not possible to initialize the adapter because the requested hardware options are invalid.

1116 Hardware problem: odd receive burst count.
This is a problem reported by the hardwareinterface software. There may be a DMA problem.

1117 Hardware problem: odd transmit burst count.
This is a problem reported by the hardwareinterface software. There may be a DMA problem.

1118 Hardware problem: invalid DMA threshold.
This is a problem reported by the hardwareinterface software. There may be a DMA problem.

1119 Hardware problem: invalid SCB at initialize.
This is a problem reported by the hardware interface software.

1120 Hardware problem: invalid SSB at initialize.
This is a problem reported by the hardware interface software.

1121 Hardware problem: DIO parity error.
There may be an incorrect DMA setting.

1122 Hardware problem: DMA timeout at initialize.
There may be an incorrect DMA setting.

1123 Hardware problem: DMA parity error at initialize.
There may be an incorrect DMA setting.

1124 Hardware problem: DMA bus error at initialize.
There may be an incorrect DMA setting.

1125 Hardware problem: DMA data error at initialize.
There may be an incorrect DMA setting.

1126 Hardware problem: adapter check at initialize.
There may be an incorrect DMA setting or the adapter is faulty.

1127 * Madge Smart adapter Memory is full.
The adapter may not be a Madge Smart 16/4 adapter.

1130 * Failed to open the adapter check cable is attatched.
The adapter could not open onto the ring. Check that the cable is connected to both the adapter and the hub.

1131 Failed to open the adapter duplicate node address.
The adapter could not open onto the ring as there was another adapter with the same insert address. Check that any LAA is configured correctly.

1131 Failed to open the adapter run diagnostics.
The adapter could not open onto the ring. Run the Madge Diagnostics for further information.

1139 Open failed run diagnostics.
The adapter cold not open onto the ring. Run the Madge Diagnostics software.

3211 Unable to relocate code/data.
A problem has occurred while relocating the protocol modules. The Smart II Software is unable to relocate the modules.

3233 * No protocols installed.
No protocols have been installed, due to an earlier error. This can be caused by a problem with the adapter.

3234 * Insufficient memory space on adapter.
There is not sufficient memory space on the adapter to download all the protocols specified.

3257 Unable to lock memory, use PIO mode.
The Smart II kernel cannot allocate the memory it needs to do LOMEM DMA transfers. Use PIO instead.

3212 Missing ']'
The parser was expecting a closing ']' to match a previous '[', it did not find one.

3213 Unexpected '['
The parser was not expecting a '[' at this point.

3214 Unexpected ']'
The parser was not expecting a ']' at this point.

3215 Unexpected `;'
The parser was not expecting a `;' at this point.

3216 * Misplaced section heading.
The parser was not expecting a section heading here.

3217 * Misplaced data.
There is a mistake in your SMART.CFG or on the command line.

3218 Too many parameters in a section, limit is...
The parser has run out of space to process a section in the SMART.CFG file. The maximum number of parameters it can parse is given.

3219 Too many protocols in section, limit is...
You have asked for too many protocols on one Ringnode, the maximum possible number is given. (This is not directly related to error 3234 in prevous section. It is a parsing error.)

3220 Too many cards, limit is...
You have asked to download protocols to more Ringnodes than the Smart II Software can handle. The maximum number possible is displayed. (This is normally 4.)

3221 Section name is too long.
The name in a section delimited by [ ] is too long.

3222 * Unable to find protocol.
The parser cannot find the named protocol, either in the executable file created by SMTLINK, or on the disk in the path. Try changing the PATH= parameter.

3223 * Module version is incompatible.
Specified protocol modules are incompatible. Be sure to have versions that are compatible.

3224 * Unrecognized keyword.
The Smart II Software does not recognize the specified keyword; check the spelling, or that the keyword is in the appropriate protocol section.

3225 * Unrecognized data.
The data given in the SMART.CFG file, or on the commandline, could not be recognized by the parser.

3226 Value too large, maximum is...
The given value is more than the maximum allowed. The maximum possible value is displayed.

3227 Value too small, minimum is...
The given value is less than the minimum allowed. The minimum possible value is displayed.

3228 I/O location already used.
The specified I/O location has been given twice to refer to different Ringnodes.

3229 * String is too long, maximum length is...
The parser is trying to handle a string that is too long. The maximum possible length is given.

3230 * Keyword requires data.
A keyword was given but the necessary data was not present.

3231 Adapter resources cannot be initialized.
There is a problem allocating space for the resources that the different protocols on the Ringnode need.

3235 Bad node address (range is 400000000000 to 7FFFFFFFFFFF)
The specified node address is not in the allowed range 400000000000 to 7FFFFFFFFFFF.

3236 Bad hexadecimal digit.
A digit in a node address is incorrect.

3232 * Too many LLC instances.
You have tried to install too many LLCs on the host. The maximum is normally 4.

3237 Unable to allocate receive buffer memory.
There is insufficient host memory for the LLC to allocate its receive buffer.

3238 * Failed to register LLC.
The LLC failed to register with the arbitrator.

3275 Bad adapter type specified.
ADAP.TYPE parameter in the LLC section of smart.cfg.

2123 * Failed to define MIF.
The NetBIOS Define MIF call failed.

2401 * Failed to register NetBIOS.
The NetBIOS failed to register with the arbitrator. There may already be a NetBIOS registered with the arbitrator.

3232 * Too many instances of NetBEUI. Maximum is...
An attempt has been made to install too many NetBIOSs on a host. The maximum is normally 2.

3277 NDIS driver name too long (max 15 characters).
The name given in SMART.CFG should not be longer than 15 characters.

3278 NDIS cannot register driver with protocol manager.
The protocol has been unable to register with the protocol manager. Check the configuration of your software and PROTOCOL.INI.

3279 No entry for this NDIS module found in PROTOCOL.INI.
Check PROTOCOL.INI has a correctly named section for the Smart NDIS software.

2403 * IPX interface already installed.
There is already an IPX interface on the computer. A new one cannot be loaded unless this interface is removed.

3229 ODI configuration line too long.
There is an error in the ODI section of your SMART.CFG file or command line. You have used a line that is longer than the maximum the parser can handle.

3240 * LSL not loaded.
The LSL, required by ODI, has not been loaded.

3241 Failed to register protocol.
ODI has failed to register with the LSL.

3242 Failed to register frame.
ODI has failed to register its frame type with the LSL.

3243 * Smart ODI internal error.
A serious internal error has occurred with the ODI protocol module. Fatal, cannot continue.

(no code) * External file: no further information available.
An error occurred parsing NET.CFG.

3250 * Bad IP address.
You have specified an incorrect IP address.

3251 * Router not on local network.
The default router is not on the same IP network as the host.

3252 * Specified ip.netmask not suitable for Class A network.
The IP address you have specified is for a Class A network, but the net mask is not suitable for a Class A network.

3253 Specified ip.netmask not suitable for Class B network.

The IP address you have specified is for a Class B network, but the net mask is not suitable for a Class B network.

3254 Specified ip.netmask not suitable for Class C network.
The IP address you have specified is for a Class C network, but the net mask is not suitable for a Class C network.

3256 * Failed to set ip.address.
The Smart II Software cannot discover your PC's IP address.

3258 Cannot open the ETHERS file.
The RARPD smart module cannot find the ethers file which specifies the IP address to MAC address mapping. Use the ETHERS parameter in the RARPD section of smart.cfg to configure the location of the ETHERS file.

3259 TCP/IP interface already loaded.
The Smart TCP/IP protocol suite is already loaded and you cannot reload it.

3261 No valid entries found in the ETHERS file.
No valid entries were found in the ETHERS file which specifies the MAC address to IP address mapping used by the RARPD.SMT module. Refer to SMTRARPD.TXT for the correct formatting of the ETHERS file.

3262 TCP/IP requires the LSL to provide tunneling support.
You must run the LSL before running Smart TCP/IP when NWIP support is required. NWIP support is selected using the TUNNEL and TUNNEL.BUFFERS parameters in the NOVAPI section of smart.cfg.

3264 Bad Winsock interface specified, choose MADGE or LANWORKPLACE.
Only MADGE and LANWORKPLACE may be used with the WINSOCK.INTERFACE parameter in the NOVAPI section of smart.cfg.

3265 Loading VNOVAPI.386 failed.
NOVAPI.SMT is not loaded. NOVAPI.SMT must be loaded as part of Smart TCP/IP before VNOVAPI.386 and WINSOCK.DLL will successfully install. The option to continue into Windows, without loading VNOVAPI.386 is provided.

3266 Loading VNOVAPI.386 failed. Use NOVAPI.SMT v3.18 or later.
The versions of VNOVAPI and NOVAPI being used are incompatible. You must use NOVAPI.SMT v3.18 or later.

3267 Smart Winsock configuration error.
VNOVAPI.386 and VTCPIP.386 are both loading but are incompatible. You cannot load both VTCPIP and VNOVAPI. Consult the WINSOCK.TXT file for information on how you should resolve this conflict.

3268 Smart Winsock configuration error
A potentially incompatible DLL is using the VNOVAPI interface. You should use our Smart Winsock DLL v1.05 or later.WINSOCK.DLL is attempting to use the VNOVAPI interface. You should remove any superfluous WINSOCK.DLL files from your path and consult WINSOCK.TXT information file for more details.

3269 WARNING VNOVAPI.386 has already been loaded by NOVAPI.SMT, notloading the VNOVAPI.386 file specified in SYSTEM.INI
There is an unnecessary reference to VNOVAPI.386 in your system.ini file. This reference is not required for later versions of NOVAPI.SMT as VNOVAPI will be auto loaded.

3270 Too many IP addresses specified in net.cfg.
Multiple IP addresses are invalid with Smart TCP/IP.

3271 Too many IP routers specified in net.cfg.
Only one default IP Router may be specified with Smart TCP/IP. Smart TCP/IP will in fact store multiple IP routers internally, but these are detected dynamically by the ICMP protocol and cannot be configured in smart.cfg ( the size of this internal cache can be configured in smart.cfg see SMTTCPIP.TXT for details).

3272 Too many IP netmasks specified in net.cfg.
Multiple IP netmasks are invalid with Smart TCP/IP.

3273 NOVAPI.SMT has not been loaded.
NOVAPI.SMT must be loaded as part of Smart TCP/IP before VNOVAPI.386 and WINSOCK.DLL will successfully install.

3274 VNOVAPI.SMT has not been loaded.
VNOVAPI.386 must be loaded before WINSOCK.DLL will successfully load.

2503 Insufficient memory.
Check the server's memory requirement. (This applies only to SMART386.LAN.)

2508 This frame is already registered.
Specify the frame type correctly or use the default.

2512 LOAD aborted.
The driver did not load as information was displayed.

2513 PC 16/4 card not supported.
The Smart 16/4 PC Ringnode is not supported.

9356 PIO not supported on MC Ringnodes.
Switch the MC card to Bus Master mode.

103 * Binary file is incorrect.
The firmware file, MDGDOS??.BIN, found in the directory containing MADGEODI.COM is incorrect. Ensure that the .BIN & .COM files are from the same release of software.

2701 * Invalid slot in NET.CFG.
There is no Madge Smart 16/4 Ringnode at the slot you specified.

2702 * Invalid DMA in NET.CFG.
The Ringnode cannot use the DMA channel you specified. Check your NET.CFG settings for SLOT, PORT, DMA, and IRQ.

2703 * Invalid IRQ in NET.CFG.
The Ringnode cannot use the interrupt level you specified. Check your NET.CFG settings for SLOT, PORT, DMA, and IRQ.

2704 * Can not open MDGDOS??.BIN.
The MADGEODI driver cannot find the firmware file MDGDOS??.BIN. Put in the same directory as MADGEODI.COM.

2707 Unable to lock contiguous high memory.
The correct driver buffers could not be allocated. Check your configuration, and memory drivers. Try reducing memory usage.

9901 Locally Administered Address is out of range.
The LAA specified in the NET.CFG file is incorrect.

9902 LSL Buffer size too small (minimum 626).
Check your NET.CFG file contains the correct parameters.

9905 * Unable to allocate memory for buffers.
There is insufficient memory for receive and/or transmit buffers.

2002 Failed to register hardware options.
The driver could not reserve the adapter card hardware resources. Check the configuration for an IO, interrupt or DMA clash.

2003 Failed to register MLID with LSL.
The driver could not register itself with the LSL. Check the configuration files.

2004 No adapter or incorrect type.
No adapter can be found. Check it is configured and enabled by running the Madge Diagnostics software.

2005 No adapter at specified location.
The adapter is not present at the location specified. Check the configuration is correct, or the adapter is functional.

2006 Error while locating adapters.
An error occured while the driver attempted to locate adapters. Check that all adapters are configured correctly using the Madge Diagnostics software.

2007 Failed to allocate memory for buffers.
There is not enough memory for the driver internal buffers. Try reconfiguring to reduce memory usage (eg. reduce frame size).

2008 Adapter failed to open onto the ring.
Check that the lobe cable is securely attached and that the correct ring speed is selected.

2009 Error in test transfers.
The adapter failed the transfer check to or from the adapter. Run the Madge Diagnostic software.

2010 Failed to download code onto adapter.
There is a problem accessing the adapter hardware. Run the Madge Diagnostics software.

2011 Download image corrupt.
There is a problem with the driver. Check you have the correct files from the release disk.

2012 Failed to enable interrupt.
There may be an invalid interrupt or interrupt clash.

2013 Failed to enable DMA channel.
There may be an invalid DMA or DMA clash.

2014 The adapter has not been enabled.
Run the relevant configuration software to enable the card.

2015 The adapter's ring speed has not been configured.
Run the hardware configuration software to set the ring speed.

2017 Error bringingup adapter.
There is a problem accessing the adapter hardware. Run the Madge Diagnostics software.

2018 Error initializing .
There is a problem with the driver. Check you have the correct files from the release disk. Run the Madge Diagnostics software.

9201 Cannot open Protocol Manager device driver
The operating system returned an error when the driver attempted to open the Protocol Manager device driver. This normally indicates that the Protocol Manager has not been loaded: it is normally loaded prior to MDGND by a 'DEVICE=' line in CONFIG.SYS (although this is not the case with Windows for WorkGroups).

9202 Problem performing IOCTL request with Protocol Manager
The operating system returned an error when the driver attempted to perform an IOCTL request to the Protocol Manager. This probably indicates a problem with the Protocol Manager.

9203 There are no usable Madge Smart 16/4 Ringnodes
The driver failed to find any suitable network adapters for any of the MDGND modules defined in PROTOCOL.INI. As a result the driver will not register any modules with the Protocol Manager, and unload itself if InitOnLoad is set to TRUE.

9204 No modules in PROTOCOL.INI require Madge NDIS driver
The driver failed to find any section in PROTOCOL.INI that included the line 'DriverName = MDGND$'. Hence, there is no module pertaining to MDGND, and the driver is not required; consequently, it will unload itself.

9205 Insufficient adapter memory to support maximum frame size
There is not enough memory on the adapter associated with this module for the driver to allocate enough buffers for the maximum frame size required. The solution is to reduced this size by using the MaxFrameSize parameter.

9206 Internal driver error during initialisation
The driver discovered an internal consistancy error during initialisation. This indicates a fatal error in the driver: it should never be seen in practice.

9207 Interrupt number verification failed
The value for the IRQNumber parameter in the MDGND module didn't match the IRQ configured for the adapter associated with that module.

9208 DMA channel verification failed
The value for the DMAChannel parameter in the MDGND module didn't match the DMA channel configured for the adapter associated with that module.

9209 Fastmac Plus image file is too big for available memory
This error only applies to MDGND.DOS. The driver failed to allocate enough internal memory to load the MDGND30.BIN file. This indicates a fatal error in the driver: it should never be seen in practice.

9210 Set interrupt number failed
The value for the SetIRQNumber parameter in the MDGND module could not be used for the adapter associated with that module.

9211 Set DMA channel failed
The value for the SetDMAChannel parameter in the MDGND module could not be used for the adapter associated with that module.

9212 MaxSmallBufSize value is larger than RxTxBufSize value
The value for the MaxSmallBufSize parameter in the MDGND module was set to be larger than that for the RxTxBufSize paramerter. This is invalid.

9213 Problem with Fastmac Plus image
The driver discovered that the Fastmac Plus image had an invalid structure. This probably indicates that the file has become corrupted.

9214 Ringnode is not recognised by this driver
The driver found an adapter to associate with the MDGND module, but was not able to initialise the adapter. This indicates a fatal error in the driver: it should never be seen in practice.

9215 Failed to allocate GDT selector for module
This error only applies to MDGND.OS2. OS/2 returned an error to the driver when asked for a GDT. This probably indicates that there is insufficient memory available in the machine.

9216 Failed to allocate GDT selectors for driver
This error only applies to MDGND.OS2. OS/2 returned an error to the driver when asked for a GDT. This probably indicates that there is insufficient memory available in the machine.

9219 * Module was not registered with Protocol Manager
The driver did not register the MDGND module with the Protocol Manager due to the error described in the above error message.

9224 This version of the driver does not support DTRmode
The DTR parameter was set for this MDGND module, but this version driver only supports Classicmode.

9225 The Fastmac Plus image file is not compatible
This error only applies to MDGND.DOS. The version of the MDGND30.BIN file was not compatible with the version of the MDGND.DOS file.

5.1.2 Errors
5075 Adapter
Insufficient memory or system resources was available for the netcard driver to initialise.

5076 Adapter
The adapter hardware/MAC failed to initialise.Check that the adapter card is properly inserted into its slot and that the network cable is connected. If its is an ISA adapter check that the interrupt number, DMA channel and I/O location in the adapter configuration match the settings on the adapter card. (The last two DWORDS of the data section below the message give a detailed error code.) See below for a full description (section 5.3).

5078 Adapter
The netcard driver was not able to connect the adapter card's interrupt. Ensure that the adapter card is properly inserted into its slot. If it is an ISA adapter then check that the interrupt number specified in the adapter configuration matches that set on the adapter card.

5082 Adapter
The adapter could not be opened onto the ring. ensure that the network cable is connected to the adapter and that the token ring is fully connected. Also ensure that all the nodes on your ring are set to the same speed and that all nodes have different addresses.

5083 Adapter
An essential registry parameter is missing for this adapter. For MCA and EISA adapters the registry must contain BusType and SlotNumber parameters. For ISA adapters the registry must contain IO location, interrupt number and DMA channel parameters.

5085 Adapter
Either the file MDGMPORT.BIN is not present in the device drivers directory, the file is of the wrong version or the file is corrupt.

5088 Adapter
A Madge PCI adapter of the specified type was not found or is not present at the PCI Device ID specified.

There will be two values following the AAAAAAAAAA code which detail the reason for the hardware error (section 5.3)

Error Codes 0XC00013D3
Insufficient memory or system resources was available for the network card driver to initialise.

0XC00013D4
The adapter hardware/MAC failed to initialise. Check that the adapter card is properly inserted into its slot and that the network cable is connected. If its is an ISA adapter check that the interrupt number, DMA channel and I/O location in the adapter configuration match the settings on the adapter card.

0X800013D5
The netcard driver could not allocate sufficient memory for transmit and recive buffers. The number of RX and TX slots and the maximum frame size may have been reduced to reduce the amount of memory required.

0XC00013D6
The netcard driver was not able to connect the adapter card's interrupt. ensure that the adapter card is properly inserted into its slot. If it is an ISA adapter then check that the interrupt number specified in the adapter configuration matches that set on the adapter card.

0X800013D7
One of the parameters in the registry entry for this adapter is invalid. If possible a default value will have been used.

0X800013D9
The maximum frame size setting in the registry is too large. The driver has trimmed it down to the maximum allowable setting. (The data section below specifies the actual maximum frame size used in the last DWORD. Replace the value in the registry with this.)

0XC00013DA
The adapter could not be opened onto the ring. Ensure that the network cable is connected to the adapter and that the token ring is fully connected. Also ensure that all the nodes on your ring are set to the same speed and that all nodes have different addresses.

0XC00013DB
An essential registry parameter is missing for this adapter. For MCA and EISA adapters the registry must contain BusType and SlotNumber parameters. For ISA adapters the registry must contain IO Location, interrupt number and DMA channel parameters.

0X800013DC
Either MMIO memory was not assigned or could not be mapped into virtual memory. PIO transfer method is being used instead of MMIO.

0XC00013DD
Either the file MDGMPORT.BIN is not present in the device drivers directory, the file is of the wrong version or the file is corrupt.

0X400013DE
The adapter has opened in classic token ring mode.

0X400013DF
The adapter has opened in DTR (full duplex) mode.

0XC00013E0
A Madge PCI adapter of the specified type was not found or is not present at the PCI Device ID specified.

Category 04; Type 05, 06, or 12
There is not enough memory available to the system for DMA buffers. Reduce the maximum frame size or the number of TX/RX buffers.

Category 05; Type 02
The IO location given is not valid for the adapter card you are using. Check that the IO location in the registry matches the card IO location.

Category 05; Type 03
The interrupt number you have given is not valid for the Ringnode you are using. Check that the interrupt number in the registry matches the card interrupt number.

Category 05; Type 04
Either the DMA channel you have given is not valid for the Ringnode you are using, or you have specified a DMA channel for a Ringnode that is configured to perform PIO. Check that the DMA channel in the registry matches the card DMA setting.

Category 05; Type 05
No adapter card has been found at the IO location you gave. Check that the Ringnode details you gave were correct and that you have installed the Ringnode correctly into your computer.

Category 05; Type 06
You cannot use DMA with your Ringnode in an 8bit slot.

Category 05; Type 0D
The Ringnode has not been enabled. You must configure your EISA or MC Ringnode properly before you use it.

Category 05; Type 0E
You have not selected a Ring Speed (either 16 Mbps or 4Mbps) for your Ringnode.

Category 05; Type 07, 08, or 09
NT has been unable to download your driver software to the Ringnode. Run the Madge Ringnode Diagnostics to see if there is a hardware problem.

Category 05; Type 0B, or 0C
The system has been unable to enable an interrupt (0x0B) or a DMA channel (0x0C). Check that there are no conflicting settings.

Category 06; Type 00, 01, 02, 03, 04, 05, 06, or 10
Your Ringnode could not be initialised. Run the Madge Ringnode Diagnostics to see if there is a hardware problem.

Category 07; Type 09, 0A, 0B, or 0C
Your Ringnode cannot perform DMA transfers properly. Run the Madge Ringnode Diagnostics to see if there is a hardware problem.

8202 * The Smartrom on this ringnode is disabled.
The Smartron must be enabled by using the configuration utility.

8203 * The Smartrom cannot be found in upper memory.
It may be mapped over by a memory manager. This error only occurs on ringnodes with a soldered on Smartrom.

8204 * The Smartrom cannot be found in upper memory.
There is either no Smartrom fitted to this ringnode or it may be mapped over by a memory manager. This error can occur on ringnodes which have a socketed Smartrom.

8205 * The Smartrom cannot be found in upper memory.
There may either be no Smartrom fitted to this ringnode, it may be disabled, or it may be mapped over by a memory manager. To enable the Smartrom change the switch on the ringnode. This error only occurs on the Smart 16/4 AT and PC Ringnodes.

8206 The Smartrom on this ringnode appears to be in an invalid state.
Ensure that the correct device is properly fitted, otherwise contact Madge Technical Support.

8207 No configuration information could be found in the Smartrom.

8208 * There appears to be writeable memory mapped in over the Smartrom.
This may be due to a memory manager. The machine should be rebooted after having reconfigured the memory manager.

8209 Unable to page Smartrom.
Ensure that ROM shadowing is disabled in the BIOS configuration and that a memory manager has not shadowed the Smartrom.

8210 * The Smartrom cannot be found.
There may be no Smartrom fitted to this ringnode. If there is and this error is repeated contact Madge Technical support. This error should only occur on I/O mapped Smartroms (e.g Smart 16/4 PCI (BM)).

8211 * The Smartrom is mapped over by a memory manager.
The machine should be rebooted after having reconfigured the memory manager.

8212 The checksum for the first 8Kb of the Smartrom is incorrect.
Try reprogramming the Smartrom, but if the error is repeated then contact Madge Technical Support.

8301 Failure while reprogramming Smartrom.
If this error is repeated contact Madge Technical Support.

8302 Verification failed.
The Smartrom has NOT programmed successfully. If this error is repeated contact Madge Technical Support.

8303 * The Smartrom has not been reprogrammed as it is already correct

8304 * This ringnode does not support the ROM image file specified.

8305 * The specified ROM image file is not supported.

8306 * Failed to open ROM image file.
Check that it is present in the current directory.

8307 Failed while reading ROM image file.

8308 The ROM image file is too big for the Smartrom.
Use a smaller ROM image file.

8309 Failed to allocate sufficient memory.
Free some memory and try again.

8310 The version of NRPL.ROM does not support the /netware_os2 option.
Use NRPL.ROM v3.10 or later.

8311 This version of ATPLUS.ROM found is not compatible with the Smartrom hardware.
Use ATPLUS.ROM v1.08 or later.

8312 The Smartrom is password protected, but the specified ROM image file does not support password protection.
Either clear the current password using the password utility or use ATPLUS.ROM v1.11 or later.

8313 There is not sufficient room in this ROM image file for the configuration data.
Use the latest ROM image file.

8314 No configuration space was found in the ROM image file.
The image file may be corrupted.

8315 The ROM image file is not valid.
The image file may be corrupted.

E9901 Error initializing Network Interface Board.
The adapter could not initialised and started. Check that the cable is connected.

Error finding server.
Server cannot be found. Check that it is running on the same network.

Opening bootimage on file server . Error opening bootdisk image file.
The specified disk image could not be found. Ensure that it is present in the relevant SYS:\LOGIN directory.

3501 The password you entered is incorrect .
The chosen adapter has been setup with a password to protect its configuration. Enter the correct password or contact your network administrator.

3504 Invalid I/O address.
An I/O address was entered that was out of range for the specified adapter type.

3505 Invalid decimal number.
A bad character was found in a decimal string.

3506 An internal error has been detected contact Madge technical support. The configuration has not been altered.
This indicates that an unsafe configuration has been onstructed. This error message is also printed with the error codes 3507, 3508, 3509, and 350A.

350B Invalid INT channel.
An interrupt channel (IRQ) was entered that was out of range for the specified adapter type.

350D Invalid transfer mode.
The chosen data transfer mode is inappropriate for the adapter.

350E Invalid DMA channel.
A DMA channel was entered that was out of range for the specified adapter type.

350F Invalid MEMORY base address.
The start address (used for the start of a ROM) was entered that was out of range for the specified adapter type.

3512 The SERIAL EEPROM failed to complete a write request . The configuration information is held in a read/write device on the card. This error indicates that the utility was unable to write to that device.

3513 A check read of the SERIAL EEPROM failed .
The configuration information is held in a read/write device on the card. This error indicates that the utility was able to write to that device but the data read back as a check did not match that written.

3514 No ringnodes found : This software is applicable only to SMART 16/4 AT Plus, ISA Client Plus Ringnodes PCI, PCMCIA, and ISA PnP Ringnodes.

3515 The adapter you specified (SLOT n) does not exist.
You chose an adapter by specifying an invalid slot number (n).

3516 The adapter you specified (SLOT = n, SUBPORT = e) does not exist.
You chose an adapter by specifying an invalid slot number (n) and/or invalid subport number (e).

3517 The adapter you specified (at I/O address hhhh) does not exist.
You chose an adapter by specifying an invalid IO address (hhhh).

351A Invalid hex parameter value.
A bad character was found in a hexadecimal string.

351B Invalid decimal parameter value.
A bad character was found in a decimal string.

351C Decimal parameter value is too big.

351D Hex string is odd length.
Hexadecimal strings are always expected to have an even number of digits.

351F Hex byte string is too long.

3520 Hex byte string is too short.

3521 The adapter you specified cannot support BUS MASTER DMA .
ISA Client Plus cards and some other cards cannot support DMA.

3522 The /ASYNCH and /SYNCH switches are not appropriate for this adapter .
These switches apply only to cards that support DMA.

3540 This utility has detected that a network adapter is running. If you continue then any network connections may be lost.
In an OS/2 environment it is not possible to access adapters that are running network software without reseting the card this will cause existing network applications to fail. You can continue if you wish or you may choose to shut down any critical applications and then rerun this utility.

3541 The I/O address you have specified seems to be in use .

3542 The IRQ channel you have specified seems to be in use .

3543 The DMA channel you have specified seems to be in use .

3544 The DMA channel used by the chosen transfer method seems to be in use by another adapter.
Use option 'L' to alter the DMA channel, or use a different transfer method.

3545 The MEMORY base address you have specified seems to be in use.

3547 You have specified a ringspeed that does not match the value detected earlier by this utility. The network may hang if the adapter is opened at the wrong speed.
You have specified that this utility should detect the ringspeed of the network that the adapter is connected to. However, you have changed the ringspeed to one that does not match the detected value.

3548 The adapter you specified (at I/O address hhhh) could not be found .
You have specified that this utility should detect the ringspeed of the network that the adapter is connected to. However, for some reason the card was not accessible to the detection subsystem at an I/O address of "hhhh".

354A Unable to open adapter This may be because it is not connected to a network.
You have specified that this utility should detect the ringspeed of the network that the adapter is connected to. However, the adapter could not be opened onto the network. This may be due to a cabling fault.

354B Cannot determine the ring speed as this appears to be the only adapter on this ring.
You have specified that this utility should detect the ringspeed of the network that the adapter is connected to. However, since the card is the only one on the ring it is detecting its own ring speed rather than the speed of other nodes already on the ring. This may indicate a cabling fault or that the adapter is "wrapped" at the hub.

354C This adapter does not support the detection of ring speed.

354D Cannot determine the ring speed as the adapter is running driver software.
You have specified that this utility should detect the ringspeed of the network that the adapter is connected to. However, since the adapter is running any attempt to determine the ringspeed may cause the adapter to loose any network connections.

354F The setting of the IO ADDRESS switches do not match the new configuration.
To avoid confusion we recommend that you alter the switch settings and/or rerun this utility to correct the mismatch.

3551 The setting of the RING SPEED switch does not match the new configuration. To avoid confusion we strongly recommend that you either alter the switch settings and/or rerun this utility to correct the mismatch.
Note that Software configuration of Ring Speed requires drivers from LAN Support Software 4.2 or later. Driver software prior to this will use the RING SPEED switch and NOT the configured speed.

3552 The selected configuration of Smartrom, DMA transfer mode and 8 bit mode is not available on this adapter. The transfer mode has been changed to PIO to ensure correct operation.

3553 DMA channel 5 (the default used by the chosen transfer method) seems to be in use by another adapter.
Use the /DMA= switch to override the default channel.

3554 The DMA channel used by the chosen transfer method seems to be in use by another adapter .
Use option 'L' to alter the DMA channel, or use a different transfer method.

Invalid ram size.
The parameter specifying the ram size is incorrect.

Invalid I/O location.
The parameter specifying the io location is incorrect.

Invalid Slot number.
The parameter specifying the slot number is incorrect.

Invalid parameters.
A unrecognised parameter has been specified.

No report file specified.

8442 This ringnode does not support Smart 16/4 AT compatible mode.

8443 This ringnode may be faulty. Run diagnostics.

8445 Failed to write the new mode to the ringnode.

2721 MADGECS has already been installed.

2722 MADGECS was not installed, since Card Services software was detected.

2723 MADGECS was not installed since the present Socket Services reports no PCMCIA socket controllers.

2724 MADGECS was not installed as the Socket Services software present was not a known version.

2725 MADGECS was not installed as no Socket Services implementation was present.
Use a Card Services and a Socket Services implementation (or just a Socket Services implementation suitable for the PCMCIA controller in this machine. (Support for some PCMCIA controllers can be provided by MADGECS using internal Socket Services emulations. To utilise this facility, place 'EMULATE_SOCKET_SERVICES=YES' (which can be abbreviated to 'ESS=Y') in MADGECS.CFG, and put '/CFG=&It;path of MADGECS.CFG file > MADGECS.CFG' on the MADGECS command line if MADGECS.CFG did not previously exist.)

2726 The PCMCIA controller is unknown or not present.
An Intel compatible controller was expected. Use a Card Services implementation suitable for the PCMCIA controller in this machine.

2727 Failed to open file < configuration file name specified >. Default settings will be used.

2728 Failed to open file <configuration file name specified>.

2729 < configuration file name specified > is too long.

2730 At least one interrupt is required for MADGECS to function.

2731 The list of available IO locations is empty.

2732 At least 4Kbytes of contiguous memory, on a 4Kbyte boundary are required for MADGECS to function.

2733 Unknown text.

2734 Invalid keyword.

2735 '=' missing.

2736 Value missing.

2737 Expected 'Y' or 'N'.

2738 Expected a number.

2739 Interrupt number out of range.

2740 Expected a hexadecimal number.

2741 List of interrupt numbers is full.

2742 List of IO locations is full.

2743 List of memory locations is full.

2744 Unknown option.

2745 Option appears twice.

2746 '=' missing.

2747 Unknown text.

2748 Filename missing.

2749 Filename too long.

2750 '' expected.

2751 Invalid memory range.

2752 Unable to obtain GDT selector from OS/2.
This indicates a serious lack of memory resources under OS/2, and should never occur.

2753 Unable to unload since the MADGECS found is an old version.

2754 Unable to unload since another TSR program has been loaded since MADGECS. This TSR program must be unloaded before MADGECS can be unloaded.

2756 Unload failed.

2757 Expected 'ALWAYS', 'ONLY_ON_LOAD' or 'NEVER'.

2758 Illegal slot number.

2759 Too many slots specified.

2770 No Ringnodes have been configured.

2772 MADGECS requires that the list of memory ranges (shown above) should only contain memory ranges that are not being used by memory managers. The following list entries do not comply with this requirement: .
The memory ranges used can be changed by use of a MADGECS.CFG file. Alternatively, the command line for the memory manager being used could be modified. For example, if using EMM386.EXE from CONFIG.SYS, the option <e.g. X=CC00C1FF> should be added.

2773 All slots have been excluded.

2774 The list of interrupts to use contains both interrupt 2 and interrupt 9.
These interrupts are just different names for the same interrupt, and hence should not both be in the list. Change the MADGECS configuration file to avoid this.