XPe on nforce2: hangs at DVD-ROM drive in fba

[Jay]

We are bringing up XPe on an nforce2 platform:
- MSI K7N2GM-L mobo
- 2x256MB DDR PC2700
- AMD Athlon XP 2500+
- 20GB Western Digital WD200 HD
- either LG GDR8162B or Samsung SD-616E 16xDVD drive

For some reason, the presence of a DVD-ROM drive causes FBA to hang
indefinitely. Disconnecting the DVD-ROM drive during FBA allows
everythign to proceed as normal; even re-attaching it later works fine
after FBA is complete.

When a DVD-ROM drive is attached, FBA hangs at ~60% and the last line
in the fbalog.txt is either:
"[FBAAddDevInstanceId]
IDE\CDROMSAMSUNG_DVD-ROM_SD-616E_________________F502____\4&13856F44&0&1.0.0"
or
"[FBAAddDevInstanceId]
IDE\CDROMHL-DT-ST_DVD-ROM_GDR8162B_______________0015____\4&13856F44&0&1.0.0"

This occurs regardless of whether the CD-ROM drive components (brought
in via TAP -> Target Designer -> Auto-resolve) are present in the XPe
build. These components are:

Primitive: cdrom.sys
Class Installer - DVD/CD-ROM
CoDevice Installer - DVD/CD-ROM drives
CD-ROM Drive*

*The CD-ROM Drive component that gets pulled in via TAP is the 12th
"CD-ROM Drive" in the list in Hardware... Devices... DVD/CD-ROM...
which has, under Resources...
PnPID(819):"SCSI\WormPIONEER_CD-WO_DR-R504X__"
PnPID(819):"SCSI\WormSONY____CD-R__CDU920S__"
PnPID(819):"SCSI\WormSONY____CD-R__CDU948S__"

Question:

Because our XPe application does not use the DVD-ROM drive, we would
prefer to have the associated components left out of the build (the
DVD-ROM is used only to update the XPe image in the field). Can we
"force" fba to ignore the presence of the DVD-ROM drive? And if not,
what CD-ROM or DVD drive component(s) should we be including? Could
it be that a driver didn't get pulled in by TAP?

Thank you for all your help now and in the past,


Jay

 

[Slobodan Brcin \(eMVP\)]

Hi Jay,

I can't give you detailed explanation right now.
But try doing following.
1. Resolve all dependencies.
2. Remove all CD/DVD components.
3. Make your component or copy manually files that any of these components bring to your image.

That is it.

BTW: FBA log tell you what passed not what went wrong.
Try setupapi.log

Best regards,
Slobodan

 

[Jay]

Slobodan,

Not sure if I'm completely clear here, but I tried removing the 4
components related to CD/DVD, then manually copying the following
files to the installation that those components were bringing in:

(from CD-ROM Drive component)
- cdrom.inf -> \WINDOWS\inf\
- imapi.sys -> \SYSTEM32\drivers\
- redbook.sys -> \SYSTEM32\drivers\
and
(from Primitive: cdrom.sys)
- cdrom.sys -> \SYSTEM32\drivers\

The other 2 components (Class Installer, CoDevice Installer) appear to
bring in registry keys only. It still hangs with the same msgs in
setupapi.log (yes, this file is much more informative, thanks!) as
when the actual components are included in Target Designer:

