This article has been archived. It is offered "as is" and will no longer be updated.
After you start a Windows XP Embedded image by using Remote Boot Server, you cannot see the local disk drives. If you view the drive in Device Manager, you find that the drive cannot be installed. Additionally, you receive error code 39. When this problem occurs, you cannot prepare the drive or copy data to the drive.
This problem does not occur if one of the following conditions is true:
The local disk drive is a removable media object, such as a compact flash card.
The Windows XP Embedded image has previously recognized the local disk drive during First Boot Agent (FBA).
This problem occurs because the driver for the local disk drive is automatically loaded when the system starts, even if the system is started from a Ramdisk drive instead of from a disk drive. This may cause a problem during the installation of a disk drive.
To work around this problem, delete the following registry entry in the critical device database:
Right-click the gendisk registry entry, click Delete, and then click Yes.
On the File menu, click Exit.
At the end of FBA, use an FBA generic command to delete this registry entry. For example, in the FBA generic command, you can specify “%11%\regedt32.exe” for the FilePath property and specify “/s gendisk.reg” for the Arguments property.
Note The placeholder gendisk.reg represents the file that you create and that contains the following content:
Windows Registry Editor Version 5.00[-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\gendisk]
For more information about how to use the FBA Generic Command resource, visit the following Microsoft Web site:
After you delete this registry entry, the driver for the local disk drive is not automatically loaded when the system starts. This is necessary when the Windows XP embedded image is started from a Ramdisk drive. In this case, the Ramdisk.sys file is the correct driver.