Can't see CF disks when booting from USB device (RAMDisk)

  • Thread starter Mark K Vallevand
  • Start date
M

Mark K Vallevand

I'm building a new USB boot image based on the RAMDisk technique that is
commonly discussed in this group. I followed my decumented procedures and
found that I can't see any drives except the C: (RAMDisk). Normally I see
the RAMDisk, the USB drive, and the partitions on my CF drive. I checked
the group (google) to see if I missed anything, and I think I've got it
right. This procedure worked before. Obviously I've messed up.

In the registry, I've deleted SystemPartition, the entries under
MountedDrives, and the gendisk entry. I've changed the disk service start
to 3.

After booting, I see that all the registry changes are properly made, except
that the disk service start is back to 0. Under the MountedDrives I see
entries that seem to correspond to the USB disk device and the first CF disk
partition. When I run diskpart, it fails. Only the RAMDisk shows up in the
file explorer.

As I said, I missed something. Any ideas jump out?
 
S

Slobodan Brcin \(eMVP\)

Hi Mark,

Check setupapi.log or use device manager or devcon to see if drivers were installed.
I've changed the disk service start to 3.
Click to expand...

Probably pulled from inf file during the PnP, it does not matter.
Under the MountedDrives I see
entries that seem to correspond to the USB disk device and the first CF disk
Click to expand...

Do see there volumes like D:, E:, etc? What do you see?

Regards,
Slobodan
 
M

Mark K Vallevand

Forgot to look at setupapi.log. I'll do that this time. I'll boot this
thing in a few minutes and look.

The volumes D: and E: appear in the MountedDrives. Again, I didn't write
they exact stuff down, but it looks correct. Something about USB device and
D:. Something about STI disk and E:. (I'm using STI CF devices.)

Stay tuned.
 
M

Mark K Vallevand

OK.

The setupapi.log shows that both had error 0x27 and the driver failed to
load.

The IDE lights flash. The USB lights flash. That is something.

I'm running late. I'll chase 0x27 tomorrow. I'm sure its been seen before.
I probably have seen it before. But, my memory gets purged sometimes.
 
S

Slobodan Brcin \(eMVP\)

Hi Mark,

Yes there were always problems with drivers being started and then failing to unload.
You will have to analyze setupapi more closely or give us here relevant pieces of log.

Regards,
Slobodan
 
K

KM

Hi Mark,
Yes there were always problems with drivers being started and then failing to unload.
Click to expand...

Isn't the 0x27 - Device Not Started (CM_PROB_DRIVER_FAILED_LOAD)?
I mean it seem to fail to load.

Mark, I wonder if you run through FBA with the same disks presented?
Something similar has been discussed here:
http://groups.google.com/[email protected]

And one more quick question.. When you capture the image in SDI file, did you delete the MountedDevices key? And
[HKLM\SYSTEM\Setup],"SystemPartition" value as well?
 
S

Slobodan Brcin \(eMVP\)

Hi Konstantin,
And one more quick question.. When you capture the image in SDI file, did you delete the MountedDevices key? And
[HKLM\SYSTEM\Setup],"SystemPartition" value as well?
Click to expand...

I don't think that not removing these entries it would produce this error. Anyway in his first post he said that he deleted all
these entries. Although I can't explain how he can see D:, E: etc if 0x27 error is reported.

Regards,
Slobodan

KM said:
Hi Mark,

Yes there were always problems with drivers being started and then failing to unload.
Click to expand...

Isn't the 0x27 - Device Not Started (CM_PROB_DRIVER_FAILED_LOAD)?
I mean it seem to fail to load.

Mark, I wonder if you run through FBA with the same disks presented?
Something similar has been discussed here:
http://groups.google.com/[email protected]

And one more quick question.. When you capture the image in SDI file, did you delete the MountedDevices key? And
[HKLM\SYSTEM\Setup],"SystemPartition" value as well?

--
Regards,
KM
You will have to analyze setupapi more closely or give us here relevant pieces of log.

Regards,
Slobodan
Click to expand...
Click to expand...
 
M

Mark K Vallevand

OK. Here is the registry that shows the MountedDevvices.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices]
"\\??\\Volume{a4d19900-2ceb-11d9-93bd-806d6172696f}"=hex:b0,ea,de,a0,00,7e,0
0,\
00,00,00,00,00
"\\??\\Volume{a4d19901-2ceb-11d9-93bd-806d6172696f}"=hex:b0,ea,de,a0,00,78,6
a,\
1d,00,00,00,00
"\\DosDevices\\D:"=hex:b0,ea,de,a0,00,7e,00,00,00,00,00,00
"\\DosDevices\\E:"=hex:b0,ea,de,a0,00,78,6a,1d,00,00,00,00

Here is the edited setupapi.log file.

[2004/11/02 16:25:51 620.3 Driver Install]
#-019 Searching for hardware ID(s):
ide\disksti_flash_6.1.0_________________________rev6.1.0,ide\sti_flash_6.1.0
_________________________rev6.1.0,ide\disksti_flash_6.1.0___________________
______,sti_flash_6.1.0_________________________rev6.1.0,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\DISKSTI_FLASH_6.1.0_________________________REV6.1.0\532049545031423030
3232333634303231323435".
#-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\DISKSTI_FLASH_6.1.0_________________________REV6.1.0\532049545031423030
3232333634303231323435".
#I163 Device not started: Device has problem: 0x27:
CM_PROB_DRIVER_FAILED_LOAD.
#I121 Device install of
"IDE\DISKSTI_FLASH_6.1.0_________________________REV6.1.0\532049545031423030
3232333634303231323435" finished successfully.
[2004/11/02 16:25:55 620.8 Driver Install]
#-019 Searching for hardware ID(s):
pci\ven_1002&dev_4c59&subsys_4c591002&rev_00,pci\ven_1002&dev_4c59&subsys_4c
591002,pci\ven_1002&dev_4c59&cc_030000,pci\ven_1002&dev_4c59&cc_0300
#-018 Searching for compatible ID(s):
pci\ven_1002&dev_4c59&rev_00,pci\ven_1002&dev_4c59,pci\ven_1002&cc_030000,pc
i\ven_1002&cc_0300,pci\ven_1002,pci\cc_030000,pci\cc_0300
#-198 Command line processed: C:\windows\system32\services.exe
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#W059 Selecting best compatible driver failed. Error 0xe0000228: There are
no compatible drivers for this device.
#W157 Default installer failed. Error 0xe0000228: There are no compatible
drivers for this device.
[2004/11/02 16:25:55 620.11 Driver Install]
#-019 Searching for hardware ID(s): ramdisk\ramvolume
#-198 Command line processed: C:\windows\system32\services.exe
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#W059 Selecting best compatible driver failed. Error 0xe0000228: There are
no compatible drivers for this device.
#W157 Default installer failed. Error 0xe0000228: There are no compatible
drivers for this device.

