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

Here's a poser!



 
 
Thread Tools Display Modes
  #11  
Old January 9th 05, 08:45 AM
Brian A.
external usenet poster
 
Posts: n/a
Default

Another CDO user lost in the mix.

--=20

Brian A.

Conflicts start where information lacks.
http://www.dts-l.org/goodpost.htm
  #12  
Old January 9th 05, 08:55 AM
NevBud
external usenet poster
 
Posts: n/a
Default

Thanks to all who responded. My Windows 98 SE doesn't have a 'Config.sys'
file so any editing in it is impossible. Some people have scolded me for even
mentioning 'Config.sys' in the same breath as Windows 98SE because it doesn't
have or require one.
I've tried every suggestion by anyone and articles by Microsoft all to no
avail. I've tried editing the System.ini 386Enh
with: MaxPhysPage=20000/240000/28000/30000/40000, Vcache with
MaxFileCache=512000/524288 & even tried MinFileCache=51200,
MaxFileCache=56320.
Sometimes I get VFAT, sometimes I get "Not eneough memory..., sometimes I
get constant reboots. When in Safe Mode the System sees the quanity of memory
OK but won't normal boot with it.
You talk about confusing, why the amount of memory would confuse the OS into
craping out is beyond me. Now XP doesn't have any of these restrictions and
the fact that it doesn't use DOS is significant I think.

The only thing that works is the line "Reduce the amount of memory that is
installed in your computer to 512 MB or less." found in MS article Q253912.

So I don't believe anything will allow me to install more than 512 MB of
memory with the Windows 98SE Operating System. So thanks again and if you
come up with any other outlandish suggestions please let me know.


"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

  #13  
Old January 9th 05, 09:13 AM
Gary S. Terhune
external usenet poster
 
Posts: n/a
Default

Windows 98 and 98SE don't have Autoexec.bat of Config.sys files by =
default, but there's no reason you can't add them. On the other hand, =
you are right in thinking that the "usual" things that these files were =
used for in prior versions of MS-DOS and Windows are handled in other =
ways by Win98/98SE. In other words, these two venerable files are =
perfectly acceptable in Windows 98/98SE, but you have to be sure you're =
employing them appropriately.

Which is all rather beside the point: If you read the responses to your =
case in this newsgroup, all suggestions for how to remedy your issue =
involve editing System.ini. Safest way to do that is to use SYSEDIT, =
launched from the Run box, but Notepad will also suffice (however, don't =
use WordPad or any more complicated text editor, since they may throw in =
formatting characters and destroy the file.)

You really can't read anything into the fact that XP has no problem with =
the amount of RAM you now have installed, but Win98 does. They employ =
RAM in significantly different ways, and the amount may really have =
nothing to do with the issue. What's true is that either OS is more =
likely to have problems with RAM upgrades if you are pushing the =
envelope with regard to the max allowable RAM for the motherboard, or if =
your RAM sticks aren't matched (sometimes right down to being from the =
same batch, nevermind being from the same manufacturer.) You may also =
have other BIOS settings in play that worked fine with only 512 MB of =
RAM but which are pushing the envelope when you double that.

I could go on, and I hope you can read into the above what I might =
suggest as solutions. The most *common* reasons for Win98/98SE having =
problems with the amounts of RAM you are talking about are remedied by =
the settings suggestions given thus far, but they don't rule out simple =
borderline flakiness that happens to present itself more readily in =
98/98SE than in XP.

--=20
Gary S. Terhune
MS MVP Shell/User
=20
"NevBud" wrote in message =
...
Thanks to all who responded. My Windows 98 SE doesn't have a =

'Config.sys'=20
file so any editing in it is impossible. Some people have scolded me =

for even=20
mentioning 'Config.sys' in the same breath as Windows 98SE because it =

doesn't=20
have or require one.
I've tried every suggestion by anyone and articles by Microsoft all to =

