This page describes Madge LAN Support Software error codes. It consists of the following sections:
The following errors are general to all components of this LSS release. Where applicable, these are also common to previous LSS drivers.
0100 "The
adapter found is not supported by this software"
The adapter specified is not supported. Use a driver from a previous Madge
software release.
0101 "The
adapter switches have been moved since the adapter was last software-configured,
and hence is currently disabled. Run
the software configuration program on the adapter to correct this"
This only applies to Smart 16/4 AT Plus and ISA Client Plus Ringnodes,
where the switches have been moved since the last time the adapter was
programmed.
0103 "The
adapter's soft configuration has become corrupt. Reconfigure the adapter"
This only applies to EISA adapters. To correct the fault, run the EISA
configuration program.
0104 "Only DMA is supported on this adapter. Reconfigure the adapter so that the 'arbitration level' is not 'disabled', to allow DMA to be used"
This only applies to Smart 16/4 MC and MC32 Ringnodes. Run the ADF
configuration utility to change the arbitration level from 15 (disabled).
0110 "Access
to adapter IO region refused by operating system"
The driver could not register an I/O region.
0111 "Access
to RAM region refused by operating system"
The driver could not register an adapter RAM region.
0112 "Access
to PCI configuration space refused by operating system"
The driver could not register the PCI configuration space.
0116 "Adapter
code file is corrupt"
The type of an adapter code image was incorrect. This means that the reading
has failed in some way, or that the image is corrupt, or that it is download
code for another type of adapter which has been erroneously read in -
e.g. because the user has renamed it.
0117 "Wrong
version of adapter code file"
The version of an adapter code image was incorrect.
0118 "Adapter
code file is corrupt"
The contents of an adapter code image were invalid.
0120 "Invalid
IO location"
An error has been detected with the I/O discovered. e.g. an invalid value
from PCI.
0121 "Invalid
IRQ"
An error has been detected with the IRQ discovered.
0122 "Invalid
BIA"
An error has been detected in the BIA discovered.
0140 "The
adapter has failed to initialise"
The adapter failed initialisation.
0141 "Timed
out waiting for response from adapter"
The host timed out waiting for the adapter to process a command. This usually
occurs during initialisation.
0145 "Failed
to open adapter"
The adapter failed to open on to the token ring network. Check the cabling,
ring speed and status of the network before retrying.
0160-0167 "Bring
up diagnostics failed"
The adapter's self-test failed or the test of data transfer between the
adapter and the host computer failed.
0168 "Bring
up diagnostics timed out without a specific error being reported"
The Bring Up Diagnostics timed out without any specific error being reported
by the adapter.
0170 "Insufficient
adapter RAM for code and data"
There is not enough adapter RAM to hold the download image and necessary
data.
0171 "Checksum
failed on data transferred to adapter"
A check of the data transferred to the adapter failed. This generally means
that the adapter is not compatible with the computer.
1003 "No
adapter at specified I/O location"
No adapter was found at the I/O location specified. Either there is no
adapter at this location or there is an adapter but it is failing to respond
correctly, perhaps due to an I/O clash with another device.
1004 "No
adapter or incorrect type"
No adapter was found. Either there are no supported adapters in the machine
or the adapter is present but not responding correctly (it may be incorrectly
configured).
1005 "Invalid
interrupt number specified"
An interrupt number override was specified but the adapter could not be
forced to use that interrupt.
1006 "Invalid
DMA channel specified"
A DMA channel override was specified but the adapter could not be forced
to use that channel.
1007 "No
interrupt number has been configured for this MC adapter."
Interrupts are disabled on an MC adapter. You must configure it.
1009 "No adapter with specified I/O location and slot"
An adapter was found at the specified I/O location but was not at the specified slot.
1012 "Invalid
memory range specified"
The specified MMIO/Shared RAM location override is invalid.
1017 "Adapter
has not had its ringspeed configured"
Adapter has no ring speed configured. Only possible for EISA and ISA Client
PnP Ringnodes.
1020 "No
adapter at specified slot"
No adapter was found at the specified slot. Either there is no adapter
at this slot or there is an adapter but it is failing to respond correctly.
1027 "Unable
to obtain an IO location from Card Services"
Request for an I/O window from Card Services failed. This means that the
Card Services implementation being used does not have a sufficiently large
span of I/O space in its list of resources. Card Services will need to
be reconfigured to allow use of more IO space. If an I/O location has
been specified then this error means that Card Services does not have
that I/O location available for use in its list of resources.
1028 "Unable
to obtain an IRQ from Card Services"
Request for an IRQ from Card Services failed. This means that the Card
Services implementation being used does not have a suitable IRQ in its
list of resources. Card Services will need to be reconfigured to allow
use of more IRQs space. If an IRQ has been specified then this error means
that Card Services
does not have that IRQ available for use in its list of resources.
1029 "Failed
to configure card using Card Services"
Card Services failed to configure the adapter.
1036 "Failed
to download code to the adapter"
Failed to verify download code. On Smart adapters, the download is written
to the adapter and read back to verify that it was written correctly.
This error occurs when the data read back is different from that written.
It usually means that the adapter could not be accessed correctly through
I/O space, usually because of an I/O clash with another device. It may
mean that the adapter memory is faulty.
1037 "No
adapter with specified burnt-in address"
No adapter was found with the specified burnt-in address. Either there
is no adapter with a matching BIA or there is an adapter but it is failing
to respond correctly, perhaps due to an I/O location clash with another
device.
1038 "No
adapter at specified I/O location with specified burnt-in address"
An adapter was found at the specified I/O location but did not have the
specified burnt-in address.
1042 "No
adapter at specified slot with specified burnt-in address"
An adapter was found at the specified slot but did not have the specified
burnt-in address.
1112 "Initialization
failed - transfer test failed"
Initialization test transfers failed. The data written by the adapter to
the host is incorrect. This may indicate a data transfer problem.
1113 "Initialization
timed-out - possible interrupt clash"
Adapter initialization timed-out. This error is often caused by an interrupt
clash with another device.
1114-1128 "Initialisation
error"
These are the errors which can be reported on Smart Ringnodes during initialisation.
In practice, the only likely error is 0x1125, which indicates that the
DMA data copied to the host and copied back was lost en route, not returning
intact to the adapter.
1130 "Open
failed - lobe cable fault"
Adapter failed to open due to a lobe cable fault. Ensure that the lobe
cable is securely attached to the adapter and hub.
1131 "Open
failed - duplicate node address"
Adapter failed to open because it failed the duplicate node address test.
This happens if another adapter is currently open on the ring with the
same locally administered address (LAA) as this adapter. Change the adapter's
LAA.
1139 "Open
failed - run diagnostics"
Adapter failed to open. Run adapter diagnostics to identify the problem.
1200 "No
matching adapter found"
An adapter was found but does not match the specifications given. For example,
an adapter may have been located at the specified I/O location but did
not have the specified burnt-in address.
1201 "Initialization
failed - run diagnostics"
Adapter failed to initialize. Run adapter diagnostics to identify the problem.
1202 "This
program does not operate correctly with early versions of memory
manager software (e.g. EMM386). Such a version has been detected. Please
upgrade your memory manager. For example, if you are using EMM386.EXE,
please change to the EMM386.EXE which was supplied with MSDOS 6.22 (or
any later version)."
The following errors are specific to the 32-bit ODI driver, CMDGODI.LAN.
2000 "Miscellaneous
error during initialization"
A miscellaneous error occurred during adapter initialization.
2003 "Failed
to register MLID with LSL"
The driver failed to register itself with the LSL.
2007 "Failed
to allocate memory"
The driver failed to allocate memory.
2012 "Failed
to enable interrupt"
The call to the MSM to enable the adapter's interrupt failed.
2035 "Failed
to determine adapter configuration"
The driver failed to determine the adapter configuration.
2036 "Failed
to allocate RCBs"
The driver failed to obtain the required number of RCBs from the MSM.
2040 "Mirroring
is only supported on NetWare servers"
Mirroring is only supported on a server.
2041 "The
specified mirror slave adapter is not available"
There is no such adapter available to be a mirror standby.
2042 "A
node address override (LAA) must be given when using mirroring"
An LAA must be specified when using adapter mirroring.
2043 "The
version of MSM.NLM loaded is incompatible with mirroring"
The MSM is incompatible with mirroring.
2044 "The
specified master adapter does not support mirroring"
The selected master adapter does not support mirroring.
2045 "The
specified slave adapter does not support mirroring"
The selected slave adapter does not support mirroring.
The following errors are specific to the IFADAP conditional device driver loading utility for DOS.
<no code>
"No device driver specified."
See IFADAP.TXT for description of how to use IFADAP in CONFIG.SYS.
<no code>
"No card type specified."
See IFADAP.TXT for description of how to use IFADAP.
<no code>
"Invalid card type."
The parameter specifying the adapter type is incorrect.
<no code>
"Invalid ram size."
The parameter specifying the RAM size is incorrect.
<no code>
"Invalid I/O location."
The parameter specifying the I/O location is incorrect.
<no code>
"Invalid Slot number."
The parameter specifying the slot number is incorrect.
<no code>
"Invalid parameters."
A unrecognized parameter has been specified.
<no code>
"No report file specified."
See IFADAP.TXT for description of how to use IFADAP.
The following errors are specific to the Madge Card Services driver, MADGECS.EXE.
2720 "Unloading failed since MADGECS could not be found."
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 socket controllers."
2724 "MADGECS was not installed as the Socket Services software present was not a known version."
2725 "MADGECS
was not installed, because 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 or CardBus controller
in this machine. Support for some controllers can be provided by MADGECS
using an internal Socket Services emulation. To use this facility, place
'EMULATE_SOCKET_SERVICES=YES' (which can be abbreviated to 'ESS=Y') in
MADGECS.CFG, and put '/CFG=<path of MADGECS.CFG file>MADGECS.CFG'
on the MADGECS command line if MADGECS.CFG did not previously exist."
2726 "MADGECS
was unable to find any PCMCIA or CardBus controllers."
MADGECS
only provides Socket Services emulation for Intel compatible PCMCIA controllers
and TI-1130, TI-1131, Toshiba TOPIC95, and Cirrus CL-PD6832 CardBus controllers.
If there is any other type of controller in this machine, then you will
need to load an appropriate Socket Services before MADGECS.
2727 "Failed
to open file <configuration file name specified>. Default settings will
be used."
Te specified configuration file could not be found, or could not be opened.
If it is not in the same directory as MADGECS then ensure a full path
is given.
2728 "Failed
to read file <configuration file name specified>."
The configuration file was found but an error occurred during the reading
of it.
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. It must be unloaded before MADGECS can be unloaded."
2755 "Unable to unload since another TSR program has been loaded since MADGECS. It must be unloaded before MADGECS can be unloaded."
2756 "Unloading 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: <list of memory ranges e.g. CC00-C1FF>. 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=CC00-C1FF> 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. Please change the MADGECS configuration file to avoid this."
2775 "A
Vadem PCMCIA controller was found that is not supported by MADGECS."
If you wish to use MADGECS, you will need to use a Socket Services for
this Vadem controller.
2779 "Invalid IO range."
2780 "Bad
range."
The end of the range must be equal to or larger than the start of the range.
2781 "A 4K-aligned, 4K long block of memory is required for Socket Services. There is no such range in the list of memory ranges to use. An example 4K range is D200-D2FF. Change the MADGECS configuration file to rectify this."
2782 "This version of MADGECS is a 32-bit program and requires at least an 80386 processor. To use MADGECS with an 80286 or earlier processor, use MADGECS version 1.21 or earlier. However, none of these earlier versions of MADGECS have CardBus support."
2783 "Cannot
have 'ONLY_PCMCIA' and 'ONLY_CARD_BUS'."
Both options were specified in the MADGECS configuration file. Remove one
of them.
2784 "Unable to use Socket Services. The version of Socket Services found does not support enough I/O bridge windows of the correct type to allow one window per CardBus socket. Either upgrade your Socket Services, or, if the PCMCIA controller in this machine is supported by MADGECS stop using Socket Services, and add 'EMUALTE_SOCKET_SERVICES= YES' to MADGECS.CFG."
2785 "Unable to use Socket Services. The version of Socket Services found does not support enough memory bridge windows of the correct type to allow one window per CardBus socket. Either upgrade your Socket Services, or, if the PCMCIA controller in this machine is supported by MADGECS stop using Socket Services, and add 'EMUALTE_SOCKET_SERVICES=YES' to MADGECS.CFG."
2786 "The
CardBus controller has not been assigned legal bus numbers by the
BIOS."
This indicates a lack of support for CardBus controllers in the BIOS. A
BIOS upgrade should be available if the machine has a built in CardBus
controller. If a plug-in CardBus controller is being used, then there
should have been some controller initialisation software supplied with
it which can be run before MADGECS, to assign bus numbers to the controller's
sockets.
2787 "The
CardBus controller has not been assigned a legal IRQ number by the
BIOS."
This indicates a lack of support for CardBus controllers in the BIOS. A
BIOS upgrade should be available if the machine has a built in CardBus
controller. If a plug-in CardBus controller is being used, then there
should have been some controller initialisation software supplied with
it which can be run before MADGECS, to assign IRQ numbers to the controller's
sockets.
2788 "Unable
to get required voltage codes from Socket Services"
This error indicates a problem with the Socket Services being used. If
it is not possible to obtain a newer version of Socket Services, then
you must either let MADGECS emulate socket services, or not use MADGECS
at all.
2789 "Socket
Services has specified more than one level mode interrupt for a
CardBus socket."
This error may indicate a problem with the Socket Services being used.
If it is not possible to obtain a newer version of Socket Services, then
you must either let MADGECS emulate socket services, or not use MADGECS
at all.
2790 "Socket
Services has unexpectedly reported an error."
This error may indicate a problem with the Socket Services being used.
If it is not possible to obtain a newer version of Socket Services, then
you must either let MADGECS emulate socket services, or not use MADGECS
at all.
The following errors are specific to the Madge DOS Token-Ring Adapter Test * Utility, TRTEST.EXE.
8400 "Invalid command line options"
8401 "Unknown
option"
For a list of options, put ? on the command line.
8402 "'=' required after option"
8403 "Option requires numeric value"
8404 "Only one slot may be specified"
8405 "Only one IO address may be specified"
8406 "Only one node address may be specified"
8407 "Only one ringspeed may be specified"
8408 "Invalid slot number"
8409 "Invalid value"
8410 "One must specify 'fixed', 'incremental', or 'random' frame sizes"
8411 "Frame size (in bytes) required"
8412 "Invalid frame size (the maximum is <number>; the minimum <number>)"
8413 "Invalid duration type - require one of 'seconds', 'minutes', etc"
8414 "Require duration type - one of 'seconds', 'minutes', etc"
8415 "Require frame length (in bytes). E.g. 'transmit = fixed 4000'"
8416 "Require frame length (in bytes). E.g. 'transmit = incremental 4000'"
8417 "Require frame length (in bytes). E.g. 'transmit = random 4000'"
8418 "Invalid ringspeed (use 4, 16 or 100)"
8421 "Invalid frame length selected"
8422 "Invalid duration selected"
8423 "Invalid destination selected"
8424 "Because one or more adapters are running at 4Mbps, the frame size is restricted to 4486 bytes, so the length of transmitted frames must be reduced to run the test"
8430 "Unable to obtain full adapter details"
8431 "The adapter's shared RAM region is being used by a memory manager"
8432 "Insufficient RAM for adapter"
8433 "Insufficient RAM for transmit and receive buffers"
8438 "Test aborted"
8440 "Opened single station"
8441 "Too many frames lost"
8442 "Adapter closed unexpectedly"
8443 "Adapter halted"
8444 "The adapter has been ejected"
8445 "The adapter has been removed from the ring"
8446 "Trtest is not able to test an adapter which has software running on it"
8447 "It is not possible to run the stand-alone test at 100Mbps. Either use a different ringspeed or use a connection test"
8448 "Unable to locate a TRTEST server on the network"
8449 "To send frames to the found server, source routing information is required. The specified frame size (n bytes) is too small, and should increased to at least m bytes"
8450 "The specified frame size (n bytes) is too large for 4Mbps operation and should be decreased to m bytes or less"
8451 "The specified frame size (n bytes) is too large for the source routing connection that has been established to the server, and should be decreased to m bytes or less"
8452 "Adapter details specified on the command line matched different adapters, but only one adapter can be chosen"
The following messages are specific to the Madge Miniport drivers, * MDGMPORT.SYS, MDGNDIS4.SYS and MDGNDIS5.SYS.
Each error has two corresponding codes, the 8-digit code is displayed by Windows 95, the 4-digit code by Windows NT/2000 in the event log.
For the 8-digit Windows 95 codes, the first digit indicates the severity of the message:
Numbers starting '4' are purely informational
Numbers starting '8' are warnings
Numbers starting 'C' are errors
C00013D3 / 5075 "A Madge PCI adapter of the specified type was not found or is not present at the PCI Device ID specified. The last DWORD in the data section below contains the specified PCI device ID."
C00013D4 / 5076 "PCI resources could not be allocated for the PCI adapter at the PCI Device ID specified. The last DWORD in the data section below contains the specified PCI device ID."
C00013D5 / 5077 "An I/O location required by the adapter could not be registered. This usually means that the I/O location is already in use by some other device. The last DWORD in the data section below contains the I/O location that could not be registered."
C00013D6 / 5078 "An interrupt required by the adapter could not be registered. This usually means that the interrupt is already in use by some other device. The last DWORD in the data section below contains the interrupt that could not be registered."
800013D7 /5079 "An invalid transfer type has been specified for the adapter. The adapter will be started using 16 bit PIO."
C00013D8 / 5080 "An invalid transfer type has been specified for the adapter and the adapter cannot be started."
C00013D9 / 5081 "There is insufficient memory available to allocate transfer buffers. Try reducing the maximum frame size and/or the number of RX and TX slots"
C00013DA / 5082 "A region of physical memory required for access to the adapter could not be mapped into virtual memory. This usually means that some other device is trying to map the same physical memory. The last DWORD in the data section below contains the physical memory address that could not be mapped."
C00013DB / 5083 "An internal error has occurred. The last three DWORDs in the data section below contain an error code that should be passed to Madge Technical Support."
C00013DC / 5084"Cannot read the registry."
800013DD / 5085 "A parameter in the registry does not have a valid value. The default value for the parameter has been used instead."
C00013DE / 5086 "The adapter could not open onto the ring. Please ensure that the lobe cable is properly attached, that any LAA set is unique and that the your adapter is configured to run at the correct ring speed. Please note that 100MBit/s Token-Ring (HSTR) can only operate in DTR (full duplex) mode."
800013DF / 5087 "The adapter has crashed and will be reset."
400013E0 / 5088 "The adapter has opened in classic token ring mode."
400013E1 / 5089 "The adapter has opened in DTR (full duplex) mode."
800013E2 "The adapter has closed - probably because the lobe cable has
5090 been removed."
400013E3 / 5091 "The adapter has opened in single station mode."
800013E4 / 5092 "The adapter has been sent a MAC remove frame and de-inserted from the ring."
800013E5 / 5093 "The adapter has failed the lobe wrap test due to a beacon and de-inserted from the ring."
800013E6 / 5094 "The adapter has detected a problem with the lobe cable."
800013E7 / 5095"The adapter is transmitting beacon frames onto the ring."
800013E8 / 5096 "The adapter has received a hard error."
800013E9 / 5097 "The adapter has detected a loss of signal on the ring."
800013EA / 5098 "The adapter has been reset by one of the protocols."
C00013EB / 5099 "A Madge adapter cannot be found at the I/O location or PCI slot number specified in the register."
C00013EC / 5100 "The I/O location or PCI or slot number specified in the registry is not valid."
C00013ED / 5101 "The adapter failed to initialise. Please run Madge Assist to try and identify any hardware problems. If this is not successfully please report this error and the three DWORDs at the end of the data section below to Madge Technical support."
C00013EE / 5102 "A command issued to the adapter did not complete within the timeout period. This is usually due to an interrupt clash with another device."
C00013EF / 5103 "The adapter has not been properly configured. If it is an EISA adapter please run the EISA configuration utility. Otherwise run Madge Assist."
C00013F0 / 5104 "The adapter has failed to go into Wake-On-LAN mode."
800013F1 / 5105 "The adapter does not support Wake-On-LAN mode or auxiliary power is not available."
5120 "A mirror slave adapter has been successfully installed for this master adapter. In the event of a problem with the master adapter, the driver will automatically switch to using the slave."
5121 "A slave adapter has NOT been installed for this adapter. Either the master and slave adapters are not of the same type or they don't support mirroring (refer to the driver documentation for more details)"
5122 "A slave adapter has NOT been installed for this adapter. A locally administered node address (LAA) has not been specified."
5123 - "The adapter has successfully undergone a mirror switch due to a ring beacon timeout."
5124 "The adapter has successfully undergone a mirror switch due to a single-station timeout."
5125 "The adapter has successfully undergone a mirror switch due to a bad ring status."
5126 "The adapter has successfully undergone a mirror switch due to the adapter closing."
5127 "The adapter has successfully undergone a mirror switch due to the adapter failing."
5128 "The adapter has successfully undergone a mirror switch due to a user request."
5129 "The adapter has successfully undergone a mirror switch after a previous switch failed."
5130 "The adapter has attempted a mirror switch but the Slave adapter failed to start. Check that the Slave adapter is correctly installed and has its cable attached."
5140 "The internal CardBus enabler successfully configured an adapter. The socket number, IO location and interrupt number are given in the last three dwords of the data below."
5141 "The internal CardBus enabler failed to find any supported CardBus controllers in the machine."
5142 "The internal CardBus enabler failed to find an adapter to enable. Check that the adapter is properly inserted."
5143 "The internal CardBus enabler failed to configure the machine's CardBus controller."
5144 "The internal CardBus enabler failed to find a free interrupt for the adapter to use."
5145 "The internal CardBus enabler has determined that the interrupt selected for the adapter is not available. Select a different interrupt using the adapter properties from the Network dialog."
See Also: