A Windows 98 & ME forum. Win98banter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » Win98banter forum » Windows 98 » Improving Performance
Site Map Home Authors List Search Today's Posts Mark Forums Read Web Partners

VFAT Device Initialization Failed



 
 
Thread Tools Display Modes
  #1  
Old June 23rd 04, 09:45 PM
Margo Guda
external usenet poster
 
Posts: n/a
Default VFAT Device Initialization Failed

There is an article in the MS knowledgebase that addresses my problem,
only none of the solutions suggested there seem to apply to my
situation. And restoring a previous registry makes the problem go away,
although I cannot say this really solves the problem, because any
changes I made to my system are also gone. Specifically, Microsoft names
these possible causes for my problem:
-1- ifshlp.sys is missing from my windows folder. It is not.
-2- config.sys line points to a previous ifshlp.sys version. My
config.sys file is 0 bytes. It points nowhere.
-3- device=c:\windows\ifshlp.sys is deleted from config.sys. See above.
-4- [paths] section in msdos.sys is incorrect. No errors there.
-5- winboot.ini from previous installation in the root of the startup
disk. That would be C. I do not have this file anywhere.
-6- maxfilecache=4096 in system.ini. My maxfilecache is 16384.
I have tried making a config.sys file (with the call to ifshlp.sys the
only line). This did not help. I've made a bootlog. This shows that the
boot process ends with the device init of vfat. When I restore the
registry the system boots normally.
I hope someone can help me figure this out, I no longer know what to try
next.

Thanks in advance.
Margo Guda.
  #2  
Old June 24th 04, 01:38 AM
glee
external usenet poster
 
Posts: n/a
Default VFAT Device Initialization Failed

Please supply the MSKB article number you are referring to.

Remove *any* maxfilecache setting in the [vcache] section of System.ini

Examine the system.ini file you have in place when the error occurs, and compare it
to the System.ini file you are restoring when you restore the Registry. When you
use "scanreg /restore" from a DOS boot, you are also replacing the system.ini and
win.ini files, in addition to the Registry.
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


"Margo Guda" wrote in message
...
There is an article in the MS knowledgebase that addresses my problem,
only none of the solutions suggested there seem to apply to my
situation. And restoring a previous registry makes the problem go away,
although I cannot say this really solves the problem, because any
changes I made to my system are also gone. Specifically, Microsoft names
these possible causes for my problem:
-1- ifshlp.sys is missing from my windows folder. It is not.
-2- config.sys line points to a previous ifshlp.sys version. My
config.sys file is 0 bytes. It points nowhere.
-3- device=c:\windows\ifshlp.sys is deleted from config.sys. See above.
-4- [paths] section in msdos.sys is incorrect. No errors there.
-5- winboot.ini from previous installation in the root of the startup
disk. That would be C. I do not have this file anywhere.
-6- maxfilecache=4096 in system.ini. My maxfilecache is 16384.
I have tried making a config.sys file (with the call to ifshlp.sys the
only line). This did not help. I've made a bootlog. This shows that the
boot process ends with the device init of vfat. When I restore the
registry the system boots normally.
I hope someone can help me figure this out, I no longer know what to try
next.

Thanks in advance.
Margo Guda.


  #3  
Old June 25th 04, 02:46 PM
Margo Guda
external usenet poster
 
Posts: n/a
Default VFAT Device Initialization Failed

139063.

I compared both win.ini and system.ini as you suggested, and find no
differences. It must be in the registry. When I restore the registry I
can boot.


glee wrote:

Please supply the MSKB article number you are referring to.

Remove *any* maxfilecache setting in the [vcache] section of System.ini

Examine the system.ini file you have in place when the error occurs, and compare it
to the System.ini file you are restoring when you restore the Registry. When you
use "scanreg /restore" from a DOS boot, you are also replacing the system.ini and
win.ini files, in addition to the Registry.
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


