Here's a poser!

I'm running both Windows 98 Second Edition and Windows XP on my machine. I
started with 512MB of memory. Both OS booted fine and all worked fine. So, I
decided to increase the memory. I installed another 512MB of the exact same
type, size and manufacturer memory. The Windows XP boots fine and all works
fine. The Windows 98se fails with a 'VFAT failure' message no matter what I
do.
I've read and tried all the Microsoft remedies on VFAT failures. They all
refer to missing files that are needed for Windows to boot. My problem is
Windows 98se does boot just fine with a limited amount of memory.
First the Windows 98se doesn't have a 'CONFIG.SYS' file. The DEVIVE= files
are all loaded by another process, I suspect the HIMEM.SYS file, just as they
do with only one memory module installed.
Now for the big question! What would make Windows 98se fail to boot with a
second memory module installed but work just fine with only one?
Do you suppose something is restricting the amount of memory that my Windows
98se be allowed to use? I've used this OS for years but have never added more
than 512MB of memory until now.
The fact that the Windows XP OS works says to me that the problem may have
something to do with the MSDOS Drivers because XP doesn't use them. But if
the MSDOS drivers were bad why would 98 work with 512MB but not 1024MB?

Also can anyone tell me where I can get a file editor so I can look at the
contents of these *.sys files?

Bud

=?Utf-8?B?TmV2QnVk?= wrote in
:

The fact that the Windows XP OS works says to me that the problem may
have something to do with the MSDOS Drivers because XP doesn't use
them. But if the MSDOS drivers were bad why would 98 work with 512MB
but not 1024MB?


W98 can have problems with more than 512 MB. But there's a work around.
Read this: support.microsoft.com/default.aspx?scid=kb;en-us;253912

"Out of Memory" Error Messages with Large Amounts of RAM Installed:
http://support.microsoft.com/?kbid=253912

Set a MaxFileCache setting of 524,288, in the [vcache] section of System.ini in
Win98.
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


"NevBud" wrote in message
...
I'm running both Windows 98 Second Edition and Windows XP on my machine. I
started with 512MB of memory. Both OS booted fine and all worked fine. So, I
decided to increase the memory. I installed another 512MB of the exact same
type, size and manufacturer memory. The Windows XP boots fine and all works
fine. The Windows 98se fails with a 'VFAT failure' message no matter what I
do.
I've read and tried all the Microsoft remedies on VFAT failures. They all
refer to missing files that are needed for Windows to boot. My problem is
Windows 98se does boot just fine with a limited amount of memory.
First the Windows 98se doesn't have a 'CONFIG.SYS' file. The DEVIVE= files
are all loaded by another process, I suspect the HIMEM.SYS file, just as they
do with only one memory module installed.
Now for the big question! What would make Windows 98se fail to boot with a
second memory module installed but work just fine with only one?
Do you suppose something is restricting the amount of memory that my Windows
98se be allowed to use? I've used this OS for years but have never added more
than 512MB of memory until now.
The fact that the Windows XP OS works says to me that the problem may have
something to do with the MSDOS Drivers because XP doesn't use them. But if
the MSDOS drivers were bad why would 98 work with 512MB but not 1024MB?

Also can anyone tell me where I can get a file editor so I can look at the
contents of these *.sys files?

Bud

NevBud wrote:
Also can anyone tell me where I can get a file editor so I can look
at the contents of these *.sys files?

Any text or hex editor but unless the files are pure text that won't
tell you much.

--
dadiOH
____________________________

dadiOH's dandies v3.05...
....a help file of info about MP3s, recording from
LP/cassette and tips & tricks on this and that.
Get it at http://mysite.verizon.net/xico

NevBud wrote:

I'm running both Windows 98 Second Edition and Windows XP on my machine. I
started with 512MB of memory. Both OS booted fine and all worked fine. So, I
decided to increase the memory. I installed another 512MB of the exact same
type, size and manufacturer memory. The Windows XP boots fine and all works
fine. The Windows 98se fails with a 'VFAT failure' message no matter what I
do.

To use more than 512MB RAM with Win98 you need to make a tweak to the
system.ini file.

Find the [vcache] section, and add this line:
MaxFileCache=512000

--
Tim Slattery
MS MVP(DTS)

" Find the [vcache] section, and add this line:
MaxFileCache=512000

