23.0 HDETECT Messages
The following includes messages from the HDETECT.NLM.
A file copy error occurred. Error: code.
Source:
HDETECT.NLM
Possible Cause:
The server ran out of disk space, or the hard disk failed.
Action:
Verify that the server has enough disk space (a 50MB DOS partition) and that the hard disk is functional. For information about a specific error code, search the Error Codes online documentation.
A write error occurred on file filename. Error: code.
Source:
HDETECT.NLM
Possible Cause:
The server ran out of disk space, or the hard disk failed.
Action:
Verify that the server has enough disk space (a 50MB DOS partition) and that the hard disk is functional. For information about a specific error code, search the Error Codes online documentation.
An attempt to access DOS on this server was unsuccessful.
Source:
HDETECT.NLM
Possible Cause:
The server has run out of disk space, or the hard disk has failed.
Action:
Verify that the hard disk is functional.
An error occurred while opening the response file.
Source:
HDETECT.NLM
Possible Cause:
Installation is using outdated information from older files in the nwupdate directory.
Action:
Make sure that current files are in the nwupdate directory. Exit installation and begin again.
An error occurred while reading the response file.
Source:
HDETECT.NLM
Possible Cause:
Installation is using outdated information from older files in the nwupdate directory.
Action:
Make sure that current files are in the nwupdate directory. Exit installation and begin again.
An error occurred while writing the response file.
Source:
HDETECT.NLM
Possible Cause:
The server ran out of disk space or the hard disk failed.
Action:
Verify that the server has enough disk space (a 50MB DOS partition) and that the hard disk is functional.
Source:
HDETECT.NLM
Possible Cause:
The server ran out of disk space or the hard disk has failed.
Action:
Verify that the server has enough disk space (a 50MB DOS partition) and that the hard disk is functional.
Directory path either is invalid or does not contain the desired file filename.
Source:
HDETECT.NLM
Possible Cause:
The path or filename does not exist as you specified it.
Action:
Make sure that the directory exists and that the path correctly points to the filename.
Directory path either is invalid or does not contain the desired file filename. Press <F3> (or F4>, if applicable) and specify a different path.
Source:
HDETECT.NLM
Possible Cause:
The path or filename does not exist as you specified it.
File filename cannot be opened. Error code.
Source:
HDETECT.NLM
Possible Cause:
The filename does not exist, or you have incorrectly specified the path.
Action:
Make sure that the directory exists or specify a different path. For information about a specific error code, search the Error Codes online documentation.
File filename cannot be read. Error code.
Source:
HDETECT.NLM
Possible Cause:
The filename does not exist, or you have incorrectly specified the path.
File filename could not be saved to path.
Source:
HDETECT.NLM
Possible Cause:
The destination directory does not exist, or you have incorrectly specified the path.
Action:
Make sure that the directory exists and that you have correctly entered the path.
File filename was not found.
Source:
HDETECT.NLM
Possible Cause:
The filename does not exist, or you have incorrectly specified the path.
Action:
Make sure that the file exists or specify a different path.
No disk driver files (*.HAM, *.CDM) or their description files (*.DDI) were found.
Source:
HDETECT.NLM
Possible Cause:
The directory or files do not exist, or you have incorrectly specified the path.
Action:
Make sure that the directory or files exist and that you have correctly entered the path.
No HotPlug support module files or their description files (*.HDI) were found at this path.
Source:
HDETECT.NLM
Possible Cause:
The directory or files do not exist, or you have incorrectly specified the path.
Action:
Make sure that the directory or files exist and that you have correctly entered the path.
No HotPlug support modules were found at path.
Source:
HDETECT.NLM
Possible Cause:
The directory does not exist. The files do not exist, or you have incorrectly specified the path.
Action:
Make sure that the directory exists and that you have correctly entered the path.
No LAN driver files (*.LAN) or their description files (*.LDI) can be found. Volume SYS may be unmounted, or directory SYS:SYSTEM may not contain any driver files.
Source:
HDETECT.NLM
Possible Cause:
The directory or files do not exist, or you have incorrectly specified the path.
Action:
Make sure that the directory or files exist and that you have correctly entered the path.
Action:
Mount volume SYS.
Action:
Copy driver files from the NetWare or third-party CD-ROM to SYS:SYSTEM.
No LAN driver files (*.LAN) or their description files (*.LDI) were found at this path.
Source:
HDETECT.NLM
Possible Cause:
The directory or files do not exist, or you have incorrectly specified the path.
Action:
Make sure that the directory or files exist and that you have correctly entered the path.
No LAN driver files (*.LAN) were found at path.
Source:
HDETECT.NLM
Possible Cause:
The directory or files do not exist, or you have incorrectly specified the path.
Action:
Make sure that the directory or files exist and that you have correctly entered the path.
No psm driver files (*.PSM) or their description files (*.MDI) were found.
Source:
HDETECT.NLM
Possible Cause:
The directory or files do not exist, or you have incorrectly specified the path.
Action:
Make sure that the directory or files exist and that you have correctly entered the path.
No PSM driver files (*.PSM) or their description files (*.MDI) were found at this path.
Source:
HDETECT.NLM
Possible Cause:
The directory or files do not exist, or you have incorrectly specified the path.
Action:
Make sure that the directory or files exist and that you have correctly entered the path.
No PSM drivers were found at path.
Source:
HDETECT.NLM
Possible Cause:
The directory or files do not exist, or you have incorrectly specified the path.
Action:
Make sure that the directory or files exist and that you have correctly entered the path.
No sbd driver files (*.NLM) or their description files (*.HDI) were found.
Source:
HDETECT.NLM
Possible Cause:
The directory or files do not exist, or you have incorrectly specified the path.
Action:
Make sure that the directory or files exist and that you have correctly entered the path.
No Storage driver files (*.HAM, *.CDM) or their description files (*.DDI) were found at this path.
Source:
HDETECT.NLM
Possible Cause:
The directory or files do not exist, or you have incorrectly specified the path.
Action:
Make sure that the directory or files exist and that you have correctly entered the path.
No Storage drivers were found at path.
Source:
HDETECT.NLM
Possible Cause:
The directory or files do not exist, or you have incorrectly specified the path.
Action:
Make sure that the directory or files exist and that you have correctly entered the path.
Response File Hardware Information is missing.
Source:
HDETECT.NLM
Possible Cause:
Your customized response file has invalid information about hardware.
Action:
Make sure that the response file exists in a specified directory, that you have correctly entered the path, and that your response file contains valid information about hardware.
Response File Hardware Mode Information is missing.
Source:
HDETECT.NLM
Possible Cause:
Your customized response file has invalid information about Hardware Mode.
Action:
Make sure that the response file exists in a specified directory, that you have correctly entered the path, and that your response file contains valid information about Hardware Mode.
Response File Key string is missing.
Source:
HDETECT.NLM
Possible Cause:
Your customized response file has invalid information about File Keys.
Action:
Make sure that the response file exists in a specified directory, that you have correctly entered the path, and that your response file contains valid information concerning File Keys.
Response File Source Information is missing.
Source:
HDETECT.NLM
Explanation:
Novell provides a response file. However, you can specify for the installation software to use your own custom response file and direct the installation program to use it (by using the /rf=path parameter). When using this parameter, you specify the complete path.
Possible Cause:
You customized a response file and installation is looking for it in an incorrectly specified directory.
Action:
Make sure that the response file exists in a specified directory and that you have correctly entered the path.
The following driver instance failed to load: string.
Source:
HDETECT.NLM
Action:
Make sure that the selected driver corresponds with the hardware in your server.
Action:
Verify that the parameters are set correctly for the hardware.
Volume name is out of disk space. File filename cannot be copied.
Source:
HDETECT.NLM
Action:
Verify that the server has enough disk space (500MB NetWare partition) and that the hard disk is functional.
module name: Unable to allocate memory.
Source:
HDETECT.NLM
Possible Cause:
The software cannot get memory to create structures. The server does not have enough memory or has used up its available memory.
Action:
If the server does not have 64MB of RAM, add memory.
module name: Unable to create process.
Source:
HDETECT.NLM
Possible Cause:
The server is unable to create a process that allows HDETECT.NLM to run.
Action:
Exit installation and begin again.
module name: Unable to open screen.
Source:
HDETECT.NLM
Action:
Exit installation and begin again.