Would like to know if with 768 mb of sdram pc133 its could be better to disable virtual memory in both winxp and win98. I know then supposly windows manage his memory like this. He will use virtual memory when ram will be filled. So with 768 mb of ram i schould be able to have enough. Well just want you opinion about that. cya and tnx all
Why are the disadvantages to disabling virtual memory? I'm planning on building a new computer soon, and I was looking forward to disabling memory once I got 512 MB (originally, I was going to get 1024 MB, but it's not worth it, now). Currently, I have 192 MB of physical memory with virtual memory set to 256 MB (static). That makes about 448 MB of total useable memory on my system (XP Home, btw). Since I've never come close to running out of memory yet, why would I want have virtual memory enabled if my physical memory would exceed my current total memory?
Note 1: The "ConservativeSwapfileUsage=1" line for the System.ini file works in Win98, but not in newer operating systems like Win2K and WinXP. It's not supported in Win95, and there is some testing that indicates little or no performance gain in WinME.
Your best bet, with large amounts of RAM on the mainboard (and if you wish to have a small Swap File) is to set the Swap or Paging File to a very low number, even as low as 2MB, (both minimum and maximum) instead of disabling the file altogether.
Also, in Win9x, with the Swap File virtually eliminated (pardon the pun) and with 768MB of RAM installed, you can set the amount of memory to be accessed as a fixed amount.
Start/Run. Type MSCONFIG, and hit Enter. Under the General tab, click the Advanced button. This will open the Advanced Troubleshooting Settings window. Check the box that limits the memory to a certain amount, and set it to 768MB (or the actual amount of physical RAM in the system.)
Note 2: I <i>really</i> don't recommend doing this unless you have 512MB of RAM or more.
With the ConservativeSwapfileUsage=1 line added to the system.ini file, this will force Windows to always access the physical memory first, and never more than 768MB. You'll find that even under relatively heavy demands, Window will almost never attempt to access the Swap File with these settings in place.
With that much RAM, you'll also need to add this line to the [vcache] section of the system.ini file:
Adding this line will avoid any potential out-of-memory errors and memory address conflicts.
In operating systems such as Win2K or WinXP, the memory management is far better, and the Virtual Memory will only be accessed when actually needed, which is the exact reverse of Win9x. I have a 768MB Paging File in Win2K, but it has never been accessed to my knowledge. I just leave it, one-because I've got ample hard drive space, and two-because Win2K just doesn't need any user help for memory management. It does quite nicely without any interference. The same applies to WinXP.
Note 3: There are certain programs, like some games, that simply won't install without detecting a Swap File. Some even require a Swap File of a certain size.
Note 4: There's almost no performance advantage to installing 768MB of RAM with a Win9x operating system.
I find it hard to believe, too. It's certainly not happening on my system when I run Photoshop, even when I use many filters in one session.
The same thing applies to Acrobat, Illustrator, Premiere, or ImageReady.
I once set up my system with Win98SE, adjusted the system.ini file, and manually restricted the memory to 512MB. I fired up Photoshop and loaded a 125KB random image. I had to apply 47 radial blur filters to the image, one after the other, before I ran out of memory. (The file was pretty darn big when I was finished ... somewhere around 150MB!) At that point, if I had enabled the Swap File ... that's when the program would have gone to the disk.
I was running with a 2MB Swap File, at the time, just to see when the system would finally send me an out-of-memory message.
I really don't know how far I'd have to go with my current configuration before the paging file would be accessed. I'll have to test it sometime, just for the heck of it, and see for myself. With a gigabyte of memory on the board, I expect that it would take a while.