"Margo Guda" wrote in message
...

There is an article in the MS knowledgebase that addresses my problem,
only none of the solutions suggested there seem to apply to my
situation. And restoring a previous registry makes the problem go away,
although I cannot say this really solves the problem, because any
changes I made to my system are also gone. Specifically, Microsoft names
these possible causes for my problem:
-1- ifshlp.sys is missing from my windows folder. It is not.
-2- config.sys line points to a previous ifshlp.sys version. My
config.sys file is 0 bytes. It points nowhere.
-3- device=c:\windows\ifshlp.sys is deleted from config.sys. See above.
-4- [paths] section in msdos.sys is incorrect. No errors there.
-5- winboot.ini from previous installation in the root of the startup
disk. That would be C. I do not have this file anywhere.
-6- maxfilecache=4096 in system.ini. My maxfilecache is 16384.
I have tried making a config.sys file (with the call to ifshlp.sys the
only line). This did not help. I've made a bootlog. This shows that the
boot process ends with the device init of vfat. When I restore the
registry the system boots normally.
I hope someone can help me figure this out, I no longer know what to try
next.

Thanks in advance.
Margo Guda.



  #4  
Old June 27th 04, 01:51 AM
glee
external usenet poster
 
Posts: n/a
Default VFAT Device Initialization Failed

....and it's not a laptop with SystemSoft drivers installed, I presume.
I would export the registry to a text file, and when the error next occurs, reboot
to DOS mode and export the Registry to a text file again in real-mode. Restore the
registry so that you can boot to Windows, and do a file comparison between the two
exports, using an app such as WinDiff (available on the Win98 CD).

Have you had your physical memory (RAM) checked, to make sure it is not the problem,
corrupting the Registry in memory?
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


"Margo Guda" wrote in message
...
139063.

I compared both win.ini and system.ini as you suggested, and find no
differences. It must be in the registry. When I restore the registry I
can boot.


glee wrote:

Please supply the MSKB article number you are referring to.

Remove *any* maxfilecache setting in the [vcache] section of System.ini

Examine the system.ini file you have in place when the error occurs, and compare

it
to the System.ini file you are restoring when you restore the Registry. When

you
use "scanreg /restore" from a DOS boot, you are also replacing the system.ini

and
win.ini files, in addition to the Registry.
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


"Margo Guda" wrote in message
...

There is an article in the MS knowledgebase that addresses my problem,
only none of the solutions suggested there seem to apply to my
situation. And restoring a previous registry makes the problem go away,
although I cannot say this really solves the problem, because any
changes I made to my system are also gone. Specifically, Microsoft names
these possible causes for my problem:
-1- ifshlp.sys is missing from my windows folder. It is not.
-2- config.sys line points to a previous ifshlp.sys version. My
config.sys file is 0 bytes. It points nowhere.
-3- device=c:\windows\ifshlp.sys is deleted from config.sys. See above.
-4- [paths] section in msdos.sys is incorrect. No errors there.
-5- winboot.ini from previous installation in the root of the startup
disk. That would be C. I do not have this file anywhere.
-6- maxfilecache=4096 in system.ini. My maxfilecache is 16384.
I have tried making a config.sys file (with the call to ifshlp.sys the
only line). This did not help. I've made a bootlog. This shows that the
boot process ends with the device init of vfat. When I restore the
registry the system boots normally.
I hope someone can help me figure this out, I no longer know what to try
next.

Thanks in advance.
Margo Guda.




  #5  
Old June 28th 04, 10:39 PM
Margo Guda
external usenet poster
 
Posts: n/a
Default VFAT Device Initialization Failed