[2004/11/02 16:26:08 620.46 Driver Install]
#-019 Searching for hardware ID(s):
usb\vid_0781&pid_7101&rev_0102,usb\vid_0781&pid_7101
#-018 Searching for compatible ID(s):
usb\class_08&subclass_06&prot_50,usb\class_08&subclass_06,usb\class_08
#-198 Command line processed: C:\windows\system32\services.exe
#I022 Found "USB\Class_08&SubClass_06&Prot_50" in
C:\windows\inf\usbstor.inf; Device: "USB Mass Storage Device"; Driver: "USB
Mass Storage Device"; Provider: "Microsoft"; Mfg: "Compatible USB storage
device"; Section name: "USBSTOR_BULK".
#I023 Actual install section: [USBSTOR_BULK.NT]. Rank: 0x00002000. Effective
driver date: 07/01/2001.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [USBSTOR_BULK] in
"c:\windows\inf\usbstor.inf".
#I320 Class GUID of device remains: {36FC9E60-C465-11CF-8056-444553540000}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-166 Device install function: DIF_INSTALLDEVICEFILES.
#I124 Doing copy-only install of "USB\VID_0781&PID_7101\00388750".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [USBSTOR_BULK.NT.Interfaces] from
"c:\windows\inf\usbstor.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "USB\VID_0781&PID_7101\00388750".
#I121 Device install of "USB\VID_0781&PID_7101\00388750" finished
successfully.

[2004/11/02 16:26:10 620.6 Driver Install]
#-019 Searching for hardware ID(s):
usbstor\diskgeneric_storage_device__1.02,usbstor\diskgeneric_storage_device_
_,usbstor\diskgeneric_,usbstor\generic_storage_device__1,generic_storage_dev
ice__1,usbstor\gendisk,gendisk
#-018 Searching for compatible ID(s): usbstor\disk,usbstor\raw
#-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: 0x00000006. 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
"USBSTOR\DISK&VEN_GENERIC&PROD_STORAGE_DEVICE&REV_1.02\00388750&0".
#-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
"USBSTOR\DISK&VEN_GENERIC&PROD_STORAGE_DEVICE&REV_1.02\00388750&0".
#I163 Device not started: Device has problem: 0x27:
CM_PROB_DRIVER_FAILED_LOAD.
#I121 Device install of
"USBSTOR\DISK&VEN_GENERIC&PROD_STORAGE_DEVICE&REV_1.02\00388750&0" finished
successfully.


--
Regards.
Mark K Vallevand
Slobodan Brcin (eMVP) said:
Hi Konstantin,
And one more quick question.. When you capture the image in SDI file, did you delete the MountedDevices key? And
[HKLM\SYSTEM\Setup],"SystemPartition" value as well?
Click to expand...

I don't think that not removing these entries it would produce this error.
Click to expand...
Anyway in his first post he said that he deleted all
these entries. Although I can't explain how he can see D:, E: etc if 0x27 error is reported.

Regards,
Slobodan

Hi Mark,

Yes there were always problems with drivers being started and then
Click to expand...
failing to unload.

Isn't the 0x27 - Device Not Started (CM_PROB_DRIVER_FAILED_LOAD)?
I mean it seem to fail to load.

Mark, I wonder if you run through FBA with the same disks presented?
Something similar has been discussed here:
http://groups.google.com/[email protected]

And one more quick question.. When you capture the image in SDI file, did you delete the MountedDevices key? And
[HKLM\SYSTEM\Setup],"SystemPartition" value as well?

--
Regards,
KM
You will have to analyze setupapi more closely or give us here relevant pieces of log.

Regards,
Slobodan

OK.

The setupapi.log shows that both had error 0x27 and the driver failed to
load.

The IDE lights flash. The USB lights flash. That is something.

I'm running late. I'll chase 0x27 tomorrow. I'm sure its been seen before.
I probably have seen it before. But, my memory gets purged sometimes.

--
Regards.
Mark K Vallevand
Forgot to look at setupapi.log. I'll do that this time. I'll boot this
thing in a few minutes and look.