"...
#-019 Searching for hardware ID(s):
ide\cdromhl-dt-st_dvd-rom_gdr8162b_______________0015____,ide\hl-dt-st_dvd-rom_gdr8162b_______________0015____,ide\cdromhl-dt-st_dvd-rom_gdr8162b_______________,hl-dt-st_dvd-rom_gdr8162b_______________0015____,gencdrom
#-018 Searching for compatible ID(s): gencdrom
#-199 Executing "C:\WINDOWS\fba\fba.exe" with command line:
...\fba\fba.exe
#I022 Found "GenCdRom" in C:\WINDOWS\inf\cdrom.inf; Device: "CD-ROM
Drive"; Driver: "CD-ROM Drive"; Provider: "Microsoft"; Mfg: "(Standard
CD-ROM drives)"; Section name: "cdrom_install".
#I023 Actual install section: [cdrom_install]. Rank: 0x00000004.
Effective driver date: 07/01/2001.
#I022 Found "GenCdRom" in C:\WINDOWS\inf\cdrom.inf; Device: "CD-ROM
Drive (force CDDA accurate)"; Driver: "CD-ROM Drive (force CDDA
accurate)"; Provider: "Microsoft"; Mfg: "(Standard CD-ROM drives)";
Section name: "cdda_accurate_install".
#I023 Actual install section: [cdda_accurate_install]. Rank:
0x00001004. Effective driver date: 07/01/2001.
#I022 Found "GenCdRom" in C:\WINDOWS\inf\cdrom.inf; Device: "CD-ROM
Drive (force CDDA inaccurate)"; Driver: "CD-ROM Drive (force CDDA
inaccurate)"; Provider: "Microsoft"; Mfg: "(Standard CD-ROM drives)";
Section name: "cdda_inaccurate_install".
#I023 Actual install section: [cdda_inaccurate_install]. Rank:
0x00001004. Effective driver date: 07/01/2001.
#I022 Found "GenCdRom" in C:\WINDOWS\inf\cdrom.inf; Device: "CD-ROM
Drive (force IMAPI disable)"; Driver: "CD-ROM Drive (force IMAPI
disable)"; Provider: "Microsoft"; Mfg: "(Standard CD-ROM drives)";
Section name: "imapi_disable_install".
#I023 Actual install section: [imapi_disable_install]. Rank:
0x00001004. Effective driver date: 07/01/2001.
#I022 Found "GenCdRom" in C:\WINDOWS\inf\cdrom.inf; Device: "CD-ROM
Drive (IMAPI settings 0,1)"; Driver: "CD-ROM Drive (IMAPI settings
0,1)"; Provider: "Microsoft"; Mfg: "(Standard CD-ROM drives)"; Section
name: "imapi_buffer1_install".
#I023 Actual install section: [imapi_buffer1_install]. Rank:
0x00001004. Effective driver date: 07/01/2001.
#I022 Found "GenCdRom" in C:\WINDOWS\inf\cdrom.inf; Device: "CD-ROM
Drive (IMAPI settings 0,2)"; Driver: "CD-ROM Drive (IMAPI settings
0,2)"; Provider: "Microsoft"; Mfg: "(Standard CD-ROM drives)"; Section
name: "imapi_buffer2_install".
#I023 Actual install section: [imapi_buffer2_install]. Rank:
0x00001004. Effective driver date: 07/01/2001.
#I022 Found "GenCdRom" in C:\WINDOWS\inf\cdrom.inf; Device: "CD-ROM
Drive (IMAPI settings 0,3)"; Driver: "CD-ROM Drive (IMAPI settings
0,3)"; Provider: "Microsoft"; Mfg: "(Standard CD-ROM drives)"; Section
name: "imapi_buffer3_install".
#I023 Actual install section: [imapi_buffer3_install]. Rank:
0x00001004. Effective driver date: 07/01/2001.
#I022 Found "GenCdRom" in C:\WINDOWS\inf\cdrom.inf; Device: "CD-ROM
Drive (IMAPI settings 0,4)"; Driver: "CD-ROM Drive (IMAPI settings
0,4)"; Provider: "Microsoft"; Mfg: "(Standard CD-ROM drives)"; Section
name: "imapi_buffer4_install".
#I023 Actual install section: [imapi_buffer4_install]. Rank:
0x00001004. Effective driver date: 07/01/2001.
#I022 Found "GenCdRom" in C:\WINDOWS\inf\cdrom.inf; Device: "CD-ROM
Drive (IMAPI settings 0,5)"; Driver: "CD-ROM Drive (IMAPI settings
0,5)"; Provider: "Microsoft"; Mfg: "(Standard CD-ROM drives)"; Section
name: "imapi_buffer5_install".
#I023 Actual install section: [imapi_buffer5_install]. Rank:
0x00001004. Effective driver date: 07/01/2001.
#I022 Found "GenCdRom" in C:\WINDOWS\inf\cdrom.inf; Device: "CD-ROM
Drive (IMAPI settings 1,0)"; Driver: "CD-ROM Drive (IMAPI settings
1,0)"; Provider: "Microsoft"; Mfg: "(Standard CD-ROM drives)"; Section
name: "imapi_noopc_install".
#I023 Actual install section: [imapi_noopc_install]. Rank: 0x00001004.
Effective driver date: 07/01/2001.
#I022 Found "GenCdRom" in C:\WINDOWS\inf\cdrom.inf; Device: "CD-ROM
Drive (IMAPI settings 1,1)"; Driver: "CD-ROM Drive (IMAPI settings
1,1)"; Provider: "Microsoft"; Mfg: "(Standard CD-ROM drives)"; Section
name: "imapi_noopc_buffer1_install".
#I023 Actual install section: [imapi_noopc_buffer1_install]. Rank:
0x00001004. Effective driver date: 07/01/2001.
#I022 Found "GenCdRom" in C:\WINDOWS\inf\cdrom.inf; Device: "CD-ROM
Drive (IMAPI settings 1,2)"; Driver: "CD-ROM Drive (IMAPI settings
1,2)"; Provider: "Microsoft"; Mfg: "(Standard CD-ROM drives)"; Section
name: "imapi_noopc_buffer2_install".
#I023 Actual install section: [imapi_noopc_buffer2_install]. Rank:
0x00001004. Effective driver date: 07/01/2001.
#I022 Found "GenCdRom" in C:\WINDOWS\inf\cdrom.inf; Device: "CD-ROM
Drive (IMAPI settings 1,3)"; Driver: "CD-ROM Drive (IMAPI settings
1,3)"; Provider: "Microsoft"; Mfg: "(Standard CD-ROM drives)"; Section
name: "imapi_noopc_buffer3_install".
#I023 Actual install section: [imapi_noopc_buffer3_install]. Rank:
0x00001004. Effective driver date: 07/01/2001.
#I022 Found "GenCdRom" in C:\WINDOWS\inf\cdrom.inf; Device: "CD-ROM
Drive (IMAPI settings 1,4)"; Driver: "CD-ROM Drive (IMAPI settings
1,4)"; Provider: "Microsoft"; Mfg: "(Standard CD-ROM drives)"; Section
name: "imapi_noopc_buffer4_install".
#I023 Actual install section: [imapi_noopc_buffer4_install]. Rank:
0x00001004. Effective driver date: 07/01/2001.
#I022 Found "GenCdRom" in C:\WINDOWS\inf\cdrom.inf; Device: "CD-ROM
Drive (IMAPI settings 1,5)"; Driver: "CD-ROM Drive (IMAPI settings
1,5)"; Provider: "Microsoft"; Mfg: "(Standard CD-ROM drives)"; Section
name: "imapi_noopc_buffer5_install".
#I023 Actual install section: [imapi_noopc_buffer5_install]. Rank:
0x00001004. Effective driver date: 07/01/2001.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [cdrom_install] in
"c:\windows\inf\cdrom.inf".
#I320 Class GUID of device remains:
{4D36E965-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-124 Doing copy-only install of
"IDE\CDROMHL-DT-ST_DVD-ROM_GDR8162B_______________0015____\4&13856F44&0&1.0.0".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [cdrom_install.Interfaces] from
"c:\windows\inf\cdrom.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of
"IDE\CDROMHL-DT-ST_DVD-ROM_GDR8162B_______________0015____\4&13856F44&0&1.0.0".

Now, when no CD/DVD components or manually copied files are present,
fba hangs and setupapi.log ends with :

"#-019 Searching for hardware ID(s):
ide\cdromhl-dt-st_dvd-rom_gdr8162b_______________0015____,ide\hl-dt-st_dvd-rom_gdr8162b_______________0015____,ide\cdromhl-dt-st_dvd-rom_gdr8162b_______________,hl-dt-st_dvd-rom_gdr8162b_______________0015____,gencdrom
#-018 Searching for compatible ID(s): gencdrom
#-199 Executing "C:\WINDOWS\fba\fba.exe" with command line:
...\fba\fba.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.
#I060 Set selected driver.
#I125 Installing NULL driver for
"IDE\CDROMHL-DT-ST_DVD-ROM_GDR8162B_______________0015____\4&13856F44&0&1.0.0".
"

Can I tell XPe somehow to just disregard devices of this type and
carry on? Or is there a more forgiving CD-ROM Drive component that I
could use? I have searched for device-specific DVD-ROM drivers for
Win XP, but with no luck. Of course, that would have the very
unfortunate effect of pinning us down to using one particular model of
drive anyway.

Thank you again, your help is greatly appreciated.


Jay

Hi Jay,

I can't give you detailed explanation right now.
But try doing following.
1. Resolve all dependencies.
2. Remove all CD/DVD components.
3. Make your component or copy manually files that any of these components bring to your image.

That is it.

BTW: FBA log tell you what passed not what went wrong.
Try setupapi.log

Best regards,
Slobodan

We are bringing up XPe on an nforce2 platform:
- MSI K7N2GM-L mobo
- 2x256MB DDR PC2700
- AMD Athlon XP 2500+
- 20GB Western Digital WD200 HD
- either LG GDR8162B or Samsung SD-616E 16xDVD drive

For some reason, the presence of a DVD-ROM drive causes FBA to hang
indefinitely. Disconnecting the DVD-ROM drive during FBA allows
everythign to proceed as normal; even re-attaching it later works fine
after FBA is complete.

When a DVD-ROM drive is attached, FBA hangs at ~60% and the last line
in the fbalog.txt is either:
"[FBAAddDevInstanceId]
IDE\CDROMSAMSUNG_DVD-ROM_SD-616E_________________F502____\4&13856F44&0&1.0.0"
or
"[FBAAddDevInstanceId]
IDE\CDROMHL-DT-ST_DVD-ROM_GDR8162B_______________0015____\4&13856F44&0&1.0.0"

This occurs regardless of whether the CD-ROM drive components (brought
in via TAP -> Target Designer -> Auto-resolve) are present in the XPe
build. These components are:

Primitive: cdrom.sys
Class Installer - DVD/CD-ROM
CoDevice Installer - DVD/CD-ROM drives
CD-ROM Drive*

*The CD-ROM Drive component that gets pulled in via TAP is the 12th
"CD-ROM Drive" in the list in Hardware... Devices... DVD/CD-ROM...
which has, under Resources...
PnPID(819):"SCSI\WormPIONEER_CD-WO_DR-R504X__"
PnPID(819):"SCSI\WormSONY____CD-R__CDU920S__"
PnPID(819):"SCSI\WormSONY____CD-R__CDU948S__"

Question:

Because our XPe application does not use the DVD-ROM drive, we would
prefer to have the associated components left out of the build (the
DVD-ROM is used only to update the XPe image in the field). Can we
"force" fba to ignore the presence of the DVD-ROM drive? And if not,
what CD-ROM or DVD drive component(s) should we be including? Could
it be that a driver didn't get pulled in by TAP?

Thank you for all your help now and in the past,


Jay

 

[Slobodan Brcin \(eMVP\)]

Hi Jay,

Second case is when no cdrom.inf is present in your image, right?

If so then this problem is caused by some hardware incompatibility. Really can't tell what is wrong here, but since CD driver is not
present at least it was not a cause for this behavior.
I have no idea for a moment except that you should try second same platform and CD drive, there might be some weird hardware
malfunction that is hard to detect in normal work.

Best regards,
Slobodan

PS:
Let us know when you solve the problem about the cause of error.

Slobodan,

Not sure if I'm completely clear here, but I tried removing the 4
components related to CD/DVD, then manually copying the following
files to the installation that those components were bringing in:

(from CD-ROM Drive component)
- cdrom.inf -> \WINDOWS\inf\
- imapi.sys -> \SYSTEM32\drivers\
- redbook.sys -> \SYSTEM32\drivers\
and
(from Primitive: cdrom.sys)
- cdrom.sys -> \SYSTEM32\drivers\

The other 2 components (Class Installer, CoDevice Installer) appear to
bring in registry keys only. It still hangs with the same msgs in
setupapi.log (yes, this file is much more informative, thanks!) as
when the actual components are included in Target Designer:

"...
#-019 Searching for hardware ID(s):
ide\cdromhl-dt-st_dvd-rom_gdr8162b_______________0015____,ide\hl-dt-st_dvd-rom_gdr8162b_______________0015____,ide\cdromhl-dt-st_dvd
-rom_gdr8162b_______________,hl-dt-st_dvd-rom_gdr8162b_______________0015____,gencdrom
#-018 Searching for compatible ID(s): gencdrom
#-199 Executing "C:\WINDOWS\fba\fba.exe" with command line:
..\fba\fba.exe
#I022 Found "GenCdRom" in C:\WINDOWS\inf\cdrom.inf; Device: "CD-ROM
Drive"; Driver: "CD-ROM Drive"; Provider: "Microsoft"; Mfg: "(Standard
CD-ROM drives)"; Section name: "cdrom_install".
#I023 Actual install section: [cdrom_install]. Rank: 0x00000004.
Effective driver date: 07/01/2001.
#I022 Found "GenCdRom" in C:\WINDOWS\inf\cdrom.inf; Device: "CD-ROM
Drive (force CDDA accurate)"; Driver: "CD-ROM Drive (force CDDA
accurate)"; Provider: "Microsoft"; Mfg: "(Standard CD-ROM drives)";
Section name: "cdda_accurate_install".
#I023 Actual install section: [cdda_accurate_install]. Rank:
0x00001004. Effective driver date: 07/01/2001.
#I022 Found "GenCdRom" in C:\WINDOWS\inf\cdrom.inf; Device: "CD-ROM
Drive (force CDDA inaccurate)"; Driver: "CD-ROM Drive (force CDDA
inaccurate)"; Provider: "Microsoft"; Mfg: "(Standard CD-ROM drives)";
Section name: "cdda_inaccurate_install".
#I023 Actual install section: [cdda_inaccurate_install]. Rank:
0x00001004. Effective driver date: 07/01/2001.
#I022 Found "GenCdRom" in C:\WINDOWS\inf\cdrom.inf; Device: "CD-ROM
Drive (force IMAPI disable)"; Driver: "CD-ROM Drive (force IMAPI
disable)"; Provider: "Microsoft"; Mfg: "(Standard CD-ROM drives)";
Section name: "imapi_disable_install".
#I023 Actual install section: [imapi_disable_install]. Rank:
0x00001004. Effective driver date: 07/01/2001.
#I022 Found "GenCdRom" in C:\WINDOWS\inf\cdrom.inf; Device: "CD-ROM
Drive (IMAPI settings 0,1)"; Driver: "CD-ROM Drive (IMAPI settings
0,1)"; Provider: "Microsoft"; Mfg: "(Standard CD-ROM drives)"; Section
name: "imapi_buffer1_install".
#I023 Actual install section: [imapi_buffer1_install]. Rank:
0x00001004. Effective driver date: 07/01/2001.
#I022 Found "GenCdRom" in C:\WINDOWS\inf\cdrom.inf; Device: "CD-ROM
Drive (IMAPI settings 0,2)"; Driver: "CD-ROM Drive (IMAPI settings
0,2)"; Provider: "Microsoft"; Mfg: "(Standard CD-ROM drives)"; Section
name: "imapi_buffer2_install".
#I023 Actual install section: [imapi_buffer2_install]. Rank:
0x00001004. Effective driver date: 07/01/2001.
#I022 Found "GenCdRom" in C:\WINDOWS\inf\cdrom.inf; Device: "CD-ROM
Drive (IMAPI settings 0,3)"; Driver: "CD-ROM Drive (IMAPI settings
0,3)"; Provider: "Microsoft"; Mfg: "(Standard CD-ROM drives)"; Section
name: "imapi_buffer3_install".
#I023 Actual install section: [imapi_buffer3_install]. Rank:
0x00001004. Effective driver date: 07/01/2001.
#I022 Found "GenCdRom" in C:\WINDOWS\inf\cdrom.inf; Device: "CD-ROM
Drive (IMAPI settings 0,4)"; Driver: "CD-ROM Drive (IMAPI settings
0,4)"; Provider: "Microsoft"; Mfg: "(Standard CD-ROM drives)"; Section
name: "imapi_buffer4_install".
#I023 Actual install section: [imapi_buffer4_install]. Rank:
0x00001004. Effective driver date: 07/01/2001.
#I022 Found "GenCdRom" in C:\WINDOWS\inf\cdrom.inf; Device: "CD-ROM
Drive (IMAPI settings 0,5)"; Driver: "CD-ROM Drive (IMAPI settings
0,5)"; Provider: "Microsoft"; Mfg: "(Standard CD-ROM drives)"; Section
name: "imapi_buffer5_install".
#I023 Actual install section: [imapi_buffer5_install]. Rank:
0x00001004. Effective driver date: 07/01/2001.
#I022 Found "GenCdRom" in C:\WINDOWS\inf\cdrom.inf; Device: "CD-ROM
Drive (IMAPI settings 1,0)"; Driver: "CD-ROM Drive (IMAPI settings
1,0)"; Provider: "Microsoft"; Mfg: "(Standard CD-ROM drives)"; Section
name: "imapi_noopc_install".
#I023 Actual install section: [imapi_noopc_install]. Rank: 0x00001004.
Effective driver date: 07/01/2001.
#I022 Found "GenCdRom" in C:\WINDOWS\inf\cdrom.inf; Device: "CD-ROM
Drive (IMAPI settings 1,1)"; Driver: "CD-ROM Drive (IMAPI settings
1,1)"; Provider: "Microsoft"; Mfg: "(Standard CD-ROM drives)"; Section
name: "imapi_noopc_buffer1_install".
#I023 Actual install section: [imapi_noopc_buffer1_install]. Rank:
0x00001004. Effective driver date: 07/01/2001.
#I022 Found "GenCdRom" in C:\WINDOWS\inf\cdrom.inf; Device: "CD-ROM
Drive (IMAPI settings 1,2)"; Driver: "CD-ROM Drive (IMAPI settings
1,2)"; Provider: "Microsoft"; Mfg: "(Standard CD-ROM drives)"; Section
name: "imapi_noopc_buffer2_install".
#I023 Actual install section: [imapi_noopc_buffer2_install]. Rank:
0x00001004. Effective driver date: 07/01/2001.
#I022 Found "GenCdRom" in C:\WINDOWS\inf\cdrom.inf; Device: "CD-ROM
Drive (IMAPI settings 1,3)"; Driver: "CD-ROM Drive (IMAPI settings
1,3)"; Provider: "Microsoft"; Mfg: "(Standard CD-ROM drives)"; Section
name: "imapi_noopc_buffer3_install".
#I023 Actual install section: [imapi_noopc_buffer3_install]. Rank:
0x00001004. Effective driver date: 07/01/2001.
#I022 Found "GenCdRom" in C:\WINDOWS\inf\cdrom.inf; Device: "CD-ROM
Drive (IMAPI settings 1,4)"; Driver: "CD-ROM Drive (IMAPI settings
1,4)"; Provider: "Microsoft"; Mfg: "(Standard CD-ROM drives)"; Section
name: "imapi_noopc_buffer4_install".
#I023 Actual install section: [imapi_noopc_buffer4_install]. Rank:
0x00001004. Effective driver date: 07/01/2001.
#I022 Found "GenCdRom" in C:\WINDOWS\inf\cdrom.inf; Device: "CD-ROM
Drive (IMAPI settings 1,5)"; Driver: "CD-ROM Drive (IMAPI settings
1,5)"; Provider: "Microsoft"; Mfg: "(Standard CD-ROM drives)"; Section
name: "imapi_noopc_buffer5_install".
#I023 Actual install section: [imapi_noopc_buffer5_install]. Rank:
0x00001004. Effective driver date: 07/01/2001.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [cdrom_install] in
"c:\windows\inf\cdrom.inf".
#I320 Class GUID of device remains:
{4D36E965-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-124 Doing copy-only install of
"IDE\CDROMHL-DT-ST_DVD-ROM_GDR8162B_______________0015____\4&13856F44&0&1.0.0".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [cdrom_install.Interfaces] from
"c:\windows\inf\cdrom.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of
"IDE\CDROMHL-DT-ST_DVD-ROM_GDR8162B_______________0015____\4&13856F44&0&1.0.0".

Now, when no CD/DVD components or manually copied files are present,
fba hangs and setupapi.log ends with :

"#-019 Searching for hardware ID(s):
ide\cdromhl-dt-st_dvd-rom_gdr8162b_______________0015____,ide\hl-dt-st_dvd-rom_gdr8162b_______________0015____,ide\cdromhl-dt-st_dvd
-rom_gdr8162b_______________,hl-dt-st_dvd-rom_gdr8162b_______________0015____,gencdrom
#-018 Searching for compatible ID(s): gencdrom
#-199 Executing "C:\WINDOWS\fba\fba.exe" with command line:
..\fba\fba.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.
#I060 Set selected driver.
#I125 Installing NULL driver for
"IDE\CDROMHL-DT-ST_DVD-ROM_GDR8162B_______________0015____\4&13856F44&0&1.0.0".
"

Can I tell XPe somehow to just disregard devices of this type and
carry on? Or is there a more forgiving CD-ROM Drive component that I
could use? I have searched for device-specific DVD-ROM drivers for
Win XP, but with no luck. Of course, that would have the very
unfortunate effect of pinning us down to using one particular model of
drive anyway.

Thank you again, your help is greatly appreciated.


Jay

Hi Jay,

I can't give you detailed explanation right now.
But try doing following.
1. Resolve all dependencies.
2. Remove all CD/DVD components.
3. Make your component or copy manually files that any of these components bring to your image.

That is it.

BTW: FBA log tell you what passed not what went wrong.
Try setupapi.log

Best regards,
Slobodan

We are bringing up XPe on an nforce2 platform:
- MSI K7N2GM-L mobo
- 2x256MB DDR PC2700
- AMD Athlon XP 2500+
- 20GB Western Digital WD200 HD
- either LG GDR8162B or Samsung SD-616E 16xDVD drive

For some reason, the presence of a DVD-ROM drive causes FBA to hang
indefinitely. Disconnecting the DVD-ROM drive during FBA allows
everythign to proceed as normal; even re-attaching it later works fine
after FBA is complete.

When a DVD-ROM drive is attached, FBA hangs at ~60% and the last line
in the fbalog.txt is either:
"[FBAAddDevInstanceId]
IDE\CDROMSAMSUNG_DVD-ROM_SD-616E_________________F502____\4&13856F44&0&1.0.0"
or
"[FBAAddDevInstanceId]
IDE\CDROMHL-DT-ST_DVD-ROM_GDR8162B_______________0015____\4&13856F44&0&1.0.0"

This occurs regardless of whether the CD-ROM drive components (brought
in via TAP -> Target Designer -> Auto-resolve) are present in the XPe
build. These components are:

Primitive: cdrom.sys
Class Installer - DVD/CD-ROM
CoDevice Installer - DVD/CD-ROM drives
CD-ROM Drive*

*The CD-ROM Drive component that gets pulled in via TAP is the 12th
"CD-ROM Drive" in the list in Hardware... Devices... DVD/CD-ROM...
which has, under Resources...
PnPID(819):"SCSI\WormPIONEER_CD-WO_DR-R504X__"
PnPID(819):"SCSI\WormSONY____CD-R__CDU920S__"
PnPID(819):"SCSI\WormSONY____CD-R__CDU948S__"

Question:

Because our XPe application does not use the DVD-ROM drive, we would
prefer to have the associated components left out of the build (the
DVD-ROM is used only to update the XPe image in the field). Can we
"force" fba to ignore the presence of the DVD-ROM drive? And if not,
what CD-ROM or DVD drive component(s) should we be including? Could
it be that a driver didn't get pulled in by TAP?

Thank you for all your help now and in the past,


Jay

 

[Jay]

I'm still having the same issue here. MSoft tech support has
suggested removing the DVD-ROM drive during fba, then re-connecting it
afterwards. While this does actually work, it cant' work this way for
our product. And honestly it concerns me that perhaps devices on the
ide bus are required to have drivers in the XPe build regardless of
the need to access them from XPe.

Adding the CDFS and UDFS components was also suggested and tried
(didnt' seem to change anything), but again this seems to assume we
are accessing the drive from the XPe build. We have now tried various
XPe configurations with 3 different DVD-ROM drives, 2 of which are in
the Windows XP "catalog" (a.k.a. the HCL - Hardware Compatibility
List), and the outcome is identical. We'll keep on trying with MSoft
support, and I'll post findings/suggestions here.

We had absolutely no problem with the DVD-ROM drive when on an MSI
K4M/Athlon system - the variable here seems to be the nforce2. Has
anybody out there successfully used CD-ROM or DVD-ROM drives in an XPe
configuration with an nforce2 board, or specifically with the MSI
"K7N2GM-L" IGP board? Are there any known ide quirks or driver issues
with these nforce2 chipsets?

Thanks, again, as always,


Jay

 

[Slobodan Brcin \(eMVP\)]

Hi Jay,

Try:
1. disable cdrom.inf so it is not copied in inf folder.
2. Make fba execute command in a way that will copy/extract cdrom.inf to inf folder as last FBA step. (After FBA PnP phase 3100) It
would be best that you place it so it is executed after the first reboot. (You should experiment to see if this is necessary).
3. Make fba execute devcon.exe or your application that will remunerate hardware and make cdrom to install.

This should work.

Best regards,
Slobodan

 

[Jay]

The cdrom.inf file is part of the "CD-ROM Drive" component, which also
brings imapi.sys and redbook.sys with it. I can manually delete
cdrom.inf from the resulting image, but it behaves in the way I
described before - i.e. gets to "Installing NULL driver for
IDE\CDROMATAPI_DVD-ROM_16XMAX____________________" and hangs.

Are steps 2. and 3., (using devcon to renumerate and install),
necessary if we dont' ever need to access the DVD-ROM from our
application? I had hoped it would be possible to get fba to ignore
the drive completely, and just move on...

Could this "NULL driver" be causing a problem? Or could it mask a
problem that it encounters after dealing with the "NULL" CD-ROM
driver, such as with a totally different component? If so, I wish
setupapi.log would contain entries related to what happens after the
NULL driver install...


Jay

 

[Slobodan Brcin \(eMVP\)]

Hi Jay,

Null driver is just that. It does not have any binaries and device can't be used. It is just for visual feeling when in Device
Manager.
If what you are experiencing is true then problem could be either in some next component or in hardware itself.

If HDD and DVD are on the same cable place them on different cables.
Also check master/slave settings.

Disregard devcon statements. I told you to use that based on assumption that you were able to make XPe work without CD drivers
present.

Best regards,
Slobodan