Solved

VFAT Device Initialization Faile

Posted on 1997-10-22
6
489 Views
Last Modified: 2013-12-29
I get this errror when I try to start.  I can't figure what is missing though when I look at the bootlog.txt.  I get the following:
  Loading Vxd = ebios
  Load Failed = ebios
  Loading Vxed = vshare
  Load Failed = vsharek.
I get the same lines for EBIOS and VCACHE.
Don't have a clue where to go from here.
I can only start Win95 in Safe Mode.


 on
0
Comment
Question by:DEWEY
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 3
6 Comments
 
LVL 9

Accepted Solution

by:
magigraf earned 50 total points
ID: 1698719
Here is your solution:

SYMPTOMS

When you start Windows 95, you may receive the following error message on a blue screen:

   VFAT Device Initialization Failed

   A device or resource required by VFAT is not present
   or is unavailable. VFAT cannot continue loading.

   System halted.

CAUSE

This error message can occur when any one of the following conditions exists:

•The Ifshlp.sys file is missing from the Windows folder.
•The Config.sys file contains a line pointing to a previous  version of the Ifshlp.sys file.
•The following Ifshlp.sys statement was deleted from the Config.sys file after reinstalling Windows 95:

      DEVICE=<DRIVE>:\<WINDOWS>\IFSHLP.SYS

where <drive> is the drive containing Windows 95 and <windows> is the Windows 95 folder. For example, if Windows 95 is installed in the WINDOWS folder on drive C, the line will read:

      DEVICE=C:\WINDOWS\IFSHLP.SYS

•The [Paths] section in the Msdos.sys file is incorrect.
•A Winboot.ini file from a previous incomplete installation is  present in the root folder of the boot disk.

RESOLUTION

To resolve the problem, use the method in the appropriate section below.

Ifshlp.sys File Missing from Windows Folder

If the Ifshlp.sys file is missing from the Windows folder, extract a new copy of the file from your original Windows 95 disks or CD-ROM to the Windows folder.

Config.sys file points to Previous Version of Ifshlp.sys file

1.Restart your computer. When you see the "Starting Windows 95" message, press the F8 key, and then choose Safe Mode Command Prompt Only from the Startup menu.

2.Use any text editor (such as Edit.com) to open the Config.sys file.

3.Remove the line that loads Ifshlp.sys. (Windows 95 automatically loads this driver when you start your computer.)

4.Save and then close the Config.sys file.

5.Restart your computer.

Ifshlp.sys statement was deleted from the Config.sys file after reinstalling Windows 95

When reinstalling Windows 95, Setup will delete the Ifshlp.sys statement in the Config.sys file and not replace it. To add the Ifshlp.sys statement back to the Config.sys file, follow these steps:

1.Restart your computer. When you see the "Starting Windows 95" message, press the F8 key, and then choose Safe Mode Command Prompt Only from the Startup menu.

2.Use any text editor (such as Edit.com) to open the Config.sys file.

3.Add the following line to the Config.sys file:

      DEVICE=<DRIVE>:\<WINDOWS>\IFSHLP.SYS

where <drive> is the drive containing Windows 95 and <windows> is the Windows 95 folder. For example, if Windows 95 is installed in the WINDOWS folder on drive C, add the following line:

      DEVICE=C:\WINDOWS\IFSHLP.SYS

4.Save and then close the Config.sys file.

5.Restart your computer.

Incorrect [Paths] Section in Msdos.sys File

1.Restart your computer. When you see the "Starting Windows 95" message, press the F8 key, and then choose Safe Mode Command Prompt Only from the Startup menu.

2.Type the following line at the command prompt:

      attrib -s -h -r msdos.sys

3.Use any text editor (such as Edit.com) to open the Msdos.sys file.

4.Verify that the following lines in the Msdos.sys file are correct

      [Paths]
      WinDir=<Windows>
      WinBootDir=<Windows>
      HostWinBootDrv=C

where <Windows> is the folder containing Windows 95. Note that if you are using disk compression software (such as DriveSpace), you must change the drive letter in the "HostWinBootDrv=" line to the drive letter of the host drive.

5.Save and then close the Msdos.sys file.

6.Type the following line at the command prompt:

      attrib +s +h +r msdos.sys

7.Restart your computer.

Winboot.ini File Present in Root Folder of Boot Drive

1.Restart your computer. When you see the "Starting Windows 95" message, press the F8 key, and then choose Safe Mode Command Prompt Only from the Startup menu.

2.Delete the Winboot.ini file in the root folder of the boot drive.

3.Restart your computer.

Hope this helped
If you need help in the Extract command let me know.
Regards
0
 

Author Comment

by:DEWEY
ID: 1698720
I should have added that I normally boot up via <F4> into WFW3.11 but sometimes would like to run Win95 other than in Safe Mode as I have clients that use my Windows app in Win95.

So I have a WINDOWS directory for Win3.11 and a WIN95 directory for the other guy.

Cause #1 - I have a copy of IFSHLP.SYS in my Win95 folder.
Cause #2 - Here is a part of my current CONFIG.SYS
      DEVICE=C:\WINDOWS\HIMEM.SYS
 
       LASTDRIVE=M
       DEVICE=C:\DOS\EMM386.EXE NOEMS

       rem for Workgroup network loader
       DEVICEHIGH /L:1,4560 =C:\WINDOWS\IFSHLP.SYS

