Tape drive does not have long-tape capability
Cause: Your drive is unable to handle extended-length tapes.
Action: Use a drive that can handle extended-length tapes.
TARGET diskette bad or incompatible
Cause: DISKCOPY. You tried to write to the wrong medium in an incompatible drive.
Action: Check your diskette by using the CHKDSK command.
Target diskette may be unusable
Cause: DISKCOPY. This message follows an unrecoverable read, write, or verify error message. The copy on
the target disk may be incomplete because of the unrecoverable I/O error.
o If an error is on the target disk, use a different disk for your target, and retry the DISKCOPY command.
o If the error is on the source disk, copy all files from the source disk to another disk; then try to reformat
the source disk.
Target diskette unusable
Cause: DISKCOPY. Errors that occurred during the copying procedure show that the target disk is dirty,
damaged, or of poor quality, or the drive is malfunctioning on some tracks.
Action: Change the target drive or the disk and try again.
Text already marked
Cause: E. You tried to mark a block, word or character after you previously marked a block, word or
Action: Use Unmark (ALT+U) to remove any existing block, word, or character marks and try again.
Text not marked
Cause: E. You tried to move or copy text before you marked it.
Action: Mark the text you want to copy or move; then, try again.
That password contains illegal characters. Please try again.
Cause: PASSWD. You typed a password that contained characters that cannot be part of a password.
Action: Retype a password ensuring that you do not use the following: ;, ", /, >, <, or |.
The boot record has changed - Innoculate, Repair or Ignore?
Cause: IBMAVSP. You are attempting to run the IBM stand-alone AntiVirus product, probably for the first time.
Action: There is no problem. The program is working correctly. If this is the first time, type I and press ENTER
The disk might not be formatted
Cause: COMMANDS. The operation was not successful because the disk might be bad, the wrong type, or not
Action: Determine if the disk is usable. If it is not, use another disk.
The file xxxxxx is in the wrong format and cannot be viewed
Cause: VIEW. The file you are trying to view is not an .INF file generated by the IPF compiler.
Action: Check the filename you have typed and ensure that it is an .INF file. Rerun VIEW. If you still get this
message, it is probably because the file was not compiled by the IPF compiler and cannot be viewed using the
The help file x has incorrect version information
Cause: HELP. You are using a file whose version does not match the version you initially loaded.
Action: Determine why you are accessing the wrong version (often the result of your PATH setting) and change
your setup to find the correct version.
The last file was not restored
Cause: RESTORE. You stopped RESTORE before it completely restored the last file listed, or there was not
enough room on the hard disk, and RESTORE deleted the partially restored file.
Action: If RESTORE has ended, you can re-enter the RESTORE command with the file name of the files not
restored to continue from the point where RESTORE stopped.
If the problem occurred because you ran out of room on the hard disk, you must evaluate which files to keep
and which ones to delete. Continue processing RESTORE.
The master boot code has NOT been updated
Cause: FDISK. There is a physical problem reading or writing to the hard disk. This could indicate a bad sector
on the disk where the master (startup) record is located.
Action: Use the FDISK command to delete the partition and create a new one, or use the low-level format that
came with the hard disk to format the disk.
The name of the file you wish to view must be specified
Cause: VIEW. The VIEW command was specified without specifying the name of the file to view.
Action: To view the PC DOS 7 Command Reference, type:
To view the PC DOS Error Messages, type:
To view REXX information, type:
The new Stacker header is 0 bytes
Cause: DCONVERT. During the preliminary processing of this Stacker utility, it was determined that the header
of your CVF (compressed volume file) could not be converted. A return code of 0 is given. The data on the
file is not affected.
Action: Rerun DCONVERT. If you get the same error, you can try uncompressing your drive using the
compression product that created the CFV originally. Then reinstall Stacker compression.
The only startable partition on Drive 1 is already set active
Cause: FDISK. You specified setting your primary partition active. The partition is already active and only one
can be set active at a given time.
Action: No action is required.
There is not enough disk space for system files
Cause: FORMAT. The disk has too much data stored on it.
Action: Delete some files from this disk to increase the disk space, or use another disk.
There is not enough memory to perform this task
Cause: VIEW. An out of memory condition occurred.
Action: You need to free up more conventional memory. There are several things you could do.
o Copy old files from your system onto a diskette and then delete them from your system.
o Delete old files or files not used.
o Run MEM /c to see if there are any programs that can be loaded high.
After you have freed up more memory, rerun VIEW.
Too many arguments in command line
Cause: MORE. You have specified too many or conflicting parameters with the command.
Action: Make sure the syntax of the command is correct, and that you only specify one process at a time. For
syntax information, type help followed by the command name at the command prompt.
Too many block devices
Cause: IBMBIO. You attempted to install more than the system limit of 26 block device units.
Action: Change the DEVICE value in the CONFIG.SYS file so there are only 26 block device units (including those
automatically installed by DOS for disk drives). See the PC DOS 7 User's Guide for more information.
Too many code pages specified
Cause: DISPLAY.SYS. The number of code pages you specified to be supported on your display device is not
within the range of the valid values. For EGA or VGA displays, the value can be between 0 and 6.
Action: Edit the display device statement in your CONFIG.SYS file to specify the correct value; then, restart your
computer. The following is an example of what the display device statement looks like:
The n represents the number of code page fonts you want to load or use.
Too many files
Cause: E. The number files you tried to edit exceeded 39. The editor does not allow more than 39 files in a
Action: Decrease the number of files in the ring.
Too many files open
Cause: COMP or LABEL. You attempted to open the specified file, but were not able to.
Action: Increase the FILES value in the CONFIG.SYS file.
Too many parameters
Cause: COMMANDS. Too many positional parameters were entered on the command line.
Action: Review the command syntax and re-enter the command.
Too many rings
Cause: E. You tried to open too many file rings.
Action: Decrease the number of rings you want to edit.
Too much of memory fragmentation; MEM /C cannot be done
Cause: MEM. The memory is too fragmented, or an application that ran before the MEM /c command has
damaged the memory areas.
Note: The MEM command can still be used alone or with the /p switch.
Action: Restart your computer, or, if you are using PC DOS through a DOS box (such as a windowing-type
program), close the windowing-type program and try again.
Please see the LEGAL - Trademark notice.
Feel free - send a for any BUG on this page found - Thank you.