Hello,,,
yawn, I am up way past my bodies allowance, but I couldnt resist
clicking yet another post.

Tim, I have listened to what you said to the other person and immediately
did a "run" on 'msconfig' to see what mine said, and all I could find under
the heading of "vcache" (under sysini) was Zero.
It confuses me sometimes when I am running the same O/S as others yet all
our settings seem to be different.
In this case, I dont even have one other that the fact that I have a Tick
next to Vcache in the sysini within msconfig.
I wish things could be simple.

regards Jane

To add to the others -- having in view the advice to set
[vcache]
MaxFileCache=512000

If your Config.sys contains the lines with Himem.sys, and all the more
with Emm386.exe -- rem out these lines (add the word REM followed by
space to the beginning of these lines).

Emm386.exe was not meant for such amounts of memory, and even with 512
MB works slightly wrong (it reduces the amount of available memory from
512 to 511 MB, what you can see on General tab of System Properties --
but it seems it is, hopefully, the only undesirable effect in this
case), but with 1GB of RAM creates very significant problems. And if you
have the programs that require Emm386 loading from Config.sys -- then
you're out of luck with 1GB RAM.

Himem.sys will be loaded in any case, but in the other process, via
io.sys -- what will eliminate some very minor problems in contrast with
loading it from Config.sys when more than 512 MB of RAM is installed.
--
Mikhail Zhilin
http://www.aha.ru/~mwz
Sorry, no technical support by e-mail.
Please reply to the newsgroups only.
======
On Fri, 7 Jan 2005 11:21:03 -0800, NevBud
wrote:

I'm running both Windows 98 Second Edition and Windows XP on my machine. I
started with 512MB of memory. Both OS booted fine and all worked fine. So, I
decided to increase the memory. I installed another 512MB of the exact same
type, size and manufacturer memory. The Windows XP boots fine and all works
fine. The Windows 98se fails with a 'VFAT failure' message no matter what I
do.
I've read and tried all the Microsoft remedies on VFAT failures. They all
refer to missing files that are needed for Windows to boot. My problem is
Windows 98se does boot just fine with a limited amount of memory.
First the Windows 98se doesn't have a 'CONFIG.SYS' file. The DEVIVE= files
are all loaded by another process, I suspect the HIMEM.SYS file, just as they
do with only one memory module installed.
Now for the big question! What would make Windows 98se fail to boot with a
second memory module installed but work just fine with only one?
Do you suppose something is restricting the amount of memory that my Windows
98se be allowed to use? I've used this OS for years but have never added more
than 512MB of memory until now.
The fact that the Windows XP OS works says to me that the problem may have
something to do with the MSDOS Drivers because XP doesn't use them. But if
the MSDOS drivers were bad why would 98 work with 512MB but not 1024MB?

Also can anyone tell me where I can get a file editor so I can look at the
contents of these *.sys files?

Bud

Ah!, that explains why my system properties says 511 mb's in 98SE and 512
mb's in XP Pro. Thanks again, Mikhail.

"Mikhail Zhilin" wrote in message
...
To add to the others -- having in view the advice to set
[vcache]
MaxFileCache=512000

If your Config.sys contains the lines with Himem.sys, and all the more
with Emm386.exe -- rem out these lines (add the word REM followed by
space to the beginning of these lines).

Emm386.exe was not meant for such amounts of memory, and even with 512
MB works slightly wrong (it reduces the amount of available memory from
512 to 511 MB, what you can see on General tab of System Properties --
but it seems it is, hopefully, the only undesirable effect in this
case), but with 1GB of RAM creates very significant problems. And if you
have the programs that require Emm386 loading from Config.sys -- then
you're out of luck with 1GB RAM.

Himem.sys will be loaded in any case, but in the other process, via
io.sys -- what will eliminate some very minor problems in contrast with
loading it from Config.sys when more than 512 MB of RAM is installed.
--
Mikhail Zhilin
http://www.aha.ru/~mwz
Sorry, no technical support by e-mail.
Please reply to the newsgroups only.
======
On Fri, 7 Jan 2005 11:21:03 -0800, NevBud
wrote:

