Re: Creative Audigy 2 Value

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: KM (konstmor_at_nospam_yahoo.com)
Date: 12/15/04 

Date: Tue, 14 Dec 2004 21:54:00 -0800

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
>
>
>

Relevant Pages

  • Re: XP HOME BOOT FAILURE
    ... you remove the driver for the graphics card, ... >> If you run a repair install as I initially described, ... A repair install should bypass that but it will ... >>>> on, follow the screens. ...
    (microsoft.public.windowsxp.accessibility)
  • Problems with Touchpad,keyboard and USB after Ideacom update (solu
    ... and keyboard .I have made fresh install of XP Home and have all updated ... recomended update from Driver detective,that i use offten. ... allready and when i do this it knocks off my USB mouse leaving me not able to ... 2.Mutil-Access driver HCT driver verify crash fix! ...
    (microsoft.public.windowsxp.general)
  • Re: XP update loses sound card
    ... I assume you tried a forced install of a soundcard? ... should try the sound card driver from Toshiba ... The WINMM WDM Audio driver is out of the list now. ... The sound is enabled and uninstalling the Microsoft WINMM WDM Audio ...
    (microsoft.public.windowsupdate)
  • OT: What do you do with your old computers?
    ... connected that to the WLAN as well, using a small USB wireless link. ... And what about backups for petesp4 and Bigblack? ... Once it was talking to the network, I decided to install the printer and the ... driver, and was marked as an unknown device. ...
    (comp.lang.cobol)
  • Re: Dude !! Never Buy a Dell !!!
    ... Sounds like when you "converted" from Home to Server, you didn't install the ... go to Dell site, download the Driver, and then when installing the Driver, ... it complains, that the CD drive is missing, Darn, thing.. ...
    (microsoft.public.windows.server.general)