『楼 主』:
转贴:DOS出错提示与对策
使用 LLM 解释/回答一下
DOS出错提示与对策
如果你不懂英文,是不是对经常出现的英文提示一筹莫展,当然最好的主意是你现在就开始学习英语,未来是互联网的世纪,而互联网上的大部分资料是英文的,不懂的话,就少了一种交流的手段。不过我想给出一些常见的错误提示给大家还是必要的,不懂的时候就来查一查吧。
Abort,Retry, Ignore,fail?
退出,重试,忽略,取消?
不能识别给出的命令、或发生了使命令不能执行的磁盘或设备错误,可能是磁盘损坏或软驱门没关。
按A键 彻底终止,并回到DOS提示符。
按R键 重复执行该命令。
按I键 继续处理,忽略错误,非常冒险,建议不要采用
按F键 不执行有问题的命令,继续下述处理。有时会用到。
Access Denied
拒绝存取
试图打开一个标记为只读、存贮在写保护的磁盘上或锁定在网络上的文件。如果在子目录上使用“Type”命令,或在文件上使用“CD(chdir)”命令,也会产生这个信息。
应该用“Attrib”命令删除文件的只读状态或从磁盘中去掉写保护,然后再试试。
Bad Command or file name
错误的命令或文件名
不能识别输入的命令
应该检查以确保输入命令的正确性 确认在指定目录或用Path命令指定的搜索路径上能找到命令文件。
Boot error
引导错误
在引导时检测不到应该的外设。
应该检查计算机的设置参数,如用户自己不能解决这个问题,请找专门维修人员。
Cannot find system files
不能找到系统文件
试图从没有包含系统文件的驱动器上装入操作系统。
应该用sys命令将系统文件复制到根目录中。除非真的是不能恢复系统文件了,才可用Format/s命令重新格式化磁盘。
Cannot load command,system halted
不能加载command,系统中止
应用程序覆盖了内存中的所有或部分Command.com。
应该重新引导计算机,检查被应用程序修改过的数据是否完整,如必要可将Command.com复制到子目录,这样退出应用程序时DOS可在这儿找到Command.com。
Cannot read file allocation table
不能读到文件分配表
文件分配表已坏。
如仍能找到一些数据,那么将它们都备份到一张空盘中,也可利用Chkdsk命令修复文件分配表,如需要,可重新格式化磁盘。如果问题重复发生,那么应该修理驱动器或更换驱动器。
Divide Overflow
分配溢出,除零错误
程序可能编写有错误,未调试好,也可能是与内存中的其它程序冲突。
检查内存中的其它程序或不再使用此程序。
Drive Not Ready Error
驱动器未准备好
没有该驱动器或未放磁盘。
检查磁盘或更换磁盘。
Duplicate File Name or File Not Found
文件重名或未找到
给文件起名字时与以有的文件重名了或是在对文件操纵时根本就没这条文件。
更换名字或是检查文件名的拼写。
Error loading operating system
引导操作系统错误
操作系统文件找不到或已损坏。
用SYS命令将操作系统文件拷贝到该驱动器,如需要,可将config.sys和autoexec.bat文件拷贝到根目录中。
如不能恢复系统文件,那么从软盘引导系统,备份数据,用Format/s命令重新格式化磁盘。
EXEC failure
文件执行失败
应用程序的可执行文件包含影响处埋的错误,或者由于早已打开了太多的文件而不能打开该文件,文件可能与当前的DOS版本不兼容。
检查DOS的版本,如版本正确,可通过编辑Config.sys中的Files命令来解决这个问题。
File allocation table bad
文件分配表已损坏
很多原因,例如病毒发作,突然停机,不正常关机等都能破坏分配表
将所能找到的数据备份到空盘中,不要覆盖以前的备份。也许可通过引用Chkdsk命令来解决这个问题。如需要,重新格式化软盘,如问题反复,那么将驱动器送去修理。
File cannot be copied onto itself
文件不能拷贝成自己
你在源文件和目标文件中指定了相同的文件,或是忘了写文件名。
按需要改变源或目标文件,然后再试试看。
File creation Error
文件建立错误
可能是在磁盘中没有足够的空间为用户要创建的文件、想创建的文件早已存在,且为只读文件或是想利用早已存在的文件名来更换文件的名字。
可以换个盘,或使用别的目标名、别的目标位置,或者使用Attrib命令除去文件的只读属性。
File not found
文件未找到
在当前目录或由Path、Append命令指定的任一目录中找不到文件,或者指定的目录是空的。
检查文件名的拼法和位置,如需要改变搜索路径。
General failure
通用失败
DOS不能判断错误的原因,一般是因为驱动器中的磁盘未格式化,或格式化成非DOS系统。
应该重新格式化磁盘。
Incorrect DOS version
DOS版本不符
输入了一个不同版本的外部命令。
用setver设置版本或者使用正确的可执行文件。
Insufficient Disk Space
磁盘空间不足
磁盘中已没有可用的空间来拷贝文件或创建文件。
可以删除一些无用的文件或更换一个大一点的磁盘。
Insufficient memory
内存不足
没有足够内存来处理用户所输入的命令,一般指基本内存。
应删去一些内存驻留的文件或对内存做优化管理。还可以给系统增加更多的内存,以适应应用程序。
Invalid directory
非法目录
输入了无效的目录名或不存在的目录名。
检查目录的拼法。
Invalid Drive Specification
无效的驱动器定义
根本没有这个驱动器,可能是拼写错误。若是不能指定光驱,可能是没有安装驱动程序。
重新安装光驱。
Invalid filename or file not found
无效的文件名或文件未找到
输入的文件名包含了无效字符或通配符,或者将保留设备名用作文件名。
利用不同的文件名试试。
Invalid Media,track 0 Bad or Unusable
无效的格式,0磁道损坏或不可用
一般是磁盘损坏。
更换磁盘。
Invalid parameter
无效的参数
在命令行中没有指定正确的参数、或者有重复、禁止的 参数。
检查命令输入时的拼写或语法。
Invalid partition table
无效的分区表
硬盘分区信息中有错误。
应备份所能找到的数据,运行Fdisk来重新设置硬盘分区。
Invalid path,not directory,or directory not empty
无效的路径,非目录,或目录非空
系统不能定位指定的目录,或者用户输入了文件名来代替目录名,或者目录中包含文件(或子目录),不能被删除。
检查目录名的拼法,如果目录为空,那么它可能包含隐含文件,使用Dir/ah命令来显示任何可能的隐含文件,用attrib改变属性,删除之。
Invalid syntax
无效的语法
系统不能处理用户输入的语法格式。
应查阅正确的文件格式再试试。
No fixed disk Present
没有硬盘
系统不能检测到硬盘的存在。
应检查设置的驱动器类参数,如果不能解决这个问题,那么送去修理。
Non-System Disk or Disk Error
非系统盘或磁盘错误
系统在当前盘中找不到系统文件。
应插入包含系统文件的磁盘,或者重新引导计算机。
Not enough memory
内存不足
见Insufficient memory
NOT READY,READING DRIVE X
驱动器X未准备好
在指定的驱动器中没有盘或门没关。
插入磁盘到指定驱动器或关上驱动器门。
Program too big to fit in memory
重新太大不能载入内存
见Insufficient memory
Required Parameter missing
缺少必要的参数
见Invalid Parameter
Too many open files
打开的文件太多
超过系统规定的打开文件数目。
应在Config.sys文件中用Files命令增加最大数目,并重新引导计算机。
Unrecognized command in CONFIG.SYS
config.sys中有不可辨认的命令
在引导系统时,不能识别Config.sys文件中的命令
应编辑config.sys文件,修正无效的行。
Write fault error
写失败错误
系统不能在磁盘上写数据。
将磁盘取下再重新插好试试,仍然不行则运行Chkdsk或Scandisk,如磁盘不能恢复,扔掉它。
Write protect error
写保护错误
磁盘上有写保护
取下磁盘,去掉写保护,再试试。
DOS Error Messages and Countermeasures
If you don't understand English, are you at a loss for the often - appearing English prompts? Of course, the best idea is that you start learning English now. The future is the century of the Internet, and most of the materials on the Internet are in English. If you don't understand, you will lack a means of communication. But I think it is necessary to give some common error prompts to you. When you don't understand, just come to check.
Abort,Retry, Ignore,fail?
Quit, Retry, Ignore, Cancel?
The given command cannot be recognized, or a disk or device error that prevents the command from being executed occurs. It may be that the disk is damaged or the floppy drive door is not closed.
Press the A key to terminate completely and return to the DOS prompt.
Press the R key to execute the command again.
Press the I key to continue processing, ignoring the error. It is very risky, and it is not recommended to adopt.
Press the F key to not execute the problematic command and continue the following processing. Sometimes it will be used.
Access Denied
Access Denied
Trying to open a file marked as read - only, stored on a write - protected disk, or locked on the network. If the "Type" command is used on a sub - directory or the "CD (chdir)" command is used on a file, this information will also be generated.
The "Attrib" command should be used to remove the read - only status of the file or remove the write protection from the disk, and then try again.
Bad Command or file name
Wrong command or file name
The input command cannot be recognized.
The correctness of the input command should be checked to ensure that the command file can be found in the specified directory or in the search path specified by the Path command.
Boot error
Boot error
The corresponding peripheral cannot be detected during booting.
The setting parameters of the computer should be checked. If the user cannot solve this problem by himself, please find a professional maintenance person.
Cannot find system files
Cannot find system files
Trying to load the operating system from a drive that does not contain system files.
The sys command should be used to copy the system files to the root directory. Unless the system files are really unable to be restored, the Format/s command can be used to re - format the disk.
Cannot load command,system halted
Cannot load command, system halted
The application program overwrites all or part of Command.com in the memory.
The computer should be rebooted, and the data modified by the application program should be checked for integrity. If necessary, Command.com can be copied to a sub - directory, so that DOS can find Command.com here when exiting the application program.
Cannot read file allocation table
Cannot read file allocation table
The file allocation table is bad.
If some data can still be found, then back them up to an empty disk. The Chkdsk command can also be used to repair the file allocation table. If necessary, re - format the disk. If the problem occurs repeatedly, then the drive should be repaired or replaced.
Divide Overflow
Division overflow, division by zero error
The program may have errors in writing and not been debugged well, or may conflict with other programs in the memory.
Check other programs in the memory or stop using this program.
Drive Not Ready Error
Drive not ready
There is no such drive or no disk is inserted.
Check the disk or replace the disk.
Duplicate File Name or File Not Found
Duplicate file name or file not found
When naming a file, it is the same as an existing file, or there is no such file at all when manipulating the file.
Change the name or check the spelling of the file name.
Error loading operating system
Error loading operating system
The operating system file cannot be found or is damaged.
Use the SYS command to copy the operating system file to the drive. If necessary, copy the config.sys and autoexec.bat files to the root directory.
If the system files cannot be restored, then boot the system from a floppy disk, back up the data, and re - format the disk using the Format/s command.
EXEC failure
File execution failure
The executable file of the application program contains errors that affect processing, or the file cannot be opened because too many files have been opened already. The file may be incompatible with the current DOS version.
Check the DOS version. If the version is correct, this problem can be solved by editing the Files command in Config.sys.
File allocation table bad
File allocation table is bad
There are many reasons, for example, a virus attacks, the computer shuts down suddenly, an abnormal shutdown, etc., which can damage the allocation table.
Back up all the data that can be found to an empty disk, and do not overwrite the previous backup. Maybe the problem can be solved by using the Chkdsk command. If necessary, re - format the floppy disk. If the problem repeats, then send the drive for repair.
File cannot be copied onto itself
File cannot be copied to itself
You have specified the same file in the source file and the target file, or you have forgotten to write the file name.
Change the source or target file as needed, and then try again.
File creation Error
File creation error
There may be not enough space in the disk for the file the user wants to create, the file to be created already exists and is a read - only file, or the user wants to replace the name of the file with an existing file name.
You can change to another disk, or use another target name, another target location, or use the Attrib command to remove the read - only attribute of the file.
File not found
File not found
The file cannot be found in the current directory or in any directory specified by the Path and Append commands, or the specified directory is empty.
Check the spelling and location of the file name, and change the search path if necessary.
General failure
General failure
DOS cannot judge the cause of the error. Generally, it is because the disk in the drive is not formatted, or is formatted into a non - DOS system.
The disk should be re - formatted.
Incorrect DOS version
Incorrect DOS version
An external command of a different version is entered.
Set the version with setver or use the correct executable file.
Insufficient Disk Space
Insufficient disk space
There is no available space in the disk to copy files or create files.
Some useless files can be deleted or a larger disk can be replaced.
Insufficient memory
Insufficient memory
There is not enough memory to process the command entered by the user, generally referring to the basic memory.
Some memory - resident files should be deleted or the memory should be optimized and managed. More memory can also be added to the system to adapt to application programs.
Invalid directory
Invalid directory
An invalid directory name or a non - existent directory name is entered.
Check the spelling of the directory.
Invalid Drive Specification
Invalid drive specification
There is no such drive at all, and it may be a spelling error. If the optical drive cannot be specified, it may be that the driver program is not installed.
Re - install the optical drive.
Invalid filename or file not found
Invalid filename or file not found
The entered file name contains invalid characters or wildcards, or the reserved device name is used as the file name.
Try with a different file name.
Invalid Media,track 0 Bad or Unusable
Invalid media, track 0 is bad or unusable
Generally, the disk is damaged.
Replace the disk.
Invalid parameter
Invalid parameter
The correct parameter is not specified in the command line, or there are duplicate or forbidden parameters.
Check the spelling or grammar when entering the command.
Invalid partition table
Invalid partition table
There is an error in the hard disk partition information.
The data that can be found should be backed up, and Fdisk should be run to re - set the hard disk partition.
Invalid path,not directory,or directory not empty
Invalid path, not a directory, or directory is not empty
The system cannot locate the specified directory, or the user enters a file name instead of a directory name, or the directory contains files (or sub - directories) and cannot be deleted.
Check the spelling of the directory name. If the directory is empty, it may contain hidden files. Use the Dir/ah command to display any possible hidden files, change the attributes with attrib, and delete them.
Invalid syntax
Invalid syntax
The system cannot process the syntax format entered by the user.
The correct file format should be consulted and then try again.
No fixed disk Present
No hard disk present
The system cannot detect the existence of the hard disk.
The set drive class parameters should be checked. If this problem cannot be solved, then send it for repair.
Non - System Disk or Disk Error
Non - system disk or disk error
The system cannot find the system files on the current disk.
A disk containing system files should be inserted, or the computer should be rebooted.
Not enough memory
Insufficient memory
See Insufficient memory
NOT READY,READING DRIVE X
Drive X is not ready
There is no disk in the specified drive or the door is not closed.
Insert a disk into the specified drive or close the drive door.
Program too big to fit in memory
Program is too big to fit in memory
See Insufficient memory
Required Parameter missing
Required parameter is missing
See Invalid Parameter
Too many open files
Too many open files
The number of open files exceeds the number specified by the system.
The maximum number should be increased with the Files command in the Config.sys file, and the computer should be rebooted.
Unrecognized command in CONFIG.SYS
Unrecognized command in config.sys
The command in the Config.sys file cannot be recognized when booting the system.
The config.sys file should be edited to correct the invalid line.
Write fault error
Write fault error
The system cannot write data on the disk.
Take the disk out and insert it again. If it still doesn't work, run Chkdsk or Scandisk. If the disk cannot be restored, throw it away.
Write protect error
Write protect error
There is write protection on the disk.
Take the disk out, remove the write protection, and then try again.
|