Can not detect IDE Hard Disk

  • Thread starter Thread starter Yasutaka Nakamura
  • Start date Start date
Y

Yasutaka Nakamura

Hi all,

I found strange phenomenon at testing Remote Boot
Service. Remote boot XPe image can not detect IDE hard
disk drive. But when local booting, it can detect hard
disk drive(Secondary IDE disk) in spite of the same image.

Have you experienced same phenomenon?

regards,
 
Yes. We are working with Microsoft to resolve the problem.

Try this:
Remove HKLM\SYSTEM\CCS\Control\CriticalDeviceDatabase\gendisk registry
subkey in the remote boot image before booting. I loaded the registry hive
of my ramdisk image and made the change. Then, I created my boot media. It
helps in some cases.

If you look in the C:\Windows\setupapi.log file, you'll see the errors at
the end of the file. This happens in a ramdisk environment when installing
a disk drive that the ramdisk XPe image was never exposed too. It has to do
with the disk driver (disk.sys) being initially loaded at boot time (because
it controls critical devices, namely disk drives) and stays locked in
memory. This causes the 0x27 installation error code that you'll see in the
setupapi.log when the system later tries to install the disk drive.
 
Hi Mark,

So you are approaching my old "solution" (Eradicate registry entries related
to as many drivers as possible).

Interesting thing with ram boot is that you can remove almost all drivers
from your registry and that XPe will load. (Little slower, because PnP will
need to detect and install all drivers).

When you do that XPe will not know its hardware so it can be prepared in a
way that will install and work on all type of hardware.

I'm using ram boot solution for running our install/update wizard.

Unfortunately I never took the time to deeply investigate how to accomplish
some version of this removal from TD.

Regards,
Slobodan
 
The only problem with this approach, is that it doesn't seem to work in all
cases. Some of our testing people report that they still can't see the IDE
CF, even with this change. I'm waiting for Microsoft to respond.
 
This change is probably too light.

But you always have two things on your disposal.
Kernel Debugger and setupapi.log

With these two you can diagnose what is preventing your CF from being
detected.
Or if it is detected, why it is not working.

In any case I wish you luck.

Regards,
Slobodan

Mark K Vallevand said:
The only problem with this approach, is that it doesn't seem to work in all
cases. Some of our testing people report that they still can't see the IDE
CF, even with this change. I'm waiting for Microsoft to respond.
Click to expand...
 
Dear Mark,

Thank you for your advice!

I tryed your solution for resolve the problem. And My
remote boot image can detect and browse IDE disk volume.

Thank you very much!

Regards,
 
Back
Top