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 » General
Site Map Home Authors List Search Today's Posts Mark Forums Read Web Partners

VFAT



 
 
Thread Tools Display Modes
  #1  
Old August 8th 05, 06:55 PM
Danny
external usenet poster
 
Posts: n/a
Default VFAT

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
  #2  
Old August 8th 05, 07:43 PM
Ingeborg
external usenet poster
 
Posts: n/a
Default

"=?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.
  #3  
Old August 8th 05, 07:43 PM
PCR
external usenet poster
 
Posts: n/a
Default

Why did you leave the other thread? Go back! Ifshlp.sys is needed by
Windows. If it is not mentioned in Config.sys, it will load anyway by
IO.sys.

Here are two articles from...
http://search.support.microsoft.com/...dv=1&spid=1139 MSKB
Search "a device or resource required by VFAT"; Windows 98; This Product
Only; All Words; Full Text; Any Time. It seems, by the first, something
is going amiss during your install of that PCI card. Can you...?...

(a) Totally undo the install. (Post a plan for that.)
(b) Clear out "C:\Windows\Temp" after a fresh boot. Also, may as well
clear TIFs.
(c) Reinstall it, after re-reading instructions & posting a plan.

• Error Message: VFAT Device Initialization Failed
(139063) - When you start Windows, 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. This...
http://support.microsoft.com/default...b;en-us;139063

• VFAT Initialization Error Message Installing Windows 98
(190110) - When you are installing Windows 98, you may receive the
following error message: VFAT Device Initialization Failed A device or
resource required by VFAT is not present or is unavailable. VFAT cannot
continue loading. System halted. This behavior...
http://support.microsoft.com/default...b;en-us;190110


--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
should things get worse after this,
PCR

"Danny" wrote in message
...
| 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


  #4  
Old August 8th 05, 08:23 PM
Danny
external usenet poster
 
Posts: n/a
Default

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.

  #5  
Old August 8th 05, 08:28 PM
Danny
external usenet poster
 
Posts: n/a
Default

PCR,

I tried all in your previous post with no luck and had searched the MS
knowledge database prior to posting. Further troubleshooting has found that
the card works and all is well if I bypass the config.sys during boot.
There is not much in the config.sys and again tried enabling and adding the
ifshlp.sys, but same problem after the command line was added. Disabling the
config.sys allowed all to work again.

"PCR" wrote:

Why did you leave the other thread? Go back! Ifshlp.sys is needed by
Windows. If it is not mentioned in Config.sys, it will load anyway by
IO.sys.

Here are two articles from...
http://search.support.microsoft.com/...dv=1&spid=1139 MSKB
Search "a device or resource required by VFAT"; Windows 98; This Product
Only; All Words; Full Text; Any Time. It seems, by the first, something
is going amiss during your install of that PCI card. Can you...?...

(a) Totally undo the install. (Post a plan for that.)
(b) Clear out "C:\Windows\Temp" after a fresh boot. Also, may as well
clear TIFs.
(c) Reinstall it, after re-reading instructions & posting a plan.

• Error Message: VFAT Device Initialization Failed
(139063) - When you start Windows, 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. This...
http://support.microsoft.com/default...b;en-us;139063

• VFAT Initialization Error Message Installing Windows 98
(190110) - When you are installing Windows 98, you may receive the
following error message: VFAT Device Initialization Failed A device or
resource required by VFAT is not present or is unavailable. VFAT cannot
continue loading. System halted. This behavior...
http://support.microsoft.com/default...b;en-us;190110


--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
should things get worse after this,
PCR

"Danny" wrote in message
...
| 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



  #6  
Old August 8th 05, 10:39 PM
Brian A.
external usenet poster
 
Posts: n/a
Default

Please post the contents of your config.sys.

--

Brian A. Sesko { MS MVP_Shell/User }
Conflicts start where information lacks.
http://basconotw.mvps.org/

Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
How to ask a question: http://support.microsoft.com/kb/555375



  #7  
