win98 and 1gig memory

I'd like to redo my Win2k system, installing win98SE on C:
and Win2K on D: However, I have 1gig of memory, and I
understand Win98 cannot deal with that much. What happens if
I proceed with the install? Will Win98 choke or merely take
what memory it can and run with it? I would of course be
installing the various apps on each OS, but would be running
Win2K; Win would simply be another backup OS. Anything else
I ought to be aware of?
Bob Bollini

 

Install 98.
Run it.
If you DO get any strange memory errors, read this, which explains easily, how to get around it in 98.
http://support.microsoft.com/default.aspx?scid=kb;en-us;253912

You can also enter a line in the [386enh] section of system.ini to actually get 98 to use more RAM.
Put this:
ConservativeSwapFileUsage=1
This forces windows to use more RAM, before read/writes to the swap. Works really well with a gig or more

 

Bob,

Previous post is for Swap file only - add the following line to [boot] under System.ini ;

MaxPhysPage=20000

This should, theoritically, make 98 run with over 512mb RAM

Mick

 

Also, add this line:

Run MSCONFIG and look in system.ini for a section that says [vcache] which will be empty. Add a line directly under it that says exactly this:

MaxFileCache=524288

Save and exit, reboot.

 

pomak249, the link I provided has all the info you posted, and is NOT just for the swapfile. I did provide the link to the official MS fix for Win98 systems with more than 512 meg of RAM.

The MaxFileCache=524288 seems a little large.

 

The 524 number is correct (512MBs) for constraining the cache.

The MaxPhysPage at 20000, however, is restricting RAM to just over 512MBs.

With the cache setting in place, you should be able to get above that.

MaxPhysPage Parameter

 

Reboot,

Sorry mate no offence meant - didnt feel the conservative swap file thingy would have helped on this occassion. The link was good.

I also feel the MaxFileCache is a bit excessive.

Mick

 

The Max is just placing an upper limit on where the file cache can grow. If you have free ram available, there is no reason not to allow Windows to use it for vcache, if required.

Of course, in reality on a 512Mb system, the cache will never get that high because Windows DOES want to use some of the ram for itself.

Whatever is left, after Windows and running apps have their allocation may as well be used.

If you are running large graphics or large database apps, then every last bit of cache should result in a performance boost.

If Windows needs memory for a running program, the first thing that is shrunk is the file cache, and this exercise is very fast.

 

This is a common misnomer and is not concerned with RAM per se. It is concerned with whether or not [=1] the async manager is used.
See MSKB 223294
From this it follows that as the Swapfile in use tends to zero the effectiveness of the async manager tends to redundancy. Again, it is not RAM per see that is the issue but Swapfile use relative to RAM installed.

 

Really interesting and informative guys.
I am getting a little lost with the terminology, etc. Could you suggest a "pretty good" list of settings that would ecompass all your thoughts (or are all those stated good to be used)? Is there a concensus?

Matt

BTW I have my swap file set by Norton Utilities. Would the settings be applicable?

 

Wasn't there a patch or utility somewhere that was supposed to fix this problem? Or am I giving Gob (Good ol' Bill, instead of God) to much credit - again?

Can't complain too much, I'd be out of a job if he did his properly!

 

win98 and 1 gig memory BIS

Gents, with respect to my post, I can only say as gently as I can that I need to know what to do. Your answers suggest that there's a consensus within reach; will someone attempt it?
O.

 

Simple, put these two lines in the C:\Windows\System.Ini file under the headings below.

[386Enh]
ConservativeSwapFileUsage=1

[Vcache]
MaxFileCache=524288

Or, instead, you can go into Start\Run type in Msconfig, click on Advanced, then in the line for Limit Memory to, set it for 512 mb. Even with this setting you will want the below to be there in the System.Ini file.

[386Enh]
ConservativeSwapFileUsage=1

You do want to use all that memory, and this will do that. Else when you open a program, the swapfile will be used first rather than your Ram, hurting your performance.

 

Mark:

I agree with your suggestions.

But, that is NOT what Conservative swap does. See gammaepsilon's post above.

A change in Windows 98 allows it to "prep" the swapfile before actually swapping takes place. The "web" has interpretted this to mean, that the swapfile is being used before ram is being used. And, that is nonsense.

By setting it to one, it forces Win98 to revert to Win95 memory management. Then, if windows needs to swap something out, it must go through the "prepping" exercise at the same time that the swap is occuring. This can result in a performance hit.

 

So if I follow Mark's suggestion ...

... I can expect a performance hit? (But there really is no choice, right?)
O.

 

If you have a "ton" of ram installed, which you do, odds are very good that Windows will NOT need to do any paging.

But, with the default setting, Windows knows no better and will carry on prepping the swapfile, just in case.

So, if you set the option to one, this prepping will not occur. AND, there won't be a performance hit, because there will never be any paging occuring.

BTW The performance "hit" only happens at the time that Windows starts to run out of ram and needs to start paging. If this happens infrequently, obviously this "hit" does also, and will thus not be as noticeable.