The volumes D: and E: appear in the MountedDrives. Again, I didn't write
they exact stuff down, but it looks correct. Something about USB device
and
D:. Something about STI disk and E:. (I'm using STI CF devices.)

Stay tuned.
--
Regards.
Mark K Vallevand
Hi Mark,

Check setupapi.log or use device manager or devcon to see if drivers
were
installed.

I've changed the disk service start to 3.

Probably pulled from inf file during the PnP, it does not matter.

Under the MountedDrives I see
entries that seem to correspond to the USB disk device and the first
CF
disk

Do see there volumes like D:, E:, etc? What do you see?

Regards,
Slobodan

I'm building a new USB boot image based on the RAMDisk technique that
is
commonly discussed in this group. I followed my decumented procedures
and
found that I can't see any drives except the C: (RAMDisk). Normally I
see
the RAMDisk, the USB drive, and the partitions on my CF drive. I
checked
the group (google) to see if I missed anything, and I think I've got
it
right. This procedure worked before. Obviously I've messed up.

In the registry, I've deleted SystemPartition, the entries under
MountedDrives, and the gendisk entry. I've changed the disk service
start
to 3.

After booting, I see that all the registry changes are properly made,
except
that the disk service start is back to 0. Under the MountedDrives I
see
entries that seem to correspond to the USB disk device and the first
CF
disk
partition. When I run diskpart, it fails. Only the RAMDisk shows up
in
the
file explorer.

As I said, I missed something. Any ideas jump out?
Click to expand...
Click to expand...
Click to expand...
 
M

Mark K Vallevand

I'm going to rebuild and run through FBA and build the USB device again. I
ran FBA on a machine with the same hardware, but different BIOS. That might
maek a difference.

--
Regards.
Mark K Vallevand
Mark K Vallevand said:
OK. Here is the registry that shows the MountedDevvices.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices]
"\\??\\Volume{a4d19900-2ceb-11d9-93bd-806d6172696f}"=hex:b0,ea,de,a0,00,7e,0
0,\
00,00,00,00,00
Click to expand...
"\\??\\Volume{a4d19901-2ceb-11d9-93bd-806d6172696f}"=hex:b0,ea,de,a0,00,78,6
a,\
1d,00,00,00,00
"\\DosDevices\\D:"=hex:b0,ea,de,a0,00,7e,00,00,00,00,00,00
"\\DosDevices\\E:"=hex:b0,ea,de,a0,00,78,6a,1d,00,00,00,00

Here is the edited setupapi.log file.

[2004/11/02 16:25:51 620.3 Driver Install]
#-019 Searching for hardware ID(s):
ide\disksti_flash_6.1.0_________________________rev6.1.0,ide\sti_flash_6.1.0_________________________rev6.1.0,ide\disksti_flash_6.1.0___________________
______,sti_flash_6.1.0_________________________rev6.1.0,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\DISKSTI_FLASH_6.1.0_________________________REV6.1.0\532049545031423030
3232333634303231323435".
#-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\DISKSTI_FLASH_6.1.0_________________________REV6.1.0\532049545031423030
3232333634303231323435".
#I163 Device not started: Device has problem: 0x27:
CM_PROB_DRIVER_FAILED_LOAD.
#I121 Device install of
"IDE\DISKSTI_FLASH_6.1.0_________________________REV6.1.0\532049545031423030
3232333634303231323435" finished successfully.
[2004/11/02 16:25:55 620.8 Driver Install]
#-019 Searching for hardware ID(s):
pci\ven_1002&dev_4c59&subsys_4c591002&rev_00,pci\ven_1002&dev_4c59&subsys_4c
591002,pci\ven_1002&dev_4c59&cc_030000,pci\ven_1002&dev_4c59&cc_0300
#-018 Searching for compatible ID(s):
pci\ven_1002&dev_4c59&rev_00,pci\ven_1002&dev_4c59,pci\ven_1002&cc_030000,pc
i\ven_1002&cc_0300,pci\ven_1002,pci\cc_030000,pci\cc_0300
#-198 Command line processed: C:\windows\system32\services.exe
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#W059 Selecting best compatible driver failed. Error 0xe0000228: There are
no compatible drivers for this device.
#W157 Default installer failed. Error 0xe0000228: There are no compatible
drivers for this device.
[2004/11/02 16:25:55 620.11 Driver Install]
#-019 Searching for hardware ID(s): ramdisk\ramvolume
#-198 Command line processed: C:\windows\system32\services.exe
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#W059 Selecting best compatible driver failed. Error 0xe0000228: There are
no compatible drivers for this device.
#W157 Default installer failed. Error 0xe0000228: There are no compatible
drivers for this device.

[2004/11/02 16:26:08 620.46 Driver Install]
#-019 Searching for hardware ID(s):
usb\vid_0781&pid_7101&rev_0102,usb\vid_0781&pid_7101
#-018 Searching for compatible ID(s):
usb\class_08&subclass_06&prot_50,usb\class_08&subclass_06,usb\class_08
#-198 Command line processed: C:\windows\system32\services.exe
#I022 Found "USB\Class_08&SubClass_06&Prot_50" in
C:\windows\inf\usbstor.inf; Device: "USB Mass Storage Device"; Driver: "USB
Mass Storage Device"; Provider: "Microsoft"; Mfg: "Compatible USB storage
device"; Section name: "USBSTOR_BULK".
#I023 Actual install section: [USBSTOR_BULK.NT]. Rank: 0x00002000. Effective
driver date: 07/01/2001.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [USBSTOR_BULK] in
"c:\windows\inf\usbstor.inf".
#I320 Class GUID of device remains: {36FC9E60-C465-11CF-8056-444553540000}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-166 Device install function: DIF_INSTALLDEVICEFILES.
#I124 Doing copy-only install of "USB\VID_0781&PID_7101\00388750".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [USBSTOR_BULK.NT.Interfaces] from
"c:\windows\inf\usbstor.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "USB\VID_0781&PID_7101\00388750".
#I121 Device install of "USB\VID_0781&PID_7101\00388750" finished
successfully.

[2004/11/02 16:26:10 620.6 Driver Install]
#-019 Searching for hardware ID(s):
usbstor\diskgeneric_storage_device__1.02,usbstor\diskgeneric_storage_device__,usbstor\diskgeneric_,usbstor\generic_storage_device__1,generic_storage_dev
ice__1,usbstor\gendisk,gendisk
#-018 Searching for compatible ID(s): usbstor\disk,usbstor\raw
#-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: 0x00000006. 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
"USBSTOR\DISK&VEN_GENERIC&PROD_STORAGE_DEVICE&REV_1.02\00388750&0".
#-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
"USBSTOR\DISK&VEN_GENERIC&PROD_STORAGE_DEVICE&REV_1.02\00388750&0".
#I163 Device not started: Device has problem: 0x27:
CM_PROB_DRIVER_FAILED_LOAD.
#I121 Device install of
"USBSTOR\DISK&VEN_GENERIC&PROD_STORAGE_DEVICE&REV_1.02\00388750&0" finished
successfully.