My present CONFIG.SYS does call for a IFSHLP.SYS which is in my WINDOWS directory.  BTW, there is also a IFSHLP.SYS in the WIN95 directory.
Cause #3 -see above as there is a statement in my config.sys but it goes to my WINDOWS directory and not my WIN95 directory.
Cause #4 - looks OK
Cause #5 - If I start Win95 in Safe Mode Command there is no winboot.sys in my root directory but if I go into Windows like I normally do then there is a WINBOOT.SYS in my root.

Is it a simple matter to change the line in my CONFIG.SYS to read
      DEVICEHIGH /L:1,4560 =C:\WIN95\IFSHLP.SYS
Will that do the trick?

DeWayne

0
 
LVL 9

Expert Comment

by:magigraf
ID: 1698721
I see now better when you added that WIN 3.11 OS residing on your system.  That's fine you could use the multi-boot feature which as you now is part of Win95.

Now your system during the bootup would not even care if you have an Autoexec.bat, or Config.sys. Therefore rename your config.sys to config.001 and autoexec.bat to autoexec.001.

To be able to select the "previous version of DOS", you would have to find all your OLD autoexec.bat and Config.sys you had prior of installing WIN95 and rename the most recent ones to Autoexec.dos and config.dos consequently.

These are the files that you need when you'll hit your F4 to get into the MULTI-BOOT and start a previous version of MS-DOS and consequently WIN 3.11. Here you would go to your win3.11 directory and you type "WIN" to load the WIN3.11.

Is that scenario happening or not??
If I stated something that is not in your actual setting please modify it and post results, or else update me.
Regards

0
What Is Transaction Monitoring and who needs it?

Synthetic Transaction Monitoring that you need for the day to day, which ensures your business website keeps running optimally, and that there is no downtime to impact your customer experience.

 

Author Comment

by:DEWEY
ID: 1698722
The plot thickens.  A couple things I sud clear up:
   1.DOS is working 100%
   2.Windows is working 100% whether I start it from the dot prompt or use multi-booting feature of Win95
   3.The following files are in my root directory.
   autoexec.bat, autoexec.001, autoexec.002, autoexec.w40
   config.sys (no other).
As far as I can see I have not needed any config.dos or autoexec.dos to get into WFW3.11.
    4.I do not have an old autoexec.bat or config.sys prior to installing Win95 but I cud make one up.

I did NOT do any of what you suggested as there were already files called autoexec.001 etc etc and I can get into WFW3.11 which is the o/s I use 99% of the time.

Next round please.  Thanks.



 
0
 
LVL 9

Expert Comment

by:magigraf
ID: 1698723
Could you post your autoexec.bat and config.sys

**What a luck to have the extention 001, I always suggest to use it because normally no one does... did I pay you a visit before?? just kidding**
0
 

Author Comment

by:DEWEY
ID: 1698724
My hardware is typical: CD, Colorado tape backup etc.

***Config.sys***

DEVICE=C:\WINDOWS\HIMEM.SYS
LASTDRIVE=M
DEVICE=C:\DOS\EMM386.EXE NOEMS

rem for Workgroup network loader
DEVICEHIGH /L:1,4560 =C:\WINDOWS\IFSHLP.SYS

FILES=128
BUFFERS=50

REM loads DOS into high memory
DOS=UMB
DOS=HIGH

REM next line provides File Control Blocks
FCBS=16,0

REM a Mouse mite need the next line
STACKS=9,256

rem for CD ROM
DEVICE=C:\DEV\HIT-IDE.SYS /D:MSCD004 /N:1



***Autoexec.bat***

@REM ===== Gravis initialization (4.11) =====
@SET ULTRASND=240,7,7,11,11
@SET BLASTER=A220 I2 D1 T4
@SET ULTRADIR=C:\ULTRASND
@C:\ULTRASND\ULTRINIT.EXE -ej
@REM ===== Gravis initialization ends =====

@ECHO OFF
PROMPT $p$g
rem C:\dos\share.exe /f:4096 /l:40

SET PATH=C:\ULTRASND;C:\;C:\WINDOWS;C:\EXCAL\NETSCAPE;C:\WINFAX;        C:\DOS;C:\PKZIP;D:\ODAPI;D:\PDOXRUN;C:\UTIL;C:\MOUSE;
SET TEMP=C:\DOS
LH C:\WINDOWS\MSCDEX.EXE /S /D:MSCD004  /M:8
LH /L:1,56944 C:\MOUSE\MOUSE
LH C:\DOS\SMARTDRV.EXE /X
DOSEDIT
win :

MENU

SET PATH=%PATH%;C:\IEXPLORE
set ieppp=C:\IEXPLORE
set pctcp=C:\IEXPLORE\pctcp.shv

*** end of my autoexec.bat file

Thanks for the help.
0

Featured Post

On Demand Webinar: Networking for the Cloud Era

Did you know SD-WANs can improve network connectivity? Check out this webinar to learn how an SD-WAN simplified, one-click tool can help you migrate and manage data in the cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Learn how to PXE Boot both BIOS & UEFI machines with DHCP Policies and Custom Vendor Classes
I was prompted to write this article after the recent World-Wide Ransomware outbreak. For years now, System Administrators around the world have used the excuse of "Waiting a Bit" before applying Security Patch Updates. This type of reasoning to me …
As developers, we are not limited to the functions provided by the VBA language. In addition, we can call the functions that are part of the Windows operating system. These functions are part of the Windows API (Application Programming Interface). U…
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.

717 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question