User`s guide

MBX Driver Help
Cyberlogic Technologies Inc. - 105 -
Adapter card ID for <device name> in selected slot does not match the
expected card ID.
Invalid configuration parameter. MCA adapter cards, such as SM85 and MC984, have
unique ID codes used to identify them. The card inserted in the specified MCA slot does
not match the expected card ID.
Adapter card initialization for <device name> failed. The AIDA command
<command name> timed-out. Please contact technical support of
manufacturer for more assistance.
The PCMCIA 416NHM21234 card failed its initialization sequence. This may indicate a
faulty card or a compatibility problem with your computer’s PCMCIA controller
chip/device driver. Contact the board manufacturer’s technical support for more
information on a possible solution.
Adapter card initialization for <device name> failed. Received tuple code
<received code>. Expected to receive <expected code>. Please contact
technical support of manufacturer for more assistance.
The PCMCIA 416NHM21234 card failed its initialization sequence. This may indicate a
faulty card or a compatibility problem with your computer’s PCMCIA controller
chip/device driver. Contact the board manufacturer’s technical support for more
information on a possible solution.
Adapter card's dual-port memory diagnostics for <device name> at selected
memory address failed (Pattern 0x<hex value>). Check the selected memory
range for the card and make sure that the card is plugged in. Also, check
Resources under Windows NT Diagnostics for possible conflicts with other
devices in the system. Try another adapter card.
May indicate a faulty card.
Adapter card's interface diagnostics for <device name> failed (Pattern
0x<hex value>). Check the selected memory range for the card and make
sure that the card is plugged in. Also, check Resources under Windows NT
Diagnostics for possible conflicts with other devices in the system. Try another
adapter card.
May indicate a faulty card.
Connecting ISR routine to selected interrupt line for <device name> failed.
Some device driver in the system did not report it's resource usage. Try to
remove some questionable drivers from the system and restart this driver. You
may also select another interrupt line.
Unreported interrupt already used by another device driver.
Hardware resources allocation for device <device name> failed. Check
Resources under Windows NT Diagnostics for possible conflicts with other