Win98se RAM problems SOLVED!

I am posting this because people often post problems, but NOT the
answers!

Well I have the answer - at least for my situation.

I have a 3 GHz system running a P4P800 motherboard. The user requires
dual boot Win98se and WinXP.

The original deployment had 512MB of RAM and worked perfectly. Due to
memory hogging bloatware in WinXP - not to mention WinXP itself! - we
had to upgrade to 1 GB of RAM.

This is when the fun began. I was aware that Win98se has "problems"
with large amounts of RAM, and this was no exception. I tried the
tweaks from kb 253912, and 184447, and then some. No dice!

What DID work, was installing Cacheman! (v5.11 I think).

Cacheman has a profile option for resolving memory problems when you
have 512MB of memory. The first option did not work in my case. The
second option - identified as "safe" sorta worked.

After loading the "safe" profile and rebooting, I did some adjustments
to the various settings and was able to get Win98se working properly.
Thank GOD for this wonderful utility - since, as usual, the Microsoft
KB falls seriously short of expectations.

I hope this helps others.

Maybe you didn't look in the KB good enough:

768 mb or more of ram:

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

This article contains instructions which basically say: add this line in
system.ini, under [vcache]: MaxFileCache=512000
***************************

1 gb or more of ram:

Error Message: Insufficient Memory to Initialize Windows 184447
http://support.microsoft.com/?kbid=184447
***************************

1.5 gb or more of ram:

Computer May Reboot Continuously with More Than 1.5 GB of RAM 304943
http://support.microsoft.com/?kbid=304943


--
Regards

Ron Badour, MS MVP for W98
Tips: http://home.satx.rr.com/badour
Knowledge Base Info:
http://support.microsoft.com/default.aspx?pr=kbinfo

"Cloaked" wrote in message
...
I am posting this because people often post problems, but NOT the
answers!

Well I have the answer - at least for my situation.

I have a 3 GHz system running a P4P800 motherboard. The user requires
dual boot Win98se and WinXP.

The original deployment had 512MB of RAM and worked perfectly. Due to
memory hogging bloatware in WinXP - not to mention WinXP itself! - we
had to upgrade to 1 GB of RAM.

This is when the fun began. I was aware that Win98se has "problems"
with large amounts of RAM, and this was no exception. I tried the
tweaks from kb 253912, and 184447, and then some. No dice!

What DID work, was installing Cacheman! (v5.11 I think).

Cacheman has a profile option for resolving memory problems when you
have 512MB of memory. The first option did not work in my case. The
second option - identified as "safe" sorta worked.

After loading the "safe" profile and rebooting, I did some adjustments
to the various settings and was able to get Win98se working properly.
Thank GOD for this wonderful utility - since, as usual, the Microsoft
KB falls seriously short of expectations.

I hope this helps others.

Did you even read what I posted????

This is when the fun began. I was aware that Win98se has "problems"
with large amounts of RAM, and this was no exception. I tried the
tweaks from kb 253912, and 184447, and then some. No dice!

I specifically reference KB 253912, and 184447. I did NOT mention
304943 because it simply references settings previously addressed by
the aforementioned KBs.

After trying MS first, and spending hours, I loaded Cacheman and was
running in minutes.

YMMV!

On Wed, 15 Sep 2004 12:26:21 -0500, "Ron Badour"
wrote:

Maybe you didn't look in the KB good enough:

768 mb or more of ram:

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

This article contains instructions which basically say: add this line in
system.ini, under [vcache]: MaxFileCache=512000
***************************

1 gb or more of ram:

Error Message: Insufficient Memory to Initialize Windows 184447
http://support.microsoft.com/?kbid=184447
***************************

1.5 gb or more of ram:

Computer May Reboot Continuously with More Than 1.5 GB of RAM 304943
http://support.microsoft.com/?kbid=304943


--
Regards

Ron Badour, MS MVP for W98
Tips: http://home.satx.rr.com/badour
Knowledge Base Info:
http://support.microsoft.com/default.aspx?pr=kbinfo

"Cloaked" wrote in message
...
I am posting this because people often post problems, but NOT the
answers!

Well I have the answer - at least for my situation.

I have a 3 GHz system running a P4P800 motherboard. The user requires
dual boot Win98se and WinXP.

The original deployment had 512MB of RAM and worked perfectly. Due to
memory hogging bloatware in WinXP - not to mention WinXP itself! - we
had to upgrade to 1 GB of RAM.

This is when the fun began. I was aware that Win98se has "problems"
with large amounts of RAM, and this was no exception. I tried the
tweaks from kb 253912, and 184447, and then some. No dice!

What DID work, was installing Cacheman! (v5.11 I think).

Cacheman has a profile option for resolving memory problems when you
have 512MB of memory. The first option did not work in my case. The
second option - identified as "safe" sorta worked.

After loading the "safe" profile and rebooting, I did some adjustments
to the various settings and was able to get Win98se working properly.
Thank GOD for this wonderful utility - since, as usual, the Microsoft
KB falls seriously short of expectations.

I hope this helps others.

(Cloaked) wrote:


I specifically reference KB 253912, and 184447. I did NOT mention
304943 because it simply references settings previously addressed by
the aforementioned KBs.

After trying MS first, and spending hours, I loaded Cacheman and was
running in minutes.

YMMV!

I suspect that you may have put the entries into the wrong section of
the system.ini file.

The MaxFileCache entry goes into the already-existing [vcache] section
of the file. It is quite common to discover that it has been put into
the [386enh] section instead, or that a second [vcache] header has
been added to the file. That would result inthe MaxFileCache entry
not being implemented properly.

Likewise with the MaxPhysPage entry. It goes into the [386enh]
section of the file and I have seen instances where users have placed
this entry in the [vcache] section, right below the MaxFileCache
entry. Again that means that the MaxPhysPage entry will be
ineffecftive.