No it is not a laptop.
I have not had memory checked especially; the check at powerup says
memory is OK. And it's not every registry edit that gets corrupted, just
after some installs. I have done as you suggested, and exported a
restored registry to a text file. Then I installed the software that
causes the trouble. I booted into safe mode and exported its registry. I
tried to do it from a DOS prompt but after two hours of waiting for
regedit I thought it wouldn't finish the job.
I did the comparison; this is an html file of about 50kb. I don't know
what to look for in this file in terms of errors however. Would you be
so kind to take a look at it for me? Can I mail it to you?

With thanks for your help.

glee wrote:
...and it's not a laptop with SystemSoft drivers installed, I presume.
I would export the registry to a text file, and when the error next occurs, reboot
to DOS mode and export the Registry to a text file again in real-mode. Restore the
registry so that you can boot to Windows, and do a file comparison between the two
exports, using an app such as WinDiff (available on the Win98 CD).

Have you had your physical memory (RAM) checked, to make sure it is not the problem,
corrupting the Registry in memory?
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


"Margo Guda" wrote in message
...

139063.

I compared both win.ini and system.ini as you suggested, and find no
differences. It must be in the registry. When I restore the registry I
can boot.


glee wrote:


Please supply the MSKB article number you are referring to.

Remove *any* maxfilecache setting in the [vcache] section of System.ini

Examine the system.ini file you have in place when the error occurs, and compare


it

to the System.ini file you are restoring when you restore the Registry. When


you

use "scanreg /restore" from a DOS boot, you are also replacing the system.ini


and

win.ini files, in addition to the Registry.
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


"Margo Guda" wrote in message
...


There is an article in the MS knowledgebase that addresses my problem,
only none of the solutions suggested there seem to apply to my
situation. And restoring a previous registry makes the problem go away,
although I cannot say this really solves the problem, because any
changes I made to my system are also gone. Specifically, Microsoft names
these possible causes for my problem:
-1- ifshlp.sys is missing from my windows folder. It is not.
-2- config.sys line points to a previous ifshlp.sys version. My
config.sys file is 0 bytes. It points nowhere.
-3- device=c:\windows\ifshlp.sys is deleted from config.sys. See above.
-4- [paths] section in msdos.sys is incorrect. No errors there.
-5- winboot.ini from previous installation in the root of the startup
disk. That would be C. I do not have this file anywhere.
-6- maxfilecache=4096 in system.ini. My maxfilecache is 16384.
I have tried making a config.sys file (with the call to ifshlp.sys the
only line). This did not help. I've made a bootlog. This shows that the
boot process ends with the device init of vfat. When I restore the
registry the system boots normally.
I hope someone can help me figure this out, I no longer know what to try
next.

Thanks in advance.
Margo Guda.



  #6  
Old June 29th 04, 02:55 AM
glee
external usenet poster
 
Posts: n/a
Default VFAT Device Initialization Failed

Yes, you can email it to me at this address:
glenv @ mvps . org
(remove the spaces)
I can't say that I will find anything that points to registry corruption, though.

FWIW, the memory test at powerup just counts the memory....it does not do any
extensive testing. In Safe Mode, only slightly more testing is done at startup.
This is the first you have mentioned that a particular software install is what is
causing the problem....that sheds a different light on the problem. What program
installation is causing the error?

FYI, when exporting the registry from DOS mode, you should first run the command
SMARTDRV, or it will take nearly forever:
smartdrv
regedit.exe /e drivepathfilename.txt
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


"Margo Guda" wrote in message
...
No it is not a laptop.
I have not had memory checked especially; the check at powerup says
memory is OK. And it's not every registry edit that gets corrupted, just
after some installs. I have done as you suggested, and exported a
restored registry to a text file. Then I installed the software that
causes the trouble. I booted into safe mode and exported its registry. I
tried to do it from a DOS prompt but after two hours of waiting for
regedit I thought it wouldn't finish the job.
I did the comparison; this is an html file of about 50kb. I don't know
what to look for in this file in terms of errors however. Would you be
so kind to take a look at it for me? Can I mail it to you?

With thanks for your help.