I'm running both Windows 98 Second Edition and Windows XP on my machine.
I
started with 512MB of memory. Both OS booted fine and all worked fine.
So, I
decided to increase the memory. I installed another 512MB of the exact
same
type, size and manufacturer memory. The Windows XP boots fine and all
works
fine. The Windows 98se fails with a 'VFAT failure' message no matter what
I
do.
I've read and tried all the Microsoft remedies on VFAT failures. They all
refer to missing files that are needed for Windows to boot. My problem is
Windows 98se does boot just fine with a limited amount of memory.
First the Windows 98se doesn't have a 'CONFIG.SYS' file. The DEVIVE=
files
are all loaded by another process, I suspect the HIMEM.SYS file, just as
they
do with only one memory module installed.
Now for the big question! What would make Windows 98se fail to boot with
a
second memory module installed but work just fine with only one?
Do you suppose something is restricting the amount of memory that my
Windows
98se be allowed to use? I've used this OS for years but have never added
more
than 512MB of memory until now.
The fact that the Windows XP OS works says to me that the problem may
have
something to do with the MSDOS Drivers because XP doesn't use them. But
if
the MSDOS drivers were bad why would 98 work with 512MB but not 1024MB?

Also can anyone tell me where I can get a file editor so I can look at
the
contents of these *.sys files?

Bud

Jane,
With all due respect, Stay Out of areas you are not familiar with. I =
don't mean this in a bad way, it's always good to see learning efforts =
made by others. All that's needed is one wrong move in an unforgiving =
area and you'll be learning how to place the machine properly nudged =
against the door. One should really only use msconfig for =
troubleshooting.

You should not have nor need to set a max cache if your systems RAM is =
512 or . For some reading info on the purpose of this setting.

Error Message: Insufficient Memory to Initialize Windows:
http://support.microsoft.com/default...b;EN-US;184447

"Out of Memory" Error Messages with Large Amounts of RAM Installed:
http://support.microsoft.com/support.../Q253/9/12.ASP

Computer May Reboot Continuously with More Than 1.5 GB of RAM:
http://support.microsoft.com/default...n-us;304943=20

As per your statement;
quote
It confuses me sometimes when I am running the same O/S as others yet =
all our settings seem to be different.
/quote

Think of your machine like you think of your house, car, purse, etc. No =
2 will be exactly the same unless they started out exactly the same and =
anything/everything done to one was done exactly to the other at the =
same time.=20

--=20

Brian A.

Conflicts start where information lacks.
http://www.dts-l.org/goodpost.htm


"jane" wrote in message =
...
=20
" Find the [vcache] section, and add this line:
MaxFileCache=3D512000
=20
Hello,,,
yawn, I am up way past my bodies allowance, but I couldnt resist
clicking yet another post.
=20
Tim, I have listened to what you said to the other person and =
immediately
did a "run" on 'msconfig' to see what mine said, and all I could find =
under
the heading of "vcache" (under sysini) was Zero.
It confuses me sometimes when I am running the same O/S as others yet =
all
our settings seem to be different.
In this case, I dont even have one other that the fact that I have a =
Tick
next to Vcache in the sysini within msconfig.
I wish things could be simple.
=20
regards Jane
=20

"NevBud" wrote:

I'm running both Windows 98 Second Edition and Windows XP on my machine. I
started with 512MB of memory. Both OS booted fine and all worked fine. So, I
decided to increase the memory. I installed another 512MB of the exact same
type, size and manufacturer memory. The Windows XP boots fine and all works
fine. The Windows 98se fails with a 'VFAT failure' message no matter what I
do.
I've read and tried all the Microsoft remedies on VFAT failures. They all
refer to missing files that are needed for Windows to boot. My problem is
Windows 98se does boot just fine with a limited amount of memory.
First the Windows 98se doesn't have a 'CONFIG.SYS' file. The DEVIVE= files
are all loaded by another process, I suspect the HIMEM.SYS file, just as they
do with only one memory module installed.
Now for the big question! What would make Windows 98se fail to boot with a
second memory module installed but work just fine with only one?
Do you suppose something is restricting the amount of memory that my Windows
98se be allowed to use? I've used this OS for years but have never added more
than 512MB of memory until now.
The fact that the Windows XP OS works says to me that the problem may have
something to do with the MSDOS Drivers because XP doesn't use them. But if
the MSDOS drivers were bad why would 98 work with 512MB but not 1024MB?

Also can anyone tell me where I can get a file editor so I can look at the
contents of these *.sys files?

Bud