Tried three different slots and the issues persists. I tried adding a line
in config.sys:
device=c:\windows\ifshlp.sys. It did not make a difference. In trobule shooting I have since found that if I do not load the config.sys the cared works and the vfat error is gone. There is not much in the config.sys so I am a little puzzled as to why it appears to be the conflict.


"Ingeborg" wrote:

"=?Utf-8?B?RGFubnk=?=" wrote in
:

I have been battling a VFAT error (a device or resource required by
vfat is not present or is unavailable. Vfat cannot continue loading).

The error message only occurs when a wireless pci card and drivers are
loaded. It disappears if the card is removed. I have tried the MS
knowldge base articles on this issue with no luck in the results.

However, I have noticed the following, but do not know if it is the
issue:

If I do a step by step confirmation during boot, the cpu will load,
but the card still does not function. I did noticed that during boot
the ifshlp.sys file is loading as follows:
devicehigh=c:\windows\ifshlp.sys

This file is one that comes up in the knowldge abase articles, but it
should be located in the config.sys, and not loading to high mem.

My problems is that I cannot find where this command is located. It
is definitly not in the autexec.bat, config.sys, win.ini, system.ini
or protocol.ini, by checking with the sysedit command.

The ifshlp.sys loading into high mem may not be the root cause, but I
would like to at least check. Where \ how can I find this boot
command to change.

Thanks,

Danny


ifshlp.sys is automatically loaded when windows boots. When you want to
overrule *how* it's loaded you should put a line in config.sys:
device=c:\windows\ifshlp.sys


Maybe your problem is caused by an interrupt conflict. You could try the
NIC in a different slot.