Old August 8th 05, 10:59 PM
PCR
external usenet poster
 
Posts: n/a
Default

Right. "START button, Run, SysEdit", & post Config.sys, as Brian A.
said. May as well post Autoexec.bat as well, if any. Seems you are close
to the end of it!


--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
should things get worse after this,
PCR

"Danny" wrote in message
...
| PCR,
|
| I tried all in your previous post with no luck and had searched the MS
| knowledge database prior to posting. Further troubleshooting has
found that
| the card works and all is well if I bypass the config.sys during
boot.
| There is not much in the config.sys and again tried enabling and
adding the
| ifshlp.sys, but same problem after the command line was added.
Disabling the
| config.sys allowed all to work again.
|
| "PCR" wrote:
|
| Why did you leave the other thread? Go back! Ifshlp.sys is needed by
| Windows. If it is not mentioned in Config.sys, it will load anyway
by
| IO.sys.
|
| Here are two articles from...
|
http://search.support.microsoft.com/...dv=1&spid=1139 MSKB
| Search "a device or resource required by VFAT"; Windows 98; This
Product
| Only; All Words; Full Text; Any Time. It seems, by the first,
something
| is going amiss during your install of that PCI card. Can you...?...
|
| (a) Totally undo the install. (Post a plan for that.)
| (b) Clear out "C:\Windows\Temp" after a fresh boot. Also, may as
well
| clear TIFs.
| (c) Reinstall it, after re-reading instructions & posting a plan.
|
| • Error Message: VFAT Device Initialization Failed
| (139063) - When you start Windows, 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. This...
| http://support.microsoft.com/default...b;en-us;139063
|
| • VFAT Initialization Error Message Installing Windows 98
| (190110) - When you are installing Windows 98, you may receive the
| following error message: VFAT Device Initialization Failed A device
or
| resource required by VFAT is not present or is unavailable. VFAT
cannot
| continue loading. System halted. This behavior...
| http://support.microsoft.com/default...b;en-us;190110
|
|
| --
| Thanks or Good Luck,
| There may be humor in this post, and,
| Naturally, you will not sue,
| should things get worse after this,
| PCR
|
| "Danny" wrote in message
| ...
| | 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
|
|
|


  #8  
Old August 9th 05, 04:45 PM
Danny
external usenet poster
 
Posts: n/a
Default

Brian & PCR,

Thanks for the help! Mostly likely will not be able to check your reply
until this Friday. I was going to go through the config.sys line by line to
troubleshoot.

Here is the config.sys:

REM To make a DOS Boot Diskette; See the file C:\DOSBOOT\DOSBOOT.TXT

[common]
dos=high,umb
buffers=40
device=c:\windows\himem.sys /testmemff
DEVICE=C:\WINDOWS\EMM386.EXE NOEMS
REM DEVICE=C:\WINDOWS\EMM386.EXE NOEMS

rem The below DOS CD ROM driver is not required to run Windows 98.
rem DEVICE=c:\cdrom\OakCdRom.SYS /D:IDECD000


Here is the autoexec.bat

@ECHO OFF
SET BLASTER=A220 I7 D1 H5 P330 T6

REM To make a DOS Boot Diskette; See the file C:\DOSBOOT\DOSBOOT.TXT

path C:\WINDOWS;C:\WINDOWS\COMMAND

sPower will initialize the USB Keyboard in DOS.
sPower will initialize the USB Keyboard in DOS.
TShoot: rem call c:\dosboot\sPower
call c:\dosboot\sPower





"PCR" wrote:

Right. "START button, Run, SysEdit", & post Config.sys, as Brian A.
said. May as well post Autoexec.bat as well, if any. Seems you are close
to the end of it!


--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
should things get worse after this,
PCR

