NLSFUNC not installed
Cause: CHCP. NLSFUNC must be installed before running the CHCP command.
Action: Start NLSFUNC. Prepare devices using the MODE command. Retry the CHCP command.
No code page has been selected
Cause: MODE. In the MODE STATUS code page operation, the device reports that no code page is selected for
that device.
Action: No action is required. If desired, use MODE to select a code page from the list of prepared code pages
that immediately follow this message.
No Drive Specified
Cause: DRIVER.SYS. You did not specify the physical drive number in the DEVICE statement in the CONFIG.SYS
file.
Action: See the DRIVER.SYS command for the correct format to use.
No Extended DOS Partition to delete.
Cause: FDISK. You selected the Delete extended DOS partition option, but there is no extended DOS partition
on the current hard disk.
Action: Return to the FDISK Options menu and select Display Partition Data to review.
No files added
Cause: REPLACE. The /a switch was specified but all the files on the source already exist in the target
directory.
Action: No action is required.
No files found - x
Cause: REPLACE. No files described by the source path and file name were found on the source.
Action: No action is required.
No files replaced
Cause: REPLACE. All files found on the target were not replaced because you answered N to all REPLACE
<filename> prompts, or no source files existed on the target.
Action: No action is required.
No free file handles
Cause: DOS. An attempt to load the command processor failed because there are too many files open.
Action: Increase the number in the FILES command in the configuration file (CONFIG.SYS) and restart PC DOS.
No hard disks present
Cause: FDISK. The FDISK program was run on a personal computer that:
o Does not have a hard disk, or
o Has a hard disk in the expansion unit and the expansion unit is not powered on, or
o Has a hard disk that is not properly installed.
Action: From the preceding list, determine what caused the problem and act appropriately. Make sure that the
expansion unit is powered on first.
No logical drives defined
Cause: FDISK. No logical drives have been defined in the extended DOS partition.
Action: To use the space on the disk reserved for the extended DOS partition, create one or more logical DOS
drives using FDISK and format the logical drives using the FORMAT command.
No Logical DOS Drives to delete.
Cause: FDISK. Information message. There are no logical DOS drives in this partition.
Action: Press Esc to return to the previous screen.
No media in drive
Cause: EJECT. You issued the EJECT command on a drive containing no medium.
Action: No action is required.
No Non-DOS Partition to delete
Cause: FDISK. There are no non-DOS partitions on your disk. To see how your disk is currently partitioned,
choose option 4, Display partition information, from the FDISK main menu.
Action: No action is required.
No partitions defined
Cause: FDISK. There are no partitions defined on the hard disk.
Action: If you wish to use the hard disk for a DOS disk, create a primary DOS partition using FDISK, and format
the created drive letter using the FORMAT command.
No partitions to delete
Cause: FDISK. You selected the Delete partition or logical DOS drive option, and there are no partitions created
on this hard disk.
Action: Return to the FDISK Options menu and select a different option.
No partitions to make active
Cause: FDISK. You selected the Set active partition option, but there were no partitions on the current hard
disk to be made active.
Action: Return to the FDISK Options menu and select the Create DOS partition or Logical DOS Drive option to
create a partition, and then select the Set active partition option to make it the active partition.
No Path
Cause: PATH. You typed the PATH command and pressed Enter to find out what your search path is, but an
alternate path for DOS to search for commands and batch files was not specified.
Action: This is an information message. Defining a set of paths is optional. If you want to define the path, type
path and the set of paths you want; then press Enter.
No Primary DOS Partition to delete.
Cause: FDISK. You selected the Delete Primary DOS Partition option, but there is no DOS partition on the
current hard disk.
Action: Return to the FDISK Options menu and select Display Partition Information to review.
No room for system on destination disk
Cause: SYS. The destination disk does not contain the required reserved space for DOS; therefore, the system
cannot be transferred.
Action: Format a blank diskette (use the FORMAT /s command) and copy any other files to the new diskette.
No source drive specified
Cause: COMMANDS. You did not specify a source drive.
Action: Try the command again, specifying both the source and destination drives.
No space to create a DOS partition
Cause: FDISK. You selected the Create DOS Partition or Logical DOS Drive option on the current hard disk.
There is no space on the current hard disk to create a DOS partition.
Action: Remove or reduce the size of the existing partition. Run FDISK again to create the DOS partition.
No system on default drive
Cause: SYS. The system files to be transferred were not found on the disk or the diskette in the default
drive.
Action: Select a disk or a diskette with the system files on it (DOS disk) and try again.
No target drive specified
Cause: COMMANDS. You did not specify a target (destination) drive.
Action: Try the command again, specifying both the source and destination drives.
Non-removable drive full
Cause: There is no more space on the destination drive during restoring or backing up.
Action: You should cancel the process and check your destination drive for files you can remove, or check
whether the specified drive and path (restore to) is valid. This error may occur if you are backing up to a hard
drive.
Non-System disk or disk error
Replace and press any key when ready
Cause: No entry exists for IBMBIO.COM or IBMDOS.COM in the directory; or a disk read error occurred when you
started up the system.
Action: Insert the Setup Diskette from the PC DOS installation diskettes in drive A and restart your system.
Not able to restore file
Cause: RESTORE. The file you want to restore cannot be opened because of a sharing conflict.
Action: Try again at a later time.
Not able to SYS to name file system
Cause: SYS. You tried to transfer system files to a non-DOS drive.
Action: Specify a DOS drive as the destination drive.
Not enough drive letters available
Cause: MSCDEX. There are 26 drive letters available to your system. You have either used up all 26 letters or
you are attempting to assign a drive letter beyond the specification set with the LASTDRIVE= command.
Action: Use the PC DOS E Editor to check and adjust the LASTDRIVE=statement in your CONFIG.SYS file. If all
drive letters have been allocated, examine the possibility of removing programs that use drive letter assignments
such as RAMDRIVE.
Not enough memory
Cause: E. There is not enough memory for processing the save operation.
Action: You need to increase the amount of available memory in your system. Before you work with your
system memory, you might try saving your file by block copying the entire file to a diskette.
To increase your system memory, do one or more of the following:
o Change the buffers parameter in the CONFIG.SYS file to a smaller value.
o Remove device driver programs.
Restart the system and try the command again. If the message still appears, your system does not have enough
memory to process the command.
Not enough memory to load help
Cause: IBMBIO. There is not enough memory to load the help.
Action: You need to increase the amount of available memory in your system. You can do this in several ways
including:
o Changing the buffers parameter in the CONFIG.SYS file to a smaller value.
o Removing device driver programs.
Restart the system and try the command again. If the message still appears, your system does not have enough
memory installed.
Not enough memory to verify cluster integrity
Cause: CHECK. There is not enough memory for the CHECK command to complete its verification process.
Action: Increase the amount of available conventional memory in your system. There are several things you
might try.
o Run MEM /c to ensure that your compression driver (STACHIGH.SYS) is loaded high.
o Press F8 immediately after your computer displays the text
Starting PC DOS....
Answer yes to the prompt to load Stacker high and DPMS high. Answer no to all other prompts. Rerun
CHECK.
Not ready
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 and you get the message to
Abort, Retry, or Fail, try typing f to return to the command prompt.
Not resetting hidden file filename
Cause: COMMANDS. The specified files with a hidden attribute are not being modified.
Action: If you want to reset attributes on these files, use the ATTRIB command with the -h switch to remove
the hidden attribute from these files before continuing the process.
Not resetting system file filename
Cause: COMMANDS. The specified files with a system attribute are not being modified.
Action: If you want to reset attributes on these files, use the ATTRIB command with the -s switch to remove
the system attribute from these files before continuing the process.
Please see the LEGAL - Trademark notice.
Feel free - send a for any BUG on this page found - Thank you.