--
Regards.
Mark K Vallevand
Slobodan Brcin (eMVP) said:
Hi Konstantin,
And one more quick question.. When you capture the image in SDI file, did you delete the MountedDevices key? And
[HKLM\SYSTEM\Setup],"SystemPartition" value as well?
Click to expand...

I don't think that not removing these entries it would produce this
Click to expand...
error.
Anyway in his first post he said that he deleted all
these entries. Although I can't explain how he can see D:, E: etc if
Click to expand...
0x27
error is reported.
Regards,
Slobodan
Click to expand...
http://groups.google.com/[email protected]
And one more quick question.. When you capture the image in SDI file, did you delete the MountedDevices key? And
[HKLM\SYSTEM\Setup],"SystemPartition" value as well?

--
Regards,
KM

You will have to analyze setupapi more closely or give us here relevant pieces of log.

Regards,
Slobodan

OK.

The setupapi.log shows that both had error 0x27 and the driver failed to
load.

The IDE lights flash. The USB lights flash. That is something.

I'm running late. I'll chase 0x27 tomorrow. I'm sure its been
Click to expand...
Click to expand...
seen
before.
Click to expand...
USB
device
Click to expand...
the
first
Click to expand...
drive.
I
Click to expand...
the
first
Click to expand...
Click to expand...
 
M

Mark K Vallevand

Yep. It works now. I guess the BIOS really matters.

--
Regards.
Mark K Vallevand
Mark K Vallevand said:
I'm going to rebuild and run through FBA and build the USB device again. I
ran FBA on a machine with the same hardware, but different BIOS. That might
maek a difference.

--
Regards.
Mark K Vallevand
Mark K Vallevand said:
OK. Here is the registry that shows the MountedDevvices.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices]
Click to expand...
"\\??\\Volume{a4d19900-2ceb-11d9-93bd-806d6172696f}"=hex:b0,ea,de,a0,00,7e,0"\\??\\Volume{a4d19901-2ceb-11d9-93bd-806d6172696f}"=hex:b0,ea,de,a0,00,78,6
a,\
1d,00,00,00,00
"\\DosDevices\\D:"=hex:b0,ea,de,a0,00,7e,00,00,00,00,00,00
"\\DosDevices\\E:"=hex:b0,ea,de,a0,00,78,6a,1d,00,00,00,00

Here is the edited setupapi.log file.

[2004/11/02 16:25:51 620.3 Driver Install]
#-019 Searching for hardware ID(s):
Click to expand...
ide\disksti_flash_6.1.0_________________________rev6.1.0,ide\sti_flash_6.1.0_________________________rev6.1.0,ide\disksti_flash_6.1.0___________________
______,sti_flash_6.1.0_________________________rev6.1.0,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
Click to expand...
"IDE\DISKSTI_FLASH_6.1.0_________________________REV6.1.0\532049545031423030
3232333634303231323435".
#-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
Click to expand...
"IDE\DISKSTI_FLASH_6.1.0_________________________REV6.1.0\532049545031423030
3232333634303231323435".
#I163 Device not started: Device has problem: 0x27:
CM_PROB_DRIVER_FAILED_LOAD.
#I121 Device install of
Click to expand...
"IDE\DISKSTI_FLASH_6.1.0_________________________REV6.1.0\532049545031423030
3232333634303231323435" finished successfully.
[2004/11/02 16:25:55 620.8 Driver Install]
#-019 Searching for hardware ID(s):
Click to expand...
pci\ven_1002&dev_4c59&subsys_4c591002&rev_00,pci\ven_1002&dev_4c59&subsys_4c
591002,pci\ven_1002&dev_4c59&cc_030000,pci\ven_1002&dev_4c59&cc_0300
#-018 Searching for compatible ID(s):
Click to expand...
pci\ven_1002&dev_4c59&rev_00,pci\ven_1002&dev_4c59,pci\ven_1002&cc_030000,pc
i\ven_1002&cc_0300,pci\ven_1002,pci\cc_030000,pci\cc_0300
#-198 Command line processed: C:\windows\system32\services.exe
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#W059 Selecting best compatible driver failed. Error 0xe0000228: There are
no compatible drivers for this device.
#W157 Default installer failed. Error 0xe0000228: There are no compatible
drivers for this device.
[2004/11/02 16:25:55 620.11 Driver Install]
#-019 Searching for hardware ID(s): ramdisk\ramvolume
#-198 Command line processed: C:\windows\system32\services.exe
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#W059 Selecting best compatible driver failed. Error 0xe0000228: There are
no compatible drivers for this device.
#W157 Default installer failed. Error 0xe0000228: There are no compatible
drivers for this device.

[2004/11/02 16:26:08 620.46 Driver Install]
#-019 Searching for hardware ID(s):
usb\vid_0781&pid_7101&rev_0102,usb\vid_0781&pid_7101
#-018 Searching for compatible ID(s):
usb\class_08&subclass_06&prot_50,usb\class_08&subclass_06,usb\class_08
#-198 Command line processed: C:\windows\system32\services.exe
#I022 Found "USB\Class_08&SubClass_06&Prot_50" in
C:\windows\inf\usbstor.inf; Device: "USB Mass Storage Device"; Driver: "USB
Mass Storage Device"; Provider: "Microsoft"; Mfg: "Compatible USB storage
device"; Section name: "USBSTOR_BULK".
#I023 Actual install section: [USBSTOR_BULK.NT]. Rank: 0x00002000. Effective
driver date: 07/01/2001.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [USBSTOR_BULK] in
"c:\windows\inf\usbstor.inf".
#I320 Class GUID of device remains: {36FC9E60-C465-11CF-8056-444553540000}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-166 Device install function: DIF_INSTALLDEVICEFILES.
#I124 Doing copy-only install of "USB\VID_0781&PID_7101\00388750".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [USBSTOR_BULK.NT.Interfaces] from
"c:\windows\inf\usbstor.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "USB\VID_0781&PID_7101\00388750".
#I121 Device install of "USB\VID_0781&PID_7101\00388750" finished
successfully.

