China DOS Union

After I boot up I can't get into 98. It says:
Cannot find a device file that may be needed to run windows or a
windows application

the windows registry or system.ini file refers to this device file,but
the device file no longer exits

if you deletde this file on perpose ,try uninstlling the associated
application using its uninstall or setupprogram

if you still want to use the application associated with this device file
try reinstalling that appliation to replace the missing file

g:\ccdos\ccdos.exe
press any key to continune
What's going on? I hope someone can help me solve this.
I'm dual-booting, c:\98 d:\2000




————— Edited by willsort —————
Original title changed: Help!!!!!!!!!!!!
For the convenience of all users browsing and the moderator's management,
the OP should note that the title ought to summarize the content
————— Edited by willsort —————

[ Last edited by willsort on 2005-10-27 at 11:26 ]

It means it can't find the G:\CCDOS\CCDOS.EXE file; just press Enter and it will enter normally. Restore the CCDOS.EXE file, or delete the CCDOS.EXE entry in the registry.

No, pressing Enter doesn't work. It says the system is busy.

What the poster above said is correct. If it really still won't work, then try the method below!
Before entering win98, when your machine is starting up, hold down the crtl key or the F8 key so you can enter DOS mode. Then copy ccdos.exe back into your G：\CCDOS\ directory. Then restart the machine and it should be fine. . .
If you don't know how to enter DOS mode, read wengier's article. . . Go to New DOS Paradise and take a look at the articles written by wengier! If you don't know where New DOS Paradise is, then look at wengier's signature when he posts here.

No, under my ccdos I do have ccdos.exe啊
If I just press Enter it says
a device orresource required by vfat is not present
or is unavailable vfat can't continue loading
systen halted

Oh right, I moved the ccdos folder somewhere else.
I'll try again.

Still no good, it says
a device orresource required by VFAT is not present
or is unavailable VFAT can't continue loading
systen halted

If you boot into pure DOS only, you won't see those messages. Are you sure you booted into pure DOS? Please read wengier's article on how to enter pure DOS mode. Please go to New DOS Paradise and read the articles written by wengier!!!

Or try holding down SHIFT while booting (or press F8 and choose it from the menu), and see whether you can get into Safe Mode. If you can enter Safe Mode, then check whether there is a problem with the system drivers, or just delete the drivers you think are unnecessary.
If you can't even get into Safe Mode, then it means files required by your WINDOWS system are damaged, and the only option is to reinstall.

I can get into Safe Mode,
but I don't know what to do.
Before this I ran CardWare.
Could it be because of that?

CardWare shouldn't have anything to do with this, right!

Normally, what should it be?
I didn't touch anything either.

The following was copied from win2000 Help. You can use it for reference. (At the moment I don't have a win98 environment, so we'll just have to make do with win2000 Help.)

Repair startup failures
If the disk system or boot volume fails, the system will be unable to start. The recovery process from a startup failure depends on the disk configuration and the type of microprocessor in the computer system.

For a system or boot volume configured as part of a mirrored volume (the only fault-tolerant method that can be applied to boot and system volumes), the recovery procedure may use a boot disk.

Boot disk
To create a Windows boot disk, see creating a boot disk. After creating the boot disk, it should be tested before any failure occurs; otherwise, if the primary disk is lost, it will not be possible to start the computer from the mirrored volume. Check the boot disk by using it to start the system from the mirrored volume. Test your disk by first turning the primary disk power on and then off. In both cases, if you can log in, then the boot disk works.

Whenever a volume is changed, the boot disk should also be updated. For example, if the system is being started using volume 2 and volume 1 is deleted, the ARC name must be changed to enable volume 1. Similarly, if the system is started from volume 2 and volume 1 is deleted, and it is split into volume 1 and volume 2, the ARC name must be changed to enable volume 3.

Maintain the boot configuration
After Windows starts successfully, back up the configuration directory (\Systemroot\System32\Config), and keep the backup current whenever configuration and accounts are changed. The registry consists of the files in the configuration directory.

If it is necessary to use the repair process in Windows Setup to restore the registry files, the configuration can be restored from the backup.

Never delete Boot.ini, Ntldr, Bootsect.dos, Ntdetect.com, or Ntbootdd.sys (if Windows is installed on a SCSI disk) from the root directory of the system volume.

If you change a system that previously started Windows successfully but now fails, you can return to the previous configuration by selecting "Last Known Good Configuration" during system startup. If Windows still cannot start, use the repair process in Windows Setup to start the system. After the system restarts, data can be restored using the backup tape.

Repair Config.nt and Autoexec.nt
If Windows displays error messages related to these files, or if failures occur when running MS-DOS-based programs, check whether the Config.nt or Autoexec.nt file is incorrect or missing. These files are located in the \Systemroot\System32 directory.

If these files are incorrect or missing, new versions of the files can be copied from the boot disk into the \System32 directory.

Moderator, ah, it was because of cardware.
I remember this software modified config.sys, so I deleted everything in config.sys.
As a result, it's fixed. I couldn't understand what was written in there.
FILES=20
device=G:\NET\ifshlp.sys
LASTDRIVE=Z

Then restoring the contents of CONFIG.SYS would also work. I tried installing it at the time, but I didn't find any problem.