Other than putting these two entries into the file, and often doing so
incorrectly (Cacheman tends to use a MaxFileCache value that is more
appropriate for Windows 95 on Windows 98 systems) there is nothing
that Cacheman can or does do to remedy the types of problems you
describe.


Ron Martell Duncan B.C. Canada
--
Microsoft MVP
On-Line Help Computer Service
http://onlinehelp.bc.ca

"The reason computer chips are so small is computers don't eat much."

Not very well it appears--my apologies

--
Regards

Ron Badour, MS MVP for W98
Tips: http://home.satx.rr.com/badour
Knowledge Base Info:
http://support.microsoft.com/default.aspx?pr=kbinfo

"Cloaked" wrote in message
...
Did you even read what I posted????

This is when the fun began. I was aware that Win98se has "problems"
with large amounts of RAM, and this was no exception. I tried the
tweaks from kb 253912, and 184447, and then some. No dice!

I specifically reference KB 253912, and 184447. I did NOT mention
304943 because it simply references settings previously addressed by
the aforementioned KBs.

After trying MS first, and spending hours, I loaded Cacheman and was
running in minutes.

YMMV!

On Wed, 15 Sep 2004 12:26:21 -0500, "Ron Badour"
wrote:

Maybe you didn't look in the KB good enough:

768 mb or more of ram:

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

This article contains instructions which basically say: add this line in
system.ini, under [vcache]: MaxFileCache=512000
***************************

1 gb or more of ram:

Error Message: Insufficient Memory to Initialize Windows 184447
http://support.microsoft.com/?kbid=184447
***************************

1.5 gb or more of ram:

Computer May Reboot Continuously with More Than 1.5 GB of RAM 304943
http://support.microsoft.com/?kbid=304943


--
Regards

Ron Badour, MS MVP for W98
Tips: http://home.satx.rr.com/badour
Knowledge Base Info:
http://support.microsoft.com/default.aspx?pr=kbinfo

"Cloaked" wrote in message
...
I am posting this because people often post problems, but NOT the
answers!

Well I have the answer - at least for my situation.

I have a 3 GHz system running a P4P800 motherboard. The user requires
dual boot Win98se and WinXP.

The original deployment had 512MB of RAM and worked perfectly. Due to
memory hogging bloatware in WinXP - not to mention WinXP itself! - we
had to upgrade to 1 GB of RAM.

This is when the fun began. I was aware that Win98se has "problems"
with large amounts of RAM, and this was no exception. I tried the
tweaks from kb 253912, and 184447, and then some. No dice!

What DID work, was installing Cacheman! (v5.11 I think).

Cacheman has a profile option for resolving memory problems when you
have 512MB of memory. The first option did not work in my case. The
second option - identified as "safe" sorta worked.

After loading the "safe" profile and rebooting, I did some adjustments
to the various settings and was able to get Win98se working properly.
Thank GOD for this wonderful utility - since, as usual, the Microsoft
KB falls seriously short of expectations.

I hope this helps others.

No problem. Happens to us all.

On Wed, 15 Sep 2004 14:55:21 -0500, "Ron Badour"
wrote:

Not very well it appears--my apologies

--
Regards

Ron Badour, MS MVP for W98
Tips: http://home.satx.rr.com/badour
Knowledge Base Info:
http://support.microsoft.com/default.aspx?pr=kbinfo

"Cloaked" wrote in message
...
Did you even read what I posted????

This is when the fun began. I was aware that Win98se has "problems"
with large amounts of RAM, and this was no exception. I tried the
tweaks from kb 253912, and 184447, and then some. No dice!

I specifically reference KB 253912, and 184447. I did NOT mention
304943 because it simply references settings previously addressed by
the aforementioned KBs.

After trying MS first, and spending hours, I loaded Cacheman and was
running in minutes.

YMMV!

On Wed, 15 Sep 2004 12:26:21 -0500, "Ron Badour"
wrote:

Maybe you didn't look in the KB good enough:

768 mb or more of ram:

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

This article contains instructions which basically say: add this line in
system.ini, under [vcache]: MaxFileCache=512000
***************************

1 gb or more of ram:

Error Message: Insufficient Memory to Initialize Windows 184447
http://support.microsoft.com/?kbid=184447
***************************

1.5 gb or more of ram:

Computer May Reboot Continuously with More Than 1.5 GB of RAM 304943
http://support.microsoft.com/?kbid=304943


--
Regards

Ron Badour, MS MVP for W98
Tips: http://home.satx.rr.com/badour
Knowledge Base Info:
http://support.microsoft.com/default.aspx?pr=kbinfo

"Cloaked" wrote in message
...
I am posting this because people often post problems, but NOT the
answers!

Well I have the answer - at least for my situation.

I have a 3 GHz system running a P4P800 motherboard. The user requires
dual boot Win98se and WinXP.

The original deployment had 512MB of RAM and worked perfectly. Due to
memory hogging bloatware in WinXP - not to mention WinXP itself! - we
had to upgrade to 1 GB of RAM.

This is when the fun began. I was aware that Win98se has "problems"
with large amounts of RAM, and this was no exception. I tried the
tweaks from kb 253912, and 184447, and then some. No dice!

What DID work, was installing Cacheman! (v5.11 I think).

Cacheman has a profile option for resolving memory problems when you
have 512MB of memory. The first option did not work in my case. The
second option - identified as "safe" sorta worked.

After loading the "safe" profile and rebooting, I did some adjustments
to the various settings and was able to get Win98se working properly.
Thank GOD for this wonderful utility - since, as usual, the Microsoft
KB falls seriously short of expectations.

I hope this helps others.