no=20
avail. I've tried editing the System.ini 386Enh
with: MaxPhysPage=3D20000/240000/28000/30000/40000, Vcache with=20
MaxFileCache=3D512000/524288 & even tried MinFileCache=3D51200,=20
MaxFileCache=3D56320.
Sometimes I get VFAT, sometimes I get "Not eneough memory..., =

sometimes I=20
get constant reboots. When in Safe Mode the System sees the quanity of =

memory=20
OK but won't normal boot with it.
You talk about confusing, why the amount of memory would confuse the =

OS into=20
craping out is beyond me. Now XP doesn't have any of these =

restrictions and=20
the fact that it doesn't use DOS is significant I think.
=20
The only thing that works is the line "Reduce the amount of memory =

that is=20
installed in your computer to 512 MB or less." found in MS article =

Q253912.
=20
So I don't believe anything will allow me to install more than 512 MB =

of=20
memory with the Windows 98SE Operating System. So thanks again and if =

you=20
come up with any other outlandish suggestions please let me know.
=20
=20
"NevBud" wrote:
=20
I'm running both Windows 98 Second Edition and Windows XP on my =

machine. I=20
started with 512MB of memory. Both OS booted fine and all worked =

fine. So, I=20
decided to increase the memory. I installed another 512MB of the =

exact same=20
type, size and manufacturer memory. The Windows XP boots fine and =

all works=20
fine. The Windows 98se fails with a 'VFAT failure' message no matter =

what I=20
do.
I've read and tried all the Microsoft remedies on VFAT failures. =

They all=20
refer to missing files that are needed for Windows to boot. My =

problem is=20
Windows 98se does boot just fine with a limited amount of memory.=20
First the Windows 98se doesn't have a 'CONFIG.SYS' file. The =

DEVIVE=3D files=20
are all loaded by another process, I suspect the HIMEM.SYS file, =

just as they=20
do with only one memory module installed.
Now for the big question! What would make Windows 98se fail to boot =

with a=20
second memory module installed but work just fine with only one?
Do you suppose something is restricting the amount of memory that my =

Windows=20
98se be allowed to use? I've used this OS for years but have never =

added more=20
than 512MB of memory until now.
The fact that the Windows XP OS works says to me that the problem =

may have=20
something to do with the MSDOS Drivers because XP doesn't use them. =

But if=20
the MSDOS drivers were bad why would 98 work with 512MB but not =

1024MB?
=20
Also can anyone tell me where I can get a file editor so I can look =

at the=20
contents of these *.sys files?
=20
Bud

  #14  
Old January 9th 05, 02:22 PM
Dan
external usenet poster
 
Posts: n/a
Default

Gary, if the user posted his computer information to this newsgroup then
perhaps we could determine if he needs to flash his BIOS. What do you
think?

"Gary S. Terhune" wrote in message
...
Windows 98 and 98SE don't have Autoexec.bat of Config.sys files by default,
but there's no reason you can't add them. On the other hand, you are right
in thinking that the "usual" things that these files were used for in prior
versions of MS-DOS and Windows are handled in other ways by Win98/98SE. In
other words, these two venerable files are perfectly acceptable in Windows
98/98SE, but you have to be sure you're employing them appropriately.

Which is all rather beside the point: If you read the responses to your case
in this newsgroup, all suggestions for how to remedy your issue involve
editing System.ini. Safest way to do that is to use SYSEDIT, launched from
the Run box, but Notepad will also suffice (however, don't use WordPad or
any more complicated text editor, since they may throw in formatting
characters and destroy the file.)

You really can't read anything into the fact that XP has no problem with the
amount of RAM you now have installed, but Win98 does. They employ RAM in
significantly different ways, and the amount may really have nothing to do
with the issue. What's true is that either OS is more likely to have
problems with RAM upgrades if you are pushing the envelope with regard to
the max allowable RAM for the motherboard, or if your RAM sticks aren't
matched (sometimes right down to being from the same batch, nevermind being
from the same manufacturer.) You may also have other BIOS settings in play
that worked fine with only 512 MB of RAM but which are pushing the envelope
when you double that.

