Remoteboot and harddisks

  • Thread starter Thread starter Pieter
  • Start date Start date
P

Pieter

Hello group,

I am still trying to create a remoteboot image for deploying purpose.

Everything works fine when I am using a harddisk without partitions.

However when I am using a harddisk which contains partitions and data
I can not acces the drive with diskpart.
Looking closer I discoverd that the ide harddisk driver failed with
error 39.

According to:
http://www.microsoft.com/technet/tr...prodtechnol/winxppro/reskit/prjk_dec_lgsc.asp
this means:

Windows cannot load the device driver for this hardware. The driver
may be corrupted or missing. (Code 39)

and the resolotiun:

Reasons for this error include a driver that is not present; a binary
file that is corrupt; a file I/O problem, or a driver that references
an entry point in another binary file that could not be loaded.
Uninstall the driver, and then click Scan for hardware changes to
reinstall or upgrade the driver.

If have tried this using devcon:
devcon remove ide\*
devcon rescan

this does not solve the problem.

Does anyone know how to solve this problem or give me some directions
where to look?

thanks


Pieter
 
Hi Pieter,

Recently I had similar problem.

Check your setupapi.log file, and if your driver is installed, and then
removed, and then PnP tries to install new driver.
If this is the case just before you make SDI image delete file mshdc.inf it
was causing problems (for me anyway).

Regards,
Slobodan
 
Hi Slobodan,

Here are the entries in setupapi.log after I did devcon rescan:


[2003/11/10 16:02:48 304.3 Driver Install]
#-019 Searching for hardware ID(s):
ide\diskmaxtor_6e020l0__________________________nar61590,ide\maxtor_6e020l0__________________________nar61590,ide\diskmaxtor_6e020l0__________________________,maxtor_6e020l0__________________________nar61590,gendisk
#-018 Searching for compatible ID(s): gendisk
#-198 Command line processed: C:\windows\system32\services.exe
#I022 Found "GenDisk" in C:\windows\inf\disk.inf; Device: "Disk
drive"; Driver: "Disk drive"; Provider: "Microsoft"; Mfg: "(Standard
disk drives)"; Section name: "disk_install".
#I023 Actual install section: [disk_install.NT]. Rank: 0x00000004.
Effective driver date: 07/01/2001.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [disk_install] in
"c:\windows\inf\disk.inf".
#I320 Class GUID of device remains:
{4D36E967-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-166 Device install function: DIF_INSTALLDEVICEFILES.
#I124 Doing copy-only install of
"IDE\DISKMAXTOR_6E020L0__________________________NAR61590\314543414737454B202020202020202020202020".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [disk_install.NT.Interfaces] from
"c:\windows\inf\disk.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of
"IDE\DISKMAXTOR_6E020L0__________________________NAR61590\314543414737454B202020202020202020202020".
#I163 Device not started: Device has problem: 0x27:
CM_PROB_DRIVER_FAILED_LOAD.
#I121 Device install of
"IDE\DISKMAXTOR_6E020L0__________________________NAR61590\314543414737454B202020202020202020202020"
finished successfully.



Error 0x27 CM_PROB_DRIVER_FAILED_LOAD is the same error 39 I mentiond
below.
I removed MSHDC.INF. That didn't solve the problem.

I am puzzeld by the fact that the driver works with no partitions on
the harddisk. All drivers must be in the right place.

Does anyone have a idea what is going on?

Regards,

Pieter
 
Hi Pieter,

This is hard error to find.

But you don't need to use rescan, PnP should install drivers by it self.
If you have removed mshdc.inf from SDI image then you don't have problem
that I had.

Also check setupapi.log that is created during boot from SDI file, not after
rescan. So you will see what happened before error you describe.


Sorry I could not help you,
Slobodan



Pieter said:
Hi Slobodan,

Here are the entries in setupapi.log after I did devcon rescan:


[2003/11/10 16:02:48 304.3 Driver Install]
#-019 Searching for hardware ID(s):
ide\diskmaxtor_6e020l0__________________________nar61590,ide\maxtor_6e020l0_
_________________________nar61590,ide\diskmaxtor_6e020l0____________________
______,maxtor_6e020l0__________________________nar61590,gendisk
#-018 Searching for compatible ID(s): gendisk
#-198 Command line processed: C:\windows\system32\services.exe
#I022 Found "GenDisk" in C:\windows\inf\disk.inf; Device: "Disk
drive"; Driver: "Disk drive"; Provider: "Microsoft"; Mfg: "(Standard
disk drives)"; Section name: "disk_install".
#I023 Actual install section: [disk_install.NT]. Rank: 0x00000004.
Effective driver date: 07/01/2001.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [disk_install] in
"c:\windows\inf\disk.inf".
#I320 Class GUID of device remains:
{4D36E967-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-166 Device install function: DIF_INSTALLDEVICEFILES.
#I124 Doing copy-only install of
"IDE\DISKMAXTOR_6E020L0__________________________NAR61590\314543414737454B20
2020202020202020202020".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [disk_install.NT.Interfaces] from
"c:\windows\inf\disk.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of
"IDE\DISKMAXTOR_6E020L0__________________________NAR61590\314543414737454B20
2020202020202020202020".
#I163 Device not started: Device has problem: 0x27:
CM_PROB_DRIVER_FAILED_LOAD.
#I121 Device install of
"IDE\DISKMAXTOR_6E020L0__________________________NAR61590\314543414737454B20
2020202020202020202020"
finished successfully.



Error 0x27 CM_PROB_DRIVER_FAILED_LOAD is the same error 39 I mentiond
below.
I removed MSHDC.INF. That didn't solve the problem.

I am puzzeld by the fact that the driver works with no partitions on
the harddisk. All drivers must be in the right place.

Does anyone have a idea what is going on?

Regards,

Pieter


Hi Pieter,

Recently I had similar problem.

Check your setupapi.log file, and if your driver is installed, and then
removed, and then PnP tries to install new driver.
If this is the case just before you make SDI image delete file mshdc.inf it
was causing problems (for me anyway).

Regards,
Slobodan



http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtech n
Click to expand...
Click to expand...
 
Back
Top