EMM386: Exception error #12
Cause: EMM386. EMM386 Exception error #12 is a stack fault.
Action: Determine if you have a conflicting device driver or increase your stacks.
EMM386: Unable to start Enhanced Mode Windows due to invalid path specification for EMM386
Cause: EMM386. The EMM386 path in the CONFIG.SYS is invalid.
Action: Edit your CONFIG.SYS file and type the correct drive and path name on the EMM386 line.
Entry has a bad attribute (or size or link)
Cause: CHKDSK. This message might begin with one or two periods, indicating which entry in the subdirectory
was in error. One period shows that the current directory is in error. Two periods mean that the parent
directory is in error. If you did not enter the /f switch, no corrective action is taken.
Action: Type:
chkdsk /f
CHKDSK tries to correct the error.
Entry has a bad link
Entry has a bad size
Cause: CHKDSK. The "." (current directory) or ".." (parent directory) entry contains incorrect information.
Action: Use the CHKDSK command with the /f switch to correct the error.
ERROR: Bad command line, no installation
Cause: PCMCIA. The specified command line parameter is not correct.
Action: Specify the correct parameter in the PCM.INI file; then try the command again.
ERROR: Card Services already present
Cause: PCMCIA. You are attempting to install Card Services which is already installed.
Action: No action required.
ERROR: Card Services is not installed
Cause: PCMCIA. Card Services is not installed on your system.
Action: Check for PCMCIA support on your system. If your system has PCMCIA support, install Card Services.
ERROR: Card Services not found!
Cause: PCMCIA. Common causes of this error are as follows:
o The PCMCIA path is not found.
o The Card Services driver is not installed.
Action:
o Make sure the PCMCIA path is being accessed.
o Install Card Services; then try the command again.
ERROR: Could not register as client
Cause: PCMCIA (PCMSCD). Maximum clients allowed to register was reached.
Action: Edit the PCM.INI file and increase the value for the /client parameter.
ERROR: Fail to register client with Card Services!
Cause: PCMCIA (PCMATA). Maximum clients allowed to register was reached.
Action: Edit the PCM.INI file and increase the value for the /client parameter.
ERROR: Incorrect command line parameters detected
Cause: PCMCIA. The specified command line parameter is not correct.
Action: Edit your PCM.INI file and ensure that the parameters listed are correct. Rerun the command.
ERROR: No PCMCIA Adapters present
Cause: PCMCIA (PCMSS). An attempt was made to load Socket Services but your system does not support
PCMCIA.
Action: Install PCMCIA hardware support in your current system.
ERROR: PC DOS Docking support unsuccesful.
Unable to locate a DOC or UNDOCK command to process.
Use the SET command to initialize these commands.
Cause: DOSDOCK. The DOCK and UNDOCK commands are
not stored in the DOS environment.
Action: Use the SET command to assign these commands to the DOS environment.
ERROR: PCM.INI missing
Cause: PCMCIA. You attempted to load a PCMCIA driver but the initialization file, PCM.INI, could not be found.
Action:
o Ensure that the correct PCMCIA directory is being accessed.
o Reinstall PCMCIA from the installation diskettes and run PCMDINST.
ERROR: The PCMCIA configuration program requires a CONFIG.SYS file
Cause: PCMDINST. CONFIG.SYS file is missing.
Action: Create CONFIG.SYS file or copy CONFIG.SYS to the root directory and rerun.
ERROR: Unable to initialize Card Services
Cause: PCMCIA (PCMCS). Invalid parameters or resource conflicts.
Action: Verify that the parameters in the PCM.INI file for PCMCS are all valid and within range. Also, check that
there are no memory or IRQ conflicts between your PCMCIA settings and other programs or devices in your
system.
ERROR: Unable to locate a DOCK command in the environment to process
Cause: DOSDOCK. The DOCK command is not stored in the DOS environment.
Action: Use the SET command to assign these commands in the DOS environment.
ERROR: Unable to locate an UNDOCK command in the environment to process
Cause: DOSDOCK. The DOCK command is not stored in the DOS environment.
Action: Use the SET command to assign these commands in the DOS environment.
ERROR: Unable to read PCM.INI
Cause: PCMCIA. You attempted to load a PCMCIA driver but the initialization file, PCM.INI, could not be found.
Action:
o Ensure that the correct PCMCIA directory is being accessed.
o Reinstall PCMCIA from the installation diskettes and run PCMDINST.
Error during read of font file
Cause: MODE. While attempting to carry out a MODE PREPARE code page function, the record from the
specified code page font file had an unrecoverable I/O error. The code page definition sent to the device is
incomplete.
Action: Try to determine the readability problem and restore the file from a master copy, or direct MODE to an
alternate device to access a copy of the file.
Error in CONFIG.SYS line x
Cause: IBMBIO. An error occurred during startup when PC DOS reads the CONFIG.SYS file and interprets the
commands within the file. The x variable shows you where the error occurred.
This message might also be shown when a device driver attempts to install itself but is not needed by the
system.
Action: Edit the CONFIG.SYS file and re-enter the correct format of the command.
Error in COUNTRY command
Cause: DOS. The code page was missing from the COUNTRY command and the default was not requested, or
the country information file:
o Is not in correct format.
o Contains invalid information.
Action: Make sure that the country information is correct, or correct the COUNTRY command in the CONFIG.SYS
file and restart the computer.
Error in EXE file
Cause: DOS. An error was detected in the relocation information placed in the file by the LINK program. This
might be caused by a change to the file.
Action:
o If you are using a purchased program, rerun the program, using your backup copy.
o If you are using a program you wrote yourself, go through the LINK procedure again.
Error in margin settings
Cause: E. Possible causes are as follows:
o You tried to set the margin past the maximum margin column.
o You tried to set a margin in the zero or negative column.
o You tried to set the left margin in a column greater than the right margin.
Action: Refer to the "PC DOS 7 User's Guide" for more information about the appropriate margin settings.
Error loading operating system
Cause: DOS. A disk error occurred while attempting to load your operating system from the hard disk.
Action: Restart the system. If the error persists after several tries, restart the system (you should start DOS
from your Setup diskette in the PC DOS installation diskettes), and use the SYS command to transfer a new
copy of DOS to your hard disk.
Error not a CP Backup disk
Cause: The disk you are attempting to restore from was created by an earlier version of Backup, or you may
have the wrong backup speed selected.
Action: Low-speed backups can only be restored at low speed. High- or medium-speed backups may be
restored at either high or medium speed. Also, check the media settings to be sure they are correct.
Error occurred in environment variable
Cause: DIR. The command-line error which appeared just before this message occurred because the value of
the DIRCMD environment variable is not proper DIR command syntax.
Action: Check the description of the DIR command or type DIR /? to display the proper command syntax. Use
the SET command to view, change, or clear the value of the DIRCMD environment variable.
Error on device d
Cause: COMMANDS. An error occurred while trying to read an indicated device. Common causes of this error
are as follows:
o The diskette drive door is not closed.
o The diskette is not properly formatted.
o The printer is not online.
o The printer does not have enough paper or is busy.
Action: Correct the error and try again. If your default drive is a diskette drive, try typing f to return to the
command prompt.
Error on drive d:
Cause: COMMANDS. An error occurred while trying to read or write to the indicated drive. Common causes of
this error are as follows:
o The diskette drive door is not closed.
o The diskette is not properly formatted.
o The printer is not online.
o The printer does not have enough paper or is busy.
Action: Correct the error and try again. If your default drive is a diskette drive, try typing f to return to the
command prompt.
Error on hard disk d:
Cause: FDISK. The FDISK program was unable to read the startup record of the current hard disk after five
attempts.
Action: Try the FDISK program again. If, after several attempts, you get the same error, consult the
documentation that came with your system.
Error opening file
Cause: E. The file you are trying to open might not exist.
Action: Verify that you used the correct file name and the correct path that leads to the file that you want to
open.
Error reading file
Cause: E, VIEW. Either the editor does not recognize the file format used or VIEW could not read the file
format.
Action: If you are using the E Editor, ensure that the file you are editing is an ASCII text file. You cannot edit
files created with word processing programs. If you are attempting to view a file, ensure that it is an .INF file
compiled by an IPF compiler.
Error reading hard disk
Cause: FDISK. The FDISK program was unable to read the startup record of the current hard disk after five
attempts.
Action: Try the FDISK program again. If, after several attempts, you get the same error, consult the
documentation that came with your system.
Error reading partition table
Cause: FORMAT. An error (probably hardware) occurred while reading the partition table.
Action: Run FDISK on the drive and try again.
Error reading the file
Cause: UNFORMAT. While attempting to restore the partitions of a hard disk, the UNFORMAT command was
unable to locate, or read the PARTNSAV.FIL file on the diskette.
Action: Make sure that the file exists on the diskette and try the UNFORMAT command again.
Error Track 0 bad or check your drive and media settings
Cause: This error can indicate:
o A damaged disk. Try another disk.
o The wrong backup speed. Try a different setting.
o A conflict with a TSR.
Action: Check your drive and media settings and be sure you are using the correct media.
Note: Try using Media Format _ DOS Format if you are experiencing trouble on an Amstrad computer.
Error writing directory
Cause: FORMAT. There are bad sectors within the directory or file allocation table (FAT) structure. This is a
write problem.
Action: Try formatting the disk to make it usable again.
Error writing FAT
Cause: FORMAT. A disk error occurred while FORMAT was attempting to update the file allocation table (FAT)
on the specified drive.
Action: If this message appears twice for FATs 1 and 2, format the disk to make it usable again.
Error writing file
Cause: E. The file might be read-only or there is not enough available free storage space left on the disk.
Action: Do one of the following:
o Specify a file that can be written to.
o Make storage space available by erasing unneeded files.
o Use the ATTRIB command to change the attributes of the file you want to write to.
For information about changing file attributes, see the command ATTRIB in the PC DOS 7 Command Reference.
Error writing hard disk
Cause: FDISK. The FDISK program was unable to write the startup record of the current hard disk after five
attempts.
Action: Try the FDISK program again. If, after several attempts, you get the same error, consult the
documentation that came with your system.
Error writing partition table
Cause: FORMAT. An error (probably hardware) occurred while writing the partition table.
Action: Run FDISK on the drive and try again.
Error writing to device
Cause: COMMANDS. DOS encountered an I/O error when writing output to a device. The device is unable to
handle the number of bytes requested.
Action: Change the amount of data in the file and retry the command.
Error writing to the image file. The copy process could not be completed
Cause: DISKCOPY. There was not enough space on the hard drive.
Action: Free up space on the hard drive or try the command again using the /m switch. This will force a
multi-pass copy using memory only.
Errors found, /F switch not specified
Corrections will not be written to disk
Cause: CHKDSK. Information message. An error was found and you have not used the /f switch. CHKDSK
carries out its analysis as though it were going to correct any errors detected, so that you can see the results
of its analysis, but it does not write the corrections to the disk.
Action: Use the /f switch if you want CHKDSK to try to correct any errors detected.
Errors on list device indicate that it may be off-line. Please check it.
Cause: PRINT. The printer was not recognized as being online.
Action: Ensure that the printer is plugged in, switched on, and that it is ready to print.
Error: Syntax error in command line!
Cause: PCMCIA. An incorrect parameter was detected.
Action: Check your PCM.INI file for incorrect parameter settings.
EXEC failure
Cause: DEBUG. DOS either found an error when reading a command, or the FILES command in the CONFIG.SYS
file is set too low.
Action: Increase the value of the FILES command in the CONFIG.SYS file, and restart PC DOS.
Expanded memory not available
Cause: COMMANDS. Information message. You have specified the /x or /a switch but you do not have an
expanded memory card installed in your system.
Action: Remove the /x or /a switch from the command.
Extended DOS Partition already exists
Cause: FDISK. An extended partition for DOS has already been set up.
Action: Return to the FDISK Options menu and select a different option.
Extended error #
Cause: DOS. An error occurred for a command-line statement.
Action: The "#" position in this message represents a number that corresponds to a particular error that caused
this message to be displayed. The specific causes and actions for these errors are listed in this book in
alphabetic order. Use the following list to find the message that corresponds to the number displayed on your
screen:
1. - Invalid Function
2. - File not found
3. - Path not found
4. - Too many open files
5. - Access denied
6. - Invalid handle
7. - Memory control blocks destroyed
8. - Insufficient memory
9. - Invalid memory block address
10. - Invalid Environment
11. - Invalid format
12. - Invalid function parameter
13. - Invalid data
15. - Invalid drive specification
16. - Attempt to remove current directory
17. - Not same device
18. - No more files
19. - Write protect error
20. - Invalid unit
21. - Not ready
22. - Invalid device request
23. - Data error
24. - Invalid device request parameters
25. - Seek error
26. - Invalid media type
27. - Sector not found
28. - Printer out of paper error
29. - Write fault error
30. - Read fault error
31. - General failure
32. - Sharing violation
33. - Lock violation
34. - Invalid disk change
35. - FCB unavailable
36. - System resource exhausted
38. - Out of input
39. - Insufficient disk space
80. - File exists
82. - Cannot make directory entry
83. - Fail on INT 24
84. - Too many redirections
85. - Duplicate redirection
86. - Invalid password
87. - Invalid parameter
88. - Network data fault
90. - Required system component not installed
EMM386: Exception error #12
Cause: EMM386. EMM386 Exception error #12 is a stack fault.
Action: Determine if you have a conflicting device driver or increase your stacks.
EMM386: Unable to start Enhanced Mode Windows due to invalid path specification for EMM386
Cause: EMM386. The EMM386 path in the CONFIG.SYS is invalid.
Action: Edit your CONFIG.SYS file and type the correct drive and path name on the EMM386 line.
Entry has a bad attribute (or size or link)
Cause: CHKDSK. This message might begin with one or two periods, indicating which entry in the subdirectory
was in error. One period shows that the current directory is in error. Two periods mean that the parent
directory is in error. If you did not enter the /f switch, no corrective action is taken.
Action: Type:
chkdsk /f
CHKDSK tries to correct the error.
Entry has a bad link
Entry has a bad size
Cause: CHKDSK. The "." (current directory) or ".." (parent directory) entry contains incorrect information.
Action: Use the CHKDSK command with the /f switch to correct the error.
ERROR: Bad command line, no installation
Cause: PCMCIA. The specified command line parameter is not correct.
Action: Specify the correct parameter in the PCM.INI file; then try the command again.
ERROR: Card Services already present
Cause: PCMCIA. You are attempting to install Card Services which is already installed.
Action: No action required.
ERROR: Card Services is not installed
Cause: PCMCIA. Card Services is not installed on your system.
Action: Check for PCMCIA support on your system. If your system has PCMCIA support, install Card Services.
ERROR: Card Services not found!
Cause: PCMCIA. Common causes of this error are as follows:
o The PCMCIA path is not found.
o The Card Services driver is not installed.
Action:
o Make sure the PCMCIA path is being accessed.
o Install Card Services; then try the command again.
ERROR: Could not register as client
Cause: PCMCIA (PCMSCD). Maximum clients allowed to register was reached.
Action: Edit the PCM.INI file and increase the value for the /client parameter.
ERROR: Fail to register client with Card Services!
Cause: PCMCIA (PCMATA). Maximum clients allowed to register was reached.
Action: Edit the PCM.INI file and increase the value for the /client parameter.
ERROR: Incorrect command line parameters detected
Cause: PCMCIA. The specified command line parameter is not correct.
Action: Edit your PCM.INI file and ensure that the parameters listed are correct. Rerun the command.
ERROR: No PCMCIA Adapters present
Cause: PCMCIA (PCMSS). An attempt was made to load Socket Services but your system does not support
PCMCIA.
Action: Install PCMCIA hardware support in your current system.
ERROR: PC DOS Docking support unsuccesful.
Unable to locate a DOC or UNDOCK command to process.
Use the SET command to initialize these commands.
not stored in the DOS environment.
Cause: DOSDOCK. The DOCK and UNDOCK commands are
Action: Use the SET command to assign these commands to the DOS environment.
ERROR: PCM.INI missing
Cause: PCMCIA. You attempted to load a PCMCIA driver but the initialization file, PCM.INI, could not be found.
Action:
o Ensure that the correct PCMCIA directory is being accessed.
o Reinstall PCMCIA from the installation diskettes and run PCMDINST.
ERROR: The PCMCIA configuration program requires a CONFIG.SYS file
Cause: PCMDINST. CONFIG.SYS file is missing.
Action: Create CONFIG.SYS file or copy CONFIG.SYS to the root directory and rerun.
ERROR: Unable to initialize Card Services
Cause: PCMCIA (PCMCS). Invalid parameters or resource conflicts.
Action: Verify that the parameters in the PCM.INI file for PCMCS are all valid and within range. Also, check that
there are no memory or IRQ conflicts between your PCMCIA settings and other programs or devices in your
system.
ERROR: Unable to locate a DOCK command in the environment to process
Cause: DOSDOCK. The DOCK command is not stored in the DOS environment.
Action: Use the SET command to assign these commands in the DOS environment.
ERROR: Unable to locate an UNDOCK command in the environment to process
Cause: DOSDOCK. The DOCK command is not stored in the DOS environment.
Action: Use the SET command to assign these commands in the DOS environment.
ERROR: Unable to read PCM.INI
Cause: PCMCIA. You attempted to load a PCMCIA driver but the initialization file, PCM.INI, could not be found.
Action:
o Ensure that the correct PCMCIA directory is being accessed.
o Reinstall PCMCIA from the installation diskettes and run PCMDINST.
Error during read of font file
Cause: MODE. While attempting to carry out a MODE PREPARE code page function, the record from the
specified code page font file had an unrecoverable I/O error. The code page definition sent to the device is
incomplete.
Action: Try to determine the readability problem and restore the file from a master copy, or direct MODE to an
alternate device to access a copy of the file.
Error in CONFIG.SYS line x
Cause: IBMBIO. An error occurred during startup when PC DOS reads the CONFIG.SYS file and interprets the
commands within the file. The x variable shows you where the error occurred.
This message might also be shown when a device driver attempts to install itself but is not needed by the
system.
Action: Edit the CONFIG.SYS file and re-enter the correct format of the command.
Error in COUNTRY command
Cause: DOS. The code page was missing from the COUNTRY command and the default was not requested, or
the country information file:
o Is not in correct format.
o Contains invalid information.
Action: Make sure that the country information is correct, or correct the COUNTRY command in the CONFIG.SYS
file and restart the computer.
Error in EXE file
Cause: DOS. An error was detected in the relocation information placed in the file by the LINK program. This
might be caused by a change to the file.
Action:
o If you are using a purchased program, rerun the program, using your backup copy.
o If you are using a program you wrote yourself, go through the LINK procedure again.
Error in margin settings
Cause: E. Possible causes are as follows:
o You tried to set the margin past the maximum margin column.
o You tried to set a margin in the zero or negative column.
o You tried to set the left margin in a column greater than the right margin.
Action: Refer to the "PC DOS 7 User's Guide" for more information about the appropriate margin settings.
Error loading operating system
Cause: DOS. A disk error occurred while attempting to load your operating system from the hard disk.
Action: Restart the system. If the error persists after several tries, restart the system (you should start DOS
from your Setup diskette in the PC DOS installation diskettes), and use the SYS command to transfer a new
copy of DOS to your hard disk.
Error not a CP Backup disk
Cause: The disk you are attempting to restore from was created by an earlier version of Backup, or you may
have the wrong backup speed selected.
Action: Low-speed backups can only be restored at low speed. High- or medium-speed backups may be
restored at either high or medium speed. Also, check the media settings to be sure they are correct.
Error occurred in environment variable
Cause: DIR. The command-line error which appeared just before this message occurred because the value of
the DIRCMD environment variable is not proper DIR command syntax.
Action: Check the description of the DIR command or type DIR /? to display the proper command syntax. Use
the SET command to view, change, or clear the value of the DIRCMD environment variable.
Error on device d
Cause: COMMANDS. An error occurred while trying to read an indicated device. Common causes of this error
are as follows:
o The diskette drive door is not closed.
o The diskette is not properly formatted.
o The printer is not online.
o The printer does not have enough paper or is busy.
Action: Correct the error and try again. If your default drive is a diskette drive, try typing f to return to the
command prompt.
Error on drive d:
Cause: COMMANDS. An error occurred while trying to read or write to the indicated drive. Common causes of
this error are as follows:
o The diskette drive door is not closed.
o The diskette is not properly formatted.
o The printer is not online.
o The printer does not have enough paper or is busy.
Action: Correct the error and try again. If your default drive is a diskette drive, try typing f to return to the
command prompt.
Error on hard disk d:
Cause: FDISK. The FDISK program was unable to read the startup record of the current hard disk after five
attempts.
Action: Try the FDISK program again. If, after several attempts, you get the same error, consult the
documentation that came with your system.
Error opening file
Cause: E. The file you are trying to open might not exist.
Action: Verify that you used the correct file name and the correct path that leads to the file that you want to
open.
Error reading file
Cause: E, VIEW. Either the editor does not recognize the file format used or VIEW could not read the file
format.
Action: If you are using the E Editor, ensure that the file you are editing is an ASCII text file. You cannot edit
files created with word processing programs. If you are attempting to view a file, ensure that it is an .INF file
compiled by an IPF compiler.
Error reading hard disk
Cause: FDISK. The FDISK program was unable to read the startup record of the current hard disk after five
attempts.
Action: Try the FDISK program again. If, after several attempts, you get the same error, consult the
documentation that came with your system.
Error reading partition table
Cause: FORMAT. An error (probably hardware) occurred while reading the partition table.
Action: Run FDISK on the drive and try again.
Error reading the file
Cause: UNFORMAT. While attempting to restore the partitions of a hard disk, the UNFORMAT command was
unable to locate, or read the PARTNSAV.FIL file on the diskette.
Action: Make sure that the file exists on the diskette and try the UNFORMAT command again.
Error Track 0 bad or check your drive and media settings
Cause: This error can indicate:
o A damaged disk. Try another disk.
o The wrong backup speed. Try a different setting.
o A conflict with a TSR.
Action: Check your drive and media settings and be sure you are using the correct media.
Note: Try using Media Format _ DOS Format if you are experiencing trouble on an Amstrad computer.
Error writing directory
Cause: FORMAT. There are bad sectors within the directory or file allocation table (FAT) structure. This is a
write problem.
Action: Try formatting the disk to make it usable again.
Error writing FAT
Cause: FORMAT. A disk error occurred while FORMAT was attempting to update the file allocation table (FAT)
on the specified drive.
Action: If this message appears twice for FATs 1 and 2, format the disk to make it usable again.
Error writing file
Cause: E. The file might be read-only or there is not enough available free storage space left on the disk.
Action: Do one of the following:
o Specify a file that can be written to.
o Make storage space available by erasing unneeded files.
o Use the ATTRIB command to change the attributes of the file you want to write to.
For information about changing file attributes, see the command ATTRIB in the PC DOS 7 Command Reference.
Error writing hard disk
Cause: FDISK. The FDISK program was unable to write the startup record of the current hard disk after five
attempts.
Action: Try the FDISK program again. If, after several attempts, you get the same error, consult the
documentation that came with your system.
Error writing partition table
Cause: FORMAT. An error (probably hardware) occurred while writing the partition table.
Action: Run FDISK on the drive and try again.
Error writing to device
Cause: COMMANDS. DOS encountered an I/O error when writing output to a device. The device is unable to
handle the number of bytes requested.
Action: Change the amount of data in the file and retry the command.
Error writing to the image file. The copy process could not be completed
Cause: DISKCOPY. There was not enough space on the hard drive.
Action: Free up space on the hard drive or try the command again using the /m switch. This will force a
multi-pass copy using memory only.
Errors found, /F switch not specified
Corrections will not be written to disk
Cause: CHKDSK. Information message. An error was found and you have not used the /f switch. CHKDSK
carries out its analysis as though it were going to correct any errors detected, so that you can see the results
of its analysis, but it does not write the corrections to the disk.
Action: Use the /f switch if you want CHKDSK to try to correct any errors detected.
Errors on list device indicate that it may be off-line. Please check it.
Cause: PRINT. The printer was not recognized as being online.
Action: Ensure that the printer is plugged in, switched on, and that it is ready to print.
Error: Syntax error in command line!
Cause: PCMCIA. An incorrect parameter was detected.
Action: Check your PCM.INI file for incorrect parameter settings.
EXEC failure
Cause: DEBUG. DOS either found an error when reading a command, or the FILES command in the CONFIG.SYS
file is set too low.
Action: Increase the value of the FILES command in the CONFIG.SYS file, and restart PC DOS.
Expanded memory not available
Cause: COMMANDS. Information message. You have specified the /x or /a switch but you do not have an
expanded memory card installed in your system.
Action: Remove the /x or /a switch from the command.
Extended DOS Partition already exists
Cause: FDISK. An extended partition for DOS has already been set up.
Action: Return to the FDISK Options menu and select a different option.
Extended error #
Cause: DOS. An error occurred for a command-line statement.
Action: The "#" position in this message represents a number that corresponds to a particular error that caused
this message to be displayed. The specific causes and actions for these errors are listed in this book in
alphabetic order. Use the following list to find the message that corresponds to the number displayed on your
screen:
1. - Invalid Function
2. - File not found
3. - Path not found
4. - Too many open files
5. - Access denied
6. - Invalid handle
7. - Memory control blocks destroyed
8. - Insufficient memory
9. - Invalid memory block address
10. - Invalid Environment
11. - Invalid format
12. - Invalid function parameter
13. - Invalid data
15. - Invalid drive specification
16. - Attempt to remove current directory
17. - Not same device
18. - No more files
19. - Write protect error
20. - Invalid unit
21. - Not ready
22. - Invalid device request
23. - Data error
24. - Invalid device request parameters
25. - Seek error
26. - Invalid media type
27. - Sector not found
28. - Printer out of paper error
29. - Write fault error
30. - Read fault error
31. - General failure
32. - Sharing violation
33. - Lock violation
34. - Invalid disk change
35. - FCB unavailable
36. - System resource exhausted
38. - Out of input
39. - Insufficient disk space
80. - File exists
82. - Cannot make directory entry
83. - Fail on INT 24
84. - Too many redirections
85. - Duplicate redirection
86. - Invalid password
87. - Invalid parameter
88. - Network data fault
90. - Required system component not installed
Please see the LEGAL - Trademark notice.
Feel free - send a 
for any BUG on this page found - Thank you.