I could go on, and I hope you can read into the above what I might suggest
as solutions. The most *common* reasons for Win98/98SE having problems with
the amounts of RAM you are talking about are remedied by the settings
suggestions given thus far, but they don't rule out simple borderline
flakiness that happens to present itself more readily in 98/98SE than in XP.

--
Gary S. Terhune
MS MVP Shell/User

"NevBud" wrote in message
...
Thanks to all who responded. My Windows 98 SE doesn't have a 'Config.sys'
file so any editing in it is impossible. Some people have scolded me for

even
mentioning 'Config.sys' in the same breath as Windows 98SE because it

doesn't
have or require one.
I've tried every suggestion by anyone and articles by Microsoft all to no
avail. I've tried editing the System.ini 386Enh
with: MaxPhysPage=20000/240000/28000/30000/40000, Vcache with
MaxFileCache=512000/524288 & even tried MinFileCache=51200,
MaxFileCache=56320.
Sometimes I get VFAT, sometimes I get "Not eneough memory..., sometimes I
get constant reboots. When in Safe Mode the System sees the quanity of

memory
OK but won't normal boot with it.
You talk about confusing, why the amount of memory would confuse the OS

into
craping out is beyond me. Now XP doesn't have any of these restrictions

and
the fact that it doesn't use DOS is significant I think.

The only thing that works is the line "Reduce the amount of memory that is
installed in your computer to 512 MB or less." found in MS article

Q253912.

So I don't believe anything will allow me to install more than 512 MB of
memory with the Windows 98SE Operating System. So thanks again and if you
come up with any other outlandish suggestions please let me know.


"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



  #15  
Old January 9th 05, 05:43 PM
Gary S. Terhune
external usenet poster
 
Posts: n/a
Default

That wouldn't be the fix that pops into my mind, Dan. I truly suspect =
it's a matter of incompatible sticks of RAM or a case of BIOS settings =
being too optimistic.

--=20
Gary S. Terhune
MS MVP Shell/User
=20
"Dan" wrote in message =
...
Gary, if the user posted his computer information to this newsgroup =

then
perhaps we could determine if he needs to flash his BIOS. What do you
think?
=20
"Gary S. Terhune" wrote in message
...
Windows 98 and 98SE don't have Autoexec.bat of Config.sys files by =

default,
but there's no reason you can't add them. On the other hand, you are =

right
in thinking that the "usual" things that these files were used for in =

prior
versions of MS-DOS and Windows are handled in other ways by =

Win98/98SE. In
other words, these two venerable files are perfectly acceptable in =

Windows
98/98SE, but you have to be sure you're employing them appropriately.
=20
Which is all rather beside the point: If you read the responses to =

your case
in this newsgroup, all suggestions for how to remedy your issue =

involve
editing System.ini. Safest way to do that is to use SYSEDIT, launched =

from
the Run box, but Notepad will also suffice (however, don't use WordPad =

or
any more complicated text editor, since they may throw in formatting
characters and destroy the file.)
=20
You really can't read anything into the fact that XP has no problem =

with the
amount of RAM you now have installed, but Win98 does. They employ RAM =

in
significantly different ways, and the amount may really have nothing =

to do
with the issue. What's true is that either OS is more likely to have
problems with RAM upgrades if you are pushing the envelope with regard =

to
the max allowable RAM for the motherboard, or if your RAM sticks =

aren't
matched (sometimes right down to being from the same batch, nevermind =

being
from the same manufacturer.) You may also have other BIOS settings in =

play
that worked fine with only 512 MB of RAM but which are pushing the =

envelope
when you double that.
=20
I could go on, and I hope you can read into the above what I might =

suggest
as solutions. The most *common* reasons for Win98/98SE having problems =

with
the amounts of RAM you are talking about are remedied by the settings
suggestions given thus far, but they don't rule out simple borderline
flakiness that happens to present itself more readily in 98/98SE than =

in XP.
=20
--=20
Gary S. Terhune
MS MVP Shell/User
=20
"NevBud" wrote in message
...
Thanks to all who responded. My Windows 98 SE doesn't have a =

'Config.sys'
file so any editing in it is impossible. Some people have scolded me =