glee wrote:
...and it's not a laptop with SystemSoft drivers installed, I presume.
I would export the registry to a text file, and when the error next occurs,

reboot
to DOS mode and export the Registry to a text file again in real-mode. Restore

the
registry so that you can boot to Windows, and do a file comparison between the

two
exports, using an app such as WinDiff (available on the Win98 CD).

Have you had your physical memory (RAM) checked, to make sure it is not the

problem,
corrupting the Registry in memory?
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


"Margo Guda" wrote in message
...

139063.

I compared both win.ini and system.ini as you suggested, and find no
differences. It must be in the registry. When I restore the registry I
can boot.


glee wrote:


Please supply the MSKB article number you are referring to.

Remove *any* maxfilecache setting in the [vcache] section of System.ini

Examine the system.ini file you have in place when the error occurs, and

compare

it

to the System.ini file you are restoring when you restore the Registry. When


you

use "scanreg /restore" from a DOS boot, you are also replacing the system.ini


and

win.ini files, in addition to the Registry.
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


"Margo Guda" wrote in message
...


There is an article in the MS knowledgebase that addresses my problem,
only none of the solutions suggested there seem to apply to my
situation. And restoring a previous registry makes the problem go away,
although I cannot say this really solves the problem, because any
changes I made to my system are also gone. Specifically, Microsoft names
these possible causes for my problem:
-1- ifshlp.sys is missing from my windows folder. It is not.
-2- config.sys line points to a previous ifshlp.sys version. My
config.sys file is 0 bytes. It points nowhere.
-3- device=c:\windows\ifshlp.sys is deleted from config.sys. See above.
-4- [paths] section in msdos.sys is incorrect. No errors there.
-5- winboot.ini from previous installation in the root of the startup
disk. That would be C. I do not have this file anywhere.
-6- maxfilecache=4096 in system.ini. My maxfilecache is 16384.
I have tried making a config.sys file (with the call to ifshlp.sys the
only line). This did not help. I've made a bootlog. This shows that the
boot process ends with the device init of vfat. When I restore the
registry the system boots normally.
I hope someone can help me figure this out, I no longer know what to try
next.

Thanks in advance.
Margo Guda.




  #7  
Old June 29th 04, 03:39 AM
Margo Guda
external usenet poster
 
Posts: n/a
Default VFAT Device Initialization Failed

Thanks. I will mail the difference file tomorrow.
When I think back, every time I had this problem (and this is not the
first time) it was after an install.
The first time it happened was with the upgrade of corel wordperfect
(from 10 to 11). I've gone back to 10.
This time though the program is the palm desktop, version 4.14. Most of
the registry entries I see are related to that software, but there are
some changes that are puzzling.
Thanks for the tip on smartdrv. I'd forgotten all about that!

glee wrote:

Yes, you can email it to me at this address:
glenv @ mvps . org
(remove the spaces)
I can't say that I will find anything that points to registry corruption, though.

FWIW, the memory test at powerup just counts the memory....it does not do any
extensive testing. In Safe Mode, only slightly more testing is done at startup.
This is the first you have mentioned that a particular software install is what is
causing the problem....that sheds a different light on the problem. What program
installation is causing the error?

FYI, when exporting the registry from DOS mode, you should first run the command
SMARTDRV, or it will take nearly forever:
smartdrv
regedit.exe /e drivepathfilename.txt


 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
VFAT Art General 1 July 21st 04 01:16 AM
Please help! Display settings !! Mitzi Monitors & Displays 12 July 11th 04 05:19 AM
Plug and Play Device Driver Not Loaded rick Plug & Play 1 June 12th 04 10:42 AM
PCI multimedia Audio Device rocklady33 Multimedia 0 June 11th 04 10:12 PM
usb device driver installation problem shadoug Plug & Play 1 May 31st 04 06:01 AM


All times are GMT +1. The time now is 07:20 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 Win98banter.
The comments are property of their posters.