home *** CD-ROM | disk | FTP | other *** search
Text File | 1993-03-01 | 188.0 KB | 4,816 lines |
- Microsoft MS-DOS Version 5.0 Messages Reference
-
-
- Instructions:
- ---------------
-
- This document contains an alphabetical listing of the Microsoft(R) MS-DOS(R)
- version 5.0 messages and their descriptions. For other software messages,
- such as network or application program messages, refer to the documentation
- for your particular program.
-
- If you cannot find an MS-DOS message in this reference, check in the
- beginning of the reference. The message may begin with a replaceable
- parameter. A replaceable parameter is a place holder that is identified
- by a word enclosed in angle brackets < >. For example, in this reference,
- you may see the message "<Number> searched, <number> subdirectories
- found." On your screen, you would see the bracketed words "number"
- replaced by a number. The same thing is true for a drive letter, filename,
- command, directory, utility, and so forth.
-
-
- What you see in this reference What you see on your screen
- ------------------------------------- ------------------------------------
-
- Current time is <time> Current time is 11:45:38.01a
- Enter new time: Enter new time:
-
-
- File <filename> canceled by operator File REPORT.DOC canceled by operator
-
-
- <Utility> already installed FASTOPEN already installed
-
-
- Messages:
- -----------
-
- *
-
- This is the Edlin prompt. Start typing text here. For help, type ? at
- the prompt.
-
- /B invalid with a black and white printer
-
- You can use the /b switch with the GRAPHICS command with only COLOR4
- and COLOR8 printers. Do not use the /b switch in combination with the
- /r switch, or if you have a black and white printer.
-
- /DT was specified. Because there is no delete tracking file for this drive,
- the UNDELETE command cannot continue.
-
- Because there was no PCTRACKER.DEL deletion-tracking file, the UNDELETE
- command was canceled. You may be able to restore files from data
- contained in directory files by using the UNDELETE command with the /dos
- switch. You create the tracker file when you use the MIRROR command with
- the /t switch.
-
- <Filename> Contains <number> non-contiguous blocks
-
- The files you specified are fragmented. To reduce fragmentation, make
- new copies of the files. Reducing file fragmentation helps your system
- read and write information more quickly.
-
- <Filename> File not found
-
- MS-DOS could not find the file that you specified. Make sure you typed
- the filename and path correctly.
-
- <Filename> longer than <filename>
-
- The FC command will only compare binary files that are the same length.
- FC will compare the two files until it reaches the end of the shorter
- file.
-
- <Number> bytes disk space freed
-
- The specified number of bytes previously used by file fragments are now
- free for other programs to use.
-
- <Number> bytes disk space would be freed
-
- The CHKDSK command identified the number of bytes currently used by
- file fragments. If you want to free these bytes, use the CHKDSK command
- with the /f switch. Then reply no to the message "Convert lost chains
- to files?"
-
- <Number> bytes in bad sectors
-
- This is the number of unusable sectors on your disk. The FORMAT command
- marked them as unusable when the disk was formatted. MS-DOS will not use
- these sectors.
-
- <Number> code page driver cannot be initialized
-
- The DISPLAY.SYS or PRINTER.SYS device driver in your CONFIG.SYS file is
- invalid or unrecognizable. Correct the command in your CONFIG.SYS file.
- Make sure you specified the correct code page and that the code page
- file exists. Then restart your computer.
-
- <Number> extended memory handles available.
-
- The HIMEM extended-memory manager is making available the indicated
- number of extended-memory-block handles.
-
- <Number> files recovered.
-
- Either the RECOVER command saved the indicated number of files, or the
- UNFORMAT command restored the indicated number of files.
-
- <Number> is not a choice. Please enter <number>-<number>
-
- You selected an invalid option. Select a valid option from the range
- shown.
-
- <Number> lost allocation units found in <number> chains
-
- Your disk contains some fragments of information that are not linked
- to any file or directory. Use the CHKDSK command with the /f switch
- to fix the errors.
-
- <Number> searched, <number> subdirectories found.
-
- While attempting to restore a disk without a Mirror image file, the
- UNFORMAT command searched through the entire disk for residual
- subdirectory information left by the FORMAT command.
-
- <Program> not installed
-
- To use this command, install the specified program first.
-
- <Utility> already installed
-
- This utility has already been installed. It stays in memory until you
- restart your computer. Reinstall the utility only if you restart your
- system.
-
- A20 Hardware Error
-
- There was an error in the high memory area. Restart your computer,
- and try again. If you still get this message, load MS-DOS into the
- low memory area. To do this, remove the DOS=HIGH command line in your
- CONFIG.SYS file, and restart your computer.
-
- A copy of the EGA Device Driver is already loaded.
-
- You tried to load the EGA device driver more than once. Make sure the
- CONFIG.SYS file contains only one device command loading the EGA.SYS
- device driver.
-
- A copy of the EGA Device Driver is not installed.
-
- The EGA device driver could not be installed. Make sure the device
- command in your CONFIG.SYS file that loads the EGA.SYS device driver
- has the correct syntax.
-
- A filename with that first character already exists.
- Press any key and then re-type the first character.
-
- The character you typed as the first character of a filename would
- result in a filename identical to that of an existing file. Press
- a key to continue, and then type a different letter.
-
- A suspected MIRROR file starting at sector number has been found.
-
- While searching the disk for a Mirror image file, the UNFORMAT
- command found what appears to be an image file at the specified
- location. MIRROR will continue searching the disk for another
- Mirror image file.
-
- Abort edit (Y/N)?
-
- Type y to quit without saving your edits, or n to stay in Edlin.
-
- Abort, Retry, Ignore, Fail?
-
- This message may appear with all four of the listed options, or only
- two or three. It appears when an error has occurred in a program, and
- MS-DOS cannot continue without your instruction. This message often
- occurs when there is an error in writing to or reading from a device,
- such as a disk drive or a communications port.
-
- To stop the program that caused the error, type a. To try again, type r.
- Use the "Retry" option if you have fixed the error (for example, if your
- disk was write-protected and you removed the write-protect tab). To
- continue as though the error did not occur, type i. Note that the system
- may become unstable, and you may lose data if you type i to ignore the
- error. To allow the program to handle the error, type f. The program
- will process the error, and will either continue or end, depending upon
- the error and the behavior of the program.
-
- Access denied
-
- You tried to write to a read-only file, the file is already being used
- by another program or person on a network, or you don't have writing
- privileges for this file on a network. Use the ATTRIB command to see
- if the file is read-only. If it is read-only and you want to write to
- this file, use the ATTRIB command with the -r switch to remove the
- read-only attribute. Otherwise, make sure another program isn't using
- this file. If you are on a network and you do have privileges for this
- file, another person may be using this file. Wait a while and then try
- again.
-
- Active code page for device <device> is <number>
-
- This message specifies the current code page used by the device.
-
- Active code page not available from CON device
-
- Your screen does not support the code page the system is currently
- using.
-
- Active Code Page: <number>
-
- The system is currently using the indicated code page. If the active
- code page is "none," no code page was loaded before you used the
- GRAFTABL command. If the active code page is "non-standard," GRAFTABL
- does not recognize the current code page in memory.
-
- Add <filename>? (Y/N)
-
- Type y if you want to add the file to the disk, or n if you do not
- want to add the file.
-
- All available space in the Extended DOS Partition
- is assigned to logical drives
-
- There is no more room for logical drives in the extended partition.
-
- All files canceled by operator
-
- All files in the print queue were canceled. This message appears on
- your network printer screen.
-
- All files in directory will be deleted!
- Are you sure (Y/N)?
-
- Type y to delete all the files in the directory, or n to cancel the
- command. To see what files are in the directory before deleting them,
- type n and use the DIR command to view the files.
-
- All logical drives deleted in the Extended DOS Partition
-
- You have deleted all logical drives in the extended MS-DOS partition
- on your disk.
-
- All of the clusters for this file are available. Undelete (Y/N)?
-
- The UNDELETE command can completely restore the deleted file because
- all of its contents are still available on the disk. To undelete the
- file, type y. To leave the file deleted, type n.
-
- All specified file(s) are contiguous
-
- All of the files you specified are written on the disk sequentially;
- none are fragmented.
-
- Allocation error, size adjusted
-
- The size of the indicated file was not consistent with the amount of
- data actually allocated to the file. MS-DOS updated your directory entry
- to reflect the actual size of the file.
-
- An incompatible DOSKey is already installed
-
- There is more than one version of the Doskey program on your computer,
- and the installed version is incompatible with your system. Locate all
- versions of the program, and delete all but the correct one. If you are
- unsure which version to use, use the EXPAND command to expand and copy
- the correct version from your MS-DOS installation disks.
-
- Another program has control of the INT 2FH function number. Cannot Load
- EGA Device Driver.
-
- Other software has taken control of the default or user-specified
- Interrupt 2Fh function number. As a result, loading the EGA device
- driver could produce unpredictable results, and the loading process was
- canceled. Specify a different INT 2Fh function number in the EGA
- command line.
-
- ANSI.SYS must be installed to perform requested function
-
- To perform the screen function you requested, the ANSI.SYS device
- driver must be loaded. Include a device command in your CONFIG.SYS
- file such as DEVICE=C:\DOS\ANSI.SYS, and restart your computer.
-
- APPEND already installed
-
- The APPEND command is already installed on your system. It will stay
- in memory as long as your system is on. Reinstall APPEND only if you
- restart your system.
-
- APPEND / ASSIGN Conflict
-
- If you are going to use both the APPEND and ASSIGN commands, use APPEND
- before you use the ASSIGN command for the first time. Also, you cannot
- append directories on a drive letter created with the ASSIGN command.
-
- APPEND / TopView Conflict
-
- If you use TopView(R), start it before you use the APPEND command for
- the first time.
-
- Are you sure (<Y>/<N>)?
-
- Type y to continue, or n to quit.
-
- Are you sure you want to do this?
- If so, press Y; anything else cancels.
-
- The UNFORMAT command can partially rebuild the disk using residual
- information left by the FORMAT command. Type y if you want to rebuild
- the disk using the residual information. Press any other key to
- cancel the unformatting process.
-
- Are you sure you want to update the system area of your drive <letter> (Y/N)?
-
- Type y if you want to restore the disk to the condition before it was
- formatted or before you used the MIRROR command. If you want to leave
- the disk as it is, type n.
-
- Attempting to recover allocation unit <number>
-
- The FORMAT command detected a potentially corrupted allocation unit
- while trying to format the disk. It is now checking to see if the
- allocation unit is usable.
-
- ***Backing up files to drive <letter>: ***
- Diskette Number: <number>
-
- The BACKUP command displays this message while backing up files to
- the drive you specified. Be sure to label backup disks with the
- appropriate number. This will make it easier for you to restore files
- later.
-
- Bad command line syntax
-
- The COMP command contained too many filename parameters, or your
- response to the "Option" prompt was not preceded by a slash ( / )
- character or a minus (-) character.
-
- Bad command or file name
-
- MS-DOS couldn't interpret what you typed at the command prompt. Make
- sure you typed the command properly. Also make sure the file or program
- is on the disk, in the directory you specified, or in the search path.
-
- Bad command or parameters
-
- There is a syntax error in a command in your CONFIG.SYS file. Correct
- the command or parameters, and restart your computer.
-
- Bad numeric argument :
- <number>
-
- You did not supply a valid number for the /n switch with the COMP
- command. (The number field can only contain numbers between 0 and 9.)
-
- Bad or Missing Command Interpreter
-
- The command interpreter cannot be found. Restart your system from
- another system disk, and then check the CONFIG.SYS file of your original
- system disk for a SHELL command. If there is a SHELL command, make sure
- the path to the command interpreter is correct. If there is no SHELL
- command, either make sure there is a copy of the COMMAND.COM file in the
- root directory of the startup drive on the system disk, or add a SHELL
- command specifying the location of the COMMAND.COM file or an alternate
- command interpreter.
-
- Bad or missing Keyboard Definition File
-
- Make sure the KEYBOARD.SYS file is in your DOS directory, current
- directory, or root directory. You can also specify its path with the
- KEYB command, or in your CONFIG.SYS file with the install command. If
- you get this message again, the KEYBOARD.SYS file may be corrupted. Use
- the EXPAND command to expand and copy the file from your MS-DOS
- installation disks.
-
- Bad Partition Table
-
- There is no DOS partition on your hard disk. Use the FDISK command to
- create a primary DOS partition.
-
- Bad sector being bypassed.
-
- There is an unusable sector on the disk being restored. The UNFORMAT
- command is marking it to prevent its further use.
-
- Batch file missing
-
- Make sure the batch program exists and that you've typed the name
- correctly. Also confirm that it is in the search path or in the
- current directory. If this message occurs while running the batch
- program, there may be a command in the batch program that deletes
- or renames the batch program, or makes it inaccessible. Check the
- syntax of the batch program to determine the cause.
-
- Baud rate required
-
- Specify a baud rate so the MODE command can initialize the COM port.
-
- Because your source drive is either ASSIGNed, JOINed, or SUBSTed it is
- actually the same as the target drive
-
- Specify a source drive that is different from the target (destination)
- drive.
-
- Because your target drive is either ASSIGNed, JOINed, or SUBSTed it is
- actually the same as the source drive
-
- Specify a target (destination) drive that is different from the source
- drive.
-
- Cannot change BUFSIZE
-
- The Doskey program is already installed. To change the /bufsize switch,
- reinstall DOSKEY with the /reinstall and /bufsize switches. If you need
- to conserve memory, you can also restart your computer and install
- DOSKEY with just the /bufsize switch, because reinstalling with the
- /reinstall switch does not remove the previous Doskey program from
- memory.
-
- Cannot CHDIR to <directory name>
- tree past this point not processed
-
- The CHKDSK command checked the structure of the directory and was
- unable to change to this directory. None of the subdirectories in
- this directory will be verified.
-
- Cannot CHDIR to root
-
- The CHKDSK command could not change to the root directory, and was
- unable to continue checking the remaining subdirectories. Restart
- your computer. If you still get this message, the disk is damaged
- and should be reformatted.
-
- Cannot CHKDSK a network drive
-
- You cannot use the CHKDSK command on drives that have been redirected
- over the network.
-
- Cannot CHKDSK a SUBSTed or ASSIGNed drive
-
- You cannot use the CHKDSK command on drives that have been substituted
- or assigned. Use the original drive letters while running CHKDSK.
-
- Cannot <command> a network drive
-
- You cannot use this command on a network drive.
-
- Cannot <command> a SUBSTed or ASSIGNed drive
-
- You cannot use this command on a drive that has been redirected by
- using the ASSIGN command, or substituted using the SUBST command.
-
- Cannot create a zero size partition
-
- You can only create a partition with a size greater than zero. Using
- the FDISK command, specify the size of the partition in megabytes or
- the percentage of unused disk space. If you type a percentage, follow
- the number with a percent (%) sign. If you are creating an extended
- DOS partition and there is no room left, delete and recreate a smaller
- primary DOS partition. Or, reduce the size of any non-DOS partitions
- that exist.
-
- Cannot create Extended DOS Partition without
- Primary DOS Partition on disk 1
-
- You cannot create an extended DOS partition unless you already have
- a primary DOS partition. Create the primary DOS partition on your
- first hard disk. Then, if you have room on that disk or if you have
- a second hard disk, you can create an extended DOS partition.
-
- Cannot create Logical DOS Drive without
- an Extended DOS Partition on the current drive
-
- You must create an extended DOS partition before any logical drives
- can be created.
-
- Cannot delete Extended DOS Partition while logical drives exist
-
- Delete all logical drives using the FDISK command. Then, delete the
- extended DOS partition.
-
- Cannot delete <filename>.
-
- If there is not enough disk space for expanding an entire file, the
- EXPAND command will try to delete the portion of the file that was
- expanded before disk space ran out. If the file cannot be deleted,
- this message appears.
-
- Cannot delete Primary DOS Partition on drive 1
- when an Extended DOS Partition exists
-
- All extended DOS partitions must be deleted before deleting a
- primary DOS partition.
-
- Cannot DISKCOMP to or from a network drive
-
- You cannot use the DISKCOMP command to compare disks over a network
- drive. To compare two files over a network, use the COMP or FC command.
-
- Cannot DISKCOPY to or from a network drive
-
- You cannot use the DISKCOPY command to copy disks over a network drive.
- To copy individual files over a network, use the COPY command.
-
- Cannot do binary reads from a device
-
- A device cannot perform a binary read. Use the COPY command with the
- /a switch to perform a binary read.
-
- Cannot edit .BAK file--rename file
-
- You cannot edit an Edlin file with a .BAK extension. To edit a backup
- file, rename the file with an extension other than .BAK.
-
- Cannot execute <filename>
-
- MS-DOS cannot run the file you specified. You may have run out of
- memory; access may be denied; or the file may be corrupt. Confirm that
- you have enough memory to run the program, and make sure the program
- isn't locked by a program such as SHARE. If the file is corrupt, you
- cannot use this copy of the program. Use a backup or master copy. If
- you are trying to use the file from a network server, make sure you
- have permission to access the file.
-
- Cannot FDISK with network loaded
-
- You cannot use the FDISK command while you are connected to a network.
- Disconnect from the network before using FDISK.
-
- Cannot find FORMAT.COM
-
- Add the directory containing your FORMAT.COM file to the path, or copy
- it to the directory containing the BACKUP.EXE file.
-
- Cannot find GRAPHICS profile
-
- MS-DOS cannot find the specified printer profile. Make sure you typed
- the correct path and filenames. If you are using the standard profile
- file, GRAPHICS.PRO, make sure it is in the same directory as the
- GRAPHICS.COM file. If you cannot find GRAPHICS.PRO, use the EXPAND
- command to expand and copy the file from your MS-DOS installation disks.
-
- Cannot find System Files
-
- MS-DOS cannot find IO.SYS, MSDOS.SYS, and COMMAND.COM on your hard disk.
- Make sure the disk with which you started your computer is available.
-
- Cannot format a network drive
-
- You specified a network drive. You cannot format drives that are
- redirected over a network.
-
- Cannot format an ASSIGNed or SUBSTed drive.
-
- You cannot format a disk drive that has been created using the ASSIGN
- or SUBST commands. Use the ASSIGN command followed by the /status switch
- or the SUBST command to determine the true path of a logical drive. Then
- format the physical disk drive from which the logical drive originates.
- If you used the SUBST command to associate a path with a drive letter,
- format the entire disk containing the path. Before formatting a disk,
- make sure you have backup copies of all the files you want to save.
-
- Cannot FORMAT nonremovable drive <letter>:
-
- The BACKUP command does not format a hard disk. If you are sure you want
- to back up files to a hard disk, use the FORMAT command to format it,
- or use a hard disk that is already formatted.
-
- Cannot install. Already resident, or unknown status.
-
- You used the MIRROR command with the /t switch a second time since
- restarting your computer. If you want the Mirror program to track file
- deletions on an additional drive, remove it from memory using the
- MIRROR command with the /u switch. You can then use the MIRROR command
- with the /t switch for each drive you want to track.
-
- Cannot label a JOINed, SUBSTed or ASSIGNed drive
-
- You cannot create a volume label for a drive prepared with the JOIN,
- SUBST, or ASSIGN command.
-
- Cannot label a network drive
-
- You selected a network drive to label, but you cannot create a volume
- label for a network drive.
-
- Cannot load COMMAND, system halted
-
- Your system cannot load the COMMAND.COM file. One of the following may
- be the problem:
-
- * The COMMAND.COM file may be damaged.
-
- * Another program may have damaged memory.
-
- * Another program may have left too little memory to start COMMAND.COM.
-
- * The system could not locate COMMAND.COM.
-
- Use a system disk to restart your computer. If memory was damaged,
- that may solve your problem. If not, make sure both the SHELL command
- in your CONFIG.SYS file and COMSPEC command in your AUTOEXEC.BAT file
- point to a valid version of COMMAND.COM. If you suspect COMMAND.COM was
- damaged, use the EXPAND command to expand and copy COMMAND.COM from
- your MS-DOS installation disk.
-
- Cannot Loadhigh batch file
-
- You cannot load a batch program (.BAT file) into upper memory. You can
- load only executable (.EXE) or command (.COM) programs into the upper
- memory area with the LOADHIGH command.
-
- Cannot make directory entry
-
- The utility did not create the directory entry or volume label because
- the disk or root directory is full. There can be no more than 512 files
- and directories in the root directory of your hard disk. Move or delete
- some files to free disk space, or use another disk.
-
- Cannot open <filename> - <reason>
-
- The file cannot be opened. Resolve the specified problem and try again.
-
- Cannot open specified country information file
-
- Check the COUNTRY command in your CONFIG.SYS file to make sure you
- specified the correct path to the COUNTRY.SYS file. Make any necessary
- corrections, and restart your computer.
-
- Cannot operate on a SUBST drive.
-
- You cannot use the UNDELETE command to restore files on a drive created
- by the SUBST command. To restore files on this drive, return the drive
- and directory to its original path. Then you can use the UNDELETE
- command on this directory.
-
- Cannot operate on specified drive (<letter>). It may be a network drive.
-
- You cannot use the UNDELETE command to restore files on a network
- drive. UNDELETE works only on drives installed in or attached directly
- to your system.
-
- Cannot perform a cyclic copy
-
- When using the XCOPY command followed by the /s switch, you cannot
- copy to any subdirectories that are a subset of the directory you are
- copying from. Specify a destination that is not a subdirectory of the
- source directory.
-
- Cannot process a network, SUBST, or unrecognized disk.
-
- The UNFORMAT command cannot determine the type of disk drive that you
- specified with the UNFORMAT command. It may be a network drive, a drive
- created using the SUBST command, or a disk of unknown format.
-
- Cannot process network drive.
-
- The UNFORMAT command can restore disks on drives installed in or
- directly connected to your system. It cannot restore network drives.
-
- Cannot read file allocation table
-
- Use the CHKDSK command with the /f switch to correct the problem. If
- you still get this message, you may have to format the disk. You can
- also try to restore the file allocation table (FAT) using the MIRROR
- command. If you still get this message while using a hard disk, call
- your hardware vendor.
-
- Cannot read system area of disk.
-
- The UNFORMAT command could not read the file allocation table (FAT),
- or the root directory of the disk. The disk may be damaged or not
- formatted properly. Use the CHKDSK command with the /f switch to see
- if you can fix the problem. If not, you cannot unformat this disk.
- Format the disk again.
-
- Cannot recover . entry, processing continued
-
- The "." entry (current directory) is corrupt and cannot be recovered.
- Move the files in this directory elsewhere and delete the directory.
-
- Cannot recover .. entry
-
- The ".." entry (parent directory) is corrupt and cannot be recovered.
- Move the files in this directory elsewhere and delete the directory.
-
- Cannot RECOVER a network drive
-
- You cannot recover files on drives that are redirected over a network,
- or on files that are located on a network drive.
-
- Cannot RECOVER an ASSIGNed or SUBSTed drive
-
- You cannot recover files on disk drives that were created using the
- ASSIGN or SUBST commands. Type either the ASSIGN command or the SUBST
- command with the /d switch at the command prompt to reset all drive
- letters to their original assignments.
-
- Cannot setup expanded memory
-
- There is no EMS (expanded memory) page frame above 640K. Make sure
- the page frame address is greater than 8000h. If you are using the
- EMM386 expanded-memory manager, confirm that you set the frame switch
- to none.
-
- Cannot specify both /DT and /DOS.
-
- The UNDELETE command contained both the /dt and /dos switches.
- UNDELETE can use only one method at a time to restore files. Retype
- the command and specify only one of these two switches, or type HELP
- UNDELETE at the command prompt to see the correct syntax for this
- command.
-
- Cannot specify default drive
-
- You cannot specify the default drive as both the source and destination
- for the system files. If the system files are in the default drive,
- specify a different drive for the destination.
-
- Cannot start COMMAND, exiting
-
- Your system cannot load COMMAND.COM. Use a system disk to restart your
- computer. Then make sure the COMSPEC environment variable is set
- correctly.
-
- Cannot unload resident deletion-tracking software. Vectors or memory have
- been altered.
-
- You tried to unload your deletion-tracking program from memory using
- the MIRROR command with the /u switch. However, another program changed
- the internal state of your system such that removing the Mirror program
- from memory could cause unpredictable results. If you still want to
- remove the Mirror program from memory, restart your computer.
-
- Cannot unload. Deletion-tracking software is not resident or is a different
- version.
-
- Either you did not use the MIRROR command with the /t switch to load the
- Mirror program as a memory-resident (TSR) program, or you are attempting
- to remove the Mirror program from memory with a different version of the
- MIRROR command than you used to load it. To unload the Mirror program,
- locate and use the version of the MIRROR.COM file you used to start
- Mirror.
-
- Cannot use FASTOPEN for drive letter
-
- You cannot use the FASTOPEN command over a network, on a floppy disk,
- or on substituted drives.
-
- Cannot use PRINT - Use NET PRINT
-
- Because the PSPRINT print spooler has been loaded, use the NET PRINT
- command to print files over a network if you are using a Microsoft(R)
- LAN Manager or Microsoft(R) MS-NET compatible network.
-
- Cannot write file allocation table
-
- Use the CHKDSK command with the /f switch to identify the problem. If
- you still get this message, you may have to reformat the disk. If you
- continue to get this message with a hard disk, call your hardware
- vendor.
-
- Cannot XCOPY from a reserved device
-
- To copy files or directories from a device, use the COPY command instead
- of the XCOPY command.
-
- Cannot XCOPY to a reserved device
-
- To copy files or directories to a device, use the COPY command instead
- of the XCOPY command.
-
- Can't copy date and time stamp from input file: <filename>
-
- Generally, the date and time for the expanded file is set to the same
- date and time stamp as the compressed file. However, MS-DOS cannot
- read the date and time of the input (source) file.
-
- Can't copy date and time stamp to output file: <filename>
-
- Generally, the date and time for the output (expanded) file is set
- to the same date and time stamp as the compressed file. MS-DOS could
- read the date and time of the source file, but the stamps could not be
- copied to the expanded file.
-
- Can't find/open file: <filename>
-
- Make sure the filename is correct, and is not the name of a directory.
-
- Can't open input file: <filename>
-
- Make sure the input (source) file exists, and that another program is
- not using it.
-
- Can't open output file: <filename>
-
- The specified file cannot be opened. There may be too many files open
- already, the path may not be valid, and the destination filename may
- be the same as an existing directory name. Also, the file may be
- read-only, locked, or on a write-protected disk. Make sure you have
- correctly specified the path and filenames, and that the filename is
- not the same as an existing directory name. Use the ATTRIB command to
- see if the file is read-only, and make sure the SHARE command has not
- locked the file. If the destination file is on a floppy disk, make sure
- the disk is not write-protected. If you have other files open, close
- some files so the new file can be opened.
-
- Can't read file: <filename>
-
- The COMP command cannot read the specified file. Make sure the file is
- not locked or in use by another program. The file might also be
- corrupted or located on a bad sector. If this is the case, use a
- backup copy of the file.
-
- Can't read from input file: <filename>
-
- The input (source) file may be corrupted.
-
- Can't write to output file: <filename>
-
- Either a disk error has occurred, or access to this file has been
- denied. The file may be a read-only or locked file. Use the ATTRIB
- command to see if the file is read-only, and make sure the SHARE
- command has not locked the file. If you suspect a disk error, use the
- CHKDSK command with the /f switch to fix any errors on the disk.
-
- Checking existing disk format
-
- The format command is determining the disk type so it can save
- necessary information for the UNFORMAT command.
-
- Checking for file fragmentation...
-
- While restoring a disk without a Mirror image file, the UNFORMAT
- command is recovering files by tracing their entries in the file
- allocation table (FAT).
-
- CHKDSK /F cannot be done in a Windows/DosShell Command Prompt
-
- Quit Microsoft Windows(TM) or MS-DOS Shell before running the CHKDSK
- command with the /f switch.
-
- CHKDSK not available on drive <letter>
-
- You cannot use the CHKDSK command on the specified drive. For example,
- the drive may be a network drive, or was formed by the SUBST, ASSIGN,
- or JOIN command.
-
- Code page not prepared
-
- To prepare a device for a code page, add the correct device command
- to your CONFIG.SYS file, if necessary, and restart your computer.
- Then use the MODE CODEPAGE PREPARE command to prepare the code page.
- If you have installed the DISPLAY.SYS device driver, be sure the
- device command in your CONFIG.SYS file allows for additional code
- pages.
-
- Code page <number> not prepared for all devices
-
- The specified code page has not been loaded into memory for every
- device. To prepare a device for a code page, add the correct device
- command to your CONFIG.SYS file, if necessary, and restart your computer.
- Then use the MODE CODEPAGE PREPARE command to prepare the code page for
- each device.
-
- Code page <number> not prepared for system
-
- The specified code page has not been loaded into memory. To prepare a
- device for a code page, add the correct device command to your CONFIG.SYS
- file, if necessary, and restart your computer. Then use the MODE CODEPAGE
- PREPARE command to prepare the code page.
-
- Code page operation not supported on this device
-
- You have specified an invalid device and code page combination. Confirm
- that the device you specified exists and that you have specified a
- valid code page. Also make sure that code page is supported by that
- device.
-
- Code page requested (<number>) is not valid for given keyboard code
-
- The keyboard code and code page specified are not compatible. Retype
- the KEYB command with a compatible keyboard code and code page.
-
- Code page specified has not been prepared
-
- To prepare a device for a code page, add the correct device command to
- your CONFIG.SYS file, if necessary, and restart your computer. Then use
- the MODE CODEPAGE PREPARE command to prepare the code page. If you have
- installed the DISPLAY.SYS device driver, be sure the device command
- in your CONFIG.SYS file allows for additional code pages.
-
- Code page specified is inconsistent with the selected code page
-
- The code page you selected for your keyboard is not consistent with
- the code page for your console screen device (CON). Use the MODE CODEPAGE
- SELECT command if you want to change the code page for CON.
-
- Command line parameters:
- FUNC=XX, to change INT 2FH function number.
- (where XX is 80 through FF hexadecimal inclusive)
- For example: DEVICE=EGA FUNC=AC
- Number passed to FUNC is invalid. See example above.
-
- This message shows the syntax for the device command in your CONFIG.SYS
- file that loads the EGA.SYS device driver. In the example shown, the
- function number for Interrupt 2Fh is changed to the hexadecimal value
- ACh. The default value is BCh. Change the function number only if other
- software uses Interrupt 2Fh function BCh.
-
- Compare another diskette (Y/N) ?
-
- Type y if you want to compare more disks; type n if you don't.
-
- Compare error at LINE <number>
- file1 = <filename>
- file2 = <filename>
-
- The two files differ at the specified location (measured in number of
- lines) from the beginning of the file. This number is given in
- hexadecimal, unless you specified the /d or /a switch.
-
- Compare error at OFFSET <number>
- file1 = <filename>
- file2 = <filename>
-
- The two files differ at the specified location (measured in number of
- bytes) from the beginning of the file. This number is given in
- hexadecimal, unless you specified the /d or /a switch.
-
- Compare error on side <number>, track <number>
-
- The disks are not identical. They differ on the specified side and
- track.
-
- Compare OK
-
- The two disks are identical.
-
- Compare process ended
-
- The comparison is complete.
-
- Comparing files <filename> and <filename>
-
- The specified files are being compared.
-
- Comparing <number> tracks
- <number> sectors per track, <number> side(s)
-
- Tracks, sectors per track, and sides refer to the physical
- characteristics of the disk format.
-
- CON code page driver cannot be initialized
-
- There may be an error in your CONFIG.SYS file, or there isn't enough
- memory to set up the display configuration information. Check the device
- command in your CONFIG.SYS file to make sure the con command specifies
- a valid display name (EGA or LCD). For example, the following command
- installs the DISPLAY.SYS device driver for an EGA or VGA screen that has
- the 437 hardware code page:
-
- DEVICE=C:\DOS\DISPLAY.SYS CON=(EGA,437,1)
-
- If you ran out of memory, change the number of supported code pages to
- the actual number of code pages you use. You can also remove other
- devices that you do not need, or change the order of loading your
- devices and programs. When you have finished, restart your computer.
-
- Configuration too large for memory
-
- There was not enough memory available to carry out the commands in your
- CONFIG.SYS file. Restart your computer with a different system disk.
- Then, in your CONFIG.SYS file, remove some devices, reduce the amount of
- memory used by devices, or reduce the number of files or buffers the
- system uses. When you have finished, restart your computer.
-
- Content of destination lost before copy
-
- You tried to combine several source files into one file. The destination
- file was also one of the source files. Therefore, instead of adding the
- other source files to the destination file, the destination file was
- overwritten before it could be copied. The original content of this file
- is lost. If you want to combine files with the destination file, list the
- destination file as the first source file.
-
- Continue (Y/N)?
-
- To continue, type y. To end the process, type n.
-
- Convert lost chains to files (Y/N)?
-
- Your disk contains some information that is not linked to any file or
- directory. If you type y, the chkdsk command will store this information
- in a file named FILEnnnn.CHK. You can view the contents of this file to
- determine if you want to save any of the information. If you type n,
- the CHKDSK command will free the disk space without saving the
- information.
-
- Copy another diskette (Y/N)?
-
- The DISKCOPY process is complete. Type y if you want to copy another
- disk, or n if you don't.
-
- Copy process ended
-
- The DISKCOPY command could not copy the entire disk because of errors.
- The destination copy is not complete. Use the COPY or XCOPY command to
- copy specific files to the disk.
-
- Copying <number> tracks
- <number> sectors per track, <number> side(s)
-
- Tracks, sectors per track, and sides refer to the physical
- characteristics of the disk format.
-
- Could not copy COMMAND.COM onto target disk
-
- COMMAND.COM could not be copied to the target (destination) disk. Before
- using the disk to start your computer, copy COMMAND.COM to the disk or
- create a CONFIG.SYS file on the disk, and specify your command
- interpreter with the SHELL command.
-
- Could not expand second filename so as to match first
-
- The FC and COMP commands expand wildcard characters in the second
- filename to match appropriate characters in the first filename. The
- wildcards must match or this expansion will fail. Make sure the
- wildcard characters match, or type the filenames without wildcard
- characters.
-
- Could not successfully undelete the file. Press A to abort or R to retry
-
- The UNDELETE command could not restore the file. To cancel the process,
- type a. To attempt to restore the file again, type r.
-
- Current code page settings:
-
- Shows current and prepared code pages for the specified device and for
- the system.
-
- Current date is <date>
- Enter new date (mm-dd-yy):
-
- Type a new date in the indicated format. If the displayed date is
- correct, press ENTER.
-
- Current drive is no longer valid
-
- Your current drive is either a network drive that is no longer connected,
- or a disk drive with no disk in it. Change to a valid drive, or insert a
- disk in the floppy disk drive.
-
- Current fixed disk drive:
-
- Shows the current hard disk. The first (or only) hard disk is 1, the
- second is 2, and so on. This message applies only to physical, not
- logical, disk drives when using the FDISK program.
-
- Current keyboard does not support this code page
-
- Make sure you specified the correct code page. If the code page is
- correct, use the KEYB command to change the keyboard code to one that
- is supported by the new code page.
-
- Current keyboard ID: <number>
- code page: <number>
- Current CON code page: <number>
-
- This message displays the current keyboard code and its associated code
- page, as well as the current code page used by your console screen
- device (CON).
-
- Current time is <time>
- Enter new time:
-
- Type a new time in the indicated format. If the time is already correct,
- press ENTER.
-
- Data error
-
- There was an error when the device read the disk. Retry the process, or
- use a new disk. If the error is on your hard disk, run a diagnostic
- program such as the CHKDSK program to see if your hard disk is working
- correctly.
-
- Delete (Y/N)?
-
- Type y to delete the file, or n to continue without deleting the file.
-
- Delete current volume label (Y/N)?
-
- To delete the current volume label, type y. To cancel the process, type n.
-
- Delete Logical DOS Drive(s) in the Extended DOS Partition
- WARNING! Data in a deleted Logical DOS Drive will be lost.
-
- If you want to save files on this drive, make sure you have a backup
- before continuing.
-
- Delete tracking software must be installed before other PC Tools programs.
-
- If you use the Mirror program at the same time as other PC Tools
- programs, install the Mirror program first. Close the PC Tools programs,
- install Mirror using the MIRROR command with the /t switch, and then
- restart the PC Tools programs.
-
- Deleting crosslinked file.
-
- While restoring a disk without a Mirror image file, the UNFORMAT command
- found a file which has a file allocation table (FAT) entry belonging to
- another file. The UNFORMAT command cannot recover this cross-linked file.
-
- Deletion-tracking file contains <number> deleted files. Of those, <number>
- files have all clusters available, <number> files have some clusters
- available, <number> files have no clusters available.
-
- The UNDELETE command can completely restore only those files for which
- all clusters are available. If only some clusters are available,
- UNDELETE can partially restore the file. Generally, a partial file is
- useful only if it's a text file. UNDELETE cannot restore files for
- which no clusters are available.
-
- Deletion-tracking file not found.
-
- The UNDELETE command was unable to find the PCTRACKR.DEL file in the
- root directory of the drive on which files were being restored. Either
- you didn't use the MIRROR command to track file deletions on this drive,
- or the PCTRACKR.DEL file was deleted. You may be able to restore files
- by using UNDELETE with the /dos switch.
-
- Destination directory does not exist: <directory name>
-
- Make sure you specified an existing directory, and that you typed it
- correctly.
-
- Device <device> not prepared
-
- To prepare a device for a code page, add the correct device command to
- your CONFIG.SYS file, if necessary, and restart your computer. Then use
- the MODE CODEPAGE PREPARE command to prepare the code page.
-
- Device error during <(Status, Prepare, or Select)>
-
- Check the device command line in your CONFIG.SYS file. Make sure that
- the command syntax, limits for subfonts, and additional code pages are
- all correct. Also confirm that your device supports code-page switching.
- Consult your hardware vendor if you are unsure about your device
- supporting code page switching.
-
- Device or code page missing from font file
-
- MS-DOS did not find a definition of the indicated code page for this
- device in the font file (files with a .CPI extension). Make sure the
- font file supports the code page you want to use, or use the MODE
- command to specify another code page for this device. This error
- may also cause specified code pages to be undefined. Use the MODE command
- to prepare and refresh lost code pages.
-
- Directory already exists
-
- You cannot create two directories with the same name. Choose a new name
- for the directory you are creating, or rename or remove the old directory.
-
- Directory is joined
-
- The CHKDSK command does not process joined directories. If you want to
- check the joined directory, cancel the JOIN command by typing the JOIN
- command with the /d switch at the command prompt.
-
- Directory is totally empty, no . or ..
- tree past this point not processed
-
- The directory you specified does not contain references to "." (current)
- and ".." (parent) directories. Any subdirectories contained in this
- directory will not be checked by the CHKDSK command. Use the CHKDSK
- command with the /f switch to try to correct the error. If you still get
- this message, copy the files and subdirectories elsewhere and delete
- the directory.
-
- Directory <name>
-
- The CHKDSK command is processing the specified directory.
-
- Directory not empty
-
- You can only use the JOIN command to join onto an empty directory.
- Make sure the directory is empty before trying to join it.
-
- ** Disk error, BIOS code <number>.
- ** Disk error (BIOS code <number>) at cylinder <number>, drive <letter>.
-
- While attempting to restore the partitions of a hard drive, the
- UNFORMAT command could not access the hard drive. If you recently set
- up the drive, make sure it is properly installed. Otherwise, the disk
- may be corrupt. Back up any information you can, and then perform a
- low-level format on the disk.
-
- Disk error writing FAT <number>
-
- The CHKDSK command could not write to the file allocation table (FAT).
- Use the CHKDSK command with the /f switch to correct the error. If you
- still get this message with a hard disk, back up any information you can
- and reformat the disk.
-
- Disk full. Edits lost.
-
- There was not enough disk space to save the edits you made, so the edits
- could not be saved. Make sure there is enough disk space before editing
- the file again, and save frequently.
-
- Disk full error writing to BACKUP Log File
-
- Press a key to back up without a log file, or type CTRL+C to quit the
- backup.
-
- Disk <number> error. The boot sector for this drive is incompatible with
- the MIRROR command.
-
- Either the hard disk was not properly formatted, or the boot (startup)
- sector is corrupted. Make sure you have a backup of the information on
- this disk, and try to format the disk again.
-
- Disk unsuitable for system disk
-
- A corrupted track has been found in the area of this disk where the
- system information would be stored. You should use this disk to store
- data only. Use another disk to create a system disk.
-
- Divide overflow
-
- The program tried to divide by zero. There may be an error in the
- program.
-
- Do not specify filename(s)
- Command format: DISKCOMP drive1: drive2: [/1] [/8]
-
- Because the DISKCOMP command compares entire disks, you can specify only
- drive letters.
-
- Do not specify filename(s)
- Command Format: DISKCOPY drive1: drive2: [/1] [/v]
-
- Because the DISKCOPY command copies entire disks, you can specify only
- drive letters.
-
- Do you see the leftmost 0? (Y/N)
-
- The MODE command displays this message to help you align the test
- pattern on your screen. Type y if you can see the leftmost 0 in the
- test pattern, or type n if you want to shift the display to the right.
-
- Do you see the rightmost 9? (Y/N)
-
- The MODE command displays this message to help you align the test
- pattern on your screen. Type y if you can see the rightmost 9 in the
- test pattern, or type n if you want to shift the display to the left.
-
- Do you wish to use the maximum available size for a Primary DOS Partition
- and make the partition active (<Y>/<N>)?
-
- Type y to partition your entire hard disk as the primary active DOS
- partition. Type n to leave room to create extended DOS partitions, or
- if you do not want to make the partition active.
-
- Does name specify a file name
- or directory name on the target
- (F = file, D = directory)?
-
- The target (destination) file or directory does not exist. Type f if the
- destination you specified is a file, or d if the destination is a
- directory. Based on your response, the XCOPY command will create the file
- or directory for you.
-
- Does not exist
-
- Either the "." (current directory) or ".." (parent directory) entry does
- not exist. If you ran the CHKDSK command with the /f switch, run
- CHKDSK again to see if it was fixed. If you still get this message, move
- the files elsewhere and delete the directory.
-
- DOS is in HMA
-
- MS-DOS is running in or using the high memory area (HMA).
-
- DOS is in low memory
-
- MS-DOS is running in conventional, low memory, rather than from the
- HMA or ROM.
-
- DOS is in ROM
-
- MS-DOS is running in read-only memory (ROM).
-
- DOS version must be 2.0 or higher.
-
- This program cannot run with versions of MS-DOS lower than 2.0.
-
- DOSKey installed
-
- The Doskey program has been installed and will remain resident in
- memory until you restart your computer.
-
- Drive already SUBSTed
-
- You can only substitute a drive once. To change the substitution,
- remove the current substitution using the SUBST command with the /d
- switch, and then use the SUBST command again.
-
- Drive deleted.
-
- You deleted a volume or partition.
-
- Drive <letter> already deleted.
-
- You tried to delete the drive, but it has already been deleted.
-
- Drive <letter> cannot be inside volume label
-
- Specify a volume label with up to 11 alphanumeric characters. Do not
- include the drive letter in the volume label. Type HELP LABEL at the
- command prompt to see the correct syntax for this command.
-
- Drive <letter> could not be processed.
-
- The Mirror program could not record information about the specified
- disk drive, or the UNFORMAT command could not process the indicated
- drive. If the drive exists, the disk may be damaged.
-
- Drive <letter> error. Cannot update the MIRROR control file.
-
- An internal error occurred. Restart your computer and run the
- Mirror program again.
-
- Drive <letter> error. Could not close the MIRROR image file.
-
- An internal error occurred. Restart your computer and run the Mirror
- program again.
-
- Drive <letter> error. Could not open the MIRROR image file.
-
- The Mirror program could not open the MIRROR.FIL image file. The root
- directory of the disk may already contain the maximum number of files,
- or there may be too many files open in the system. If there are too many
- files in the root directory, delete or move one or more files in the
- root directory and then run the Mirror program again. Increase the value
- of the FILES command in your CONFIG.SYS file, and then restart your
- computer and run the Mirror program again.
-
- Drive <letter> error. Data was found in a file that appears to be a MIRROR
- control file. Cannot continue.
-
- The Mirror program found a file with a name other than MIRORSAV.FIL in
- the location generally occupied by the MIRORSAV.FIL control file. Most
- likely, the MIRORSAV.FIL file was renamed. Either rename the file to
- MIRORSAV.FIL, or delete the file and then run the Mirror program again.
-
- Drive <letter> error. Insufficient memory to read all system info.
-
- There is not enough memory available for the Mirror program to hold the
- system information for the indicated drive. Free memory by closing files
- and programs you no longer use. If you still get this message, remove
- memory-resident programs (TSRs) or unnecessary device drivers from your
- CONFIG.SYS file, and restart your computer.
-
- Drive <letter> error. Insufficient space for the MIRROR control file.
-
- Your disk is nearly full, and there is not enough room to hold the
- MIRORSAV.FIL control file on the indicated disk. Delete unnecessary
- files and run the Mirror program again.
-
- Drive <letter> error. Insufficient space for the MIRROR image file.
-
- Your disk is nearly full, and there is not enough room to hold the
- MIRROR.FIL image file on the indicated disk. Delete unnecessary files
- and run the Mirror program again.
-
- Drive <letter> error. There already is a MIRROR control file but it was
- not located in the last 25 percent of the data area. It has now been
- deleted and processing will continue.
-
- The clusters containing the MIRORSAV.FIL control file were not in
- the correct location. Most likely, a disk-compaction program relocated
- them. The Mirror program deleted the original file and created an
- updated version in the proper location on the disk.
-
- Drive <letter> error. There are no entries available in the root directory
- of the drive. Delete one or more files from the root directory.
-
- The Mirror program cannot create one or more files because the root
- directory already contains the maximum number of files. Delete or move
- one or more files in the root directory, and then run the Mirror program
- again.
-
- Drive letters have been changed or deleted
-
- You may have to make changes in any files that specify drive letters,
- because the drive letters may have changed. Check your AUTOEXEC.BAT
- and CONFIG.SYS files to be sure none of the commands have been affected.
-
- Drive types or diskette types
- not compatible
-
- The formats of the disks you want to compare or copy must be identical.
- This message appears if the disks you specified have different formats.
-
- Duplicate file name or file not found
-
- MS-DOS cannot find the file you want to rename, or there is another
- file in the directory using the new name. Make sure you typed the
- correct filename and path. If a file with that name already exists,
- rename or delete it or specify a different filename for the file you
- want to rename.
-
- Duplicate parameters not allowed
-
- You cannot specify a parameter twice. Type HELP followed by the command
- name to see the correct syntax.
-
- EMM386 already installed.
-
- Your CONFIG.SYS file may contain two device commands to set up EMM386.EXE,
- or you tried to install the EMM386 expanded-memory manager after it was
- already installed. If you have the device command for loading EMM386
- listed twice in your CONFIG.SYS file, remove one of the commands and then
- restart your computer.
-
- EMM386 DMA buffer is too small. Add D=nn parameter and reboot.
-
- A program that performs direct memory access (DMA) input and output
- requires a buffer larger than is currently provided by the EMM386
- expanded-memory manager. To use this program, add d=nnn to the device
- command in your CONFIG.SYS file that loads EMM386.EXE. If the command
- already includes this switch, increase the number of specified kilobytes.
- Then restart your computer to allow the changes to take effect.
-
- EMM386 driver not installed.
-
- You used the emm386 command without first installing the EMM386.EXE
- device driver. Edit your CONFIG.SYS file to include a device command
- that installs the EMM386 expanded-memory manager, and then restart your
- computer.
-
- EMM386: DMA mode not supported.
- Press ENTER to reboot.
-
- A program attempted to perform direct memory access (DMA) using a mode
- not supported by the EMM386 expanded-memory manager. The system has become
- unstable and must be restarted.
-
- EMM386 Exception error #
- <number> - press ENTER to reboot
-
- An internal error occurred. As a result, the system has become unstable.
- Press ENTER to restart your computer.
-
- EMM386 not installed - incorrect DOS version.
-
- The device command in your CONFIG.SYS file does not specify a version
- of EMM386.EXE that is compatible with the version of MS-DOS on your
- system. If you do not have a copy of the EMM386 expanded-memory manager
- that came with MS-DOS version 5.0, use the EXPAND command to expand and
- copy the correct version from your MS-DOS installation disks.
-
- EMM386 not installed - incorrect machine type.
-
- EMM386.EXE can run only on a computer based on an Intel 80386 or 80486
- or compatible microprocessor. The EMM386 expanded-memory manager was
- not installed.
-
- EMM386 not installed - insufficient memory.
-
- Not enough memory was available to install the EMM386 expanded-memory
- manager. Make sure that the device command in your CONFIG.SYS file
- that installs EMM386.EXE appears after the device command that installs
- the HIMEM extended-memory manager.
-
- EMM386 not installed - other expanded memory manager detected.
-
- Your CONFIG.SYS file contains a device command that installs an
- expanded-memory manager before the device command that installs
- EMM386.EXE. EMM386.EXE cannot run if an expanded-memory manager is
- already present.
-
- EMM386 not installed - protected mode software already running.
-
- You cannot install the EMM386 expanded-memory manager when other
- protected-mode software is running. The device command that installs
- EMM386.EXE must appear after the device command that installs the HIMEM
- extended-memory manager. Both must appear before other device commands
- in your CONFIG.SYS file that install protected-mode software.
-
- EMM386 not installed - unable to set page frame base address.
-
- The EMM386 expanded-memory manager could not find 64K of contiguous space
- for the page frame. Try to relocate one or more adapters in the region
- between 640K and 1 megabyte to free up some space for the page frame. Or
- if you know that E000 is free, you can specify frame=E000.
-
- EMM386 not installed - XMS manager not present.
-
- A device command to install HIMEM.SYS (or other compatible
- extended-memory manager) does not appear before the device command that
- installs the EMM386 expanded-memory manager in your CONFIG.SYS file.
- Make sure you install HIMEM.SYS before EMM386.EXE.
-
- EMM386 Privileged operation error #<number>
- Deactivate EMM386 and Continue (C) or reBoot (B)
- (C or B) ?
-
- An internal error occurred. As a result, the system may become unstable.
- Type b to restart your computer, or type c to continue. Because the
- system can fail without warning, choose to continue only to save files
- and prepare to shut down your system.
-
- EMM386/Windows interface failure.
- EMM386 will remain off.
-
- An internal error occurred. Generally Windows version 3.0 in enhanced
- mode reactivates the EMM386 expanded-memory manager when it quits, but
- there was a failure in this process. Restart your computer if you would
- like to reactivate EMM386.EXE.
-
- EMM386: Unable to start Enhanced Mode Windows due to base memory back fill.
-
- Windows version 3.0 was unable to start in 386 enhanced mode because of
- a conflicting use of memory. You may need to modify the EMM386.EXE
- configuration to eliminate the base memory backfill, and then restart
- your computer before starting Windows again.
-
- EMM386: Unable to start Enhanced Mode Windows due to invalid path
- specification for EMM386.
-
- Windows version 3.0 in enhanced mode needs to load a virtual device
- driver to work correctly with upper memory blocks, but the path to
- the EMM386 expanded-memory manager is incorrect. Make sure the device
- command line of your CONFIG.SYS file specifies the correct location for
- EMM386.EXE, or use the /y switch to specify a correct
- location. You will find information about the /y switch in the README.TXT
- file.
-
- EMM386: Unrecoverable privileged operation error #
- <number>- press ENTER to reboot
-
- An internal error occurred; as a result, the system has become unstable.
- Press ENTER to restart your computer.
-
- End of input file
-
- The entire file has been read into memory. If the file was read in
- sections, this message indicates that the last section of the file is
- in memory.
-
- Enter Fixed Disk Drive Number (1-<number>)
-
- Type the hard disk number with which you want to use the FDISK command.
-
- Enter partition size in Mbytes or percent of disk space (%) to
- create a Primary DOS Partition
-
- Type the number of megabytes or the percentage of disk space for the
- primary DOS partition. The number must be less than or equal to the
- maximum space available for the partition. If you type a percentage,
- type the number followed by a percent (%) sign.
-
- Enter Volume Label?
-
- You cannot delete a primary or logical drive unless you type the volume
- label for the drive. Type the volume label to continue.
-
- Entry error
-
- The last command you typed contained a syntax error. Check the syntax
- and retype the command.
-
- Entry has a bad attribute
-
- The "." (current directory) or ".." (parent directory) entry contains
- incorrect information. The CHKDSK command will fix this error if you
- specified the /f switch.
-
- Entry has a bad link
-
- The "." (current directory) or ".." (parent directory) entry contains
- incorrect information. The CHKDSK command will fix this error if you
- specified the /f switch.
-
- Entry has a bad size
-
- The "." (current directory) or ".." (parent directory) entry contains
- incorrect information. The CHKDSK command will fix this error if you
- specified the /f switch.
-
- Error accessing target file.
-
- An error occurred while the Mirror program was attempting to save
- information on the target (destination) disk. The destination disk may
- be full. In this case, you must change disks or delete files from the
- destination disk before running the Mirror program again.
-
- ERROR: An Extended Memory Manager is already installed.
-
- You were loading the HIMEM extended-memory manager while another
- extended-memory manager was resident in memory. Remove either the
- DEVICE=HIMEM.SYS command line or the DEVICE command that loads the
- other extended-memory manager from your CONFIG.SYS file, and restart
- your computer.
-
- ERROR: An invalid path to SETVER.EXE was specified.
-
- Make sure the SETVER.EXE file exists and that you typed the path
- correctly.
-
- ERROR: Could not find the file SETVER.EXE.
-
- You need the SETVER.EXE file to carry out this command. Make sure
- SETVER.EXE is in your DOS or current directory, or that it is on the
- path. If you cannot find SETVER.EXE, use the EXPAND command to expand
- and copy it from your MS-DOS installation disks.
-
- Error during read of font file
-
- The MODE command was unable to read the font file (files with a .CPI
- extension). Make sure the files are in your DOS or current directory,
- and that the directory is on the path. If you still get this message,
- there may be an error in the font file.
-
- Error executing FORMAT
-
- You either replied "No" to the message "Proceed with Format?", or you
- specified the wrong format parameter for the BACKUP command with the /f
- switch. Make sure the parameter you specified is correct.
-
- Error executing the given program
-
- The LOADFIX command was unable to start the specified program. This
- message may indicate an internal error in MS-DOS or in COMMAND.COM, or
- you may have run out of memory. Free some memory, and try again.
-
- ERROR: HIMEM.SYS requires an 80x86-based machine.
-
- The HIMEM extended-memory manager can load only on systems containing
- an Intel(R) 80286, 80386, or 80486, or compatible microprocessor.
-
- ERROR: HIMEM.SYS requires DOS 3.00 or higher.
-
- You can install the HIMEM extended-memory manager only when running
- MS-DOS version 3.0 or later. Remove the DEVICE command loading the
- HIMEM.SYS file from your CONFIG.SYS file if you are working with an
- earlier version of MS-DOS.
-
- Error in compressed input file format: <filename>
-
- The compressed file contains an error. Use the file from the MS-DOS
- installation disk to make another copy. If the error is on the
- installation disk, contact Microsoft customer service for a new disk.
-
- Error in CONFIG.SYS line <number>
-
- The specified line in your CONFIG.SYS file contains a syntax error, or
- the specified file cannot be found. Correct the line and restart your
- computer.
-
- Error in COUNTRY command
-
- Correct the syntax for the COUNTRY command in your CONFIG.SYS file, and
- restart your computer.
-
- Error in EXE file
-
- There is an error in the program you are running. The file may be
- damaged. If possible, use a backup copy to replace the damaged file.
-
- ERROR: Insufficient memory.
-
- Free memory by closing files and programs you no longer use. If you
- still get this message, remove memory-resident programs (TSR) or
- unnecessary device drivers from your CONFIG.SYS file, and restart your
- computer.
-
- ERROR: Invalid drive specifier.
-
- You typed an invalid drive letter when specifying the location of the
- SETVER.EXE file. Make sure you specified the correct drive and retype
- the command.
-
- ERROR: Invalid filename.
-
- Make sure the filename is in the correct format. A filename can contain
- up to eight characters with an extension of up to three characters. Make
- sure the filename does not contain any illegal characters and that it is
- not a reserved filename.
-
- ERROR: Invalid switch.
-
- You typed a switch that is not valid for this command. A switch is a
- parameter beginning with a slash, such as /s. Check the syntax and retype
- the command.
-
- ERROR: Invalid version number, format must be 2.11 - 9.99.
-
- You can only specify a version number between 2.11 and 9.99. Type a
- version number that is within the allowed values.
-
- Error: missing COMSPEC
-
- The COMSPEC environment variable is missing. The LOADFIX command relies
- on the command interpreter specified in the COMSPEC environment variable
- to start the specified program. Use the SET command to define COMSPEC
- and specify the location of COMMAND.COM or an alternate command
- interpreter.
-
- ERROR: Missing parameter.
-
- This command requires another parameter. Check the syntax and retype
- the command.
-
- ERROR: No available extended memory was found.
-
- Either your system does not contain additional memory above 640K, or
- the memory is not configured as extended memory. If you have additional
- memory, refer to the documentation for information about configuring
- the memory as extended memory.
-
- Error: No program name given
-
- Specify the name of the program you want to run. Type the command again
- and specify the name and path of the program.
-
- (Error occurred in environment variable)
-
- The error displayed with this message occurred in the DIRCMD environment
- variable, rather than on the command line. Use the SET command to view
- the current settings for the DIRCMD environment variable. Then type
- HELP DIR at the command prompt to see the correct syntax for the command.
-
- Error opening logfile
-
- The BACKUP command cannot create the log file. Specify a drive you can
- write to with the /l switch.
-
- Error reading directory
-
- An error occurred reading a directory on your floppy disk. The disk is
- unusable and should be discarded.
-
- Error reading file
-
- An error occurred reading the file currently being printed. The cause of
- the error is listed on your screen just before this message.
-
- Error reading fixed disk
-
- MS-DOS could not read your hard disk. Make sure the drive is installed
- correctly. If you still get this message, consult your system's manuals
- or call your vendor.
-
- Error reading GRAPHICS profile
-
- There is an error opening or reading the profile file (either the file
- you specified or the GRAPHICS.PRO file). Make sure another application
- is not using the profile. If you still get this message, the file may
- be corrupted. Use the EXPAND command to expand and copy the default
- GRAPHICS.PRO file from the MS-DOS installation disks. Any changes
- you made in the existing GRAPHICS.PRO will be overwritten.
-
- Error reading hard disk.
-
- The Mirror program was not able to access any data on your hard disk.
- The disk may be damaged. If you can, use the CHKDSK command with the
- /f switch from a floppy disk to fix the hard disk.
-
- Error reading help file.
-
- There may be an error in the DOSHELP.HLP file. If you continue to see
- this message, you can use the EXPAND command to create a new copy from
- the version on your MS-DOS installation disks.
-
- Error reading logical sector number
-
- The UNFORMAT command could not read data from the specified area of
- the disk. The disk may be damaged or the drive may be faulty. Reformat
- the disk using the low-level format tool, if available. If the disk is
- a floppy disk, discard the disk. If you still get this message, contact
- your hardware vendor.
-
- Error reading partition table
-
- The FORMAT command could not read the partition table. If it is a
- floppy disk, type FORMAT /u to do an unconditional format. However,
- you will not be able to UNFORMAT this disk if you do an unconditional
- format. If you still get this message, discard the disk. If the disk
- is a hard disk, contact your hardware vendor.
-
- Error reading system areas.
-
- The file allocation table (FAT) or root directory of the disk may be
- damaged and cannot be read. The Mirror program cannot record the
- information contained in these locations. Use the CHKDSK command with
- the /f switch to see if the problem can be fixed. If you still
- get this message with a floppy disk, discard the disk. If it is a hard
- disk, contact your hardware vendor.
-
- Error reading the file.
-
- While attempting to restore the partitions of a hard drive, the
- UNFORMAT command was unable to locate or read the PARTNSAV.FIL file
- on the floppy disk. Make sure that the file exists on the floppy disk,
- and try the UNFORMAT command with the /partn switch again.
-
- ERROR: Specified entry was not found in the version table.
-
- The entry does not exist in the version table used by the SETVER
- command.
-
- ERROR: The SETVER file in the specified path is not a compatible version.
-
- Make sure the current version of the SETVER.EXE file is in your search
- path. Check for any other versions of SETVER.EXE and remove them from
- your search path. If you cannot find the correct version of SETVER.EXE,
- use the EXPAND command to expand and copy it from your MS-DOS
- installation disks.
-
- ERROR: There is no more space in version table new entries.
-
- You have too many entries in your version table. Use the SETVER command
- to delete some entries before adding any new entries.
-
- ERROR: Too many command line parameters.
-
- You typed too many parameters for this command. This message generally
- refers to parameters other than switches (which begin with a slash, such
- as /s) or keywords (which contain an equal sign, such as cols=80). Check
- the syntax and retype the command.
-
- Error tracking the MIRROR image file.
-
- An error occurred while locating the Mirror image file and related files.
- This indicates that the UNFORMAT command may not be able to locate the
- files required to restore the disk. Delete the MIRORSAV.FIL, MIRROR.FIL,
- and MIRROR.BAK files and run the Mirror program again.
-
- ERROR: Unable to control A20 line!
-
- The HIMEM extended-memory manager was unable to load properly, and
- therefore cannot make extended memory available. You may be able to
- solve the problem by changing the value in the /m (or /machine) switch
- in the DEVICE command loading HIMEM.SYS. If the problem persists, contact
- your hardware vendor. While the problem exists, configure MS-DOS to load
- in low memory by adding the DOS=LOW command line to your CONFIG.SYS file.
- Then restart your computer.
-
- ERROR: VDISK memory allocator already installed.
-
- There is already a memory manager or program using extended memory
- installed, so the HIMEM extended-memory manager will not install. If
- you want to use HIMEM.SYS instead of your current memory manager, remove
- the command in your CONFIG.SYS file that loads the other memory manager.
- Otherwise, remove the command that loads HIMEM.SYS.
-
- ERROR: Version table is corrupt.
-
- The version table is corrupted. Use the EXPAND command to expand and
- copy the SETVER.EXE file from your MS-DOS installation disks.
-
- Error writing directory
-
- There was an error in writing to a directory. If the error occurred on
- your hard disk, try to format it again. If you still get this message,
- call your hardware vendor to determine the problem. If it is a floppy
- disk, discard the disk.
-
- Error writing FAT
-
- There was an error while writing to your file allocation table (FAT).
- If the error occurred on your hard disk, try to format it again. If you
- still get this message, call your hardware vendor to determine the
- problem. If it is a floppy disk, discard the disk.
-
- Error writing fixed disk
-
- MS-DOS could not write to your hard disk. Make a backup of any
- information on this disk and try to format it. Also make sure you have
- correctly installed your hard drive. If you still get this message,
- consult your system's manuals or call your vendor.
-
- Error writing logical sector <number>
-
- An error occurred while the UNFORMAT command was writing data to the
- specified area of the disk. The disk may be write-protected or damaged,
- or the drive may be faulty. Make sure the disk is not write-protected.
- Then use the CHKDSK command with the /f switch to fix any problems on
- the disk, or use another disk. If you still get this message, call
- your hardware vendor.
-
- Error writing partition table
-
- The FORMAT command could not read the partition table. You should use
- the FDISK command on the disk to partition it, and then try formatting
- it again.
-
- Error writing system areas.
-
- The Mirror program cannot record the information contained in the
- system areas of the disk. The file allocation table (FAT) or root
- directory of the disk may be damaged, or the disk may be write-protected.
- Make sure the disk is not write-protected. If you suspect an error on
- the disk, use the CHKDSK command with the /f switch to try to fix the
- disk. If you still get this message, the disk may need to be repaired
- or replaced.
-
- Error writing the MIRROR image file.
-
- The Mirror program could not write to the MIRROR.FIL file. You may not
- be able to write to the disk, or a sector allocated for the Mirror image
- file may be corrupted. Make sure you can write to the disk. If necessary,
- use the RECOVER command to rebuild the MIRROR.FIL image file and then run
- the Mirror program again.
-
- Error writing to device
-
- The COPY command could not write characters to the device. Make sure you
- have securely connected the cables and turned on the device.
-
- Errors found, F parameter not specified
- Corrections will not be written to disk
-
- The CHKDSK command found errors on the disk, but CHKDSK will not correct
- them because you did not specify the /f switch. To correct disk errors,
- use the CHKDSK command with the /f switch.
-
- Errors on list device indicate that it
- may be off-line. Please check it.
-
- Make sure you have plugged in your printer, turned it on, and that the
- printer is ready to print.
-
- Existing format differs from that specified
- This disk cannot be unformatted
- Proceed with Format (Y/N)?
-
- Make sure you have a copy of any important information on this disk
- before continuing, because you cannot unformat the disk.
-
- Expanded memory not available
-
- There is no expanded-memory manager (EMS) present, or there is no
- expanded memory available. Retype the FASTOPEN command without the
- /x switch to load it into conventional memory, or reduce the amount
- of expanded memory other programs use and retry the command. Also, try
- installing an expanded-memory manager like EMM386. If you have an
- expanded-memory manager other than MS-DOS version 5.0 EMM386.EXE set up
- on your system, make sure it supports the Lotus(R)-Intel(R)-Microsoft
- LIM/EMS specification version 4.0. For information about other
- expanded-memory managers, see the program's documentation for more
- information.
-
- Expanded memory services unavailable.
-
- The DEVICE command in your CONFIG.SYS file that installs the EMM386
- expanded-memory manager includes the noems switch. This switch provides
- access to the upper memory area without enabling access to expanded
- memory. This message confirms that you have set up EMM386.EXE without
- enabling the expanded-memory manager.
-
- Extended DOS Partition already exists
-
- You cannot create another extended DOS partition. To see how your disk is
- partitioned, choose option 4, "Display partition information" from the
- main Fdisk program menu.
-
- Extended DOS Partition created
-
- You have created an extended DOS partition on your hard disk.
-
- Extended DOS Partition deleted
-
- You have deleted an extended DOS partition from your hard disk.
-
- Extended error <number>
-
- An MS-DOS system utility tried to access an error message stored in
- the COMMAND.COM file, but one of the following problems occurred:
-
- * The utility could not find COMMAND.COM
-
- * The error code was unknown to MS-DOS
-
- * The COMSPEC environment variable did not specify the correct
- location of COMMAND.COM
-
- * The command processor you're using is not COMMAND.COM
-
- * The floppy disk in the drive from which you ran COMMAND.COM has been
- replaced with a different disk not containing COMMAND.COM
-
- If you are using COMMAND.COM, make sure it is accessible and that you
- have the COMSPEC environment variable correctly in your AUTOEXEC.BAT
- file. If all else looks correct, there may be an anomaly or unexpected
- error in the system utility or resident system software, especially
- network software or memory-resident (TSR) programs.
-
- Fail on INT 24
-
- The program stopped because it received a failure response to an
- interrupt message, probably because you chose "Fail" in response to
- the "Abort, Retry, Ignore, or Fail" message. You can now correct the
- problem that caused the message, and retry the command.
-
- Failure to access code page font file
-
- The code page information (.CPI) file cannot be found. These files are
- generally located in your DOS directory. Make sure the files exist and
- that you spelled them correctly. If necessary, use the EXPAND command
- to expand and copy them from your MS-DOS installation disks.
-
- Failure to access device: <device>
-
- You tried to specify a code page for a particular device, but MS-DOS
- cannot access the device listed. Retype the command using an existing
- device. If you are using a device driver, make sure it is properly
- installed in your CONFIG.SYS file.
-
- FASTOPEN already installed
-
- The Fastopen program is already installed on the system. If you want
- to specify different parameters, restart your computer before
- reinstalling Fastopen.
-
- FASTOPEN cannot be installed under DosShell
-
- The Fastopen program can be installed with MS-DOS Shell only if the
- Task Swapper is off. However, it is not advisable to install FASTOPEN
- while running MS-DOS Shell, because FASTOPEN could lock up your machine.
- Quit MS-DOS Shell, install the Fastopen program, and then start
- MS-DOS Shell again to use Fastopen with MS-DOS Shell.
-
- FASTOPEN EMS entry count exceeded. Use fewer entries
-
- The buffer the Fastopen program uses to keep track of files has reached
- its limit of 16K. FASTOPEN uses 48 bytes of memory for each file that it
- tracks. Either install the Fastopen program again specifying fewer files,
- or don't use the /x switch.
-
- Fatal Error: Cannot allocate Memory for DOS
-
- Your system does not have enough memory to run MS-DOS. You need at least
- 128K of conventional memory to run MS-DOS.
-
- FCB unavailable
-
- An application tried to access a file using a file control block (FCB)
- over a network or while the Share program was loaded, but the FCB was
- no longer available. End the process. If this problem occurs frequently,
- increase the value of the fcbs command in your CONFIG.SYS file, and
- restart your computer.
-
- FC: no differences encountered
-
- There were no differences between the two files.
-
- File allocation table bad drive <letter>
-
- The file allocation table (FAT) on the specified drive contains an error
- or has become corrupted. Use the CHKDSK command with the /f switch to
- check the disk and fix the error, if possible. If you still get this
- message, you may need to back up your files and reformat your disk.
-
- File allocation unit is invalid, entry truncated
-
- A link to part of your file was lost or broken, so MS-DOS cut off your
- file at that point. Look at the end of your file to see where it was
- truncated.
-
- File cannot be converted
-
- The file is not in the correct format to be converted to a command
- (.COM) file. Possible problems include:
-
- * The executable (.EXE) file contained an invalid header
-
- * A stack was declared for the source .EXE file
-
- * The source file specifies execution beginning at a time other than
- offset 100h
-
- * The source file requires segment fixes
-
- Review the requirements for .COM programs and relink, recompile, or
- rewrite your program in the appropriate format.
-
- File cannot be copied onto itself
-
- Specify a destination file that is different from the source file.
-
- File creation error
-
- MS-DOS cannot create the file you specified. Make sure you typed valid
- path and filenames. If you specified a destination filename, use the
- DIR command with the /a switch to make sure you did not specify a
- read-only, hidden or system file, or an existing subdirectory. Confirm
- that there is enough space for the file in the current directory and in
- your temporary directory, if appropriate. If the disk is write-protected,
- use another disk or remove the write-protection tab.
-
- File exists
-
- The utility tried to copy over or rename a file that already exists.
-
- File <filename> canceled by operator
-
- The specified file will not be printed. This message appears on the
- printer screen.
-
- File is READ-ONLY
-
- The file is designated read-only. Use the ATTRIB command to remove the
- read-only attribute before editing the file.
-
- File name must be specified
-
- Specify the name of the file you want to create or edit.
-
- File not found
-
- Make sure the file exists in the specified directory, and that you typed
- the filename and path correctly. If this message appears on the printer
- screen, the file has been removed, renamed, or deleted between the time
- it was queued for printing and the time it actually began printing.
-
- File not in PRINT queue
-
- The file that you specified was not in the print queue, so you cannot
- remove it from the queue. Make sure you typed the filename correctly.
-
- File1 Only Has <number> Lines
- File2 Only Has <number> Lines
-
- You specified too many lines for the /n switch. You can only specify
- a number less than or equal to the number of lines in the file. Check
- your typing, and try the command again.
-
- Files compare OK
-
- The compared files are identical.
-
- Files found in the root: <number>
-
- The UNFORMAT command may be able to recover the indicated number of
- files in the root directory.
-
- Files found: <number>
-
- The UNFORMAT command was able to locate the indicated number of files.
- It will attempt to recover those files.
-
- File(s) not found
-
- MS-DOS did not find the file or files you specified. Make sure you
- typed the filename and path correctly.
-
- Finish remainder of search (Yes/No/Quit)?
-
- While the UNFORMAT command was restoring a disk without a Mirror image
- file, you interrupted the process of searching for subdirectories. This
- prompt asks whether you want UNFORMAT to continue searching for
- additional subdirectories. If you type y, UNFORMAT will continue to look
- for subdirectories on the disk. If you type n, UNFORMAT will attempt to
- recover files from the subdirectories it has already located. If you
- type q, UNFORMAT will stop without restoring the disk.
-
- FIRST diskette bad or incompatible
-
- The DISKCOMP command cannot recognize the format on the source disk. Use
- the CHKDSK command to help identify the problem.
-
- Fix-ups needed - base segment (hex):
-
- This message prompts you to type in segment reference fixes. These fixes
- are required when the code refers to segment base addresses, such as
- with far pointers. Using hexadecimal notation, type the base segment
- address for the code being converted. If the code is meant to run
- anywhere in memory, such as an overlay, rewrite the code to determine
- and set up its own segment references when it runs. You may inspect the
- .EXE header to determine where segment references occur in the code.
-
- Fixed backup device <drive>: is full
-
- Use another disk to finish the backup.
-
- Font file contents invalid
-
- The code page information (.CPI) files are corrupted. Use the EXPAND
- command to expand and copy the files from the MS-DOS installation disks
- into your DOS directory to replace the corrupted files.
-
- FOR cannot be nested
-
- You specified a FOR command that calls another FOR command. If you need
- to nest FOR commands, create a batch file for the second command and
- call the batch file from the first command.
-
- Format another (Y/N)?
-
- The FORMAT command displays this message when it has finished
- formatting a disk. Type y if you want to format another disk, or type
- n if you don't. If you accidentally type y, you can end the format
- process by typing CTRL+C in response to the message "Strike any
- key."
-
- Format complete
-
- The FORMAT command displays this message when it has finished formatting
- the disk in the specified drive.
-
- Format not supported on drive <letter>:
-
- The FORMAT command is not necessary or will not work on this drive. For
- example, you do not have to format a RAM drive. The disk being formatted
- may not be usable if it has been only partially formatted.
-
- Format terminated
-
- The format process has been discontinued.
-
- Formatting while copying
-
- The destination disk is being formatted with the same format as the
- source disk.
-
- Function not supported on this computer - <function>
-
- Your machine lacks the appropriate adapter, device, or ROM BIOS for
- this process.
-
- General failure
-
- Either you tried to access an unformatted disk, or there has been a
- hardware error. If it is a floppy disk, use the FORMAT command with t
- he /u switch to format the disk. If it is a hard disk, try low-level
- formatting the disk. If formatting the disk does not fix the problem,
- contact your hardware vendor.
-
- Has invalid allocation unit, file truncated
-
- A link to part of your file was lost or broken, and MS-DOS had to
- shorten your file. Look at the end of your file to see where it was
- truncated.
-
- Help file could not be found.
-
- Make sure the DOSHELP.HLP file exists and that the directory containing
- DOSHELP.HLP is on your search path. If you cannot find DOSHELP.HLP, you
- can use the EXPAND command to expand and copy it from your MS-DOS
- installation disks into your DOS directory.
-
- Help not available for this command.
-
- The help file does not contain information for the command you
- specified.
-
- HMA not available : Loading DOS low
-
- The high memory area (HMA) is not present or has already been allocated,
- or an extended memory (XMS) driver is not present. MS-DOS will be loaded
- into low memory. If you want to load MS-DOS into the high memory area,
- check your CONFIG.SYS file to make sure the HIMEM extended-memory manager
- has been loaded using the DEVICE command and the high memory area is
- available before trying to load MS-DOS. If you want to load MS-DOS into
- low memory in the future, include the DOS=LOW command line in your
- CONFIG.SYS file.
-
- Ignoring this subdirectory.
-
- A subdirectory contains invalid information. The UNFORMAT command will
- not restore files in this subdirectory.
-
- Illegal device name
-
- Your computer does not recognize this device name. Make sure you typed
- the device name correctly and that you've correctly set up and configured
- the device.
-
- Incompatible file version #.
-
- While restoring the partitions of a hard drive, the UNFORMAT command
- determined that the PARTNSAV.FIL file on the floppy disk was created by
- an incompatible version of the Mirror program. Use the versions of
- MIRROR and UNFORMAT on your MS-DOS installation disks.
-
- Incompatible switches
-
- Two of the switches you specified cannot be used together. A switch is
- a parameter beginning with a slash, such as /s. Check the syntax and
- retype the command.
-
- Incorrect APPEND version
-
- Make sure you are using the MS-DOS version 5.0 copy of the append
- command, or use the EXPAND command to copy the correct version from
- the MS-DOS installation disks into your DOS directory.
-
- Incorrect DOS version
-
- Make sure the directory that contains the correct version of this
- utility appears in the path before any other directories containing a
- copy of this utility. Also, confirm that the current directory does not
- contain another copy of this utility. If you cannot find the correct
- version of this utility, use the EXPAND command to copy the correct
- version from your MS-DOS installation disks.
-
- Incorrect number of parameters
-
- You specified either too many or too few parameters for the command
- line.
-
- Incorrect parameter
-
- Make sure each parameter you specified is correct.
-
- Infinite retry not supported on network printer
-
- Your system cannot support the infinite retry option through the
- network interface. You should either use a printer with a direct
- connection or not specify a retry value in the MODE command.
-
- Infinite retry on parallel printer time-out:
-
- MS-DOS will keep trying to print until the file prints, or you restart
- your computer.
-
- Input file <filename> already in expanded format
-
- The file you specified is already uncompressed, so you don't have to
- uncompress it using the EXPAND command. Use the COPY command to copy
- the file to the destination.
-
- Insert backup diskette <number> in drive <letter>:
-
- Insert the specified backup disk into the specified drive. To quit the
- process, type CTRL+C.
-
- Insert backup source diskette in drive <letter>:
-
- Insert the source disk for the backup in the specified drive. To quit
- the process, type CTRL+C.
-
- Insert disk with batch file
-
- Insert the disk that contains the batch program in the appropriate drive.
- If you made a mistake or do not have a disk with the batch program, type
- CTRL+C to quit.
-
- Insert diskette for drive <letter> and press any key when ready
-
- Insert a disk in the appropriate drive and press a key to begin.
-
- Insert DOS disk in drive <letter>:
-
- You specified the FORMAT command with the /s switch, but the FORMAT
- command cannot find the MS-DOS system files (IO.SYS, COMMAND.COM,
- and MSDOS.SYS). Insert a disk containing these files in the specified
- drive, or type CTRL+C to stop the format.
-
- Insert DOS system diskette in drive A:
- Press any key when ready . . .
-
- Insert a system disk in drive A and press a key to continue. A system
- disk is a startable (bootable) disk containing the files COMMAND.COM,
- IO.SYS, and MSDOS.SYS.
-
- Insert FIRST diskette in drive <letter>:
-
- Insert the first disk you want to compare.
-
- Insert last backup diskette in drive <letter>:
-
- Insert the final backup disk from your last backup into the drive.
-
- Insert new diskette for drive <letter>:
-
- Insert the disk you want to format. All information on the disk will be
- erased. To quit the formatting process, press CTRL+C.
-
- Insert restore target in drive <letter>:
-
- Insert the disk where you want to place the restored files. To quit the
- process, type CTRL+C.
-
- Insert SECOND diskette in drive <letter>:
-
- Insert the second disk for comparison.
-
- Insert SOURCE diskette in drive <letter>:
-
- Insert the source disk in the specified drive.
-
- Insert system disk in drive <letter>
-
- Insert a system disk (a disk containing the files MSDOS.SYS, IO.SYS,
- and COMMAND.COM) in the specified drive and press a key to start the
- system copy process.
-
- Insert target disk in drive <letter>
-
- Place the target (destination) disk into the specified drive.
-
- Insert TARGET diskette in drive <letter>:
-
- Insert the target (destination) disk in the specified drive. If you
- have only one floppy drive, remove the source disk and insert the
- destination disk.
-
- Insufficient disk space
-
- The disk is full and the process cannot be completed. Move or delete
- some files to free disk space, or use another disk.
-
- Insufficient disk space. Insert a new disk in drive <letter>: and
- press RETURN:
-
- There is not enough room on the disk for the file. Insert a new disk
- in the specified drive and press ENTER, or press CTRL+C to cancel.
- You can then delete some files to make room on the disk before trying
- again, or specify a different destination.
-
- Insufficient disk space
- *** Not able to restore file ***
-
- The disk is full and the file cannot be restored. Move or delete some
- files to free disk space, or use another disk.
-
- Insufficient disk space on drive <letter>:
-
- There is not enough room on the disk for the file. Delete some files
- to make room on the disk before trying again, or specify a different
- destination.
-
- Insufficient memory
-
- There was not enough memory to carry out this command. Free memory by
- closing files and programs you no longer use. If you still get this
- message, remove memory-resident programs (TSRs) or unnecessary device
- drivers from your CONFIG.SYS file, and restart your computer.
-
- Insufficient memory for buffers.
-
- There was not enough memory for the internal buffers of the EXPAND
- command. Free memory by closing files and programs you no longer use.
- If you still get this message, remove memory-resident (TSR) programs
- or unnecessary device drivers from your CONFIG.SYS file, and restart
- your computer.
-
- Insufficient memory for COUNTRY.SYS file
-
- There was not enough memory to load the COUNTRY.SYS file. Free memory
- by closing files and programs you no longer use. If you still get this
- message, remove memory-resident programs (TSRs) or unnecessary device
- drivers from your CONFIG.SYS file, and restart your computer.
-
- Insufficient memory for UMBs or virtual HMA.
-
- There was not enough free memory available to allow EMM386.EXE to provide
- upper memory blocks (UMBs) or virtual high memory area (HMA). Make sure
- that the DEVICE command that installs EMM386.EXE appears immediately
- after the DEVICE command that installs HIMEM.SYS. Both commands must
- appear in your CONFIG.SYS file before any other DEVICE command. If you
- make changes to your CONFIG.SYS file, restart your computer to have the
- changes take effect.
-
- Insufficient memory to load system files
-
- There was not enough memory to keep all of the system files in RAM.
- Free memory by closing files and programs you no longer use. If you
- still get this message, remove memory-resident programs (TSRs) or
- unnecessary device drivers from your CONFIG.SYS file, and restart your
- computer.
-
- Insufficient memory to read entire directory.
-
- There was not enough memory for the UNDELETE command to read the
- directory file. Free memory by closing files and programs you no
- longer use. If you still get this message, remove memory-resident
- programs (TSRs) or unnecessary device drivers from your CONFIG.SYS
- file, and restart your computer.
-
- Insufficient memory to store macro. Use the DOSKEY command with the /BUFSIZE
- switch to increase available memory.
-
- Use the DOSKEY command with the /macros switch to see a list of the
- macros currently resident in memory. Delete the ones you don't need
- to free some memory for the new macro. If you continue to see this
- message, install the Doskey program again. Note that any macros not
- saved in a batch file will be erased. To reinstall the Doskey program,
- restart your computer and specify the DOSKEY command with a larger
- /bufsize switch. You can also reinstall Doskey without having to restart
- your system by using the /bufsize and /reinstall switches. However, the
- memory used by your original Doskey will not be available unless you
- restart your computer.
-
- Insufficient number of filespecs
-
- You did not include enough information in the command. Check the syntax
- of the command. Type HELP followed by the command name to see the correct
- syntax.
-
- Insufficient room in root directory,
- Move files from root directory and repeat CHKDSK
-
- When the CHKDSK command converts lost chains into files, it places the
- files in the root directory. There are already too many files in the
- root directory. Copy some files from the root directory into a
- subdirectory and use the CHKDSK command with the /f switch again.
-
- Intermediate file error during pipe
-
- MS-DOS could not create a temporary file. Make sure there is enough room
- in the directory for the temporary file and that the disk is not
- write-protected. If you set a TEMP environment variable, make sure it
- is set to a valid, writeable drive, and that there is room in the
- directory and on the disk.
-
- Internal error
-
- This message indicates a severe system error. Contact Microsoft Product
- Support Services to help you identify the problem.
-
- Internal stack overflow
- System halted
-
- Restart your computer, add or increase the STACKS command parameters in
- your CONFIG.SYS file, and restart your computer again. If you still get
- this message, return the stacks values to the default values (0,0 or
- 9,128 depending on your system), and restart your computer.
-
- Invalid baud rate specified
-
- You specified an incorrect baud rate. Valid choices are 110, 150, 300,
- 600, 1200, 2400, 4800, and 9600, and 19200 on some machines. Specify at
- least the first two digits of the baud rate.
-
- Invalid boot record signature.
-
- The UNFORMAT command detected invalid data in the partition information
- for a hard drive. Consequently, you cannot unformat the disk.
-
- Invalid characters in volume label
-
- Specify a volume label with up to 11 alphanumeric characters.
-
- Invalid code page
-
- Check the code page value, and try again.
-
- Invalid code page specified
-
- Make sure the code page value is correct for your keyboard layout, and
- try again.
-
- Invalid COMMAND.COM
-
- Your COMMAND.COM file is damaged and cannot be used. If you set a
- COMSPEC environment variable in your CONFIG.SYS file, make sure it
- specifies the correct version of COMMAND.COM. If necessary, use the
- EXPAND command to make another copy of the COMMAND.COM file from the
- MS-DOS installation disks.
-
- Invalid country code or code page
-
- The country code or code page specified in the COUNTRY command of your
- CONFIG.SYS file is either out of range or not found in the file you
- specified. Make sure the country code and country code page numbers are
- correct for the COUNTRY command in your CONFIG.SYS file, and restart
- your computer.
-
- Invalid date
-
- Type a valid date. The date format is determined by the country code
- setting in your CONFIG.SYS file.
-
- Invalid device
-
- The CTTY command displays this message if the specified device is
- invalid. Valid values for the device parameter are: PRN, LPT1, LPT2,
- LPT3, CON, AUX, COM1, COM2, COM3, COM4.
-
- Invalid device parameters from device driver
-
- The floppy disk that you are trying to format contains an error. If
- you want to format this disk, use the FORMAT command followed by the
- /u switch to do an unconditional format. However, if you use the
- unconditional switch, you will not be able to use the UNFORMAT command
- on the disk. Make sure you back up any files you want to save before
- formatting this disk.
-
- Invalid directory
-
- Make sure you typed the directory name correctly, or use the DIR command
- followed by the /ad switch to view a list of valid directories. You
- cannot specify a wildcard character with directory names.
-
- Invalid disk change
-
- You changed the disk while MS-DOS was writing to it. Insert the original
- disk and retry the command.
-
- Invalid drive in search path
-
- There is a drive on the path that does not exist. MS-DOS will still
- search for and carry out commands, but the directory on the invalid
- drive will be ignored.
-
- Invalid drive or file name
-
- Make sure the drive exists and that the filename is valid and exists on
- the path specified.
-
- Invalid drive specification
-
- The drive you specified does not exist. Retype the command with a valid
- drive letter.
-
- Invalid drive specification
- Specified drive does not exist
- or is non-removable
-
- The DISKCOMP and DISKCOPY commands work only on local, removable drives.
- You may have specified a non-existent drive letter, a hard disk, or a
- drive letter that was assigned or substituted. Specify the name of a
- valid floppy drive.
-
- Invalid entry
-
- The entry you typed was not valid. Check your typing and type a correct
- value.
-
- Invalid entry, please enter <number>-<number>
-
- The entry you typed was not valid. Make sure your entry is within the
- specified values.
-
- Invalid existing format
- This disk cannot be QuickFormatted
- Proceed with Unconditional Format (Y/N)?
-
- You cannot use the FORMAT command followed by the /q switch with a disk
- that has an invalid format because the invalid format would not be
- erased. To unconditionally format the disk (deleting all existing data),
- type y. You will not be able to unformat the disk, so make sure you have
- a backup of any information you want to save before continuing. To quit
- the formatting process, type n.
-
- Invalid filename character.
-
- You typed a character which cannot appear in MS-DOS filenames. Type a
- valid filename.
-
- Invalid filename or file not found
-
- The RENAME command displays this message if you used the command to
- rename a file and place the newly named file in a different directory.
- If you want to do this, use the COPY command instead to copy the file
- to the new directory and give it a different name. You can then delete
- the old file.
-
- The TYPE command displays this message if you included wildcard
- characters when specifying the file. If you want to view a set of files
- specified by wildcards, use the TYPE command to view each one separately.
-
- Invalid filename. Press any key and then re-type filename.
-
- The name you typed cannot be used by MS-DOS as a valid filename. Press
- a key to continue, and then type a different filename.
-
- Invalid keyboard code specified
-
- Make sure the keyboard code value is correct, and try again.
-
- Invalid keyboard ID specified
-
- Make sure the keyboard identification code for your keyboard layout is
- correct, and try again.
-
- Invalid keyword
-
- A keyword is a name followed by an equal sign and a value, like COLS=80.
- You typed a keyword that is not valid for this command. Check the syntax
- and retype the command.
-
- Invalid macro definition.
-
- The command you typed contained a syntax error. Type HELP DOSKEY at the
- command prompt for help on the correct syntax.
-
- Invalid media or Track 0 bad - disk unusable
-
- The disk may be unusable, or you may be trying to format the disk to an
- incorrect format. Make sure you are formatting the correct density. For
- example, you cannot format a double-density disk as a high-density disk.
-
- If you continue to get this message, the disk may have bad sectors near
- the beginning of the disk. The FORMAT command can accommodate defective
- sectors on the disk, except those near the beginning. If the disk is a
- floppy disk, use another disk. If the disk is a hard disk, contact your
- hardware vendor.
-
- Invalid media type
-
- You have tried to access a non-DOS disk, a disk that was only partially
- formatted, or a disk whose formatting is corrupted. Specify another disk,
- or reformat this disk.
-
- Invalid number of file/directory entries
-
- The Fastopen program can work with between 10 and 999 files at one time.
- The number you specified is not within that range. Retype the command
- using a value between 10 and 999.
-
- Invalid number of parameters
-
- You specified too many or too few parameters for this command. To find
- out which parameters are valid for this command, type HELP at the
- command prompt followed by the command name.
-
- Invalid option(s).
-
- The UNFORMAT command was followed by a switch or parameter that the
- UNFORMAT command did not recognize. Type HELP UNFORMAT at the command
- prompt to see a list of valid options.
-
- Invalid or unspecified drive.
-
- Either you did not specify a drive to be restored by the UNFORMAT
- command, or the drive you specified is invalid. The UNFORMAT command
- cannot restore drives either redirected over a network or created
- using the SUBST, ASSIGN, or JOIN command.
-
- Invalid parameter
-
- You specified a parameter that is not valid for this command. To find
- out which parameters are valid for this command, type HELP at the
- command prompt followed by the command name.
-
- Invalid parameter combination
-
- You specified two or more parameters that cannot be used together. To
- find out which parameters are valid for this command, type HELP at
- the command prompt followed by the command name.
-
- Invalid parameter - <parameter>
-
- You used an incorrect parameter for the EMM386.EXE device driver. Check
- the syntax, and try again.
-
- Invalid parameter specifications.
-
- The UNDELETE command contained one or more switches that the UNDELETE
- command did not recognize. Type HELP UNDELETE to display the correct
- syntax for this command.
-
- Invalid parameter specified.
-
- The DEVICE command in your CONFIG.SYS file that installs EMM386.EXE
- contains an invalid parameter. Check the syntax and retype the command.
-
- Invalid parameter(s) specified.
-
- You used the MIRROR command with an incorrect switch or specified a
- drive that does not exist on your system. Type HELP MIRROR at the
- command prompt to see a list of valid switches. If you specify a drive,
- it must be on your system. (For example, you cannot specify a network
- drive.)
-
- Invalid path
-
- Make sure the path and file you specified are valid and retype the
- command.
-
- Invalid Path, not all directories/files copied
-
- Make sure the filename characters and format are valid, and the path
- exists.
-
- Invalid path, not directory, or directory not empty
-
- Make sure the path is correct, that the name you specified is the name
- of a directory and not a file, and that the directory is empty and
- contains no hidden files. Use the DIR command followed by the /a switch
- to view hidden files. You can remove hidden, system, or read-only files
- by using the ATTRIB command to remove the file attributes and then
- deleting the file.
-
- Invalid path or file name
-
- Make sure the directory path and filename exist and are valid. The
- directory path cannot contain more than 64 characters, and the
- filename cannot contain more than 8 characters with an extension of
- up to 3 characters. Make sure the filename does not contain any illegal
- characters, and is not a reserved filename.
-
- If you are renaming a file, use the DIR command to make sure you are
- renaming a file and not a directory. If you are renaming a directory,
- you cannot rename it from the command prompt. Use MS-DOS Shell to
- rename a directory.
-
- Invalid path or file not found
-
- Make sure the path is less than 64 characters and that the filename
- characters and format are valid.
-
- Invalid path or System files not found
-
- MS-DOS could not find the system files. Make sure you specified the
- correct path to the MSDOS.SYS, IO.SYS, and COMMAND.COM files, and that
- the files exist on the disk.
-
- Invalid profile statement on line <number>
-
- You used an invalid statement in the profile file on the specified line.
- Type a valid statement on the specified line. If you are using the
- GRAPHICS.PRO file, you may want to use the EXPAND command to expand
- and copy the default file from the MS-DOS installation disks.
-
- Invalid STACK parameters
-
- The STACKS command in your CONFIG.SYS file contains an invalid
- combination of stack size and number of stacks. Correct the parameters,
- and restart your computer.
-
- Invalid sub-directory entry
-
- The "." (current directory) or ".." (parent directory) entry contains
- invalid information. If you haven't already done so, use the CHKDSK
- command with the /f switch to fix the directory. If you still get this
- message, move the files elsewhere and delete the directory.
-
- Invalid switch
-
- You typed a switch that is not valid for this command. A switch is a
- parameter beginning with a slash, such as /s. Check the syntax and
- retype the command.
-
- Invalid syntax on DISPLAY.SYS code page driver
-
- Check your CONFIG.SYS file to make sure the DEVICE command loading
- DISPLAY.SYS has the correct syntax, and restart your computer.
-
- Invalid syntax on PRINTER.SYS code page driver
-
- Check your CONFIG.SYS file to make sure the DEVICE command loading
- PRINTER.SYS has the correct syntax, and restart your computer.
-
- Invalid time
-
- Type a valid time. The time format is determined by the country code
- setting in your CONFIG.SYS file.
-
- Is cross linked on allocation unit <number>
-
- Two files or directories attempted to access the same disk space. Copy
- the specified file or directory elsewhere and delete the original.
-
- Just checking this time. No changes written to disk.
-
- You used the /j switch with the UNFORMAT command. The UNFORMAT command
- is simulating how it would restore the disk using a Mirror image file
- without actually making changes to the disk.
-
- KEYB has not been installed
-
- An internal error occurred when you used the KEYB command to install
- your keyboard. The keyboard information is no longer in memory. The
- command may have been specified from the command prompt or in your
- CONFIG.SYS or AUTOEXEC.BAT file. Check the syntax and retype the KEYB
- command to install your keyboard. If this message is combined with an
- insufficient memory message, you can free memory by closing files and
- programs you no longer use, or by removing memory-resident programs
- (TSRs) from your CONFIG.SYS file. If you make changes to your CONFIG.SYS
- file, restart your computer to make the changes take effect.
-
- Keyboard ID specified is inconsistent with the selected keyboard layout
-
- The keyboard identification and the country or language keyboard codes
- you specified were incompatible. Make sure the keyboard code and
- identification numbers are compatible, and try the KEYB command again.
-
- Label not found
-
- A GOTO command in a batch program points to a nonexistent label. Make
- sure the label exists and is spelled correctly.
-
- Last backup diskette not inserted
-
- Insert the final backup disk from your most recent backup into the drive.
-
- *** Last file not backed up ***
-
- The destination disk may be full, or there may be an error in the
- source file or on the destination disk. Use another disk to back up this
- file separately.
-
- Line too long
-
- The replacement string caused the line to be longer than 253 characters.
- Divide the line in two and try again.
-
- List output is not assigned to a device
-
- The PRINT command has not been told where to send the print job. To
- specify the name of a print device, first restart your computer so you
- can reinstall PRINT, and then use the PRINT command followed by the /d
- switch.
-
- LoadHigh: Invalid filename
-
- The format of the program you specified is invalid, or the program is
- not in the path or current directory. The program must be an .EXE or
- .COM program to run in upper memory. Make sure you typed the filename
- correctly, that the program exists, and that it is in the path.
-
- Lock violation
-
- A program tried to access a file that another program was using. Close
- the file in the second program, and try the command again.
-
- Logging to file filename
-
- The BACKUP command is creating a backup log to the file specified.
-
- Logical DOS Drive created, drive letters changed or added
-
- You may have to make changes if you have files specifying drive letters
- and the drive letters have changed. For example, check your
- AUTOEXEC.BAT and CONFIG.SYS files to be sure none of the commands have
- been affected.
-
- LPT<number> : not rerouted
-
- You canceled the rerouting, or the MODE command could not reroute the
- parallel printer port. Make sure you have specified the proper
- parameters with the MODE command.
-
- LPT<number> : rerouted to COM<number> :
-
- Output being sent to the parallel printer port will now be sent to the
- serial port specified.
-
- LPT<number> : set for 80
-
- The parallel printer port has been set for 80 columns.
-
- LPT<number> : set for 132
-
- The parallel printer port has been set for 132 columns.
-
- Make sure a diskette is inserted into the drive and the door is closed
-
- Make sure you put the disk in the correct disk drive and that the drive
- door is closed.
-
- Maximum number of Logical DOS Drives installed.
-
- You have installed the maximum number of logical DOS drives allowed by
- MS-DOS. You cannot create any more logical DOS drives.
-
- Maximum space available for logical drive is <number> Mbytes
- Enter logical drive size in Mbytes or percent of disk space (%)
-
- Type the amount or percentage of disk space for the logical drive. If
- you type the percentage, follow the number with a percent (%) sign. The
- number must be less than or equal to the maximum space available for
- the logical drive.
-
- Maximum space available for partition is <number> Mbytes
-
- This is the maximum amount of space available for the partition.
-
- Memory allocation error
-
- Either MS-DOS could not process one of the INSTALL commands you
- specified in your CONFIG.SYS file, or the program you are running
- corrupted memory. First, restart your computer to see if that solves
- the problem. If you still get this message, remove or remark out all of
- the INSTALL commands from your CONFIG.SYS file, and restart your
- computer. Then reinsert the commands one by one to determine which
- command caused the error. Once you have identified the command that
- caused the problem, remove the INSTALL command from your CONFIG.SYS
- file. Then load that program from your AUTOEXEC.BAT file, or from the
- command prompt.
-
- Memory control blocks destroyed
-
- MS-DOS found a memory problem. Restart your computer.
-
- Message string error <number>. See header of FDISKC.MSG for error definition
-
- This message indicates an internal error in the Fdisk program. Contact
- Microsoft Product Support Services to help you identify the problem.
-
- Minimum HMA size set to <number> K.
-
- Because you specified the /hmamin switch when you loaded HIMEM.SYS, the
- HIMEM.SYS file is confirming the minimum amount of memory a program must
- request before it can use the high memory area (HMA).
-
- MIRROR image file not found.
-
- The disk was not formatted by MS-DOS version 5.0, and cannot be restored.
-
- MODE <number> code page function completed
-
- The MODE command you specified worked correctly, and has finished.
-
- -- More --
-
- Press a key to display the next page.
-
- MS-DOS directory contains <number> deleted files. Of those, <number> files
- may be recovered.
-
- This message indicates the number of files that can be recovered using
- information contained in a directory file, rather than the PCTRACKR.DEL
- deletion-tracking file. Using information in the PCTRACKR.DEL
- deletion-tracking file is more reliable than using directory information
- to undelete a file.
-
- Multiple drive letters specified
-
- You specified more than one drive letter, but the LABEL command does
- not allow you to specify more than one drive at a time. If you need to
- label more than one drive, use the LABEL command separately for each
- drive.
-
- Must enter both /T and /N parameters
-
- Type both switches with this command.
-
- Must specify COM1, COM2, COM3 or COM4
-
- Specify COM1, COM2, COM3, or COM4 for the serial port that you want
- the MODE command to configure.
-
- Must specify destination line number
-
- Specify the line number where you want the text to be placed.
-
- Must specify ON or OFF
-
- This command does not accept any other options besides ON or OFF.
-
- Name of list device [PRN]:
-
- Specify the name of any valid device, which then becomes the print
- output device. If you press the ENTER key, the default list device
- is PRN.
-
- Need DOS version 2.x or higher
-
- You cannot use the UNFORMAT command with versions of MS-DOS lower
- than 2.0.
-
- New file
-
- Edlin did not find an existing file with this name, so Edlin is creating
- a new file.
-
- NLSFUNC not installed
-
- Install the Nlsfunc program before using this command.
-
- No action taken.
-
- You canceled the UNFORMAT command before it made any changes to the
- disk.
-
- No Append
-
- No paths are currently appended. Either no paths have been appended, or
- the list of appended directories was canceled using the APPEND command.
-
- No code page has been selected
-
- You have prepared a code page with the DEVICE command, but you have not
- specified which code page to use for the device.
-
- No drive specified
-
- DRIVER.SYS requires you to specify the drive number. Include a /d switch
- for each DEVICE=DRIVER.SYS command in your CONFIG.SYS file, and restart
- your computer.
-
- No EGA hardware detected
-
- The EGA device driver could not locate an EGA-compatible video device
- adaptor. If you have EGA hardware, make sure it is installed correctly.
-
- No entries found.
-
- The UNDELETE command did not find a directory entry for a deleted file.
- This indicates that no files have been deleted in the directory, or that
- new files were created that replaced the directory entries for deleted
- files. The UNDELETE command cannot recover files from this directory
- using information contained in the directory file. In the future, use
- the MIRROR command to help with deletion-tracking.
-
- No Extended DOS Partition to delete.
-
- You do not have an extended DOS partition, so MS-DOS cannot delete one.
- To see how your disk is partitioned, choose option 4, "Display partition
- information," from the main Fdisk menu.
-
- No files added
-
- You specified the /a switch with the REPLACE command, but replace did
- not find any files that needed to be added to the specified destination
- directory.
-
- No files found - <filename>
-
- The REPLACE command could not find the files specified in the source
- path. Retype the command with the correct source path for the files.
-
- No files or subdirectories found for the root.
-
- If any files or subdirectories existed in the root directory before the
- disk was formatted, they cannot be recovered.
-
- No files replaced
-
- None of the files in the destination directory that needed to be
- replaced.
-
- No fixed disks present
-
- MS-DOS cannot find a fixed (hard) disk on your system. If you do have a
- hard disk, make sure it is installed correctly.
-
- No free file handles
-
- There are too many open files. Close some files that you have finished
- using, or increase the value of the FILES command in your CONFIG.SYS
- file, and restart your computer.
-
- No hard drives found.
-
- No hard disk drive was found on your system, so the UNFORMAT command
- could not restore the partitions of your hard drive. If you do have a
- hard drive on your system, make sure it is installed correctly.
-
- No Logical DOS Drive(s) to delete
-
- If you would like to see how your system is currently set up, choose
- option 4, "Display partition information," from the main Fdisk menu.
-
- No logical drives defined
-
- To define a logical drive, use the FDISK command.
-
- No memory available
-
- There is not enough free memory available to use the COMP command. Free
- memory by closing files and programs you no longer use. If you still
- get this message, remove memory-resident programs (TSRs) or unnecessary
- device drivers from your CONFIG.SYS file, and restart your computer.
-
- No Non-DOS Partition to delete
-
- 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 main Fdisk menu.
-
- No partitions defined
-
- All partitions have been deleted from the hard disk.
-
- No partitions to delete.
-
- Choose option 4, "Display partition information," from the main Fdisk
- menu to see how your hard disk is set up.
-
- No partitions to make active.
-
- From the Fdisk menu, choose option 1, "Create DOS partition or logical
- DOS drive" to create a primary partition. After creating a primary
- partition, return to the Fdisk main menu and choose option 2, "Set
- active partition," to make the partition you just created the active
- partition.
-
- No partitions to save
-
- The hard disk in your system does not contain a primary DOS partition.
- Most likely, your system is not set up to start MS-DOS from the hard
- disk. Choose option 4, "Display partition information," from the main
- Fdisk menu to view partition information for your hard disk.
-
- No Path
-
- No path is defined.
-
- No Primary DOS Partition to delete.
-
- You do not have a primary DOS partition, so MS-DOS cannot delete one.
- To see how your disk is partitioned, choose option 4 "Display partition
- information" from the main Fdisk menu.
-
- No retry on parallel printer time-out:
-
- If the printer is not ready, MS-DOS will not try to print again.
-
- No room for system on destination disk
-
- Delete some files on the destination disk to make room for the system
- files, or use another disk.
-
- No room in directory for file
-
- The root directory or disk is full. Move some files out of the root
- directory, or copy the Edlin file to a subdirectory and edit it there.
- If the disk is full, delete some files or use another disk.
-
- No source drive specified
-
- Specify a source drive.
-
- No space to create a DOS partition.
-
- You do not have enough space on your current hard disk to create a DOS
- partition. Either remove or reduce the size of the existing partitions,
- and then use the FDISK command again to create the DOS partitions.
-
- No sub-directories exist
-
- The directory does not contain subdirectories.
-
- No system on default drive
-
- You did not specify the location of the system files (MSDOS.SYS, IO.SYS,
- and COMMAND.COM) and the SYS command did not find them on the default
- drive. Specify the location of the system files. You can use the DIR
- command followed by the /a switch to check for the hidden system files.
-
- No target drive specified
-
- Specify a target (destination) drive.
-
- Non-DOS Partition deleted
-
- The non-DOS partition you selected was deleted from your disk.
-
- Non-standard, missing, or bad partition table.
-
- The Mirror program was not able to locate the table that describes
- primary DOS partition on your hard disk. Your hard disk may have been
- partitioned by software other than the FDISK command. Use the FDISK
- command to view partition information for your hard disk.
-
- Non-System disk or disk error
- Replace and press any key when ready
-
- You cannot start your system from that disk because it is not a system
- disk. To restart your system from a floppy disk, insert a disk containing
- the system files MSDOS.SYS, IO.SYS, and COMMAND.COM and press a key. To
- restart your system from the hard disk, remove the floppy disk from the
- drive and press a key. Once you have started MS-DOS again, you can create
- a system disk by using the FORMAT command followed by the /s switch or
- use the SYS command.
-
- *** Not able to backup file ***
-
- The specified file is either being used by another program, or there is
- something wrong with the file. Determine if another program is using the
- file, and close the file. If the file is not being used, use the CHKDSK
- command to see if the file contains any errors.
-
- Not able to SYS to <name> file system
-
- Specify an MS-DOS drive as the destination drive.
-
- Not enough memory.
-
- Not enough memory was available to complete the process. Free memory by
- closing files and programs you no longer use. If you still get this
- message, remove memory-resident programs (TSRs) or unnecessary device
- drivers from your CONFIG.SYS file, and restart your computer.
-
- Not enough room to merge the entire file
-
- The file is too large to merge. Divide the file into smaller files, and
- merge each file one at a time.
-
- Not found
-
- There are no further occurrences of the specified search or replace
- string.
-
- Not ready
-
- You specified a drive letter that does not contain a disk or has its
- drive door open. Make sure the disk is inserted correctly and the drive
- door is closed.
-
- Not resetting hidden file filename
-
- The specified files with a hidden attribute are not being modified. If
- you want to reset attributes on these files, you should 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
-
- The specified files with a system attribute are not being modified. If
- you want to reset attributes on these files, you should use the ATTRIB
- command with the -s switch to remove the system attribute from these
- files before continuing the process.
-
- NOTE: SETVER device not loaded. To activate SETVER version reporting you
- must load the SETVER.EXE device in your CONFIG.SYS.
-
- The SETVER command must be loaded as a device. Insert a DEVICE command
- in your CONFIG.SYS file specifying the path to SETVER.EXE, and restart
- your computer.
-
- Number passed to FUNC is invalid. See example above.
-
- The command that loaded EGA.SYS included a FUNC parameter with an
- Interrupt 2Fh function number that was less than 80h. The function
- number must be in the range 80h to FFh. See the examples listed on your
- screen for more information.
-
- O.K.?
-
- If you type y or press ENTER, Edlin will accept the last result of the
- search or replace process and will continue. If you type n, Edlin will
- undo the last replacement and continue. To end the search or replace
- process, type CTRL+C.
-
- One or more CON code pages invalid for given keyboard code
-
- The KEYB command examined all prepared code pages, and has found that at
- least one code page is incompatible for your screen console device
- (CON). This is only information to let you know that your keyboard and
- screen console are working with different code pages.
-
- Only non-startable partitions exist.
-
- You do not have any partitions that are marked "Active." Using the Fdisk
- program main menu, choose option 2, "Set active partition," to mark a
- primary partition on the first fixed (hard) disk as active.
-
- Only <number> bytes are recoverable
- Truncate or Delete this file?
-
- The UNFORMAT command could recover only a portion of a file. Choose
- whether to truncate or delete the file. Typically, a partial file is
- likely to be useful only if it is a text file.
-
- Only partitions on Drive 1 can be made active.
-
- You may only create an active partition on your first hard disk.
-
- Operation completed. Insert a DOS boot disk in drive A and press ENTER
- to reboot....
-
- The UNFORMAT command has successfully restored the partitions of your
- hard drive. To allow MS-DOS to use the hard disk, restart your computer
- using an MS-DOS version 5.0 system disk in drive A.
-
- Original <path>: set to <drive>:
-
- The original path specified was substituted using the SUBST command, and
- is currently set to the specified drive.
-
- Out of disk space while writing output file: <filename>
-
- Your destination disk is full, so the rest of the file will not fit on
- the disk. Delete some files to make room or use another disk.
-
- Out of environment space
-
- The environment space cannot be expanded any further, so the specified
- environment variable cannot be added or redefined. You can increase the
- size of the existing environment by using the SET command to delete some
- of the existing environment variables before redefining or adding new
- environment variables. If you are using the SET command within a batch
- file and get this message, try typing the SET command again at the
- command prompt. If you are running a secondary prompt through another
- program such as MS-DOS Shell or Microsoft Windows, use the /e switch with
- the COMMAND command to allocate more environment space for the secondary
- command interpreter.
-
- If you still get this message or want to create more permanent
- environment space, specify a larger environment using the /e switch with
- the SHELL command in your CONFIG.SYS file, and then restart your computer.
- The environment space will be reset to the number of bytes you specified.
- If you still get this message, try freeing some memory by removing some
- memory-resident (TSR) programs, device drivers or some existing
- environmental variables from your CONFIG.SYS file, and restart your
- computer.
-
- Out of memory
-
- The utility ran out of memory before it could finish. You can free
- memory by closing files and programs you no longer use. If you still get
- this message, remove memory-resident programs (TSRs) or unnecessary
- device drivers from your CONFIG.SYS file, and restart your computer.
-
- Packed file corrupt
-
- The program cannot be successfully loaded into the first 64K of
- conventional memory. This error is most likely to occur when you load
- device drivers into the upper memory area, thereby freeing more
- conventional memory. Try starting the program with the LOADFIX command.
- For help on the syntax of the LOADFIX command, type HELP LOADFIX at
- the command prompt. You can also reconfigure your system so MS-DOS loads
- into low memory. To do this, add the command DOS=LOW to your CONFIG.SYS
- file, and restart your computer.
-
- Parameter format not correct
-
- You typed a parameter that is not in a valid format for this command. For
- example, you may have added a numerical value for a switch that will not
- allow a value to be specified. To find out which parameters are valid for
- this command, type HELP at the command prompt followed by the command
- name.
-
- Parameter value not allowed
-
- You typed a parameter value that is not among the values allowed by the
- command. To find out which parameters are valid for this command, type
- HELP at the command prompt followed by the command name.
-
- Parameter value not in allowed range
-
- You typed a numeric parameter value that is not in the range of values
- allowed by this command. To find out which parameters are valid for this
- command, type HELP at the command prompt followed by the command name.
-
- Parameters not compatible
-
- You specified switches that cannot be used together. To find out which
- switches are valid for this command, type HELP at the command prompt
- followed by the command name.
-
- Parameters not compatible with fixed disk
-
- You used a parameter that is not compatible with the specified drive.
- Check they syntax and type the command again. You can get help on most
- commands by typing HELP at the command prompt followed by the command
- name.
-
- Parameters not supported
-
- You have specified parameters that MS-DOS does not support on that
- drive. To find out which parameters are valid for this command, type
- HELP at the command prompt followed by the command name.
-
- Parameters not supported by drive
-
- Make sure you specified the correct parameters with the FORMAT command.
- For example, you cannot type the command FORMAT A: /F:720 if the drive
- is a 1.2 megabyte drive. Type the FORMAT command again and specify the
- correct format with the /f switch.
-
- Parse error <number>
-
- An error occurred on the command line. Check the syntax and try again.
-
- Partition selected is not a Non-DOS Partition
-
- You selected the option to delete a non-DOS partition, but the partition
- you selected is a DOS partition. Select a non-DOS partition, or press
- ESC to return to the main Fdisk menu.
-
- Partition selected is not a Primary DOS Partition
-
- You tried to delete a non-DOS primary partition but this Fdisk option
- can only be used for DOS primary partitions. Specify a primary DOS
- partition or press ESC to return to the main Fdisk menu.
-
- Partition selected (<number>) is not startable, active partition not changed.
-
- MS-DOS cannot be restarted from the partition you selected, so the
- active partition was not changed. You chose either an extended partition
- or a non-DOS primary partition. Use the Fdisk program again to select a
- DOS primary partition as the active partition.
-
- Path(name) too long
-
- The path you specified was too long. Make sure the path contains no more
- than 66 characters, including the drive letter and colon.
-
- Path not found
-
- MS-DOS cannot find the path you specified. Make sure you typed the
- directory names correctly and that the directory exists.
-
- Please type the first character for <filename>
-
- When MS-DOS deletes a file, it erases the first character of the
- filename in the file's directory. To restore the file using directory
- information, the UNDELETE command must supply MS-DOS with a first
- letter for the file. Type any valid filename character. (The letter does
- not have to be the first letter of the filename when it was deleted.)
-
- Press any key to begin copying file(s)
-
- This message occurs when you specify the XCOPY command with the /w
- switch. When you are ready to begin copying, press a key.
-
- Press any key to begin recovery of the file(s) on drive <letter>
-
- Press a key to begin the recovery. Recovered files are named
- FILE<NNNN>.REC. If you wish to end this command, press CTRL+C.
-
- Press any key to continue . . .
-
- Press a key on the keyboard to continue the process.
-
- Press CTRL+C to abort,
- or correct this problem and press any other key to continue . . .
-
- If you would like to end the process, press the CTRL key and the C key
- at the same time. To continue, take the necessary action to correct the
- problem and press any other key.
-
- Previous Code Page: <Number>
-
- This code page was active before the current code page. If the previous
- code page was "none," no graphics character font set was present when the
- GRAFTABL command was loaded. If the previous code page was "non-standard,"
- the previous Graphics font set loaded in memory was not recognized by the
- GRAFTABL command.
-
- Previously prepared code page replaced
-
- The existing code page for the device was changed to another prepared
- code page.
-
- Primary DOS Partition already exists.
-
- You cannot create two primary DOS partitions. To see how your disk is
- partitioned, choose option 4, "Display partition information," from the
- main Fdisk menu.
-
- Primary DOS Partition created
-
- You have successfully created a primary DOS partition on your disk.
-
- Primary DOS Partition created, drive letters changed or added
-
- You may have to make changes in any files that specify drive letters,
- because the drive letters may have changed. For example, check your
- AUTOEXEC.BAT and CONFIG.SYS files to be sure none of the commands have
- been affected.
-
- Primary DOS Partition deleted
-
- You have deleted the primary DOS partition from your disk.
-
- PRINT queue is empty
-
- There are no files waiting to be printed.
-
- PRINT queue is full
-
- No more files can fit in the print queue. Wait until several files have
- printed and then try again, or cancel some files currently in the print
- queue.
-
- Printbox ID not in GRAPHICS profile
-
- Specify a printbox size (ID) that matches the first operand of a
- PRINTBOX in your profile file.
-
- Printer error
-
- The printer is turned off or not ready to print. Make sure you connected
- the printer and turned it on.
-
- Printer lines per inch set
-
- The MODE command set the number of lines per inch for the printer.
-
- Printer out of paper error
-
- The printer is out of paper, or there is no printer installed.
-
- Printer type not in GRAPHICS profile
-
- The printer type you specified must be listed in your profile file.
-
- Probable non-DOS disk
- Continue (Y/N)?
-
- The CHKDSK command should only be used on MS-DOS disks. Confirm that
- the disk or drive is an MS-DOS disk and that it is formatted. If you
- have a non-standard partitioning scheme, make sure the correct device
- drivers are loaded. Some disks not formatted with the MS-DOS FORMAT
- command may cause the CHKDSK command to display this message, but the
- CHKDSK process will still function properly.
-
- Processing cannot continue
-
- You may have run out of memory, or the file allocation table (FAT) may
- be corrupted. Free memory by closing files and programs you no longer
- use. If you continue to see this message, back up the information and
- reformat the disk.
-
- Profile statement out of sequence on line <number>
-
- Correct the sequence of the statements in the specified line of the
- profile file. If you are using GRAPHICS.PRO, you may want to use the
- EXPAND command to expand and copy the default file from the MS-DOS
- installation disks.
-
- Program too big to fit in memory
-
- Free memory by closing files and programs you no longer use. If you still
- get this message, remove memory-resident programs (TSRs) or unnecessary
- device drivers from your CONFIG.SYS file, and restart your computer.
-
- QuickFormat another (Y/N)?
-
- Type y if you want to format another disk using the /q switch. Type n if
- you do not want to format another disk.
-
- RAMDrive: Bad Extended Memory Manager control chain
-
- There is an error in your extended-memory manager program (HIMEM.SYS or
- another extended-memory manager). If you use HIMEM.SYS, use the EXPAND
- command to expand and copy the correct version from your MS-DOS
- installation disks. If you use another extended-memory manager, make a
- copy from the master file, or do not use RAMDRIVE.SYS in extended memory.
-
- RAMDrive: Error in extended memory allocation
-
- Either there is not enough extended memory for the RAMDrive cache, or
- HIMEM.SYS (or another extended-memory manager) could not access the
- extended memory. If you have extended memory, make sure HIMEM.SYS or
- your extended-memory manager is installed correctly.
-
- RAMDrive: Expanded Memory Manager not present
-
- For RAMDRIVE.SYS to use expanded memory, configure your system so it
- provides expanded memory. In your CONFIG.SYS file, make sure the DEVICE
- command that loads the expanded-memory manager precedes the DEVICE
- command that loads RAMDRIVE.SYS. Also make sure the expanded-memory
- manager exists and is loaded correctly.
-
- RAMDrive: Expanded Memory Status shows error
-
- Expanded memory was not loaded properly. Make sure the expanded memory
- manager you are using exists and is loaded correctly.
-
- RAMDrive: Extended Memory Manager not present
-
- To use RAMDRIVE.SYS with the /e switch, an extended-memory manager (such
- as HIMEM.SYS) must be loaded before RAMDRIVE.SYS. Check your CONFIG.SYS
- file to make sure a DEVICE command loads an extended-memory manager
- before loading RAMDRIVE.SYS. If you do not have extended memory on your
- system, do not use the /e switch.
-
- RAMDrive: Incompatible parameters: sector size adjusted
-
- The SectorSize and DiskSize parameters you specified are not compatible.
- If you include a value for the SectorSize parameter, you must also
- include a value for the DiskSize parameter. Valid values for SectorSize
- are 128, 256, and 512. Valid values for DiskSize are in the range 4
- through 32767. Although you can change the SectorSize value, the default
- value (512) is strongly recommended.
-
- RAMDrive: Incorrect DOS version
-
- Make sure the most recent version of the RAMDRIVE.SYS device driver
- appears in the path before any other directories containing a copy of this
- device driver. Also make sure the current directory does not contain an
- older version of RAMDRIVE.SYS. Check the DEVICE command in your CONFIG.SYS
- file that loads RAMDRIVE.SYS to make sure it is the correct version. If
- necessary, use the EXPAND command to expand and copy the correct version
- from your MS-DOS installation disks.
-
- RAMDrive: Insufficient memory
-
- There is not enough conventional, extended, or expanded memory to run
- the RAMDRIVE.SYS device driver. If you specified the /e switch, you must
- have at least 4K of extended memory available, or if you specified the
- /a switch, you must have at least 16K of expanded memory available.
-
- RAMDrive: Invalid parameter
-
- You specified a parameter that is not valid with this command. Check the
- syntax and retype the command.
-
- RAMDrive: I/O error accessing drive memory
-
- RAMDRIVE.SYS could not access its allocated memory. The RAM disk may
- have been set up incorrectly, or an application corrupted the RAM disk.
- If an application affected the RAM disk memory, restart your computer. If
- you still get this message, make sure RAMDRIVE.SYS is installed
- correctly.
-
- RAMDrive: No extended memory available
-
- Your system does not have extended memory, or the extended memory isn't
- managed or configured properly by the extended-memory manager. If you do
- have extended memory, make sure it is configured correctly.
-
- Rate and delay must be specified together
- Rate=<number>
- Delay=<number>
-
- You must specify both the typematic rate and the delay value when you
- change the setting of either. Valid values for the rate are in the
- range 1 through 32, and the default value is 20 or 21 depending on your
- keyboard. Valid values for the delay are 1,2,3,4, and the default value
- is 2.
-
- Read error in: <filename>
-
- MS-DOS could not read the specified file. Use the CHKDSK command with
- the /f switch on the file to see if the file contains an error that can
- be fixed.
-
- Read fault error
-
- MS-DOS cannot read data from the device you specified. Make sure you
- correctly connected and configured the device.
-
- Reading source file(s)
-
- The XCOPY command is reading the source files that you specified.
-
- Replace <filename>? (Y/N)
-
- Type y if you want to replace the existing file, or type n if you do
- not want to replace the file.
-
- Requested logical drive size exceeds the maximum available space.
-
- You tried to create a logical drive that is larger than the space
- available. Type a size smaller than or equal to the maximum available
- space.
-
- Requested partition size exceeds the maximum available space.
-
- You tried to create a partition that is larger than the space available.
- Type a partition size smaller or equal to the maximum available space.
-
- Required font not loaded
-
- The DISPLAY.SYS file doesn't have the correct font size to carry out
- your request. Increase the number of subfonts in the DEVICE=DISPLAY.SYS
- command line in your CONFIG.SYS file, and then restart your computer.
-
- Required parameter missing
-
- The command you specified requires another parameter. To find out which
- parameters are valid for this command, type HELP at the command prompt
- followed by the command name.
-
- Required profile statement missing before line <number>
-
- You left out a statement in the profile file before the specified line
- and need to add it. If you are using GRAPHICS.PRO, you may want to use
- the EXPAND command to expand and copy the default file from the MS-DOS
- installation disks.
-
- Resident part of PRINT installed
-
- The PRINT command has been set up with the parameters you specified. To
- change the /d, /b, /u, /m, /s, and /q switches, restart your computer.
-
- Resident portion of MODE loaded
-
- Part of the MODE command is currently resident in memory.
-
- Restore file sequence error
-
- You have restored files in the wrong order. Insert the disks in the
- same order in which they were backed up.
-
- *** Restoring files from drive <letter>: ***
-
- This message is displayed during the file-restoration process.
-
- Resync failed. Files are too different
-
- The FC command could not find enough similarities to continue comparing
- the files. You can only use the FC command to compare these two files
- in binary mode.
-
- Same drive specified more than once
-
- There is no need to specify the same drive twice with the FASTOPEN
- command.
-
- Same parameter entered twice
-
- You typed a parameter twice. To check the correct syntax, type HELP
- followed by the command name.
-
- Saving UNFORMAT information
-
- The FORMAT command is saving the information needed for the unformat
- command.
-
- SECOND diskette bad or incompatible
-
- The second disk does not have the same format as the first disk, is
- unformatted, or has an unrecognizable format. Use the CHKDSK command
- to help you identify the problem.
-
- Sector not found
-
- An error occurred while reading a sector from the disk. Copy all of the
- files on this disk to a new disk. You may be able to use the RECOVER
- command to recover data on this disk.
-
- Sector size too large in file
-
- An installable physical drive (not a logical or virtual drive) has a
- sector size that is larger than the sector size specified by the default
- devices in the BIOS. For more information about your installable device
- driver, see the device owner's manual. By default, MS-DOS supports a
- 512 byte sector size. If necessary, remove the DEVICE command from your
- CONFIG.SYS file, and restart your computer.
-
- SHARE cannot be installed under DOSSHELL
-
- To set up the SHARE command, first quit MS-DOS Shell. Then install SHARE
- from the command prompt, and start MS-DOS Shell again.
-
- Share: Internal error
-
- An internal error occurred. Restart your computer and try again.
-
- Sharing violation
-
- Another program is currently using the file. Close the file in the
- second program, and try the process again.
-
- Simulation only.
-
- You used the /test switch with the UNFORMAT command. The UNFORMAT
- command is simulating how it would restore the disk without using a
- Mirror image file. It will not make changes to the disk.
-
- SMARTDrive: Bad Extended Memory Manager control chain
-
- One or more programs that manage extended memory did not install
- themselves properly. Remove the incorrectly installed device.
-
- SMARTDrive: Error in extended memory allocation
-
- An internal error occurred and the extended-memory manager did not
- provide memory requested by SMARTDRV.SYS. Make sure the HIMEM.SYS
- extended-memory (XMS) manager is installed correctly.
-
- SMARTDrive: Error reading disk. Possible virtual addressing problem.
-
- An internal error occurred. There may be a hardware problem. Contact your
- hardware vendor.
-
- SMARTDrive: Expanded Memory Manager not present
-
- You did not install an expanded-memory manager before installing
- SMARTDRV.SYS with the /a switch. Make sure that a DEVICE command
- that successfully installs an expanded-memory manager appears in your
- CONFIG.SYS file before the DEVICE command that installs SMARTDRV.SYS.
-
- SMARTDrive: Expanded Memory Status shows error
-
- The expanded-memory manager reported an error to SMARTDRV.SYS. Make sure
- that the expanded-memory manager is installed correctly before installing
- SMARTDRV.SYS.
-
- SMARTDrive: Extended Memory Manager not present
-
- You did not install an extended-memory manager before installing
- SMARTDRV.SYS. Make sure that a DEVICE command that installs an
- extended-memory manager (such as HIMEM.SYS) appears in your CONFIG.SYS
- file before the DEVICE command that installs SMARTDRV.SYS.
-
- SMARTDrive: Incompatible disk partition detected.
-
- Your hard drive was not partitioned by the MS-DOS FDISK command and
- contains a disk-partition format unknown by SMARTDRV.SYS. To use
- SMARTDRV.SYS with this disk, back up your hard disk and then repartition
- it using the FDISK command, or load SMARTDRV.SYS with the /p switch if
- you can determine that it is safe to use SMARTDRV.SYS with your
- partition.
-
- SMARTDrive: Incorrect DOS version
-
- The DEVICE command in your CONFIG.SYS file that loads SMARTDRV.SYS
- specifies a version that is not compatible with the version of MS-DOS on
- your system. Make sure the DEVICE command loads the SMARTDRV.SYS file
- distributed with MS-DOS version 5.0.
-
- SMARTDrive: Insufficient memory
-
- There is not enough memory to initialize the SMARTDRV.SYS device driver,
- or there is not enough extended memory available for SMARTDRV.SYS. Make
- sure there is at least 128K of extended memory on your system. You can
- free memory by installing SMARTDRV.SYS in your CONFIG.SYS file before
- other device drivers, or by loading MS-DOS into conventional memory
- (DOS=LOW).
-
- SMARTDrive: Invalid parameter
-
- The DEVICE command that installs SMARTDRV.SYS contains an invalid
- parameter or switch. Check the syntax and fix the command.
-
- SMARTDrive: I/O error accessing cache memory
-
- An internal error occurred that prevented SMARTDRV.SYS from using the
- memory set aside for the disk cache. There may be a hardware problem.
- Contact your hardware vendor.
-
- SMARTDrive: No extended memory available
-
- There is no extended memory available to install SMARTDRV.SYS. Another
- program may have used the memory, or your system does not have extended
- memory. Make sure you have extended memory.
-
- SMARTDrive: No hard drives on system
-
- The SMARTDrive disk caching program could not locate any hard drives on
- your system. If your hard drive requires an installable device driver,
- make sure the DEVICE command that installs the hard drive appears before
- the DEVICE command that installs SMARTDRV.SYS in your CONFIG.SYS file.
-
- SMARTDrive: Not enough memory to load driver
-
- Your system does not have enough memory available to install
- SMARTDRV.SYS. Make sure there is at least 128K of extended memory on your
- system. You can free memory by installing SMARTDRV.SYS in your CONFIG.SYS
- file before other device drivers, or by loading MS-DOS into conventional
- memory (DOS=LOW).
-
- SMARTDrive: Too many bytes per track on hard drive
-
- SMARTDRV.SYS cannot store data from this disk.
-
- Source and target drives are the same
-
- The source drive must be different from the target (destination) drive.
- Specify different source and destination drives.
-
- SOURCE diskette bad or incompatible
-
- Your disk has an unrecognizable format or bad sectors, or is incompatible
- with the source drive type. The DISKCOPY command cannot be used to copy
- this disk. Use the COPY or XCOPY command instead.
-
- Source does not contain backup files
-
- This disk does not contain backup files, so none can be restored. Insert
- a disk containing backup files.
-
- Source path and target drive cannot be the same
-
- Specify a source path that is different from the target (destination)
- drive.
-
- Source path required
-
- Specify the path of the original file or directory.
-
- Specified COMMAND search directory bad
-
- The directory containing COMMAND.COM has been damaged or is incorrect.
- Check your CONFIG.SYS file to make sure the COMSPEC environment
- variable is set correctly. If necessary, use an MS-DOS version 5.0
- system disk to restart your computer. If the disk is a hard disk, use
- the EXPAND command to expand and copy COMMAND.COM from the MS-DOS
- installation disks onto your disk. If the disk is a floppy disk, use
- either the FORMAT command with the /s switch or the SYS command to
- create a new system disk. You may have to change your CONFIG.SYS file to
- reflect the new location of COMMAND.COM.
-
- Specified COMMAND search directory bad access denied
-
- The directory containing COMMAND.COM has been damaged or is incorrect.
- Check your CONFIG.SYS file to make sure the COMSPEC environment variable
- is set correctly. If necessary, use an MS-DOS version 5.0 system disk to
- restart your computer. If the disk is a hard disk, use the EXPAND
- command to expand and copy COMMAND.COM from the MS-DOS installation
- disks onto your disk. If the disk is a floppy disk, use either the FORMAT
- command with the /s switch or the SYS command to create a new system
- disk. You may have to change your CONFIG.SYS file to reflect the new
- location of COMMAND.COM.
-
- Starting cluster is unavailable. This file cannot be recovered with the
- UNDELETE command.
- Press any key to continue.
-
- Although the UNDELETE command located information about this deleted file
- in the PCTRACKR.DEL deletion-tracking file, the first cluster of the
- deleted file has been used by another file. As a result, the UNDELETE
- command cannot locate the remainder of the deleted file to restore it.
- Press a key to continue.
-
- Subdirectories found in the root: <number>
-
- The UNFORMAT command may be able to recover the indicated number of
- subdirectories in the root directory.
-
- Syntax error
-
- Make sure you typed the command correctly and that the parameters are
- correct. You can get help on most commands by typing HELP at the command
- prompt followed by the command name.
-
- Syntax errors in GRAPHICS profile
-
- There are syntax errors in your profile file. Correct the errors, or use
- the EXPAND command to expand and copy the default GRAPHICS.PRO file from
- the MS-DOS installation disks. If you do this, you will overwrite any
- changes you made in the existing GRAPHICS.PRO.
-
- System resource exhausted
-
- The Share program has no more space for open file names. Add the /f
- switch to the share command in your AUTOEXEC.BAT or CONFIG.SYS file to
- increase the filename buffer size of the SHARE command, and then restart
- your computer.
-
- System transferred
-
- MS-DOS system files have been transferred. You can now use this disk to
- start your computer.
-
- System will now restart
-
- You changed partitions, so MS-DOS will restart to ensure the hard drive
- is accessed normally.
-
- Target cannot be used for backup
-
- The target (destination) disk has an unrecognizable format, is unusable,
- or is incompatible with the source drive type. Use another disk.
-
- TARGET diskette bad or incompatible
-
- The target (destination) disk could not be formatted to match the source
- disk. Try again with another disk.
-
- Target diskette may be unusable
-
- An error occurred while writing to the target (destination) disk. Format
- the destination disk with the FORMAT command followed by the /u switch
- and try again, or use another disk for the destination disk.
-
- If you saw the message "Formatting while copying" while using the
- DISKCOPY command, and this error occurred during the copy, then the
- destination disk cannot be used with the DISKCOPY command.
-
- TARGET media has lower capacity than SOURCE
- Continue anyway (Y/N]?
-
- You tried to copy a disk from a larger capacity disk to a smaller
- capacity disk using the DISKCOPY command. It may not be possible to
- reliably format the target (destination) disk to match the source disk.
- If you choose to continue, DISKCOPY will format the destination to match
- the source, or will report an error if it is not able to do so.
-
- Terminate batch job (Y/N)?
-
- Type y if you would like to end the batch program you are running. Type
- n to continue.
-
- The entire drive will be reconstructed, directory structures will be
- destroyed
- Are you sure (Y/N)?
-
- If you type y, all files in the disk will be renamed and placed in the
- root directory. If you type n, no changes will be made.
-
- CAUTION: You should not continue unless it is absolutely necessary. If
- you need to recover all the files on a disk, it is better to recover
- them one at a time so information will not be lost.
-
- The Extended DOS Partition contains Logical DOS Drives.
- Do you want to display the logical drive information (<Y>/<N>)......?
-
- If you want to see the logical drive information, type y. Otherwise,
- type n.
-
- The file is a backup to a more recent MIRROR image file.
-
- While searching the disk for a Mirror image file, the UNFORMAT command
- found what appears to be a backup image file at the specified location.
- There may be a more recent Mirror image file elsewhere on the disk. The
- Mirror program will continue to search for a more recent Mirror image
- file.
-
- The filename already exists. Type a different filename. Press F5 to bypass
- this file.
-
- A file already exists with the same name as that of a file being restored.
- Either type a new name for the file being restored, or press the F5 key if
- you do not want to recover the file.
-
- The following drives are supported:
- Drive <letter> - <number> files saved.
-
- The number following the drive letter indicates the maximum number of
- entries the Mirror program will maintain in the file that records file
- deletions. This should match the size you specified with the /t switch
- when you installed the Mirror program. If the word "Default" appears
- instead of a number, you did not specify a size and Mirror will maintain
- a maximum number of entries in the file that is appropriate for the size
- of the disk.
-
- The last file was not restored
-
- There was not enough room on the destination disk for the file, or the
- file was corrupt. Use the RESTORE command to restore the file separately
- on another disk.
-
- The last time the MIRROR or FORMAT command was used was at <time> on <date>.
- The prior time the MIRROR or FORMAT command was used was at <time> on <date>.
- If you wish to use the last file as indicated above, press L.
- If you wish to use the prior file as indicated above, press P.
- Press ESC to cancel UNFORMAT.
-
- Two Mirror image files exist on your disk. To use the most recent one,
- type L. To use the older one, type p. You will normally want to use the
- most recent file unless you believe it doesn't contain the correct
- information. For example, if you used the FORMAT command, then
- immediately used the MIRROR command, and then decided you needed to
- unformat the disk, you would want to use the older file. The newer one
- created by Mirror will contain the state of the disk after formatting the
- disk, not before.
-
- The master boot code has NOT been updated.
-
- There is a physical problem reading or writing to the hard disk. There is
- probably a bad sector on the disk where the master boot (startup) record
- is located. Either 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 MIRROR command cannot operate on a network drive.
-
- The drive you specified for the MIRROR command is redirected over a
- network. Specify a drive that is not a network drive.
-
- The MIRROR image file found has inconsistent information. It cannot be used.
-
- The image file created by the FORMAT or MIRROR command is corrupted and
- cannot be used. The UNFORMAT command will rebuild the disk using residual
- data on the disk left by the FORMAT command.
-
- The MIRROR process was unsuccessful.
-
- The Mirror program did not record information about the drive you
- specified.
-
- The only startable partition on Drive 1 is already set active.
-
- There is only one primary partition on your first hard disk, and that
- partition is already active. You do not have to make the partition active
- again.
-
- The saved information is incompatible with fixed disk <number>.
- Restoration is not possible; drive <letter> is skipped.
-
- The UNFORMAT command determined that information in the PARTNSAV.FIL
- file for the indicated drive was inconsistent with the drive actually
- installed on the system. UNFORMAT could not restore the partition
- information for the drive.
-
- The suspected MIRROR file is invalid. Continuing search.
-
- A file that appeared to be a Mirror image file did not contain the
- information needed by the UNFORMAT command to recover the disk.
-
- The system area does not agree with the MIRROR image file.
-
- The system area and Mirror image file are different. You have changed
- files on your disk since using the MIRROR or FORMAT command. Using the
- UNFORMAT command will restore your disk to a less recent condition.
-
- The system area of drive <letter> has been rebuilt. You may need to restart
- the system.
-
- Restart your computer if the disk you recovered was the disk with which
- you started your system.
-
- There is not enough disk space for system files
-
- The FORMAT command will not copy the system files. Delete some files from
- this disk to make room, or use a different disk.
-
- There is not enough space to create an UNFORMAT file.
- This disk cannot be unformatted.
- Proceed with Format (Y/N)?
-
- Since you cannot UNFORMAT the disk, make sure you have a copy of any
- information you want to save before continuing. If you do not have a
- backup and want to make one, type n to quit the format. Or type y to
- continue.
-
- There was an error creating the format recovery file
- This disk cannot be unformatted
- Proceed with Format (Y/N)?
-
- There may not be enough room on the disk to create the format recovery
- file. This file contains information MS-DOS uses to recover information
- with the UNFORMAT command. If this file is not created, you will not be
- able to unformat the disk. Type y at this message if you are sure you do
- not want to recover any information from the disk. If you may need to
- unformat the disk, type n, and delete some files to make room for the
- recovery file. Then try formatting the disk again.
-
- This file cannot be automatically recovered because not all of the
- clusters are available. Only some of the clusters for this file are
- available. Do you want to recover this file with only the available
- clusters? (Y/N)
-
- The UNDELETE command can completely restore files for which all clusters
- are available. If only some clusters are available, UNDELETE can
- partially restore the file. However, the partial file is probably useful
- only if it is a text file.
-
- Too many arguments in command line
-
- Make sure the syntax of the command line is correct, and that you only
- specify one process at a time.
-
- Too many block devices
-
- Each block device (physical drive, not logical or virtual drive) is
- assigned a drive letter. You cannot install another block device that
- will result in a drive letter past Z. Specify fewer drives in your
- CONFIG.SYS file, and restart your computer.
-
- Too many characters in volume label
-
- The volume label contains more than 11 characters. Specify a volume
- label with up to 11 alphanumeric characters.
-
- Too many code pages specified
-
- The number of code pages you specified to be supported on this device is
- out of the range of valid values. For EGA or VGA displays, the value can
- be between 0 and 6. For LCD displays, the value can be 0 or 1. Check the
- appropriate DEVICE command in your CONFIG.SYS file and fix the error.
- Then, restart your computer.
-
- Too many command-line arguments
-
- Make sure the syntax of the command line is correct, and that you only
- specify one process at a time. Type HELP followed by the command name to
- see the correct syntax for this command.
-
- Too many drive entries
-
- You specified more than 24 drives at the command prompt, but you can only
- specify up to 24 drives (C-Z). Retype the FASTOPEN command with up to 24
- valid drive letters.
-
- Too many extended partitions.
-
- The partition table for your hard disk contains descriptions for more
- partitions than MS-DOS allows. Most likely, the partition table itself
- is corrupted. If possible, back up any information you want to save.
- Use the FDISK command to change the partitions. (Or, if you used a
- third-party utility to partition your disk, use that tool.) If you still
- get this message, perform a low-level format on the disk.
-
- Too many file/directory entries
-
- The total number of file or directory entries specified at the command
- prompt exceeded memory capacity, or a total of 999. For example, if you
- used the FASTOPEN command and specified that it should keep track of 600
- files each on drives C and D, the total combined files would be greater
- than 999. Retype the command and make sure the total number of files and
- directories you specify is less than 999.
-
- Too many filenames
-
- You specified too many filenames for this command. Type HELP followed by
- the command name to see the correct syntax for this command.
-
- Too many files open
-
- You have reached the maximum number of files that may be opened. Close
- some files, or increase the value of the FILES command in your CONFIG.SYS
- file. Then, restart your computer.
-
- Too many open files
-
- You have reached the maximum number of files that may be opened. Close
- some files, or increase the value of the FILES command in your
- CONFIG.SYS file. Then, restart your computer.
-
- Too many parameters
-
- You typed too many parameters for this command. This message usually
- refers to parameters other than switches (which begin with a slash, such
- as /s) or keywords (that contain an equal sign such as COLS=80). To
- determine which parameters are valid for this command, type HELP at the
- command prompt followed by the command name.
-
- Too much of memory fragmentation; MEM /C cannot be done
-
- The memory is too fragmented, or an application that ran before the MEM
- command has corrupted the memory areas. Restart your computer, or if you
- are using MS-DOS through a DOS box (such as with Microsoft Windows),
- close the windowing program and try again. Note that you can still use the
- MEM command alone or with the /p switch.
-
- Top level process aborted, cannot continue
-
- You chose "Abort," but MS-DOS cannot return to the command interpreter.
- Use a system disk to restart your computer. If you see the error message
- "Abort, Retry, Fail?" again, choose "Fail" instead of "Abort."
-
- Unable to access Drive <letter>
-
- There is a hardware problem with the specified drive and it cannot be
- accessed. Call your hardware vendor.
-
- Unable to allocate segment
-
- There is not enough memory to carry out the command you specified. Free
- memory by closing files and programs you no longer use. If you still get
- this message, remove memory-resident programs (TSRs), or unneeded device
- drivers from your CONFIG.SYS file, and restart your computer.
-
- Unable to create directory
-
- You may have a file with the same name, the path may be incorrect, the
- disk may be full, or the root directory may be full. Use the DIR
- command with the /a switch to make sure no hidden files have the same
- name as the directory. Also make sure the path is valid and that there is
- room on the disk. If you tried to create the directory in the root
- directory but the root was full, move or delete some files to make room,
- or create the directory within an existing directory.
-
- Unable to create KEYB table in resident memory
-
- Free memory by closing files and programs you no longer use. If you
- still get this message, increase the amount of conventional memory you
- have available.
-
- Unable to disable Weitek Coprocessor support
-
- The EMM386.EXE device driver cannot disable support for the Weitek(R)
- coprocessor.
-
- Unable to do requested command
-
- The network cannot carry out the command due to errors. Contact your
- network administrator. Check the network connection to make sure the
- connection is secure and that the network is installed correctly.
- Restarting your computer may also help. If you continue to see this
- message, you may need to reinstall the network.
-
- Unable to enable Weitek Coprocessor support
-
- The high memory area (HMA) is already in use. If you want to enable the
- Weitek Coprocessor, the HMA must be available. Make sure your CONFIG.SYS
- file contains the command line DOS=LOW and that no other programs are
- using the HMA before enabling the Weitek Coprocessor.
-
- Unable to find the MIRROR control file. If you want to search for the
- MIRROR image file through the entire hard drive, press Y, or press N
- to cancel the UNFORMAT command.
-
- The UNFORMAT command cannot locate a Mirror image file in the usual
- location. UNFORMAT can search throughout the disk for the Mirror image
- file, but it may take a long time. To be able to recover the disk, you
- must type y. If UNFORMAT cannot locate a Mirror image file elsewhere on
- the disk, it will attempt to rebuild the disk using traces of information
- left by the FORMAT command. To quit the unformatting process, type n.
-
- Unable to load command.com (or dosswap.exe), Retry (y/n)?
-
- The MS-DOS command interpreter (COMMAND.COM) or Task Swapper
- (DOSSWAP.EXE) cannot be found on your disk, or there is not enough free
- memory in your system to contain the program. Make sure the COMMAND.COM
- and DOSSWAP.EXE files are in the path and are specified correctly in
- the COMSPEC environment variable, the files exist on the disk, and the
- files are in the same directory as the DOSSHELL files. To increase
- memory, close files and programs you no longer use. If you still get this
- message, remove memory-resident programs (TSRs) or unnecessary device
- drivers from your CONFIG.SYS file, and restart your computer.
-
- Unable to load MS-DOS Shell, Retry (y/n)?
-
- MS-DOS cannot load MS-DOS Shell into memory. The DOSSHELL.EXE file
- cannot be found on your disk, or there is not enough free memory in
- your system for the program. Type y to try to load MS-DOS Shell again, or
- n to quit. Make sure the path to DOSSHELL.EXE is correct and that the
- file exists on the disk. Free memory by closing files and programs you
- no longer use. If you still get this message, remove memory-resident
- programs (TSRs) or unnecessary device drivers from your CONFIG.SYS file,
- and restart your computer.
-
- Unable to perform refresh operation
-
- The code pages could not be reinstated with the MODE CODEPAGE REFRESH
- command. Either the files cannot be found, or you have run out of memory.
- Make sure the code page information (.CPI) files exist. You an also use
- the MODE command to prepare and select the code page again.
-
- Unable to place EMM386 in Auto mode.
-
- Due to an internal error, the EMM386 expanded-memory manager cannot
- automatically provide expanded memory to applications that request it.
- Use the EMM386 command with the W=ON switch to turn on expanded memory
- before running such applications.
-
- Unable to print message
-
- There was an error in your COMMAND.COM file. Save your work, and restart
- your computer. If you still get this message, you may want to use the
- EXPAND command to expand and copy COMMAND.COM from your MS-DOS
- installation disks.
-
- Unable to reload with profile supplied
-
- There is not enough memory for the Graphics program to load the new
- printer profile on top of the old printer profile. To use GRAPHICS
- with the new printer profile, restart your computer. Or, if you are
- using MS-DOS through a window (such as with MS-DOS Shell or Microsoft
- Windows), close the windowing program and try again.
-
- Unable to shift screen <left>, <right>
-
- The MODE command is unable to shift the test pattern on the screen any
- further.
-
- Unable to turn EMM386 ON - protected mode software already running.
-
- The EMM386 expanded-memory manager cannot be used when other
- protected-mode software is running. Quit the protected-mode software
- before using the EMM386 command with the W=ON switch.
-
- Unable to write BOOT
-
- If the first track of the disk or DOS partition is bad, MS-DOS cannot
- use the disk. If your disk is a floppy disk, it is unusable. If your
- disk is a hard disk, contact your hardware vendor.
-
- Unexpected End of File
-
- This message may appear if you press CTRL+Z at the LABEL prompt, or if
- the COMP command unexpectedly reached the end of one of the files. If
- you see this message with the COMP command, most likely the file
- allocation table (FAT) entry for the file has been corrupted, causing
- part of the file to be lost. The CHKDSK command with the /f switch
- may be able recover all or part of the missing portions of a text file.
-
- Unknown error
-
- An error occurred when attempting to open one of the two files for
- comparison. Make sure the two files are accessible, and try the
- command again.
-
- Unrecognized command in CONFIG.SYS
-
- One of the commands in your CONFIG.SYS file contains a syntax error. Make
- changes as necessary, and restart your computer.
-
- Unrecoverable error in directory
- Convert directory to file (Y/N)?
-
- The CHKDSK command cannot fix the error in the directory. If you type y,
- CHKDSK will convert the corrupted directory into a file on your disk. If
- you type n, CHKDSK will leave the directory untouched. Since the
- directory is unusable, you should move the information in this directory
- elsewhere and delete the directory.
-
- Unrecoverable read error on drive <letter>
- Side <number>, track <number>
-
- The data could not be read from the specified disk on the indicated side
- and track. Copy the files on this disk to another disk using the COPY
- or XCOPY command, and reformat the defective disk using the FORMAT
- command with the /u switch.
-
- If the disk is the destination disk and the "Formatting while copying"
- message was displayed, you cannot use the DISKCOPY command with this
- disk.
-
- Unrecoverable write error on drive <letter>
- Side <number>, track <number>
-
- The data could not be written to the disk in the specified drive on the
- indicated side and track. Try again with a new disk, or format the disk
- using the FORMAT command with the /u switch and try again.
-
- Using default value of BCH for interrupt 2FH function calls.
-
- The DEVICE command that loaded the EGA device driver did not include
- the FUNC parameter, so it is using the default parameter. The default
- value is BCh.
-
- Using user defined value of xxH for interrupt 2FH function calls.
-
- The DEVICE command that loaded the EGA device driver included a FUNC
- parameter with a valid Interrupt 2Fh function number.
-
- Volume in drive <letter> has no label
-
- The disk does not currently have a label. If you want to create a
- volume label, switch to the specified drive and use the LABEL command.
-
- Volume label (11 characters, ENTER for none)?
-
- Type a volume label of up to 11 characters and spaces, or press ENTER
- to indicate that you do not want a volume label for this disk.
-
- Volume label does not match.
-
- You must type the correct volume label for this drive, or you cannot
- delete the partition.
-
- Volume label is not supported with /8 parameter
-
- You cannot specify a volume label on a disk formatted with the /8 switch.
-
- Walking the directory tree to locate all files...
-
- While attempting to restore a disk without a Mirror image file, the
- UNFORMAT command is searching subdirectories to find all the files that
- were on the disk before it was formatted.
-
- WARNING, ALL DATA ON NON-REMOVABLE DISK
- DRIVE <letter>: WILL BE LOST!
- Proceed with Format (Y/N)?
-
- This message appears when you try to format a hard disk that already
- contains data. If you type y, the data on the disk will be deleted. If
- you type n, the FORMAT command will stop and return you to the command
- prompt.
-
- WARNING! Data in the deleted Extended DOS Partition will be lost.
- Do you wish to continue (Y/N).................?
-
- Make sure there is no data you want to save on this partition before
- continuing. Before deleting the extended DOS partition, you should have
- backed up any information in logical drives and deleted the logical
- drives from this partition.
-
- WARNING! Data in the deleted Non-DOS Partition will be lost.
-
- Make sure any files you want to save are backed up.
-
- WARNING! Data in the deleted Primary DOS Partition will be lost.
- Do you wish to continue (Y/N).................?
-
- If you delete the partition, the system information on this partition
- will be lost and you will not be able to start your computer from the
- (hard) drive. You will need to start your computer from a floppy disk.
- Make sure you have a system disk before continuing.
-
- WARNING - directory full
-
- There are more files on your disk than can be accommodated in the root
- directory. If you proceed after seeing this message, some of your files
- will be lost during the recovery process. Do not proceed unless
- absolutely necessary. If you need to recover all the files on a disk,
- recover them one at a time so information will not be lost.
-
- WARNING! Diskette is out of sequence
- Replace diskette or continue if OK
-
- Restore the disks in the order that you backed them up.
-
- WARNING: EMM386 installed without a LIM 3.2 compatible Page Frame
-
- The EMM386 expanded-memory manager was unable to create a page frame that
- conforms to version 3.2 of the Lotus/Intel/Microsoft extended-memory
- specification (LIM EMS). If the DEVICE command in your CONFIG.SYS file
- that installs EMM386.EXE contains the P<n> switch, make sure the
- addresses for pages 0 through 3 are contiguous, if possible.
-
- WARNING! File <filename>
- is a read-only file
- Replace the file (Y/N)?
-
- Type y if you want to restore the read-only file from the backup disk.
- Type n if you do not want to restore this file.
-
- WARNING! File <filename>
- was changed after it was backed up
- Replace the file (Y/N)?
-
- The file you specified has been changed since you created the backup.
- If you replace the file from the backup, you will lose any changes made
- since the backup was created. Type y if you want to continue, or type
- n if you do not.
-
- WARNING! Files in the target drive
- <drive>:\BACKUP directory will be erased
-
- If you do not want the BACKUP command to erase the files, insert a
- different disk, or type CTRL+C to cancel the backup process. Specify a
- different backup subdirectory, or use the BACKUP command with the /a
- switch to add the backup files without deleting existing backup files.
-
- WARNING! Files in the target drive
- <drive>:\ root directory will be erased
-
- If you do not want the BACKUP command to erase the files, type CTRL+C to
- cancel the backup process. Use a different disk or use the BACKUP
- command with the /a switch to add the backup files without deleting
- existing files.
-
- WARNING: Invalid parameter ignored:
-
- The DEVICE command in your CONFIG.SYS file that loads the HIMEM
- extended-memory manager contains an invalid parameter or switch. Fix
- the invalid parameter.
-
- WARNING! Logical drives past Z: exist and will be ignored
-
- You can create up to 24 logical drives. Extra drives will not be
- accessible. Use the FDISK command to repartition the disk with fewer
- logical drives.
-
- WARNING! No files were found to back up
-
- Make sure you typed the filenames correctly, and that the files exist.
-
- WARNING! No files were found to restore
-
- The RESTORE command did not find the file that you specified on the
- backup disk(s). Make sure you typed the filename correctly or use the
- "*.*" wildcard specification if you want to restore all the files on
- the backup disk(s).
-
- WARNING! No partitions are set active - disk 1 is not startable unless
- a partition is set active
-
- If you do not set a primary partition as active, you will not be able to
- start your computer from the hard disk. To set an active partition,
- choose option 2, "Set active partition," from the main Fdisk menu.
-
- WARNING: Option ROM or RAM detected within page frame.
-
- The DEVICE command in your CONFIG.SYS file that loads the EMM386
- expanded-memory manager specifies the address of a page frame that
- overlaps with read-only memory (ROM) or conventional random-access
- memory (RAM). Make sure that the addresses specified in the DEVICE
- command are correct. You can use the /x switch to prevent EMM386.EXE
- from using a particular range of memory for a page.
-
- Warning! Partitions were saved from <number> fixed disk(s), but this
- system has <number>.
-
- The PARTNSAV.FIL file contains partitioning information for a different
- number of disk drives than exists on your system. Most likely, a fixed
- (hard) drive was added or removed since PARTNSAV.FIL was created by
- the Mirror program. The UNFORMAT command will only be able to restore
- the partition information for drives that were on the system when
- PARTNSAV.FIL was created.
-
- WARNING: Shadow RAM disable not supported on this system.
-
- You turned off shadow RAM using the /SHADOWRAM:OFF switch, but the
- HIMEM extended-memory manager could not disable it. Remove the
- /SHADOWRAM:OFF switch from the DEVICE=HIMEM.SYS command in your
- CONFIG.SYS file, and restart your computer.
-
- WARNING: Shadow RAM is in use and can't be disabled.
-
- You turned off shadow RAM using the /SHADOWRAM:OFF switch, but the
- HIMEM extended-memory manager could not disable it. Remove the
- /SHADOWRAM:OFF switch from the DEVICE=HIMEM.SYS command in your
- CONFIG.SYS file, and restart your computer.
-
- WARNING: The A20 Line was already enabled.
-
- The HIMEM extended-memory manager determined that another program had
- already enabled an internal communication channel used by the
- extended-memory manager. This could mean that another memory manager
- was active before HIMEM.SYS was loaded, or that HIMEM.SYS may not be
- able to control the A20 line.
-
- WARNING: The High Memory Area is unavailable.
-
- The HIMEM extended-memory manager could not use the memory in the high
- memory area (HMA). Either the high memory area is already being used, or
- your computer does not have a high memory area.
-
- Warning! The next step writes changes to disk.
-
- The UNFORMAT command is preparing to restore files and subdirectories.
- If you want to quit without making changes to the disk, type CTRL+C.
-
- WARNING! The partition set active is not startable.
-
- Set a primary DOS partition as the active partition. The primary DOS
- partition must contain the files MSDOS.SYS, IO.SYS, and COMMAND.COM so
- that you can start your system.
-
- WARNING: This disk cannot be unformatted if system files are transferred
- Proceed with system transfer anyway (Y/N)?
-
- Because you cannot unformat the disk, make sure you have a copy of any
- information you want to save before continuing.
-
- WARNING: This version of HIMEM.SYS may cause conflicts with EMM386.
-
- The DEVICE commands in your CONFIG.SYS file that install HIMEM.SYS and
- EMM386.EXE specify versions of these files that may be incompatible. If
- you do not have the HIMEM.SYS and EMM386.EXE files that came with
- MS-DOS version 5.0, use the EXPAND command to expand and copy the
- correct version from your MS-DOS installation disks.
-
- WARNING!
- Unrecognized DOS INT 25h/26h handler. Some other TSR programs may behave
- erratically while deletion-tracking software is resident! Try installing
- MIRROR program before your other resident programs.
-
- You installed the Mirror program after another memory-resident (TSR)
- program that monitors the same system events as Mirror. As a result,
- Mirror may interfere with the program that was loaded first. Restart
- your computer and then use the MIRROR command with the /t switch before
- installing other memory-resident programs.
-
- WARNING: User specified ranges overlap.
-
- The DEVICE command in your CONFIG.SYS file that installs the EMM386
- expanded-memory manager specifies address ranges that overlap. Make
- sure the specified address ranges are separate or contiguous.
-
- WARNING: Weitek Coprocessor not installed.
-
- The DEVICE command in your CONFIG.SYS file that installs the EMM386
- expanded-memory manager contains the W=ON switch to enable support for
- the Weitek coprocessor. However, there is no Weitek coprocessor on your
- system. Remove the W=ON switch from your CONFIG.SYS file.
-
- Weitek Coprocessor is inaccessible until EMM386 is re-activated.
-
- Reactivate the EMM386 expanded-memory manager in order to access the
- Weitek Coprocessor.
-
- Weitek Coprocessor not installed.
-
- You used the EMM386 command with the W switch to enable or disable
- support for a Weitek coprocessor. However, EMM386.EXE cannot locate a
- Weitek coprocessor on your system. If you have a Weitek coprocessor
- installed, make sure it is functioning properly.
-
- What drive do you want to delete?
-
- Type the letter of the logical drive that you want to delete. Before
- continuing, make sure you have made a backup of any information you want
- to save.
-
- What Non-DOS partition do you want to delete?
-
- Type the number of the non-DOS partition that you want to delete.
-
- What primary partition do you want to delete?
-
- Type the number of the primary partition that you want to delete.
-
- Write failure, diskette unusable
-
- Use a different disk for the destination.
-
- Write fault error
-
- MS-DOS cannot write data to the device. Make sure you correctly connected
- and configured the device.
-
- Write protect error
-
- You cannot format or write a file to a write-protected disk. Either
- remove the write-protection or use another disk.
-
- Wrong DOS version.
-
- You cannot use the UNFORMAT command with versions of MS-DOS lower
- than 2.0.
-
- XMS Driver not installed.
-
- An error occurred and the HIMEM extended-memory manager was not able
- to load the extended memory handler.
-
- You must have the file WINA20.386 in the root of your boot drive
- to run Windows in Enhanced Mode
-
- Make sure WINA20.386 is in the root directory of the drive you use to
- start MS-DOS. If the file has been moved, make sure the command line
- SWITCHES=/W appears in your CONFIG.SYS file and the command line
- DEVICE=[<drive>:][<path>]WINA20.386 appears in the [386Enh] section of
- your Windows SYSTEM.INI file. If you cannot find this file, use
- the EXPAND command to expand and copy the file from your MS-DOS
- installation disks.
-
- Your target disk is unformatted and No FORMAT program was found.
- Do you have another disk with FORMAT on it (Y/N)?
-
- You specified an unformatted target (destination) disk. The BACKUP
- command tried to start the MS-DOS Format program to format the disk,
- but it could not find FORMAT.COM. If you have a floppy disk containing
- FORMAT.COM, type y and insert the disk into the specified disk drive.
- Press a key to continue, or CTRL+C to quit. If you do not have a disk
- containing FORMAT.COM, type n to cancel the backup process. Use a
- different disk for the destination disk, or use the EXPAND command to
- expand and copy FORMAT.COM from your MS-DOS installation disks.