In the Forums...
Posted: May 26, 2000
Written By: Keith "Farrel" McClellan
Pagefile Sharing Continued...
Now, you can either choose to edit the value manually or use one of my pre-defined defaults. To edit the value manually, right click on the value and select Modify. You will want to modify the letters/numbers on the far right – they will automatically change the hex values to the left for you. Just be careful to leave those dots in between each character (be careful not to delete them – I haven’t yet figured out how to type them using the keyboard – they are different than regular periods). If you are going to be less brave, here are the default registry files for 128, 192, and 256 MB of virtual memory for both the C and D drives.
C Drive: 128 MB; 192 MB; 256 MB
D Drive: 128 MB; 192 MB; 256 MB
After changing the registry setting reboot into Win2k and log on to an administrator account. Then go ahead and delete pagefile.sys from your root directory – there should be a warning of some sort about deleting the file. Ignore it and delete it anyway, and then reboot again. Check and see if the file was recreated – if it wasn’t, you are in the clear.
To change the name and directory of the swapfile in Win9x so it uses the Win2k pagefile, you need to go into the system.ini file and insert the following lines underneath the [386Enh] section:
Where z: is the drive on which your pagefile resides (ex: c: or d:). After changing the setting make sure that the permanent swap file size settings for Windows are identical to the ones being used by Win2k (you can either do that from within the system.ini file or using the system applet in the control panel) and reboot Win9x and delete win386.swp. Yes, this is much easier than the previous method. Why do I include both methods? Because choices are important!
Other Performance Options
Within the Performance Options section of the system applet, there is a setting called Application response. There are two possible values for this setting. The Optimize Performance for Applications setting devotes an uneven amount of processor power to the foreground application (effectively upping the program's priority by one or two steps) at the cost of background performance. This setting is generally optimal for most users. If you, however, are commonly running a server of some sort or have other important programs crunching numbers in the background, Optimizing this setting for Background services would be advisable. This setting equally distributes processor time between all of the programs of the same priority setting no matter what is currently in the foreground.
Priority, for those of you not familiar with this term, is how the computer determines which programs should get processor time, and how much to give each one. There are six basic priority settings (although in the background it is much more complicated and tiered): Real time, High, Above Normal, Normal, Below Normal, and Low. Real time is actually something of a misnomer, and is should really be called Extra High because of the way the computer manages priority settings – and certain, special functions of the OS will receive a ‘higher than real time’ priority rating.