for
even
mentioning 'Config.sys' in the same breath as Windows 98SE because =

it
doesn't
have or require one.
I've tried every suggestion by anyone and articles by Microsoft all =

to no
avail. I've tried editing the System.ini 386Enh
with: MaxPhysPage=3D20000/240000/28000/30000/40000, Vcache with
MaxFileCache=3D512000/524288 & even tried MinFileCache=3D51200,
MaxFileCache=3D56320.
Sometimes I get VFAT, sometimes I get "Not eneough memory..., =

sometimes I
get constant reboots. When in Safe Mode the System sees the quanity =

of
memory
OK but won't normal boot with it.
You talk about confusing, why the amount of memory would confuse the =

OS
into
craping out is beyond me. Now XP doesn't have any of these =

restrictions
and
the fact that it doesn't use DOS is significant I think.

The only thing that works is the line "Reduce the amount of memory =

that is
installed in your computer to 512 MB or less." found in MS article

Q253912.

So I don't believe anything will allow me to install more than 512 =

MB of
memory with the Windows 98SE Operating System. So thanks again and =

if you
come up with any other outlandish suggestions please let me know.


"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=3D
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

=20

  #16  
Old January 9th 05, 09:23 PM
Dan
external usenet poster
 
Posts: n/a
Default

Well thanks Gary that seems really clear to me and hope it will help the
original poster.

"Gary S. Terhune" wrote in message
...
That wouldn't be the fix that pops into my mind, Dan. I truly suspect it's a
matter of incompatible sticks of RAM or a case of BIOS settings being too
optimistic.

--
Gary S. Terhune
MS MVP Shell/User

"Dan" wrote in message
...
Gary, if the user posted his computer information to this newsgroup then
perhaps we could determine if he needs to flash his BIOS. What do you
think?

"Gary S. Terhune" wrote in message
...
Windows 98 and 98SE don't have Autoexec.bat of Config.sys files by

default,
but there's no reason you can't add them. On the other hand, you are right
in thinking that the "usual" things that these files were used for in

prior
versions of MS-DOS and Windows are handled in other ways by Win98/98SE. In
other words, these two venerable files are perfectly acceptable in Windows
98/98SE, but you have to be sure you're employing them appropriately.

Which is all rather beside the point: If you read the responses to your

case
in this newsgroup, all suggestions for how to remedy your issue involve
editing System.ini. Safest way to do that is to use SYSEDIT, launched from
the Run box, but Notepad will also suffice (however, don't use WordPad or
any more complicated text editor, since they may throw in formatting
characters and destroy the file.)

You really can't read anything into the fact that XP has no problem with

the
amount of RAM you now have installed, but Win98 does. They employ RAM in
significantly different ways, and the amount may really have nothing to do
with the issue. What's true is that either OS is more likely to have
problems with RAM upgrades if you are pushing the envelope with regard to
the max allowable RAM for the motherboard, or if your RAM sticks aren't
matched (sometimes right down to being from the same batch, nevermind

being
from the same manufacturer.) You may also have other BIOS settings in play
that worked fine with only 512 MB of RAM but which are pushing the

envelope
when you double that.

I could go on, and I hope you can read into the above what I might suggest
as solutions. The most *common* reasons for Win98/98SE having problems

with
the amounts of RAM you are talking about are remedied by the settings
suggestions given thus far, but they don't rule out simple borderline
flakiness that happens to present itself more readily in 98/98SE than in

XP.

--
Gary S. Terhune
MS MVP Shell/User

"NevBud" wrote in message
...
Thanks to all who responded. My Windows 98 SE doesn't have a

'Config.sys'
file so any editing in it is impossible. Some people have scolded me for

even
mentioning 'Config.sys' in the same breath as Windows 98SE because it

doesn't
have or require one.
I've tried every suggestion by anyone and articles by Microsoft all to

no
avail. I've tried editing the System.ini 386Enh
with: MaxPhysPage=20000/240000/28000/30000/40000, Vcache with
MaxFileCache=512000/524288 & even tried MinFileCache=51200,
MaxFileCache=56320.
Sometimes I get VFAT, sometimes I get "Not eneough memory..., sometimes