"Danny" wrote in message
...
| PCR,
|
| I tried all in your previous post with no luck and had searched the MS
| knowledge database prior to posting. Further troubleshooting has
found that
| the card works and all is well if I bypass the config.sys during
boot.
| There is not much in the config.sys and again tried enabling and
adding the
| ifshlp.sys, but same problem after the command line was added.
Disabling the
| config.sys allowed all to work again.
|
| "PCR" wrote:
|
| Why did you leave the other thread? Go back! Ifshlp.sys is needed by
| Windows. If it is not mentioned in Config.sys, it will load anyway
by
| IO.sys.
|
| Here are two articles from...
|
http://search.support.microsoft.com/...dv=1&spid=1139 MSKB
| Search "a device or resource required by VFAT"; Windows 98; This
Product
| Only; All Words; Full Text; Any Time. It seems, by the first,
something
| is going amiss during your install of that PCI card. Can you...?...
|
| (a) Totally undo the install. (Post a plan for that.)
| (b) Clear out "C:\Windows\Temp" after a fresh boot. Also, may as
well
| clear TIFs.
| (c) Reinstall it, after re-reading instructions & posting a plan.
|
| • Error Message: VFAT Device Initialization Failed
| (139063) - When you start Windows, 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. This...
| http://support.microsoft.com/default...b;en-us;139063
|
| • VFAT Initialization Error Message Installing Windows 98
| (190110) - When you are installing Windows 98, you may receive the
| following error message: VFAT Device Initialization Failed A device
or
| resource required by VFAT is not present or is unavailable. VFAT
cannot
| continue loading. System halted. This behavior...
| http://support.microsoft.com/default...b;en-us;190110
|
|
| --
| Thanks or Good Luck,
| There may be humor in this post, and,
| Naturally, you will not sue,
| should things get worse after this,
| PCR
|
| "Danny" wrote in message
| ...
| | 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
|
|
|



  #9  
Old August 9th 05, 08:08 PM
PCR
external usenet poster
 
Posts: n/a
Default

(1) Here, use this for "Config.sys"...

DEVICE=C:\Windows\HIMEM.sys
DEVICE=C:\Windows\EMM386.exe NOEMS
DOS=HIGH,UMB,AUTO
FILESHIGH=80
BUFFERSHIGH=40,4
rem The below DOS CD ROM driver is not required to run Windows 98.
rem DEVICE=c:\cdrom\OakCdRom.SYS /D:IDECD000
......END above this line.........

| sPower will initialize the USB Keyboard in DOS.
| sPower will initialize the USB Keyboard in DOS.

(2) "START button, Find, F/F, sPower.bat".
R-Clk it in "c:\dosboot", & select "Edit".
Post it for examination, as it may be changing your PATH or
something.

(3) Delete one of the lines that begins "sPower" in your Autoexec.bat".
Looks like you turned sPower off in MSConfig, but it got turned back on
a different way.

(4) Put a "REM " (with blank) in front of the other one...
REM sPower will initialize the USB Keyboard in DOS.

| TShoot: rem call c:\dosboot\sPower
| call c:\dosboot\sPower

(5) Do you want it to run or don't you? You don't need one line REMming
it & another running it. Delete the line that begins "TShoot: rem",
which was MSConfig's way of deactivating it.

Let us see that "sPower.bat". After it passes muster, try a boot with
the changes above. Then, try with "sPower" deactivated by unchecking it
at "START button, Run, MSConfig, Startup tab". However, you must double
check that it does not turn itself back on!


--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
should things get worse after this,
PCR

