Aces High Bulletin Board
Help and Support Forums => Technical Support => Topic started by: Griego on February 02, 2003, 10:18:25 PM
-
I just learned some new setting in [Vcache] to get W98 to reconize and use 512mb Ram. I've tried some other setting in Vcache and they didn't work for me.
Old setting were:
[Vcache]
MinFileCache=16384
MaxFileCache=65536
ChunkSize=512
these didn't work I couldn't get more that 384mb of Ram anything more system would freeze. I had unchecked Ram limitations in the Adv Tab in MSconfig with the settings also.
New settings are:
[Vcache]
MaxCacheSize=98303
MinFileCache=16834
MaxFileCache=172032
wondering if these would work. Are these setting for more than the 512mb of Ram I'm going to upgrade to.
I also have in [Vcache] ChunkSize=512 still. There was no mention that I had to put in ChunkSize at all in the tweak to get windows to reconize and use 512mb or Ram. It also said I had to deactivate Ram limitations under the Adv tab in Msconfig. I had already done that.
Anyone that has done this. Does it work before I go out and buy more Ram for my system. Right now I use 384mb of Ram and it's all that will work. When I put more Ram in it Windows freezes and I have to reboot.
I got a K7T Turbo2 MSI mobo.
window 98 first edition
Athlon 1800xp
384 SDram
Sb live 512 sound card
Geforce 4 ti 4200 64mb ddr
19" view sonic
Thanks for any help on this subject.
-
why not just get an OEM version of XP when you get a piece of hardware? Your performance gains are probably going to be so minimal that you won't even notice the difference.
-
What your saying is that in Windows 98 384mb of Ram is about the same as 512mbs of Ram. Since there isn't that much of a performance gain going from 384mb to 512mb using windows 98.
Why would there be a difference in performance using windows xp. When windows xp is suppose to use more ram to function.
-
** notes that I kept
Vcache is essentially smartdrv (Disk caching) for Windows, except that it's 32 bit, built into the Windows 9X/NT OS, and shares the same memory pool as running applications. The reason you add the vcache lines is that by default, Microsoft rather generously grants memory to vcache, which is an incredible miser about returning it to the free memory pool. So what happens and why it helps is that by default eventually all or nearly all free physical memory in your machine not already allocated to running applications will be allocated to vcache, and once that happens any application requesting memory is allocated from the virtual memory swap file.
Vcache is the disk cache. It's a region of RAM that the windows
uses to read pieces of recently used data on the disk. When
windows needs something off the disk, it will look in the cache
first for it. If it's not there, then it will go to the disk for
it. Likewise, when ever a disk write operation occurs, it is also
written to the cache. By keeping recently used data in the cache,
which is also the data that windows will most likely need in the
immediate future, disk access is kept to a minimum and made more efficient. RAM access is orders of magnitude faster than disk
access. The entries in system.ini what we typically do are to
size the cache region of RAM manually, as windows default values
are thought to be too small. If you make the cache too big however, it can decrease performance 'cause you're tying up RAM that windows could use for other things.
For up to 128Mb use the max setting formula of (RAM in MB)(0.25)
x 1025
For 128 to 256Mb I generally use the same formula except I multiply it all by 0.75
For 256 to 384Mb I multiply it all by 0.50
For over 384, I keep it at 384 x .25 x 1024 x .5 = 49152...
(which is getting pretty stinkin huge, no sense going any
larger no matter how much ram you have)
For the Min amount, just halve whatever the Max amount is.
Chunksize is always 512. (In fact, that's the default)
128 megs x 0.25 x 1024 = 32768 max
128 megs x 0.25 x 1024 x 0.75 = 24576 max
256 megs x 0.25 x 1024 x 0.75 = 49152 max
256 megs x 0.25 x 1024 x 0.50 = 32768 max
384 megs x 0.25 x 1024 x 0.50 = 49152 max
512 megs x 0.25 x 1024 x 0.50 = 65536 max
(The "MIN" are half of the "MAX )
>>> OR <<<<
MinFileCache=32768
MaxFileCache=65536
ChunkSize=512
PS: And add this to your 386Enh section
[386Enh]
ConservativeSwapfileUsage=1
Your choice really what number you use... the differences it will
make are trivial after you reach a certain level of ram,
that's why after you hit 384 you level off on the cache size.
49152 is a pretty big cache allocation...
The best writeup of vcache optimization and why it is (and isn't in some cases) necessary is here: http://www.rojakpot.com/Speed_Demonz.htm
Give it a read.. this guy's done his homework. While you're at it, read the chunksize and swapfile optimizations too. Pay particular attention to the section on sizing the swapfile. Note that the more ram you have, the SMALLER it should be.... not the opposite.
When you're done that and really want to be confused, readup about the Namecache and Pathcache settings in your registry under the heading "MAX CACHE SPEED" here: http://users.aol.com/axcel216/newtip16.htm
-
well the Rojak link is dead. The other link worked and is rather interesting. HOwever this link is a little bit better done and actually provides references. Click Here (http://www.aumha.org/a/memmgmt.php)
-
Good article .. certainly added it to my Favorites List.
Thanks for the heads up.
sprint
-
Originally posted by sprint
>>> OR <<<<
MinFileCache=32768
MaxFileCache=65536
ChunkSize=512
PS: And add this to your 386Enh section
[386Enh]
ConservativeSwapfileUsage=1 [/B]
Thanks for your input. I have used these numbers also with no results. I have the ConservativeSwapFileUsage=1 under [386Enh] already. My problem though is that with only these numbers under [Vcache] It still didn't let me use 512mb of Ram. my system would freeze. It would freeze with anything above 384mb of Ram.
So my question is. Is MaxCachSize=xxxxx the entry that will let me use 512mb of Ram in my system because using MaxFileCache=xxxxx, MinFileCache=xxxxx, and ChunckSize=xxxxx alone did not work. I have used the numbers stated above and still it didn't work. I couldn't use anything higher than 384mbs of Ram. My system would just freeze up in windows, and I had to reboot the PC using the restart button.
Thanks for the links Sprint and Dingbat. they were very helpfull but they too left out the MaxCacheSize=xxxxx entry. HMMMM.
I'm going to reduce the MaxFileCache entries to what you have stated above for 384mb of Ram until I by more Ram. Maybe I bought a bad stick of Ram.
If you find any information on the MaxCacheSize=xxxxx entry being the missing link in my persuit of using more ram in my system I would greatlly appreciate any Information.
Thanks again.
-
Will your machine handle 512? I had an older abit that could only take 384 MB's anymore and it would freeze. My asus tusl2 also has a limit at 512, even though I still have two more open slots. If I populate it, it freezes like a deer in headlights.
-
Dingbat,
I have an identical system to you with the exception of a Ti600 & Audigy.
What sort've FPS do you get? also has your Asus board got the optional onboard sound the ALC650, if so have you tried it out?
Regards
Mandrill
-
yes mobo says it will handle 1.5ghz of ram.
Does anyone have any insight on the maxcachesize=xxxx setting
-
Originally posted by woodfordb
Dingbat,
I have an identical system to you with the exception of a Ti600 & Audigy.
What sort've FPS do you get? also has your Asus board got the optional onboard sound the ALC650, if so have you tried it out?
Regards
Mandrill
Sorry I didn't see this sooner, bro. I ditched the On board sound got lame results with it. I lock my frames at 45 but generally I get between 75-100
I lock mine at 45 because it appears to make the game run smoother by not letting the CPU spend all it's time trying ti keep a higher framerate. I think I asked scuzzy for an answer on this but don't recall if I ever asked.