[2004/11/02 16:26:10 620.6 Driver Install]
#-019 Searching for hardware ID(s):
Click to expand...
usbstor\diskgeneric_storage_device__1.02,usbstor\diskgeneric_storage_device__,usbstor\diskgeneric_,usbstor\generic_storage_device__1,generic_storage_dev
ice__1,usbstor\gendisk,gendisk
#-018 Searching for compatible ID(s): usbstor\disk,usbstor\raw
#-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: 0x00000006. 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
"USBSTOR\DISK&VEN_GENERIC&PROD_STORAGE_DEVICE&REV_1.02\00388750&0".
#-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
"USBSTOR\DISK&VEN_GENERIC&PROD_STORAGE_DEVICE&REV_1.02\00388750&0".
#I163 Device not started: Device has problem: 0x27:
CM_PROB_DRIVER_FAILED_LOAD.
#I121 Device install of
"USBSTOR\DISK&VEN_GENERIC&PROD_STORAGE_DEVICE&REV_1.02\00388750&0" finished
successfully.


--
Regards.
Mark K Vallevand
Slobodan Brcin (eMVP) said:
Hi Konstantin,

And one more quick question.. When you capture the image in SDI
Click to expand...
file,
did you delete the MountedDevices key? And
[HKLM\SYSTEM\Setup],"SystemPartition" value as well?

I don't think that not removing these entries it would produce this
Click to expand...
error.
Anyway in his first post he said that he deleted all
these entries. Although I can't explain how he can see D:, E: etc if
Click to expand...
0x27
error is reported.
Regards,
Slobodan

Hi Mark,

Yes there were always problems with drivers being started and then failing to unload.

Isn't the 0x27 - Device Not Started (CM_PROB_DRIVER_FAILED_LOAD)?
I mean it seem to fail to load.

Mark, I wonder if you run through FBA with the same disks presented?
Something similar has been discussed here:
Click to expand...
Click to expand...
http://groups.google.com/[email protected]
And one more quick question.. When you capture the image in SDI
Click to expand...
file,
did you delete the MountedDevices key? And
[HKLM\SYSTEM\Setup],"SystemPartition" value as well?

--
Regards,
KM

You will have to analyze setupapi more closely or give us here relevant pieces of log.

Regards,
Slobodan

OK.

The setupapi.log shows that both had error 0x27 and the driver failed to
load.

The IDE lights flash. The USB lights flash. That is something.

I'm running late. I'll chase 0x27 tomorrow. I'm sure its been
Click to expand...
seen
before.
I probably have seen it before. But, my memory gets purged sometimes.

--
Regards.
Mark K Vallevand
Forgot to look at setupapi.log. I'll do that this time. I'll boot this
thing in a few minutes and look.

The volumes D: and E: appear in the MountedDrives. Again, I didn't write
they exact stuff down, but it looks correct. Something about
Click to expand...
USB
device
and
D:. Something about STI disk and E:. (I'm using STI CF devices.)

Stay tuned.
--
Regards.
Mark K Vallevand
Hi Mark,

Check setupapi.log or use device manager or devcon to see if drivers
were
installed.

I've changed the disk service start to 3.

Probably pulled from inf file during the PnP, it does not matter.

Under the MountedDrives I see
entries that seem to correspond to the USB disk device and
Click to expand...
the
first
CF
disk

Do see there volumes like D:, E:, etc? What do you see?

Regards,
Slobodan

I'm building a new USB boot image based on the RAMDisk technique that
is
commonly discussed in this group. I followed my
Click to expand...
decumented
procedures
and
found that I can't see any drives except the C: (RAMDisk). Normally I
see
the RAMDisk, the USB drive, and the partitions on my CF
Click to expand...
drive.
I
checked
the group (google) to see if I missed anything, and I
Click to expand...
think
I've got
it
right. This procedure worked before. Obviously I've
Click to expand...
messed
up.
In the registry, I've deleted SystemPartition, the entries under
MountedDrives, and the gendisk entry. I've changed the
Click to expand...
disk
service
start
to 3.

After booting, I see that all the registry changes are properly made,
except
that the disk service start is back to 0. Under the MountedDrives I
see
entries that seem to correspond to the USB disk device and
Click to expand...
the
first
CF
disk
partition. When I run diskpart, it fails. Only the
Click to expand...
RAMDisk
shows up
in
the
file explorer.

As I said, I missed something. Any ideas jump out?
Click to expand...
Click to expand...
Click to expand...
 
S

Slobodan Brcin \(eMVP\)

Hi Mark,

So you don't need more help?
It sounds strange that BIOS maters for this problem.

Regards,
Slobodan


Mark K Vallevand said:
Yep. It works now. I guess the BIOS really matters.

--
Regards.
Mark K Vallevand
Mark K Vallevand said:
I'm going to rebuild and run through FBA and build the USB device again. I
ran FBA on a machine with the same hardware, but different BIOS. That might
maek a difference.

--
Regards.
Mark K Vallevand
Mark K Vallevand said:
OK. Here is the registry that shows the MountedDevvices.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices]
Click to expand...
"\\??\\Volume{a4d19900-2ceb-11d9-93bd-806d6172696f}"=hex:b0,ea,de,a0,00,7e,0"\\??\\Volume{a4d19901-2ceb-11d9-93bd-806d6172696f}"=hex:b0,ea,de,a0,00,78,6
a,\
1d,00,00,00,00
"\\DosDevices\\D:"=hex:b0,ea,de,a0,00,7e,00,00,00,00,00,00
"\\DosDevices\\E:"=hex:b0,ea,de,a0,00,78,6a,1d,00,00,00,00