"Danny" wrote in message
...
| Brian & PCR,
|
| Thanks for the help! Mostly likely will not be able to check your
reply
| until this Friday. I was going to go through the config.sys line by
line to
| troubleshoot.
|
| Here is the config.sys:
|
| REM To make a DOS Boot Diskette; See the file C:\DOSBOOT\DOSBOOT.TXT
|
| [common]
| dos=high,umb
| buffers=40
| device=c:\windows\himem.sys /testmemff
| DEVICE=C:\WINDOWS\EMM386.EXE NOEMS
| REM DEVICE=C:\WINDOWS\EMM386.EXE NOEMS
|
| rem The below DOS CD ROM driver is not required to run Windows 98.
| rem DEVICE=c:\cdrom\OakCdRom.SYS /D:IDECD000
|
|
| Here is the autoexec.bat
|
| @ECHO OFF
| SET BLASTER=A220 I7 D1 H5 P330 T6
|
| REM To make a DOS Boot Diskette; See the file C:\DOSBOOT\DOSBOOT.TXT
|
| path C:\WINDOWS;C:\WINDOWS\COMMAND
|
| sPower will initialize the USB Keyboard in DOS.
| sPower will initialize the USB Keyboard in DOS.
| TShoot: rem call c:\dosboot\sPower
| call c:\dosboot\sPower
|
|
|
|
|
| "PCR" wrote:
|
| Right. "START button, Run, SysEdit", & post Config.sys, as Brian A.
| said. May as well post Autoexec.bat as well, if any. Seems you are
close
| to the end of it!
|
|
| --
| Thanks or Good Luck,
| There may be humor in this post, and,
| Naturally, you will not sue,
| should things get worse after this,
| PCR
|

| "Danny" wrote in message
| ...
| | PCR,
| |
| | I tried all in your previous post with no luck and had searched
the MS
| | knowledge database prior to posting. Further troubleshooting has
| found that
| | the card works and all is well if I bypass the config.sys during
| boot.
| | There is not much in the config.sys and again tried enabling and
| adding the
| | ifshlp.sys, but same problem after the command line was added.
| Disabling the
| | config.sys allowed all to work again.
| |
| | "PCR" wrote:
| |
| | Why did you leave the other thread? Go back! Ifshlp.sys is
needed by
| | Windows. If it is not mentioned in Config.sys, it will load
anyway
| by
| | IO.sys.
| |
| | Here are two articles from...
| |
http://search.support.microsoft.com/...dv=1&spid=1139 MSKB
| | Search "a device or resource required by VFAT"; Windows 98; This
| Product
| | Only; All Words; Full Text; Any Time. It seems, by the first,
| something
| | is going amiss during your install of that PCI card. Can
you...?...
| |
| | (a) Totally undo the install. (Post a plan for that.)
| | (b) Clear out "C:\Windows\Temp" after a fresh boot. Also, may as
| well
| | clear TIFs.
| | (c) Reinstall it, after re-reading instructions & posting a
plan.
| |
| | • Error Message: VFAT Device Initialization Failed
| | (139063) - When you start Windows, 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. This...
| | http://support.microsoft.com/default...b;en-us;139063
| |
| | • VFAT Initialization Error Message Installing Windows 98
| | (190110) - When you are installing Windows 98, you may receive
the
| | following error message: VFAT Device Initialization Failed A
device
| or
| | resource required by VFAT is not present or is unavailable. VFAT
| cannot
| | continue loading. System halted. This behavior...
| | http://support.microsoft.com/default...b;en-us;190110
| |
| |
| | --
| | Thanks or Good Luck,
| | There may be humor in this post, and,
| | Naturally, you will not sue,
| | should things get worse after this,
| | PCR
| |
| | "Danny" wrote in message
| | ...
| | | 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
| |
| |
| |
|
|
|


  #10  
Old August 9th 05, 09:06 PM
PCR
external usenet poster
 
Posts: n/a
Default

| Let us see that "sPower.bat". After it passes muster, try a boot with
| the changes above. Then, try with "sPower" deactivated by unchecking
it
| at "START button, Run, MSConfig, Startup tab". However, you must
double
| check that it does not turn itself back on!

Autoexec.bat tab, that is.

"PCR" wrote in message
...
....snip


 




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 Pat Miller General 3 June 3rd 05 11:04 PM
VFAT Art General 1 July 21st 04 01:16 AM
VFAT error Paradoxdb3 General 4 July 12th 04 01:22 PM
VFAT Error [email protected] Improving Performance 1 June 29th 04 02:44 AM
VFAT Error [email protected] Disk Drives 0 May 23rd 04 04:41 PM


All times are GMT +1. The time now is 04:55 PM.


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