I
get constant reboots. When in Safe Mode the System sees the quanity of

memory
OK but won't normal boot with it.
You talk about confusing, why the amount of memory would confuse the OS

into
craping out is beyond me. Now XP doesn't have any of these restrictions

and
the fact that it doesn't use DOS is significant I think.

The only thing that works is the line "Reduce the amount of memory that

is
installed in your computer to 512 MB or less." found in MS article

Q253912.

So I don't believe anything will allow me to install more than 512 MB of
memory with the Windows 98SE Operating System. So thanks again and if

you
come up with any other outlandish suggestions please let me know.


"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





  #17  
Old January 9th 05, 11:33 PM
jazz
external usenet poster
 
Posts: n/a
Default

you can use the vcach settings and increaee the amount of memoryt to 768
reliably. I have several computers with over a gig of memory and usually run
the windows 98 at this level. you won't really see any performance increase
with much more then 512 though. I have seen a noticable difference when
video editing and working with large files but it wasn't verry significant.

"why the amount of memory would confuse the OS into
craping out is beyond me"


What happens with windows 9x and the way it manages memory is why there is
a problem. with more then 768 you have another issue crop up but the main is
with the vcache or vfat wich are seperate but in this case related by use.
Windows 9x will reserve adress space for the actual memory it thinks it can
access instead of letting the aplication alocate the memory directly like
back in ther dos days. In turn the application tells windows it need memory
and it alocates it in a slightly different way. This kind of avoids
exceptions and invalide page faults (note that a page fault is normal just
not an invalid one) When you have large amounts of ram installed, windows
can reserve more adressing space then it will allow itself to use then when
a program asks for memory, windows has no memory (adress space) left to give
the program. The program that is needing memory space when this problem is
ocurring is most likley the vfat system (in your case) wich is a driver
for the file system on the harddrive. You might be able to turn the swap
file off and boot into windows but it won't be completly stable so i
wouldn't advise it unless for a test and you know how to re-enable it from
dos.

You can think of it as a phone book were all the names and adresses are
already printed and they are place holders for the actual phone number
(memory in use). Normaly there is enough room to add the newly constructed
houses as they are built and need listed. With large amounts of ram
(buildings) installed there is little to no space left to add new houses,
names and adresses. It apears in your case when the vfat system is loading
it ran out of space all together and no more adresses can be writed to the
phone book and the vfat system coulnd't get a phone number. when you add the
amount of pageing or swaping windows reserve because it is expecting to
flush items from memory the amoutn of paper fills up fast.

"NevBud" wrote in message
...
Thanks to all who responded. My Windows 98 SE doesn't have a 'Config.sys'
file so any editing in it is impossible. Some people have scolded me for

even
mentioning 'Config.sys' in the same breath as Windows 98SE because it

doesn't
have or require one.
I've tried every suggestion by anyone and articles by Microsoft all to no
avail. I've tried editing the System.ini 386Enh
with: MaxPhysPage=20000/240000/28000/30000/40000, Vcache with
MaxFileCache=512000/524288 & even tried MinFileCache=51200,
MaxFileCache=56320.
Sometimes I get VFAT, sometimes I get "Not eneough memory..., sometimes I
get constant reboots. When in Safe Mode the System sees the quanity of

memory
OK but won't normal boot with it.
You talk about confusing, why the amount of memory would confuse the OS

into
craping out is beyond me. Now XP doesn't have any of these restrictions

and
the fact that it doesn't use DOS is significant I think.

The only thing that works is the line "Reduce the amount of memory that is
installed in your computer to 512 MB or less." found in MS article

Q253912.

So I don't believe anything will allow me to install more than 512 MB of
memory with the Windows 98SE Operating System. So thanks again and if you
come up with any other outlandish suggestions please let me know.


"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



  #18  
Old January 10th 05, 07:29 AM
jane
external usenet poster
 
Posts: n/a
Default

