'VFAT Device Initialization Failed.'

The machine is a Compaq Prolinea 4/33s. This problem originally started by resetting the BIOS password, and problems with the hard drive configuration in BIOS.

The machine boots from C: into DOS. (SYS was copied from a Win95 StartUp disk.) Win95 does not start as expected. When Windows was manually started from c:\Windows, the system returned 'Could not load VFAT on StartUp' or 'VFAT Device Initialization Failed.' Is a file missing? Or something else wrong?

Who is Participating?
Jason_SConnect With a Mentor Commented:
jpas:  By looking at your other question (10223380) I believe that this is due to the change in CMOS.  Since you changed this setting, your system will have to be reloaded to run, and run optimaly.  By this I mean re-fdisk, and format.  This will wipe everything off the drive, so be sure to backup your important information.  Otherwise, you will need to change this setting back to its previous one if you can find it.

If you choose to reinstall, first make sure that the CMOS is set up properly.  Most BIOS's will have an Auto Detect setting.  Use this setting.
When you try to start WIN95 from C:\WINDOWS by typing WIN
after a failure to load windows and an automatic return to
the C:\.prompt due to windows failure to load, it means that
there are drivers that did not load and VFAT is one of them.

If these drivers are missing completely you will need to re-install them.  The quickest way is to do as Jason S says
I would consider this comment last-ditch efforts to keep from reinstalling.

The Win95 startup disk you copied the system from--was it one you created from your install (emergency startup disk) or is it the floppy disk used to setup Win95 from CDROM?  If it is the floppy for CDROM installation, it has goofy autoexec.bat/config.sys files on it.  Rename autoexec.bat and config.sys and see if it boots.  

To be absolutely sure of the OS, I would go to a working Win95 machine, run SYS C: A: from a prompt, copy SYS.COM, autoexec.bat, config.sys to the floppy, and then run SYS A: C: on the machine that is not working, copy autoexec.bat, config.sys.

Good luck.
[Webinar] Kill tickets & tabs using PowerShell

Are you tired of cycling through the same browser tabs everyday to close the same repetitive tickets? In this webinar JumpCloud will show how you can leverage RESTful APIs to build your own PowerShell modules to kill tickets & tabs using the PowerShell command Invoke-RestMethod.

Good comment kmorgan
This would certainly save this man a lot of time.
Try this:

Restart your computer and press F8 when you see the "Starting Windows 95" message. Choose Safe mode command prompt only from the startup menu.
Type attrib -s -h -r msdos.sys and press enter.
Then type edit msdos.sys.
Verify that the following lines exist in the msdos.sys:

Make any necessary changes, save, and then close the Msdos.sys file.
Type attrib +s +h +r msdos.sys. Then restart the computer. The last thing that you can try is to delete the winboot.ini file from the root folder of the boot partition. To do this restart the computer, and press F8 when you see the "Starting Windows 95" message is reported, and choose Safe Mode Command Prompt only. Then delete the winboot.ini file from the root folder and restart the computer

jpasAuthor Commented:
It'll be most of a week before I get back to this machine, but I'll try the suggestions given. If all else fails, I can do as Jason_S suggested w/fdisk. I need more experience with fdisk anyway. Thanks to all that helped with this one.
All Courses

From novice to tech pro — start learning today.