Windows XP...Very Interesting


Well-Known Member
Apr 7, 2001
Check this out guys...was checking on the Page file info for optimizing the system and I found a couple of topics to discuss and so forth...

By default, Windows places the pagefile on the boot partition where the operating system is installed. To

determine the size of the pagefile multiply the amount of physical RAM by 1.5 to a maximum of 4095MB. However,

placing the pagefile on the boot partition does not optimize performance because Windows has to perform disk I/O

on both the system directory and the pagefile. Therefore, it is recommended that you place the pagefile on a

different partition and different physical hard disk drive so that Windows can handle multiple I/O requests more


However, completely removing the pagefile from the boot partition does not allow Windows to create a crash dump

file (Memory.dmp) should a kernel mode STOP error occur. Not having this crash dump file could lead to extended

server downtime should the STOP require a debug to be performed.

The optimal solution is to create one pagefile on the boot partition using the default settings and create one

pagefile on another less frequently used partition. The best option is to create the second pagefile so that it

is on its own partition, with no data or operating system-specific files.

Windows will use the pagefile on the less frequently used partition over the pagefile on the heavily used boot

partition. Windows uses an internal algorithm to determine which page file to use for virtual memory management.

In the above scenario, the following goals of the page file would be served:

The system will be properly configured to capture a Memory.dmp file should the computer experience a kernel mode

STOP error.

The page file on the less frequently used partition will be used the majority of the time because it is not on a

busy partition.

Another advantage of using a pagefile on its own partition is that the pagefile will not become fragmented. If

the pagefile is on a partition with other data, the pagefile might experience fragmentation as it expands to

satisfy the extra virtual memory required. A defragmented pagefile leads to faster virtual memory access and

improves the chances of capturing a dump file without significant errors.

IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.

When you are setting the paging file size in Windows, the documentation states that the largest paging file you can select is 4,095 megabytes (MB). This is the limit set per volume; you can actually create paging files this large on one or more drives if you need a larger paging file. If extra drives or volumes are not available, you can create multiple paging files on a single drive by placing them in separate folders.

NOTE: To get a memory dump from machines with 4 GB RAM or greater, it is still necessary to use the /MAXMEM switch in the BOOT.ini. One of the page files on the system partition must still be 1 MB larger than the amount of RAM installed in the machine to allow for the successful creation of a memory dump.

For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

Q108393 MAXMEM Option in Windows NT BOOT.INI File

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT or Windows 2000, you should also update your Emergency Repair Disk (ERD).

Note that reading or writing a paging file of this size can be costly in terms of performance. If you find that you need a paging file of this size, it may be better to add more RAM to the computer. The current algorithm Windows uses to set the default paging file size is:

If total physical RAM is less than 2 gigabytes (GB), the paging file is set to 1.5 times the amount of RAM.

If total physical RAM is equal to or greater than 2 GB, the default size is set to 2 GB.

To create multiple paging files on one volume to overcome the 4,095-MB limit:
On the drive or volume you want to hold the paging files, create folders for the number of paging files you want to create on the volume. For example, C:pagefile1, C:pagefile2, and C:pagefile3.

Using Registry Editor (Regedt32.exe), locate the following key:

Find the Pagingfiles value, and then double-click it to open it.

Remove any existing values, and add the following values:

c:pagefile1pagefile.sys 3000 4000
c:pagefile2pagefile.sys 3000 4000
c:pagefile3Pagefile.sys 3000 4000
Click OK and quit Registry Editor. Restart the computer to cause the changes to take effect.

Check the properties of the paging file by right-clicking My Computer, and then clicking Properties. On the Advanced tab, click Performance Options.

In this example, the initial size of the paging files is set to 3000. Because they are used in the order they appear, you could save disk space by setting the initial size of the extra paging files to 0 so that the space is used only if needed. The initial size of the paging file is initialized to the minimum size when the computer starts. If the initial size is 3000, that space is reserved on the disk regardless of whether or not it is being used.

WARNING: The Virtual Memory property sheet does not reflect multiple page files. Multiple Page Files continue to be used on the same volume until a user clicks OK on the Virtual Memory property sheet. When the user clicks OK on the Virtual Memory property sheet, it causes the system to use one-page files displayed in the Virtual Memory property sheet.

To access the Virtual Memory property sheet, open System Properties from the Control Panel. Then follow these steps:
Click Advanced

Click Performance Options

Click Change

Lots o Reading but hey...that's wwhat forums a re for...hmm, anyone care to change the words to Thats what friends are for to thats' what forums are for.... :roll:


Well-Known Member
Sep 10, 2000
I keep putting-off buying a new PC because something new comes on the market every day. I'm leaning toward an Athlon, which has now raised a few questions.
The new Athlons are advertised as being optimized for Windows XP. So, if these new Athlons can simply transfer informaton faster, then shouldn't ANY operating system work better on them? How are they optimized SPECIFICALLY to handle tasks which are exclusive to WXP? Also, wouldn't the motherboard play a large part in the implementation and optimization of these new tasks? Without a CPU which is optimized for WXP, is WXP somewhat crippled or unable to utilize some of it's improvements or functions? If a person already has a puter running W98SE, fully updated, are the extra benefits of WXP worth updating-to?


Well-Known Member
Apr 7, 2001
hey ..sorry I didnt respond right away...didnt notice your post till you bumped it!!! lol
Anyways...Xp has a new coding that is backward compatible but definately takes advantage of newer processors such as the AMD XP processor. Yes, it is a combination of motherboards and processors and chipsets! Right now Win2k is definately the OS of choice as everything is gauranteed to work flawlessy. I dont see any performance differnce between XP and 2K at the moment then again I need a faster machine to begin with! If I were you I would go with Win2k instead of 98..much faster and better performance alltogether!!


Well-Known Member
Sep 10, 2000
Ummm....huh? Lol... Maybe I wasn't clear with my wording. Ok...
I'm leaning the Athlon way, with an iwill mobo, either the KA266-R or the XP333-R. I don't want to go the MP route at this point.
Right now, you will pay DOUBLE the price of a T-Bird 1400/266 for a new XPflagship model. If you use WXP, are you gaining something phenomenal by getting the AthlonXP? Are the gains worth paying double for the CPU and considerably more for the mobo and memory? AND, if you go with W2000, will it still be better to go with the AthlonXP CPU/mobo? Everything considered, which is a better OS...2000 or XP? Personally, I have a G4 and I love the Mac OS. My PC has W98SE and I think it sucks. I hate it. I've never used W2000 or XP, and I'd like to know what the differences are, and your opinion as to why one may be better than the other. Are audio apps that are compatible with W98 and/or W2000 automatically compatible with WXP, or are there "issues"?


Well-Known Member
Apr 7, 2001
I think you will benefit from the XP processor running XP...thats what they want you to think right? Right!!! I couldnt tell you if you will get better performance or not! Right now tests are proving XP to be not that much faster or to have a better performance rating! My personal belief is to go with Win2k...there is less you have to do to tweak it! That is what's important to me! The less you have to do to make a system work properly the better it is! If you use an XP processor with an XP mainboard and run 2k I think you will definately get some amazing results! I think it will still work the same personally...
Now, the differences between XP and 2K...Networking...Networking and more networking with a litle better security, also better support for plug and pray devices!!
The true test will be when 64 bit processors come out, with 64bit OS's and 64bit applications!! Right now there is WinXP64 and the new Intel processors that are 64 all we need is the apps!!!