Novell NETWARE 6-DOCUMENTATION Manual page 3350

NWCONFIG-X-304: A physical device or partition in the set you selected is no longer
valid.
Source:
Explanation:
Action:
NWCONFIG-X-305: Driver name was successfully loaded but not bound to any
protocol stacks. Press Enter to continue.
Source:
Action:
NWCONFIG-X-306: Driver name could not be loaded because command file name
could not be created. Load this driver manually from the system console.
Source:
Explanation:
Action:
NWCONFIG-X-307: Driver name could not be loaded because command file name
could not be written. Load this driver manually from the system console.
Source:
Explanation:
Action:
NWCONFIG-X-308: No disk driver files (*.DSK, *.HAM, *.CDM) were found at this path.
Source:
Explanation:
NWCONFIG.NLM
The device might have been powered off or in some other way made invisible
to NWCONFIG.
Correct the problem and retry the operation.
NWCONFIG.NLM
To bind the driver to a protocol stack, switch to the system console screen and
use the BIND command.
NWCONFIG.NLM
Normally, the program automatically creates this file with the command
parameters in it, and command parameters are read from this file. However,
the LOAD command you entered was too long (over 200 characters), so you
will have to enter the command manually.
Type LOAD driver_name parameters at the system console screen.
NWCONFIG.NLM
Normally, the program automatically creates this file with the command
parameters in it, and command parameters are read from this file. However,
the LOAD command you entered was too long (over 200 characters), so you
will have to enter the command manually.
Enter LOAD driver_name parameters at the system console screen.
NWCONFIG.NLM
The indicated files were not found at this location.
NWCONFIG Messages 399