Microsoft Windows Embedded Standard 2009 Developer Resource Kit Componentizing Windows xp professional for embedded systems developers

How to move or rename your paging file in your runtime

Or, you may want to move the paging file to another partition that is not protected by EWF.

To rename or move the paging file, make the appropriate changes to the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management

Value: PagingFiles

Type: REG_MULT_SZ

Data: C:\pagefile.sys 150 500

In that Data field, you can adjust the name of the paging file, its location, and its minimum and maximum values.

For example, if you decide that you want the paging file to reside on drive D, to be called "Oldpagefile.sys", have a minimum value of 3 MB, and a maximum value of 2 GB, the Data field of the key would look similar to the following:

Data: D:\oldpagefile.sys 3 2000

You can make these changes from within the runtime itself if you have the registry tools installed. Or you can load the System hive offline with Regedit.exe from a full build of Windows, make your changes, and then unload the hive.

How to clear the paging file

The registry key that is referenced in the above article can be found in the Session Manager (Windows subsystem) component.

Make your runtime behave as if it is installed on drive C even though it is installed on another partition

HKEY_LOCAL_MACHINE\System\MountedDevices

In Target Designer, click Import on the File menu to load registry values from that REG file. Those keys will appear in the center pane in the "Extra Registry Data" node.

Remove any imported keys that begin with

HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices\??\Volume{guid}

For example:

HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices\??\Volume{99a4d6c3-bc54-11d6-81af-fd310b342a24}

Reassign drive letters in registry key names than begin with \DosDevices\. For example, if you want to place the runtime on the G: partition but make the runtime think and behave as if it were on the C: partition, change the registry key setting from \DosDevices\G: to \DosDevices\C:.

Folder settings in Target Designer will all point to drive C. For example:

C:\Windows

C:\Program Files

C:\Documents and Settings

However, the boot Advanced Risc Computing (ARC) path should point to the true location of the runtime.

Insight to the boot process:

During the boot, Windows mounts and assigns drive letters according to following order:

• 
  First it uses letters for volumes that have reserved positions saved within entries in the following registry key:
  

• 
  Then it tries to find new volumes that do not have matching IDs in both the Volume, and the DosDevice key groups. If the volume that matches this criteria is found, Standard 2009 assigns the first available drive letter to it, and creates both Volume and DosDevice keys for it.
  

• 
  The volume ID is a binary value that is 12 or more bytes long. It is unique for every partition on a disk, and is always the same for all installed Standard 2009-based operating systems. The first 4 bytes are disk IDs and are the same as the value that you obtain when you use the DiskPart utility.
  
• 
  The last 8 bytes represent partitions offset on disk. For removable devices, there is a more complex algorithm for creating the volume ID, but it is unique for every device.
  

Easy deployment of a pre-FBA image to a remote hard drive that has Windows XP installed on drive C. This application allows you to use drive C for your Standard 2009 image without bothering about the drive letter order that will be assigned.

To enable RAMDrive. When you make a System Deployment Image (SDI), you need to have Standard 2009 installed on drive C for Windows RAM Disk Driver (RAMDrive) to work.

Testing. In test scenarios, you can have more than one working Standard 2009 environment that differ in some settings. For example, you can test application behavior on drive D while you have MinLogon and Windows Logon builds that you want to boot from drive C.