Fail on INT 24
Cause: DOS. The program stopped because it received a failure response to an interrupt message. This could
occur when you choose Fail in response to the Abort, Retry, or Fail message.
Action: Correct the problem that caused the error, and try the command again.
Failure to access code page font file
Cause: MODE. During a PREPARE, the attempt to access the indicate code page font file failed.
Action: Make sure that the font file name is spelled correctly. Verify the presence of the specified font file.
Reissue the MODE command with the proper specification of the font file name.
Failure to access device: ddd
Cause: MODE. During a code page operation, the opening of the specified DEVICE failed.
Where:
ddd = device name
Action: Make sure that the DEVICE name is spelled correctly and reissue the MODE command with the proper
spelling. If that fails to correct the situation, make sure that the specified DEVICE was loaded by the
CONFIG.SYS DEVICE command, or that the DEVICE is a standard device that is always present. If the DEVICE is
incorrectly specified in the CONFIG.SYS file, edit the file to specify it correctly and restart before retrying the
MODE command.
Fatal Error: Cannot allocate Memory for DOS
Cause: DOS. The conventional memory size in your system is too small. You need at least 128KB of
conventional memory to start PC DOS.
Action: Install the required additional memory in your system.
FCB unavailable
Cause: COMMANDS. An application tried to access a file using a File Control Block (FCB) over a network or
while the SHARE program was loaded; however, the FCB was no longer available.
Action: End the process. If this problem occurs frequently, increase the value in the FCB statement in your
CONFIG.SYS file and restart your computer.
File allocation table bad, drive d
Cause: DOS and COMMANDS. You tried to read absolute sectors on a network drive, or the disk has been
destroyed.
Action: If possible, use the Loader Write filespec option of the DEBUG command.
If this error persists, the disk is unusable and should be formatted again.
File creation error
Cause: DOS and COMMANDS. An unsuccessful attempt was made to replace a file that was already there or to
add a new file name to the directory.
Action: Proceed with one of the following:
o If the file was already there, make sure that the file is marked "read only" and cannot be replaced.
o If you are not able to add a new file name to the directory, the maximum number of directory entries to be
copied to the root directory might have been reached. Try removing a file, subdirectory, or the volume
label from the root directory.
o Run CHKDSK to determine if some other condition caused the error.
File exists
Cause: COMMANDS. You tried to add a file to your system, but the file name you specified already exists.
Action: Select another directory or file name.
File not found to save it.
Action: Use the F7 key to give the file a name; then save it.
File not found - filename
Cause: DOS and COMMANDS. A file name in a command or command parameter does not exist in the directory
on the specified (or default) drive.
Action: Retry the command, using the correct file name.
File not in PRINT queue
Cause: PRINT. You tried to remove a file that does not exist from the print queue.
Action: Type the correct name of the file you want removed from the print queue.
First Allocation unit is invalid, entry truncated
Cause: CHKDSK. The file whose name precedes this message contains an invalid pointer to the data area. If
you specify the /f switch, the file is truncated to a zero-length file.
Action: No action is required.
FIRST diskette bad or incompatible
Cause: DISKCOMP. The errors occurred while reading the diskette. The error might have been caused by bad
sectors or the diskette in the source drive might not be compatible with the source drive type (a high-capacity
diskette in a 320KB/360KB diskette drive, for example).
Action: Check your diskette by using the CHKDSK command.
Font file contents invalid
Cause: MODE. After transmitting the specified font file to the device driver during a PREPARE operation, DOS
responded with an error indicating that the font file is not in the proper format. The file indicated might not be
a font file, or the font file has been damaged, altered, or truncated.
Action: Make sure that you specified the correct name of the font file, and repeat the MODE command with the
proper spelling of the font file. Compare the font file with the master copy to see if it has been altered, and
replace it with a new copy from the Setup diskette in your PC DOS installation diskttes.
Note: The error causes the existing code pages to be undefined. All specified code pages need to be prepared
again. Refer to the MODE command.
FOR cannot be nested
Cause: Batch file. More than one FOR subcommand was found on one command-line statement in the batch
file.
Action: Use only one FOR subcommand per command-line statement; then retry the command.
FORMAT not supported on drive d:
Cause: FORMAT. The disk device driver does not support or incorrectly handles generic IOCTL calls (function
call 44 AL=0DH) for Get device parameters, and either Set device parameters or Format/Verify/Read/Write Track,
or both. Virtual drives are set up pre-formatted and cannot be reformatted.
Action: If you have replaced the default disk device driver at setup time, remove that DEVICE command from
your CONFIG.SYS file and try again. If you are using only the default disk device drivers, reinstall PC DOS on
the disk you restart from and try again.
Please see the LEGAL - Trademark notice.
Feel free - send a 
for any BUG on this page found - Thank you.