Here is the edited setupapi.log file.

[2004/11/02 16:25:51 620.3 Driver Install]
#-019 Searching for hardware ID(s):
Click to expand...
ide\disksti_flash_6.1.0_________________________rev6.1.0,ide\sti_flash_6.1.0_________________________rev6.1.0,ide\disksti_flash_6.1.0___________________
______,sti_flash_6.1.0_________________________rev6.1.0,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
Click to expand...
"IDE\DISKSTI_FLASH_6.1.0_________________________REV6.1.0\532049545031423030
3232333634303231323435".
#-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
Click to expand...
"IDE\DISKSTI_FLASH_6.1.0_________________________REV6.1.0\532049545031423030
3232333634303231323435".
#I163 Device not started: Device has problem: 0x27:
CM_PROB_DRIVER_FAILED_LOAD.
#I121 Device install of
Click to expand...
"IDE\DISKSTI_FLASH_6.1.0_________________________REV6.1.0\532049545031423030
3232333634303231323435" finished successfully.
[2004/11/02 16:25:55 620.8 Driver Install]
#-019 Searching for hardware ID(s):
Click to expand...
pci\ven_1002&dev_4c59&subsys_4c591002&rev_00,pci\ven_1002&dev_4c59&subsys_4c
591002,pci\ven_1002&dev_4c59&cc_030000,pci\ven_1002&dev_4c59&cc_0300
#-018 Searching for compatible ID(s):
Click to expand...
pci\ven_1002&dev_4c59&rev_00,pci\ven_1002&dev_4c59,pci\ven_1002&cc_030000,pc
i\ven_1002&cc_0300,pci\ven_1002,pci\cc_030000,pci\cc_0300
#-198 Command line processed: C:\windows\system32\services.exe
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#W059 Selecting best compatible driver failed. Error 0xe0000228: There are
no compatible drivers for this device.
#W157 Default installer failed. Error 0xe0000228: There are no compatible
drivers for this device.
[2004/11/02 16:25:55 620.11 Driver Install]
#-019 Searching for hardware ID(s): ramdisk\ramvolume
#-198 Command line processed: C:\windows\system32\services.exe
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#W059 Selecting best compatible driver failed. Error 0xe0000228: There are
no compatible drivers for this device.
#W157 Default installer failed. Error 0xe0000228: There are no compatible
drivers for this device.

[2004/11/02 16:26:08 620.46 Driver Install]
#-019 Searching for hardware ID(s):
usb\vid_0781&pid_7101&rev_0102,usb\vid_0781&pid_7101
#-018 Searching for compatible ID(s):
usb\class_08&subclass_06&prot_50,usb\class_08&subclass_06,usb\class_08
#-198 Command line processed: C:\windows\system32\services.exe
#I022 Found "USB\Class_08&SubClass_06&Prot_50" in
C:\windows\inf\usbstor.inf; Device: "USB Mass Storage Device"; Driver: "USB
Mass Storage Device"; Provider: "Microsoft"; Mfg: "Compatible USB storage
device"; Section name: "USBSTOR_BULK".
#I023 Actual install section: [USBSTOR_BULK.NT]. Rank: 0x00002000. Effective
driver date: 07/01/2001.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [USBSTOR_BULK] in
"c:\windows\inf\usbstor.inf".
#I320 Class GUID of device remains: {36FC9E60-C465-11CF-8056-444553540000}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-166 Device install function: DIF_INSTALLDEVICEFILES.
#I124 Doing copy-only install of "USB\VID_0781&PID_7101\00388750".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [USBSTOR_BULK.NT.Interfaces] from
"c:\windows\inf\usbstor.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "USB\VID_0781&PID_7101\00388750".
#I121 Device install of "USB\VID_0781&PID_7101\00388750" finished
successfully.

[2004/11/02 16:26:10 620.6 Driver Install]
#-019 Searching for hardware ID(s):
Click to expand...
usbstor\diskgeneric_storage_device__1.02,usbstor\diskgeneric_storage_device__,usbstor\diskgeneric_,usbstor\generic_storage_device__1,generic_storage_dev
ice__1,usbstor\gendisk,gendisk
#-018 Searching for compatible ID(s): usbstor\disk,usbstor\raw
#-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: 0x00000006. 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
"USBSTOR\DISK&VEN_GENERIC&PROD_STORAGE_DEVICE&REV_1.02\00388750&0".
#-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
"USBSTOR\DISK&VEN_GENERIC&PROD_STORAGE_DEVICE&REV_1.02\00388750&0".
#I163 Device not started: Device has problem: 0x27:
CM_PROB_DRIVER_FAILED_LOAD.
#I121 Device install of
"USBSTOR\DISK&VEN_GENERIC&PROD_STORAGE_DEVICE&REV_1.02\00388750&0" finished
successfully.


--
Regards.
Mark K Vallevand
Hi Konstantin,

And one more quick question.. When you capture the image in SDI file,
did you delete the MountedDevices key? And
[HKLM\SYSTEM\Setup],"SystemPartition" value as well?

I don't think that not removing these entries it would produce this error.
Anyway in his first post he said that he deleted all
these entries. Although I can't explain how he can see D:, E: etc if 0x27
error is reported.

Regards,
Slobodan

Hi Mark,

Yes there were always problems with drivers being started and then
failing to unload.

Isn't the 0x27 - Device Not Started (CM_PROB_DRIVER_FAILED_LOAD)?
I mean it seem to fail to load.

Mark, I wonder if you run through FBA with the same disks presented?
Something similar has been discussed here:
Click to expand...
http://groups.google.com/[email protected]
And one more quick question.. When you capture the image in SDI file,
did you delete the MountedDevices key? And
[HKLM\SYSTEM\Setup],"SystemPartition" value as well?

