Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
I have just installed an additional 484mb of ram-total 896mb.On booting to windows I received the following message.
"While initialising device V86MMGR insufficient memory to initialise windows.Quit one or more memory resident programs or remove unnessary utilities from your Config.sys & Autoexe.bat files and restart your computer.
Both files are lean as it is and I was a bit supprised at the message bearing in mind the total memory. Perhaps someone can enlighten me.

98 SE doesn't handle over 512 MB of RAM very well. I am not sure what you need to do, but I think that searching here using the search feature should help get you an answer.
Smitty

"Out of Memory" Error Messages with Large Amounts of RAM Installed
Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.

Yeah, unless you have a dual boot set up with XP you may want to remove the excess. Or, if you want to keep it, this may help.

Dave:
That file from Driverguide contains some misleading, and incorrect information.It states that the only thing required to make Win9x run with more than 512, is to add a Min and Max file cache.
Well, doing what they suggest will certainly work, BUT there tweak actually DEDICATES 132MBs of ram to the file cache,whether it is in use or not. The actual fix is to just place a MaxFileCache=524288, which puts an upper limit on the cache.
The first graphic (re resources) indicates a misunderstaning of XP and System Resources.
And, the recommendation to add ConservativeSwapFileUsage has the comments that this causes windows to use ram before the swapfile. This, of course, is not true. (it makes Win98 memory mgt run like Windows 95).
Yes, some people have indicated they have seen a performance affect, but in general, I do not think it's a good tweak.They also recommend placing an upper limit on the swapfile, which also is not a good idea.

Thanks Guys for the responses. I was a bit short fuse in posting as a search produced a number of posts with the same problem. I removed one ram chip reducing the total to 768mb and tweeked the vcache according to the link to Driverguide made by Dave. I am monitoring the ram useage and so far it seems to work. However I take on board the comments made by WhitPhil. WhitPhil could you summarise what you would do to achieve the the same end with say total ram of 768.
Richard.

Essentially, place the MaxFileCache=524288 in System.ini and it should run fine.
(even at 896)As I said, the tweak from Driver guide, because it specifies a MIN and a MAX is dedicating all that ram to the file cache. In order to work above 512, you just need to place an upper limit (of 512 or less).

Thanks WhitPhil. I know you've posted on the subject before. RPN, any additions or changes that he recommends would probably be the way to go.
I got the pics was from a site that Skipcox found a while back. I thought the screen shots made the process simple enough for even a newbie. I'd noted in a previous post that memory management for large RAM was more an art than science in that there were differing opinions on how to do it. I probably should have added that qualifier to the description at driverguide.
I never had the inclination or opportunity to test if one way is more efficient than another as I've personally never put more than 256 meg in a machine. The only alterations I've made was adding the 'conservativeswapfileusage' line. I've noticed that keeps the swap file at zero during basic operation.

But, just because the swapfile has a "size" does not actually mean that it is actively being used.Meaning, window is not continually paging ram to and from the pagefile.
With Win98, memory management became more proactive in low memory situations,and windows would start to "prepare" to do actual paging. This involved setting up space in the pagefile (thus making it have a size), BUT the memory areas were still in memory.
What this does is allow Windows to very quickly free up memory, when/if it "runs out".
With Conservativeswap set, the pagefile may or may not have a size, BUT at the point where windows "runs out", you will see a performance hit, because now windows has to REACT and figure out what can be moved out and then actually go about paging items out.You can watch some of this going on by running the Performance Monitor and monitoring swapfile size, usage, and paging rates.

Whitphil
I have been running a dual boot 98/2000 setup with 1 GB of RAM in dual channel for about a year. I have been using the method DAVINCAPS suggested all that time. Are you saying I would be better off to remove the changes made then and just add the line you posted above? If so, does it matter in what section of System.ini the line is placed? I might add that in my case it was necessary to limit the RAM. Win98se was very flaky until I did.

OtheHill
As I said, the tweaks with both Min and MaxFileCache will work, because what it has done is limit the file cache to a size under 512MBs. Which is what is required to keep Win9x happy with more than 512 installed.
But, the side affect is that by placing a MIN you have now dedicated this ram to be used ONLY by the file cache. AND, you have limited the max size to 132MBs.
So, if the PC could ever benefit by having a larger cache, it can't make it any larger.
By using just a MAX of 512, you now allow the cache to be anywhere from zero up to 512.
(and the MaxFileCache must be specified in the [vcache] section.

![]() |
Invalid System Disk
|
bad hardware and comp. cr...
|

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |