Data error
Cause: DOS. DOS was unable to read or write the data correctly (this error usually means that a disk has
developed a defective spot).
Action: Refer to the "Responses" section.
Device error during Status
Device error during Prepare
Device error during Select
Device error during Refresh
Device error during write of font file to device
Cause: MODE. During the indicated operation of the MODE code page function, the device returned a device
error. The device might not support code page functions, the device is not defined to contain enough code
pages to meet the request, or the device detected certain types of invalidities within the font file contents.
The CONFIG.SYS file might not contain the DEVICE command to properly load the device.
Action: Make sure that you specified the proper device name. Change the CONFIG.SYS file, restart, and try the
MODE command again.
Device or code page missing from font file
Cause: MODE. After transmitting the specified font file to the device handler during a PREPARE operation, PC
DOS responded with an error indicating that the font file does not contain a definition of the indicated code
page for the specified device.
Action: Specify the MODE command indicating a different code page that is supported by the device. Check the
description of the various font files to verify the device and code page combinations supported.
Note: The error causes the existing code pages to be undefined. All specified code pages must be prepared
again.
Device ddd not prepared
Cause: MODE.
Where:
ddd = device name
In response to a MODE code page status request, the indicated device has not received any code page
definitions through a MODE PREPARE command. This operation is required before carrying out the MODE SELECT
operation.
Action: Information message. If desired, use the MODE PREPARE command to pass the code page definitions to
the device.
Device driver not found
Cause: MSCDEX. The device driver that supports your CD-ROM was not found in the CONFIG.SYS file.
Action: Check your CONFIG.SYS file and ensure that a DEVICE= statement exists for the CD-ROM device. If it
does not, add the applicable device driver statement to the CONFIG.SYS file. (Check the documentation that
came with the CD-ROM device to find the name of the device driver.) Restart your system and try the MSCDEX
command again.
Did not redirect file x successfully
Cause: QCONFIG. You tried to redirect output information without correctly specifying the /o switch.
Action: Specify the name of the file you want to output information to using the /o switch. For syntax format,
see the QCONFIG command in the PC DOS 7 Command Reference, or type qconfig /? at the command prompt.
Directory already exists
Cause: MKDIR. You have tried to make a directory where one already exists by that name.
Action: Retry the MD command using another name.
Directory is joined
Cause: CHKDSK. You tried to use CHKDSK while the JOIN command was in effect. The CHKDSK command does
not process joined directories.
Action: If you want to perform the CHKDSK process, use the JOIN command with the /d switch at the command
prompt.
Directory is totally empty, no . or ..,
tree past this point not processed
Cause: CHKDSK. A subdirectory was found that did not properly contain a . or .. entry. This usually happens
when DOS is not given a chance to update the disk properly. During the updating process, the system might
have shut down, or you might have reloaded the system before DOS finished the update.
Action: Shut down the system, restart, and run CHKDSK after the system is completely loaded.
Directory not empty
Cause: JOIN. The directory you want to join to is not empty.
Action: Re-enter command with empty directory name or new directory.
DISKCOPY cannot copy memory (CMCDD) devices
Cause: DISKCOPY. DISKCOPY is not supported on the memory device specified.
Action: Use COPY or XCOPY to transfer files to and from the memory device.
Disk drive not known
Cause: COMMANDS. An invalid or nonexistent drive specification was used with the command or in one of its
parameters, or the source and target drive are the same.
Action: Re-enter the command, using a valid drive specifier.
Disk error reading FAT x
Cause: CHKDSK. The file allocation table indicated is invalid. A power failure while a file is open can cause
this.
Action: If this message appears twice for FATs 1 and 2, format the disk to make it usable again. If FORMAT
fails, the disk is probably unusable.
Disk error reading (or writing) drive x:
Cause: DOS device error. DOS could not read the data from the disk properly. This is often due to a defective
disk.
Action: Try typing r (for Retry) several times, or type a (for Abort) to end the program. Make a new copy of
the disk.
Disk error writing FAT x
Cause: CHKDSK. A disk error occurred while CHKDSK was attempting to update the file allocation table (FAT)
on the specified drive. The variable, x, is 1 or 2, depending on which of the two copies of the file allocation
table could not be written.
Action: If this message appears twice for FATs 1 and 2, format the disk to make it usable again. If FORMAT
fails, discard the disk because it is probably unusable.
Disk unsuitable for system disk
Cause: FORMAT. A defective track was detected where the PC DOS files were to reside.
Action: The disk can be used only for data. Use another disk if you wish to make a system disk.
Divide overflow
Cause: DOS. A program tried to divide a number by 0, or a logic error caused an internal malfunction. The
program ends and returns you to PC DOS.
Action: Correct the programming error and continue. If this is a purchased program, take it back to your
authorized representative.
Does not exist
Cause: CHKDSK. If you specify the /v switch, CHKDSK attempts to display every action during its processing.
This message indicates that the . or .. subdirectory entry previously displayed could not be found. This means
that the entire directory could be invalid. It might also mean that only a single byte on the disk is invalid.
Action: Run CHKDSK again with the /f switch. CHKDSK will attempt to correct the problem and return the
directory to its normal state.
Do not specify filename(s)
Cause: DISKCOMP or DISKCOPY. At least one file name was specified with the DISKCOMP or DISKCOPY command.
Action: Specify only the drive letters of the disks, not the file name.
Drive already SUBSTed
Cause: SUBST. You tried to substitute a drive that was already substituted. A drive can only be substituted
once.
Action: If you want to change the current substitution, use the SUBST command with the /d switch at the
command prompt, and use the SUBST command again.
Drive d: already deleted.
Cause: FDISK. The drive you selected to delete has already been deleted.
Action: Type in a different drive letter or press Esc to return to the FDISK Options menu.
Drive d: does not support DRVLOCK
Cause: DRVLOCK. The specified drive does not support the lock or unlock functions of DRVLOCK.
Action: Refer to the documentation that came with the drive to verify that it supports the DRVLOCK functions.
Drive d: does not support EJECT
Cause: EJECT. The specified drive does not support EJECT.
Action: Make sure the drive you specify supports the EJECT function.
Drive d: is locked
Cause: EJECT. You tried to use EJECT on a drive that is locked.
Action: Use the DRVLOCK command with the /off switch to unlock the drive. Then, try the EJECT command
again.
Drive is write protected
Cause: CHECK; SDEFRAG. It is possible that the Stacker compression optimizer was interrupted while optimizing
the drive.
Action: Run CHECK /wp or SDEFRAG to correct this problem.
Drive letters have been changed or deleted
Cause: FDISK. One or more logical DOS drives have been deleted from the extended DOS partition. The drive
letter assignments for any remaining logical drives might have changed, because DOS assigns drive letters to
logical DOS drives based on the physical location of these drives in the extended DOS partition.
Action: Note the new drive letter assignments on the FDISK option for the new drive letter assignments.
Drive or device 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, try typing f to return to the
command prompt.
Drive types or diskette types not compatible
Cause: DISKCOMP or DISKCOPY. You must have the same size and type of diskettes to run these commands.
For example, you cannot copy from a single-sided diskette to a double-sided diskette, or compare a high-density
diskette with a low-density diskette.
Action: You should use FC if you want to compare the files on the diskettes. If you want to copy the diskette,
try COPY or XCOPY. Refer to the DISKCOMP or DISKCOPY commands for the allowable combinations.
Duplicate file name or file not found
Cause: RENAME. You tried to rename a file to a file name that already exists on the disk, or the file to be
renamed could not be found on the specified (or default) drive. RENAME is warning you that you are using the
same name for two files, or it cannot find the file you are trying to rename.
Action: Make sure that you typed the file name correctly. Re-enter the RENAME command.
Please see the LEGAL - Trademark notice.
Feel free - send a for any BUG on this page found - Thank you.