--
Regards,
KM

You will have to analyze setupapi more closely or give us here
relevant pieces of log.

Regards,
Slobodan

OK.

The setupapi.log shows that both had error 0x27 and the driver
failed to
load.

The IDE lights flash. The USB lights flash. That is something.

I'm running late. I'll chase 0x27 tomorrow. I'm sure its been seen
before.
I probably have seen it before. But, my memory gets purged
sometimes.

--
Regards.
Mark K Vallevand
Forgot to look at setupapi.log. I'll do that this time. I'll
boot this
thing in a few minutes and look.

The volumes D: and E: appear in the MountedDrives. Again, I
didn't write
they exact stuff down, but it looks correct. Something about USB
device
and
D:. Something about STI disk and E:. (I'm using STI CF devices.)

Stay tuned.
--
Regards.
Mark K Vallevand
Hi Mark,

Check setupapi.log or use device manager or devcon to see if
drivers
were
installed.

I've changed the disk service start to 3.

Probably pulled from inf file during the PnP, it does not
matter.

Under the MountedDrives I see
entries that seem to correspond to the USB disk device and the
first
CF
disk

Do see there volumes like D:, E:, etc? What do you see?

Regards,
Slobodan

I'm building a new USB boot image based on the RAMDisk
technique that
is
commonly discussed in this group. I followed my decumented
procedures
and
found that I can't see any drives except the C: (RAMDisk).
Normally I
see
the RAMDisk, the USB drive, and the partitions on my CF drive.
I
checked
the group (google) to see if I missed anything, and I think
I've got
it
right. This procedure worked before. Obviously I've messed
up.

In the registry, I've deleted SystemPartition, the entries
under
MountedDrives, and the gendisk entry. I've changed the disk
service
start
to 3.

After booting, I see that all the registry changes are
properly made,
except
that the disk service start is back to 0. Under the
MountedDrives I
see
entries that seem to correspond to the USB disk device and the
first
CF
disk
partition. When I run diskpart, it fails. Only the RAMDisk
shows up
in
the
file explorer.

As I said, I missed something. Any ideas jump out?
Click to expand...
Click to expand...
Click to expand...
 
M

Mark K Vallevand

Yeah, it does seem strange, but it works.

--
Regards.
Mark K Vallevand
Slobodan Brcin (eMVP) said:
Hi Mark,

So you don't need more help?
It sounds strange that BIOS maters for this problem.

Regards,
Slobodan


Yep. It works now. I guess the BIOS really matters.

--
Regards.
Mark K Vallevand
Mark K Vallevand said:
I'm going to rebuild and run through FBA and build the USB device
Click to expand...
again.
I
ran FBA on a machine with the same hardware, but different BIOS. That might
maek a difference.

--
Regards.
Mark K Vallevand
OK. Here is the registry that shows the MountedDevvices.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices]
Click to expand...
"\\??\\Volume{a4d19900-2ceb-11d9-93bd-806d6172696f}"=hex:b0,ea,de,a0,00,7e,0
0,\
00,00,00,00,00
Click to expand...
"\\??\\Volume{a4d19901-2ceb-11d9-93bd-806d6172696f}"=hex:b0,ea,de,a0,00,78,6
a,\
1d,00,00,00,00
"\\DosDevices\\D:"=hex:b0,ea,de,a0,00,7e,00,00,00,00,00,00
"\\DosDevices\\E:"=hex:b0,ea,de,a0,00,78,6a,1d,00,00,00,00

Here is the edited setupapi.log file.

[2004/11/02 16:25:51 620.3 Driver Install]
#-019 Searching for hardware ID(s):
Click to expand...
ide\disksti_flash_6.1.0_________________________rev6.1.0,ide\sti_flash_6.1.0 _________________________rev6.1.0,ide\disksti_flash_6.1.0___________________
______,sti_flash_6.1.0_________________________rev6.1.0,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
Click to expand...
"IDE\DISKSTI_FLASH_6.1.0_________________________REV6.1.0\532049545031423030
3232333634303231323435".
#-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
Click to expand...
"IDE\DISKSTI_FLASH_6.1.0_________________________REV6.1.0\532049545031423030
3232333634303231323435".
#I163 Device not started: Device has problem: 0x27:
CM_PROB_DRIVER_FAILED_LOAD.
#I121 Device install of
Click to expand...
"IDE\DISKSTI_FLASH_6.1.0_________________________REV6.1.0\532049545031423030
3232333634303231323435" finished successfully.
[2004/11/02 16:25:55 620.8 Driver Install]
#-019 Searching for hardware ID(s):
Click to expand...
pci\ven_1002&dev_4c59&subsys_4c591002&rev_00,pci\ven_1002&dev_4c59&subsys_4c
591002,pci\ven_1002&dev_4c59&cc_030000,pci\ven_1002&dev_4c59&cc_0300
#-018 Searching for compatible ID(s):
Click to expand...
pci\ven_1002&dev_4c59&rev_00,pci\ven_1002&dev_4c59,pci\ven_1002&cc_030000,pc
i\ven_1002&cc_0300,pci\ven_1002,pci\cc_030000,pci\cc_0300
#-198 Command line processed: C:\windows\system32\services.exe
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#W059 Selecting best compatible driver failed. Error 0xe0000228:
Click to expand...
There
are
no compatible drivers for this device.
#W157 Default installer failed. Error 0xe0000228: There are no compatible
drivers for this device.
[2004/11/02 16:25:55 620.11 Driver Install]
#-019 Searching for hardware ID(s): ramdisk\ramvolume
#-198 Command line processed: C:\windows\system32\services.exe
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#W059 Selecting best compatible driver failed. Error 0xe0000228:
Click to expand...
There
are
no compatible drivers for this device.
#W157 Default installer failed. Error 0xe0000228: There are no compatible
drivers for this device.

