Article ID: 943838 - View products that this article applies to.
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:
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:
To do this, use one of the following methods.
Method 1Delete this registry entry in the post-FBA image. To do this, follow these steps:
Method 2At 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:
For more information about how to use the FBA Generic Command resource, visit the following Microsoft Web site:
http://msdn2.microsoft.com/en-us/library/bb521399.aspxAfter 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.
Article ID: 943838 - Last Review: October 30, 2007 - Revision: 1.1
Contact us for more help