25.0 IDEATA.HAM Messages

The following includes messages from the IDEATA.HAM.

IDEATA.HAM–001: This driver is not compatible with the detected bus type

Source: IDEATA.HAM
Possible Cause: The driver did not load because the hardware bus type of the server is incompatible with the bus type the driver was designed to support. The IDEATA.HAM driver supports IDE/ATA controller cards designed to work on ISA/EISA machines.
Action: Use a controller card and compatible .ham driver appropriate for the server’s I/O bus.

IDEATA.HAM–003: Insufficient memory to register the object

Source: IDEATA.HAM
Possible Cause: The driver failed to load because there was insufficient memory for the .ham driver to create the objects necessary to support the controller and attached devices.
Action: Unload any unnecessary NLM™ programs and try to reload the driver.

IDEATA.HAM–004: Could not load reentrantly

Source: IDEATA.HAM
Possible Cause: The attempt to load the driver reentrantly failed because the driver was unable to complete reentrant module registration with the NWPA.
Action: Unload any unnecessary .cdm and .ham drivers and try to reload the driver.

IDEATA.HAM–005: Exceeded the number of allowed load instances

Source: IDEATA.HAM
Explanation: This informational message means that you tried to load the .ham driver more times than allowed. The IDEATA.HAM driver can be loaded four times, which corresponds to the number of I/O channels currently supported in the IDE/ATA specification.

IDEATA.HAM–006: Insufficient memory to allocate during initialization

Source: IDEATA.HAM
Possible Cause: There is insufficient memory to load and run the driver.
Action: Unload any unnecessary NLM programs and try to reload the driver.

IDEATA.HAM–007: Invalid NWPA handle

Source: IDEATA.HAM
Possible Cause: The driver is being passed a bad handle from the NWPA.
Action: Contact Novell Technical Support.

IDEATA.HAM–008: None of the parameters matched the known resources

Source: IDEATA.HAM
Possible Cause: The load instance failed because the necessary hardware resources (port and interrupt values) for configuring the .ham driver were not specified on the command line.
Action: Reload the driver and specify the appropriate hardware resources.

IDEATA.HAM–009: Device not found at the specified port address

Source: IDEATA.HAM
Possible Cause: The driver failed to load because it did not detect any devices at the specified port address.
Action: Determine the correct port address and reload the driver using this value.

IDEATA.HAM–010: Load failed due to hardware resource conflict

Source: IDEATA.HAM
Possible Cause: The driver could not be loaded because some other driver has reserved one or all of the hardware resources (port or interrupt) specified for this driver.
Action: Resolve the resource conflict between the competing controllers and reload the driver.

IDEATA.HAM–011: I/O channel registration failed

Source: IDEATA.HAM
Possible Cause: The driver failed to load because channel registration with the server failed.
Action: Unload any unnecessary .cdm and .ham drivers, then reload the driver.

IDEATA.HAM–012: Memory allocation error. The driver was unable to allocate an IO buffer to scan PCI configuration space. The driver needs to scan configuration space to avoid unsupported controllers.

Source: IDEATA.HAM
Possible Cause: There is insufficient memory to load the driver.
Action: Unload any unnecessary NLM programs and try to reload the driver.

IDEATA.HAM–013: A CMD CSA640B ATA/IDE controller is present, so only a single IDE channel will be supported. Please ensure all IDE devices are attached to the same channel prior to loading the driver.

Source: IDEATA.HAM
Explanation: This is a warning message that the driver cannot be loaded more than once because it detected the presence of a CMD CSA640B controller, which only allows communication with one of its channels safely in NetWare.
Action: Be sure all IDE devices are attached to the same channel, then reload the server and drivers.