[2004/11/02 16:26:08 620.46 Driver Install]
#-019 Searching for hardware ID(s):
usb\vid_0781&pid_7101&rev_0102,usb\vid_0781&pid_7101
#-018 Searching for compatible ID(s):
usb\class_08&subclass_06&prot_50,usb\class_08&subclass_06,usb\class_08
#-198 Command line processed: C:\windows\system32\services.exe
#I022 Found "USB\Class_08&SubClass_06&Prot_50" in
C:\windows\inf\usbstor.inf; Device: "USB Mass Storage Device"; Driver:
"USB
Mass Storage Device"; Provider: "Microsoft"; Mfg: "Compatible USB storage
device"; Section name: "USBSTOR_BULK".
#I023 Actual install section: [USBSTOR_BULK.NT]. Rank: 0x00002000.
Effective
driver date: 07/01/2001.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [USBSTOR_BULK] in
"c:\windows\inf\usbstor.inf".
#I320 Class GUID of device remains:
{36FC9E60-C465-11CF-8056-444553540000}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-166 Device install function: DIF_INSTALLDEVICEFILES.
#I124 Doing copy-only install of "USB\VID_0781&PID_7101\00388750".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [USBSTOR_BULK.NT.Interfaces] from
"c:\windows\inf\usbstor.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "USB\VID_0781&PID_7101\00388750".
#I121 Device install of "USB\VID_0781&PID_7101\00388750" finished
successfully.

[2004/11/02 16:26:10 620.6 Driver Install]
#-019 Searching for hardware ID(s):
Click to expand...
usbstor\diskgeneric_storage_device__1.02,usbstor\diskgeneric_storage_device_ _,usbstor\diskgeneric_,usbstor\generic_storage_device__1,generic_storage_dev
ice__1,usbstor\gendisk,gendisk
#-018 Searching for compatible ID(s): usbstor\disk,usbstor\raw
#-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: 0x00000006.
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
"USBSTOR\DISK&VEN_GENERIC&PROD_STORAGE_DEVICE&REV_1.02\00388750&0".
#-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
"USBSTOR\DISK&VEN_GENERIC&PROD_STORAGE_DEVICE&REV_1.02\00388750&0".
#I163 Device not started: Device has problem: 0x27:
CM_PROB_DRIVER_FAILED_LOAD.
#I121 Device install of
"USBSTOR\DISK&VEN_GENERIC&PROD_STORAGE_DEVICE&REV_1.02\00388750&0"
finished
successfully.


--
Regards.
Mark K Vallevand
Hi Konstantin,

And one more quick question.. When you capture the image in SDI file,
did you delete the MountedDevices key? And
[HKLM\SYSTEM\Setup],"SystemPartition" value as well?

I don't think that not removing these entries it would produce this
error.
Anyway in his first post he said that he deleted all
these entries. Although I can't explain how he can see D:, E: etc if
0x27
error is reported.

Regards,
Slobodan

Hi Mark,

Yes there were always problems with drivers being started and then
failing to unload.

Isn't the 0x27 - Device Not Started (CM_PROB_DRIVER_FAILED_LOAD)?
I mean it seem to fail to load.

Mark, I wonder if you run through FBA with the same disks presented?
Something similar has been discussed here:
Click to expand...
http://groups.google.com/[email protected]
And one more quick question.. When you capture the image in SDI file,
did you delete the MountedDevices key? And
[HKLM\SYSTEM\Setup],"SystemPartition" value as well?

--
Regards,
KM

You will have to analyze setupapi more closely or give us here
relevant pieces of log.

Regards,
Slobodan

OK.

The setupapi.log shows that both had error 0x27 and the driver
failed to
load.

The IDE lights flash. The USB lights flash. That is something.

I'm running late. I'll chase 0x27 tomorrow. I'm sure its been
seen
before.
I probably have seen it before. But, my memory gets purged
sometimes.

--
Regards.
Mark K Vallevand
Forgot to look at setupapi.log. I'll do that this time. I'll
boot this
thing in a few minutes and look.

The volumes D: and E: appear in the MountedDrives. Again, I
didn't write
they exact stuff down, but it looks correct. Something about
USB
device
and
D:. Something about STI disk and E:. (I'm using STI CF
devices.)

Stay tuned.
--
Regards.
Mark K Vallevand
Hi Mark,

Check setupapi.log or use device manager or devcon to see if
drivers
were
installed.

I've changed the disk service start to 3.

Probably pulled from inf file during the PnP, it does not
matter.

Under the MountedDrives I see
entries that seem to correspond to the USB disk device and
the
first
CF
disk

Do see there volumes like D:, E:, etc? What do you see?

Regards,
Slobodan

message
I'm building a new USB boot image based on the RAMDisk
technique that
is
commonly discussed in this group. I followed my decumented
procedures
and
found that I can't see any drives except the C: (RAMDisk).
Normally I
see
the RAMDisk, the USB drive, and the partitions on my CF
drive.
I
checked
the group (google) to see if I missed anything, and I think
I've got
it
right. This procedure worked before. Obviously I've messed
up.

In the registry, I've deleted SystemPartition, the entries
under
MountedDrives, and the gendisk entry. I've changed
Click to expand...
the
disk
service
start
to 3.

After booting, I see that all the registry changes are
properly made,
except
that the disk service start is back to 0. Under the
MountedDrives I
see
entries that seem to correspond to the USB disk device and
the
first
CF
disk
partition. When I run diskpart, it fails. Only the RAMDisk
shows up
in
the
file explorer.

As I said, I missed something. Any ideas jump out?
Click to expand...
Click to expand...
Click to expand...
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Ramdisk boot cannot see IDE drives 6
When ramdisk boot formats NTFS CF, it won't boot 10
Diskpart can't clean or partition disk 0 when boot from Ramdisk 5
RAMDISK Image 1
Black Screen - Booting SDI via USB 1
Error while loading SDI image from USB flash drive 2
ramdisk on two hard drive 8
RAMDisk and HardDisk strikes back! 6

Top