Creative Audigy 2 Value

[Mike Warren]

Hi,

I'm trying to get the Creative Audigy 2 Value sound driver installed.

My first step was to try and componentize the driver. I did an install
on a fresh XPPro target using InCtrl5 to monitor what happened.

There are over 8200 registry changes and about 300 files or folders
changed or added.

What do I do with all this data? It would take me a year to create
a component with everything in it.

So I thought I would try to allow the supplied CD to do the installation
after the image was deployed...

I have had to add quite a lot to my image to make this work. Although
there were no errors during the installation and the driver shows up in Device
Manager afterwards as Creative SB Audigy 2 (WDM) the Sound Control
Panel shows "No Audio Device" and the creative mixer software doesn't
find the card.

Can anyone suggest a solution?

-Mike

 

[Slobodan Brcin \(eMVP\)]

Hi Mike,

Can you install drivers manually on running XPe? In not you must fist add enough components for this to work.
Please delete setuapi.log before attempting to install drivers. and if you have problems analyze setupapi.log for what is missing or
post it here as attachment.

Next phase would be to determine or extract driver files, service files, etc. in one flat folder for making XPe component and to
manually make component that will bring all those files in their place in XPe image folders that you can see after you install
drivers.
Now if you need only drivers. (No extra codec's/services etc) just if you have enough files in their folders will be enough for FBA
PnP to pick right drivers and to install them. Check this from device manager.

Regards,
Slobodan

 

[Mike Warren]

Hi Slobodan,

Can you install drivers manually on running XPe? In not you must fist
add enough components for this to work.
Please delete setuapi.log before attempting to install drivers. and
if you have problems analyze setupapi.log for what is missing or post
it here as attachment.

I'll try that if your last method fails.

Now if you need only drivers. (No extra codec's/services etc) just if
you have enough files in their folders will be enough for FBA PnP to
pick right drivers and to install them. Check this from device
manager.

I copied all the files listed for the driver to System32 and System32\Drivers
as appropriate and any .inf files I found with "Creative" in them. (Is there a
better way to find the .inf files?)

The driver installed but failed to start. On comparing the file list between the
working XPPro and my image I found 4 files missing from the Device Manager
list.

I tried again by finding any .inf file which mentioned the missing files.

This time the file lists match but the driver still fails to start. Here are the
sections of SetupApi.log which I think are relevent.

(The full file is here: www.cairnscarsound.com.au/temp/setupapi.log )

[2004/12/15 14:30:00 412.328 Driver Install]
#-019 Searching for hardware ID(s):
pci\ven_1102&dev_0008&subsys_10011102&rev_00,pci\ven_1102&dev_0008&subsys_10011102,pci\ven_1102&dev_0008&cc_040100,pci\ven_1102&dev_0008&cc_0401
#-018 Searching for compatible ID(s):
pci\ven_1102&dev_0008&rev_00,pci\ven_1102&dev_0008,pci\ven_1102&cc_040100,pci\ven_1102&cc_0401,pci\ven_1102,pci\cc_040100,pci\cc_0401
#-199 Executing "C:\XPE\fba\fba.exe" with command line: ..\fba\fba.exe
#I022 Found "PCI\VEN_1102&DEV_0008&SUBSYS_10011102" in C:\XPE\inf\oem0.inf; Device: "Creative Audigy
Audio Processor (WDM)"; Driver: "Creative Audigy Audio Processor (WDM)"; Provider: "Creative"; Mfg:
"Creative Technology, Ltd."; Section name: "Audigy_Device".
#I023 Actual install section: [Audigy_Device.NT]. Rank: 0x00000001. Effective driver date:
07/01/2004.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [Audigy_Device] in "c:\xpe\inf\oem0.inf".
#I320 Class GUID of device remains: {4D36E96C-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-124 Doing copy-only install of "PCI\VEN_1102&DEV_0008&SUBSYS_10011102&REV_00\4&1F7DBC9F&0&20F0".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [Audigy_Device.NT.Interfaces] from "c:\xpe\inf\oem0.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "PCI\VEN_1102&DEV_0008&SUBSYS_10011102&REV_00\4&1F7DBC9F&0&20F0".
#I163 Device not started: Device has problem: 0x0a: CM_PROB_FAILED_START.
#I121 Device install of "PCI\VEN_1102&DEV_0008&SUBSYS_10011102&REV_00\4&1F7DBC9F&0&20F0" finished
successfully.

[2004/12/15 14:36:03 1112.160 Driver Install]
#-019 Searching for hardware ID(s):
pci\ven_1102&dev_0008&subsys_10011102&rev_00,pci\ven_1102&dev_0008&subsys_10011102,pci\ven_1102&dev_0008&cc_040100,pci\ven_1102&dev_0008&cc_0401
#-018 Searching for compatible ID(s):
pci\ven_1102&dev_0008&rev_00,pci\ven_1102&dev_0008,pci\ven_1102&cc_040100,pci\ven_1102&cc_0401,pci\ven_1102,pci\cc_040100,pci\cc_0401
#-198 Command line processed: "C:\XPE\system32\mmc.exe" C:\XPE\system32\devmgmt.msc /s
#I063 Selected driver installs from section [Audigy_Device] in "c:\xpe\inf\oem0.inf".
#I320 Class GUID of device remains: {4D36E96C-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.

-Mike

 

[KM]

Hi Mike,

Just first hit from your setupapi.log: wdmaud.sys is missing.
Add "Microsoft WINMM WDM Audio Compatibility Driver" component.
If does not help, update setupapi.log on your website and we can continue looking in to the problem.

Also, regarding the software install and capturing all the reg.entires. You may want to use tools like RegSnap (search Google, or
this NG archive for it. I posted some info about the tool) instead of InCtrl5. RegSnap will save hours of work you would do with
InCtrl5. First of all, it will give you a .reg file that contains all the reg.entries. So you won't need to copy/paste all the
entries manually from the install log as you would do with InCtrl5.

KM

Hi Slobodan,

Can you install drivers manually on running XPe? In not you must fist
add enough components for this to work.
Please delete setuapi.log before attempting to install drivers. and
if you have problems analyze setupapi.log for what is missing or post
it here as attachment.

I'll try that if your last method fails.

Now if you need only drivers. (No extra codec's/services etc) just if
you have enough files in their folders will be enough for FBA PnP to
pick right drivers and to install them. Check this from device
manager.

I copied all the files listed for the driver to System32 and System32\Drivers
as appropriate and any .inf files I found with "Creative" in them. (Is there a
better way to find the .inf files?)

The driver installed but failed to start. On comparing the file list between the
working XPPro and my image I found 4 files missing from the Device Manager
list.

I tried again by finding any .inf file which mentioned the missing files.

This time the file lists match but the driver still fails to start. Here are the
sections of SetupApi.log which I think are relevent.

(The full file is here: www.cairnscarsound.com.au/temp/setupapi.log )

[2004/12/15 14:30:00 412.328 Driver Install]
#-019 Searching for hardware ID(s):
pci\ven_1102&dev_0008&subsys_10011102&rev_00,pci\ven_1102&dev_0008&subsys_10011102,pci\ven_1102&dev_0008&cc_040100,pci\ven_1102&dev_0008&cc_0401
#-018 Searching for compatible ID(s):
pci\ven_1102&dev_0008&rev_00,pci\ven_1102&dev_0008,pci\ven_1102&cc_040100,pci\ven_1102&cc_0401,pci\ven_1102,pci\cc_040100,pci\cc_0401
#-199 Executing "C:\XPE\fba\fba.exe" with command line: ..\fba\fba.exe
#I022 Found "PCI\VEN_1102&DEV_0008&SUBSYS_10011102" in C:\XPE\inf\oem0.inf; Device: "Creative Audigy
Audio Processor (WDM)"; Driver: "Creative Audigy Audio Processor (WDM)"; Provider: "Creative"; Mfg:
"Creative Technology, Ltd."; Section name: "Audigy_Device".
#I023 Actual install section: [Audigy_Device.NT]. Rank: 0x00000001. Effective driver date:
07/01/2004.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [Audigy_Device] in "c:\xpe\inf\oem0.inf".
#I320 Class GUID of device remains: {4D36E96C-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-124 Doing copy-only install of "PCI\VEN_1102&DEV_0008&SUBSYS_10011102&REV_00\4&1F7DBC9F&0&20F0".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [Audigy_Device.NT.Interfaces] from "c:\xpe\inf\oem0.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "PCI\VEN_1102&DEV_0008&SUBSYS_10011102&REV_00\4&1F7DBC9F&0&20F0".
#I163 Device not started: Device has problem: 0x0a: CM_PROB_FAILED_START.
#I121 Device install of "PCI\VEN_1102&DEV_0008&SUBSYS_10011102&REV_00\4&1F7DBC9F&0&20F0" finished
successfully.

[2004/12/15 14:36:03 1112.160 Driver Install]
#-019 Searching for hardware ID(s):
pci\ven_1102&dev_0008&subsys_10011102&rev_00,pci\ven_1102&dev_0008&subsys_10011102,pci\ven_1102&dev_0008&cc_040100,pci\ven_1102&dev_0008&cc_0401
#-018 Searching for compatible ID(s):
pci\ven_1102&dev_0008&rev_00,pci\ven_1102&dev_0008,pci\ven_1102&cc_040100,pci\ven_1102&cc_0401,pci\ven_1102,pci\cc_040100,pci\cc_0401
#-198 Command line processed: "C:\XPE\system32\mmc.exe" C:\XPE\system32\devmgmt.msc /s
#I063 Selected driver installs from section [Audigy_Device] in "c:\xpe\inf\oem0.inf".
#I320 Class GUID of device remains: {4D36E96C-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.

-Mike

 

[KM]

Mike,

Also add these components and resolve dependencies:
audio related:
"Microsoft Kernel Wave Audio Mixer"
"Microsoft Kernel System Audio Device"
"Microsoft Kernel DRM Audio Descrambler"
"Microsoft Kernel DLS Synthesizer"
"Microsoft Kernel GS Wavetable Synthesizer"
"Microsoft Kernel Acoustic Echo Canceller"
"Microsoft Kernel Audio Splitter"
"Microsoft WINMM WDM Audio Compatibility Driver"

other problems seen from your setupapi.log:
"IP Security Tools and User Interface"
"Jet Database DAO Support"
"Soap Client Runtime"
"WMI Core"
"Windows Product Activation WMI Provider"
"Primitive: Ole32"
"Primitive: Oleaut32"
"Primitive: Comcat"
"Microsoft Foundation Class Library (MFC)"
"Accessibility Core"
"Visual Basic 5.0 Runtime Library"
"Time Service Core"

KM

Hi Mike,

Just first hit from your setupapi.log: wdmaud.sys is missing.
Add "Microsoft WINMM WDM Audio Compatibility Driver" component.
If does not help, update setupapi.log on your website and we can continue looking in to the problem.

Also, regarding the software install and capturing all the reg.entires. You may want to use tools like RegSnap (search Google, or
this NG archive for it. I posted some info about the tool) instead of InCtrl5. RegSnap will save hours of work you would do with
InCtrl5. First of all, it will give you a .reg file that contains all the reg.entries. So you won't need to copy/paste all the
entries manually from the install log as you would do with InCtrl5.

KM

Hi Slobodan,

Can you install drivers manually on running XPe? In not you must fist
add enough components for this to work.
Please delete setuapi.log before attempting to install drivers. and
if you have problems analyze setupapi.log for what is missing or post
it here as attachment.

I'll try that if your last method fails.

Now if you need only drivers. (No extra codec's/services etc) just if
you have enough files in their folders will be enough for FBA PnP to
pick right drivers and to install them. Check this from device
manager.

I copied all the files listed for the driver to System32 and System32\Drivers
as appropriate and any .inf files I found with "Creative" in them. (Is there a
better way to find the .inf files?)

The driver installed but failed to start. On comparing the file list between the
working XPPro and my image I found 4 files missing from the Device Manager
list.

I tried again by finding any .inf file which mentioned the missing files.

This time the file lists match but the driver still fails to start. Here are the
sections of SetupApi.log which I think are relevent.

(The full file is here: www.cairnscarsound.com.au/temp/setupapi.log )

[2004/12/15 14:30:00 412.328 Driver Install]
#-019 Searching for hardware ID(s):
pci\ven_1102&dev_0008&subsys_10011102&rev_00,pci\ven_1102&dev_0008&subsys_10011102,pci\ven_1102&dev_0008&cc_040100,pci\ven_1102&dev_0008&cc_0401
#-018 Searching for compatible ID(s):
pci\ven_1102&dev_0008&rev_00,pci\ven_1102&dev_0008,pci\ven_1102&cc_040100,pci\ven_1102&cc_0401,pci\ven_1102,pci\cc_040100,pci\cc_0401
#-199 Executing "C:\XPE\fba\fba.exe" with command line: ..\fba\fba.exe
#I022 Found "PCI\VEN_1102&DEV_0008&SUBSYS_10011102" in C:\XPE\inf\oem0.inf; Device: "Creative Audigy
Audio Processor (WDM)"; Driver: "Creative Audigy Audio Processor (WDM)"; Provider: "Creative"; Mfg:
"Creative Technology, Ltd."; Section name: "Audigy_Device".
#I023 Actual install section: [Audigy_Device.NT]. Rank: 0x00000001. Effective driver date:
07/01/2004.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [Audigy_Device] in "c:\xpe\inf\oem0.inf".
#I320 Class GUID of device remains: {4D36E96C-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-124 Doing copy-only install of "PCI\VEN_1102&DEV_0008&SUBSYS_10011102&REV_00\4&1F7DBC9F&0&20F0".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [Audigy_Device.NT.Interfaces] from "c:\xpe\inf\oem0.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "PCI\VEN_1102&DEV_0008&SUBSYS_10011102&REV_00\4&1F7DBC9F&0&20F0".
#I163 Device not started: Device has problem: 0x0a: CM_PROB_FAILED_START.
#I121 Device install of "PCI\VEN_1102&DEV_0008&SUBSYS_10011102&REV_00\4&1F7DBC9F&0&20F0" finished
successfully.

[2004/12/15 14:36:03 1112.160 Driver Install]
#-019 Searching for hardware ID(s):
pci\ven_1102&dev_0008&subsys_10011102&rev_00,pci\ven_1102&dev_0008&subsys_10011102,pci\ven_1102&dev_0008&cc_040100,pci\ven_1102&dev_0008&cc_0401
#-018 Searching for compatible ID(s):
pci\ven_1102&dev_0008&rev_00,pci\ven_1102&dev_0008,pci\ven_1102&cc_040100,pci\ven_1102&cc_0401,pci\ven_1102,pci\cc_040100,pci\cc_0401
#-198 Command line processed: "C:\XPE\system32\mmc.exe" C:\XPE\system32\devmgmt.msc /s
#I063 Selected driver installs from section [Audigy_Device] in "c:\xpe\inf\oem0.inf".
#I320 Class GUID of device remains: {4D36E96C-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.

-Mike

 

[Slobodan Brcin \(eMVP\)]

Hi Mike,

I copied all the files listed for the driver to System32 and System32\Drivers
as appropriate and any .inf files I found with "Creative" in them. (Is there a
better way to find the .inf files?)

Yes. You can in most cases tell setup to just unpack files or do that with winzip or some similar utility. Then you have all driver
files in their folder.

The driver installed but failed to start. On comparing the file list between the
working XPPro and my image I found 4 files missing from the Device Manager
list.

You should seach trough setupapi.log for SPFILENOTIFY_NEEDMEDIA and make a list of files that are missing.

Like:
intelppm.sys
wdmaud.sys
kmixer.sys
sysaudio.sys
drmkaud.sys
DMusic.sys
swmidi.sys
aec.sys
splitter.sys

These files usually belong to MS. So you should use TD filter option and seacrh for MS components that contain these files and then
add these components. (Do not copy these files manaly). Resolve dependecnies.
And thes second round of FBA in few iteration you should be ok.

I tried again by finding any .inf file which mentioned the missing files.

Do not do that. Only for third-party drivers you need that. For MS drivers look for components that contain them.

Regards,
Slobodan

This time the file lists match but the driver still fails to start. Here are the
sections of SetupApi.log which I think are relevent.

(The full file is here: www.cairnscarsound.com.au/temp/setupapi.log )

[2004/12/15 14:30:00 412.328 Driver Install]
#-019 Searching for hardware ID(s):
pci\ven_1102&dev_0008&subsys_10011102&rev_00,pci\ven_1102&dev_0008&subsys_10011102,pci\ven_1102&dev_0008&cc_040100,pci\ven_1102&dev_
0008&cc_0401
#-018 Searching for compatible ID(s):
pci\ven_1102&dev_0008&rev_00,pci\ven_1102&dev_0008,pci\ven_1102&cc_040100,pci\ven_1102&cc_0401,pci\ven_1102,pci\cc_040100,pci\cc_040
1
#-199 Executing "C:\XPE\fba\fba.exe" with command line: ..\fba\fba.exe
#I022 Found "PCI\VEN_1102&DEV_0008&SUBSYS_10011102" in C:\XPE\inf\oem0.inf; Device: "Creative Audigy
Audio Processor (WDM)"; Driver: "Creative Audigy Audio Processor (WDM)"; Provider: "Creative"; Mfg:
"Creative Technology, Ltd."; Section name: "Audigy_Device".
#I023 Actual install section: [Audigy_Device.NT]. Rank: 0x00000001. Effective driver date:
07/01/2004.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [Audigy_Device] in "c:\xpe\inf\oem0.inf".
#I320 Class GUID of device remains: {4D36E96C-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-124 Doing copy-only install of "PCI\VEN_1102&DEV_0008&SUBSYS_10011102&REV_00\4&1F7DBC9F&0&20F0".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [Audigy_Device.NT.Interfaces] from "c:\xpe\inf\oem0.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "PCI\VEN_1102&DEV_0008&SUBSYS_10011102&REV_00\4&1F7DBC9F&0&20F0".
#I163 Device not started: Device has problem: 0x0a: CM_PROB_FAILED_START.
#I121 Device install of "PCI\VEN_1102&DEV_0008&SUBSYS_10011102&REV_00\4&1F7DBC9F&0&20F0" finished
successfully.

[2004/12/15 14:36:03 1112.160 Driver Install]
#-019 Searching for hardware ID(s):
pci\ven_1102&dev_0008&subsys_10011102&rev_00,pci\ven_1102&dev_0008&subsys_10011102,pci\ven_1102&dev_0008&cc_040100,pci\ven_1102&dev_
0008&cc_0401
#-018 Searching for compatible ID(s):
pci\ven_1102&dev_0008&rev_00,pci\ven_1102&dev_0008,pci\ven_1102&cc_040100,pci\ven_1102&cc_0401,pci\ven_1102,pci\cc_040100,pci\cc_040
1
#-198 Command line processed: "C:\XPE\system32\mmc.exe" C:\XPE\system32\devmgmt.msc /s
#I063 Selected driver installs from section [Audigy_Device] in "c:\xpe\inf\oem0.inf".
#I320 Class GUID of device remains: {4D36E96C-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.

-Mike

 

[Mike Warren]

Hi Konstantin,

Just first hit from your setupapi.log: wdmaud.sys is missing.
Add "Microsoft WINMM WDM Audio Compatibility Driver" component.
If does not help, update setupapi.log on your website and we can
continue looking in to the problem.

Ok, I've updated it. www.cairnscarsound.com.au/temp/setupapi.log

After adding "Microsoft WINMM WDM Audio Compatibility Driver" to
the image I have confirmed that wdmaud.sys is in System32\drivers and
wdmaud.drv is in System32 but the driver still does not start. I can't see
any mention of wdmaud.sys in setupapi.log. Should I?

Also, regarding the software install and capturing all the
reg.entires. You may want to use tools like RegSnap (search Google,
or this NG archive for it. I posted some info about the tool) instead
of InCtrl5. RegSnap will save hours of work you would do with
InCtrl5. First of all, it will give you a .reg file that contains all
the reg.entries. So you won't need to copy/paste all the entries
manually from the install log as you would do with InCtrl5.

Thanks, I'll look into it.

-Mike

 

[Slobodan Brcin \(eMVP\)]

Hi Mike,

Look at Konstantins and my reply. You are a few iterations away from making it work. You need to add more components.

Regards,
Slobodan

 

[Dietmar]

Hi Mike,
I have the same soundcard and have had the same problems.
I build a new image with XPE, where I first added all the drivers for
sound from the Component Database.
After the Image was build and FBA Agent runs complete ready, I installed
the driver without any changes from the .exe file from Creative.
And, all works fine. Now I delete all the sounddrivers from
the database, which I dont need.

P.S. I have XPE with SP2

 

[Mike Warren]

Hi Slobodan,

Look at Konstantins and my reply. You are a few iterations away from
making it work. You need to add more components.

Konstantins note about all the other problems made me realise that I still
had a lot of mess in the image from recent experiments. I went back to
an earlier image and started the procedure of finding missing files again.

Nothing I did would make the driver start and there were no more
SPFILENOTIFY_NEEDMEDIA messages in setupapi.log. The driver
looked ok except it would not start.

I then tried installing from the CD again and it was successful.

Although I am keen to find out what the answer is, I need to continue so
I'll have to let it ride for the moment.

The only thing left for me to do is EWF and a few little bits.

Thankyou both again for the help.

Regards
-Mike

 

[Slobodan Brcin \(eMVP\)]

Hi Mike,

Now you should post us here first setupapi.log that is made during the FBA.
Also use device manager to see if all drivers are installed.

Regards,
Slobodan

 

[Mike Warren]

Hi Slobodan,

Now you should post us here first setupapi.log that is made during
the FBA.

Ok, here it is http://www.cairnscarsound.com.au/temp/setupapi.log

There are still 2 SPFILENOTIFY_NEEDMEDIA messages in setupapi.log
but I don't think they are related to the Audigy problem. The files mentioned
are COM+ help files (comexp.hlp and comexp.chm). The odd thing there is
that COM+ is in my configuration. Not that it matters as I don't want or need
them.

Also use device manager to see if all drivers are installed.

I can't see any differences in the list of files shown in Device Manager
between XP Pro and XPe. The only thing is that in XPe the driver fails
to start.

-Mike

 

[KM]

Mike,

There are still 2 SPFILENOTIFY_NEEDMEDIA messages in setupapi.log
but I don't think they are related to the Audigy problem. The files mentioned
are COM+ help files (comexp.hlp and comexp.chm). The odd thing there is
that COM+ is in my configuration. Not that it matters as I don't want or need
them.

Find "COM+ Services" component in your configuration and on the component Settings page in TD make sure that "Do not copy help files
for this component" checkbox is not set.
Also, clear up the "Do not copy help files for this configuration" checkbox on the Configuration Setting page ("Other Settings"
section).
For some components having help files in the build is vital.

A little bit unrelated but also add "Null Device driver" component to your build.

Regarding the Audio driver.. It was not started (CM_PROB_FAILED_START) but it is hard to tell why (not reason mentioned). That could
still be a missing dependency issue. Have you verified with DependencyWalker that audio driver binaries have all their dependencies
in your image?
(btw, did you increase the setupapi.log error logging level?)

Regards,
Konstantin

 

[Slobodan Brcin \(eMVP\)]

Hi Mike,

You will need this in order to increase logging level.
http://msdn.microsoft.com/library/d..._66a07114-953e-49aa-bebf-f9b4ca60a6dd.xml.asp

This will be huge file so you either zip it ir extract the part with info about failed audigy driver.

Missing help files should not cause the error that you see, but it can't hurt for test to include them as well.

Regards,
Slobodan

 

[Mike Warren]

Hi Konstantin,

Find "COM+ Services" component in your configuration and on the
component Settings page in TD make sure that "Do not copy help files
for this component" checkbox is not set. Also, clear up the "Do not copy help files for this
configuration"
checkbox on the Configuration Setting page ("Other Settings" section).
For some components having help files in the build is vital.
Done.

A little bit unrelated but also add "Null Device driver" component to
your build.

Ok, I've added that.

Regarding the Audio driver.. It was not started
(CM_PROB_FAILED_START) but it is hard to tell why (not reason
mentioned). That could still be a missing dependency issue. Have you
verified with DependencyWalker that audio driver binaries have all
their dependencies in your image?

I ran Dependency Walker on all 16 Audigy driver binaries from my dev
machine and without getting too deep into the tree, everything seems to be
in my image. (It takes about 3 minutes to apply a filter in TD.) I then had the
bright idea of running it on the target, thinking it would highlight any prblems
for me. I must be missing a dependency for Dependency Walker because
when I try to load any file Dependency Walker throws an error message
"Unable to Create Empty"

(btw, did you increase the setupapi.log error logging level?)

I have now set it to 0xFF. This doesn't seem to have made any difference to the
file size. I checked the target registry off line and found the registry key
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\LogLevel=255.

Here is the only section in setupapi.log that mentions the Audigy.
(Full version: http://www.cairnscarsound.com.au/temp/setupapi.log )

[2004/12/16 22:05:13 404.325 Driver Install]
#-019 Searching for hardware ID(s):
pci\ven_1102&dev_0008&subsys_10011102&rev_00,pci\ven_1102&dev_0008&subsys_10011102,pci\ven_1102&dev_0008&cc_040100,pci\ven_1102&dev_0008&cc_0401
#-018 Searching for compatible ID(s):
pci\ven_1102&dev_0008&rev_00,pci\ven_1102&dev_0008,pci\ven_1102&cc_040100,pci\ven_1102&cc_0401,pci\ven_1102,pci\cc_040100,pci\cc_0401
#-199 Executing "C:\XPE\fba\fba.exe" with command line: ..\fba\fba.exe
#I022 Found "PCI\VEN_1102&DEV_0008&SUBSYS_10011102" in C:\XPE\inf\oem0.inf; Device: "Creative Audigy
Audio Processor (WDM)"; Driver: "Creative Audigy Audio Processor (WDM)"; Provider: "Creative"; Mfg:
"Creative Technology, Ltd."; Section name: "Audigy_Device".
#I023 Actual install section: [Audigy_Device.NT]. Rank: 0x00000001. Effective driver date:
07/01/2004.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [Audigy_Device] in "c:\xpe\inf\oem0.inf".
#I320 Class GUID of device remains: {4D36E96C-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-124 Doing copy-only install of "PCI\VEN_1102&DEV_0008&SUBSYS_10011102&REV_00\4&1F7DBC9F&0&20F0".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [Audigy_Device.NT.Interfaces] from "c:\xpe\inf\oem0.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "PCI\VEN_1102&DEV_0008&SUBSYS_10011102&REV_00\4&1F7DBC9F&0&20F0".
#I163 Device not started: Device has problem: 0x0a: CM_PROB_FAILED_START.
#I121 Device install of "PCI\VEN_1102&DEV_0008&SUBSYS_10011102&REV_00\4&1F7DBC9F&0&20F0" finished
successfully.

 

[Slobodan Brcin \(eMVP\)]

(btw, did you increase the setupapi.log error logging level?)

I have now set it to 0xFF. This doesn't seem to have made any difference to the
file size. I checked the target registry off line and found the registry key
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\LogLevel=255.

Have you done this in pre FBA image registry?

Regards,
Slobodan

 

[Mike Warren]

Slobodan,

Have you done this in pre FBA image registry?

I put it in the "Extra Registry Data" section of the SLX file.
Is this where I should put it?

-Mike

 

[Slobodan Brcin \(eMVP\)]

Hi Mike,

Yes that should be ok. Although I do not see what could be a reason for a problem :-(

Regards,
Slobodan

BTW why is your inf file name oem0.inf. Where did you find this file? I guess in XPP windows\inf folder right?
This is not a problem. But I'm interested why you did not extract it from setup.exe?

 

[KM]

Mike,

I ran Dependency Walker on all 16 Audigy driver binaries from my dev
machine and without getting too deep into the tree, everything seems to be
in my image. (It takes about 3 minutes to apply a filter in TD.)

Off the topic but just to save you some dev time.

Install more RAM on your dev machine (the one that runs SQL Server with XPe DB). Server will cahche most par tof the DB and on every
sequential Filter apply it will take less and less time.

Also, on the www.xpefiles.com you will find XpeTools package (Development Utilities/Main folder). If you use DependecyExplorer
component from there, it has a filtering feature that will take seconds from you to serach in XPe DB for components that hold
particular: files, registry keys, registry entries.

KM

 

[KM]

Slobodan,

BTW why is your inf file name oem0.inf. Where did you find this file? I guess in XPP windows\inf folder right?
This is not a problem. But I'm interested why you did not extract it from setup.exe?

I am going to guess here (have had similar experience) but Mike may have been trying to capture the driver (files, etc.) off a
wonking image or XP Pro machine. If the image was prepeared by OEM/ODM, they often use oem?.inf names for INF files.

KM