『楼 主』:
清华同方E700保护卡罕见故障排除
使用 LLM 解释/回答一下
长假回来上班，打开我用的清华同方E700，到了保护卡计时环节，出现bad command or filename信息，电脑卡住不动了,下面有光标在闪烁。按F10想进入保护卡设置，没任何反应。
这种电脑的保护卡是做在BIOS中的，无法禁用。
进入BIOS设置U盘先启动，仍是卡在bad command or filename，到不了U盘启动环节。
难度进入了DOS？试试DIR命令，果然可看到大批BAT、EXE、COM文件。
用VER 命令，可看到版本是DOS 5.0，这个版本也罕见。
用PROMOPT $P$G命令，出现A:\提示符。
用type autoexec.bat命令，看不到内容，type config.sys可看到内容
里面没找到任何的TXT之类文件，试运行几个BAT、EXE和COM，有的没显示有的死机。
反复试了几个小时， 终于发现运行base.exe能出保护卡界面，然后按F10可进入保护卡设置，立即卸载保护卡。
重启电脑，出现保护卡安装界面，重装保护卡软件，再设置好，问题解决。
事后思考，可能原因是autoexec.bat坏了，也许重建一个autoexec.bat，写入base.exe就能修复，不过没机会去试了。
没想到多年之后还有必须用DOS的机会。
After returning to work after a long holiday, I turned on my Tsinghua Tongfang E700. When it reached the protection card timing link, the "bad command or filename" message appeared, and the computer got stuck and wouldn't move. There was a cursor flashing below. I pressed F10 to try to enter the protection card settings, but there was no response at all.
The protection card of this kind of computer is built into the BIOS and cannot be disabled.
When I entered the BIOS settings to boot from the USB drive first, it was still stuck at the "bad command or filename" and couldn't reach the USB drive boot link.
Did I enter DOS? I tried the DIR command, and indeed a large number of BAT, EXE, COM files could be seen.
Using the VER command, I could see that the version was DOS 5.0, which is also rare.
Using the PROMPT $P$G command, an A:\ prompt appeared.
Using the type autoexec.bat command, I couldn't see the content, and using the type config.sys, I could see the content.
I couldn't find any TXT - like files inside. I ran several BAT, EXE, and COM files, some didn't display and some crashed.
After trying for several hours, I finally found that running base.exe could bring up the protection card interface, then pressing F10 could enter the protection card settings, and immediately uninstall the protection card.
I restarted the computer, the protection card installation interface appeared, reinstalled the protection card software, and then set it up properly, and the problem was solved.
Afterwards, I thought that maybe the autoexec.bat was damaged, and maybe rebuilding an autoexec.bat and writing base.exe in it could fix it, but there was no chance to try it.
I didn't expect that after many years, there would still be a chance to use DOS.
|