Hello,
I hear you Brian, they are probably very wise words and I
will heed them.
regards Jane

"Brian A." gonefish'n@afarawaylake wrote in message
...
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...b;en-us;304943

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.

--

Brian A.

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


"jane" wrote in message
...

" 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




  #19  
Old February 5th 05, 08:22 PM
Pandora
external usenet poster
 
Posts: n/a
Default

"Gary S. Terhune" wrote in message ...
Windows 98 and 98SE don't have Autoexec.bat of Config.sys files by =
default, but there's no reason you can't add them. On the other hand, =
you are right in thinking that the "usual" things that these files were =
used for in prior versions of MS-DOS and Windows are handled in other =
ways by Win98/98SE. In other words, these two venerable files are =
perfectly acceptable in Windows 98/98SE, but you have to be sure you're =
employing them appropriately.

Which is all rather beside the point: If you read the responses to your =
case in this newsgroup, all suggestions for how to remedy your issue =
involve editing System.ini. Safest way to do that is to use SYSEDIT, =
launched from the Run box, but Notepad will also suffice (however, don't =
use WordPad or any more complicated text editor, since they may throw in =
formatting characters and destroy the file.)

snip


I am trying to load Windows 98SE on to a PC with 2GB ram. (It is a new
PC with a Pentium 4 motherboard.)

On a reboot near the end of the installation process, I get the
following message:

"Insufficient memory to initialize Windows.

Quit one or more memory-resident programs or remove unnecessary
utilities from your CONFIG.SYS and AUTOEXEC.BAT files, and restart
your computer."

Having read the Microsoft Knowledgebase on this matter, I have entered
the following lines into C:\WINDOWS\SYSTEM.INI:

In the [386Enh] section -
MaxPhysPage=30000

In the [vcache] section -
MaxFileCache=275000

Despite adding these lines, I cannot get past the above error message.
Any suggestions on how to get 98SE to install on this machine?

Note that my config.sys file does not contain any reference to
himem.sys or emm386.exe
  #20  
Old February 5th 05, 09:22 PM
Brian A.
external usenet poster
 
Posts: n/a
Default

Please do not piggyback onto another thread, especially one month later.
Start a new thread and explain your situation and what has been tried to fix
it.

For now try:
Disabling the autoexec.bat and config.sys from loading during boot.
Change the MaxFileCache to = 512000


--

Brian A.

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


"Pandora" wrote in message
m...
"Gary S. Terhune" wrote in message
...
Windows 98 and 98SE don't have Autoexec.bat of Config.sys files by =
default, but there's no reason you can't add them. On the other hand, =
you are right in thinking that the "usual" things that these files were =
used for in prior versions of MS-DOS and Windows are handled in other =
ways by Win98/98SE. In other words, these two venerable files are =
perfectly acceptable in Windows 98/98SE, but you have to be sure you're =
employing them appropriately.

Which is all rather beside the point: If you read the responses to your =
case in this newsgroup, all suggestions for how to remedy your issue =
involve editing System.ini. Safest way to do that is to use SYSEDIT, =
launched from the Run box, but Notepad will also suffice (however, don't
=
use WordPad or any more complicated text editor, since they may throw in
=
formatting characters and destroy the file.)

snip


I am trying to load Windows 98SE on to a PC with 2GB ram. (It is a new
PC with a Pentium 4 motherboard.)

On a reboot near the end of the installation process, I get the
following message:

"Insufficient memory to initialize Windows.

Quit one or more memory-resident programs or remove unnecessary
utilities from your CONFIG.SYS and AUTOEXEC.BAT files, and restart
your computer."

Having read the Microsoft Knowledgebase on this matter, I have entered
the following lines into C:\WINDOWS\SYSTEM.INI:

In the [386Enh] section -
MaxPhysPage=30000

In the [vcache] section -
MaxFileCache=275000

Despite adding these lines, I cannot get past the above error message.
Any suggestions on how to get 98SE to install on this machine?

Note that my config.sys file does not contain any reference to
himem.sys or emm386.exe


 




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


All times are GMT +1. The time now is 02:23 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.