Reassign Drive Letters to Volumes in Target Designer
5/10/2007
You can use a multiple boot system to develop and test your run-time images. Using a multiple boot system allows you to build and deploy your test image on a drive other than C:. For example, the Tutorial: Building and Deploying a Run-Time Image sets up the development system with development tools and standard operating system on the C: drive, and deploys the test run-time image on the D: drive.
But if your final deployment is to a device that requires booting from a C: drive, your configuration will not boot unless you reconfigure the image with the C: drive specified in your Target Device Settings. For example, your target device may require the ability to boot from a Remote Boot Image, an SDI image (C:\Ramdrive), or from CompactFlash.
To avoid having to reconfigure and rebuild a run-time, you can add extra registry keys to your configuration to cause your run-time image to boot as if it is located on C:, no matter what drive it is on. This allows you to specify C: in your Target Device Settings and elsewhere in Target Designer.
To reassign drive letters to volumes in Target Designer
Boot your target device from the partition that contains Microsoft Windows XP Professional.
Open Microsoft Registry Editor (regedit.exe), and export the following key to a REG file:
HKLM\System\MountedDevices
In Target Designer, open your configuration.
From the File menu, choose Import.
In the Files of type box, choose Registry files (*.reg).
Locate the MountedDevices registry file that you previously exported, and then choose Open.
In the Import File dialog box, choose Start.
When the import is completed, choose Close.
On the View menu, make sure Resources is selected.
Choose Extra Registry Data in the configuration browser, and in the details pane, remove any imported keys that begin with HKLM\SYSTEM\MountedDevices\??\Volume{guid}.
For example, HKLM\SYSTEM\MountedDevices\??\Volume{99a4d6c3-bc54-11d6-81af-fd310b342a24}.
Reassign drive letters in key names that begin with \DosDevices\.
For example, to place the run-time image on the G: partition, but to make the run-time image behave like it is on the C: partition, change the \DosDevices\G: registry key to \DosDevices\C:.
At the top of the configuration browser, choose Settings.
Under Target Device Settings, choose Show.
Change your drive settings to C:.
Boot drive: C:.
Windows folder: C:\Windows.
Program Files folder: C:\Program Files.
Documents and Settings folder: C:\Documents and Settings.
Note
The Boot ARC path should point to the true location of the run-time image
Boot your target device from the partition that contains Microsoft Windows XP Professional.
Open Microsoft Registry Editor (regedit.exe), and export the following key to a REG file:
HKLM\System\MountedDevices
In Target Designer, open your configuration.
From the File menu, choose Import.
In the Files of type box, choose Registry files (*.reg).
Locate the MountedDevices registry file that you previously exported, and then choose Open.
In the Import File dialog box, choose Start.
When the import is completed, choose Close.
On the View menu, make sure Resources is selected.
Choose Extra Registry Data in the configuration browser, and in the details pane, remove any imported keys that begin with HKLM\SYSTEM\MountedDevices\??\Volume{guid}.
For example, HKLM\SYSTEM\MountedDevices\??\Volume{99a4d6c3-bc54-11d6-81af-fd310b342a24}.
Reassign drive letters in key names that begin with \DosDevices\.
For example, to place the run-time image on the G: partition, but to make the run-time image behave like it is on the C: partition, change the \DosDevices\G: registry key to \DosDevices\C:.
At the top of the configuration browser, choose Settings.
Under Target Device Settings, choose Show.
Change your drive settings to C:.
Boot drive: C:.
Windows folder: C:\Windows.
Program Files folder: C:\Program Files.
Documents and Settings folder: C:\Documents and Settings.
Note
The Boot ARC path should point to the true location of the run-time image
See Also
Concepts
Multiple-Boot System
Run-Time Image Deployment Design Considerations
Other Resources
Predefined System Environment Variables