It's supported by the driver in S\D\CR\4. The only way to find the cause now is through the setupapi.log file. Please post the relevant part or upload the file so I can select the relevant part.

It isn't fixed. The download link was fixed in that submitted news item wink

This is the relevant part from your setupapi.log:

[2006/08/23 21:23:30 944.1210 Driver Install]
#-019 Searching for hardware ID(s): pci\ven_1102&dev_0004&subsys_20021102&rev_04,pci\ven_1102&dev_0004&subsys_20021102,pci\ven_1102&dev_0004&cc_040100,pci\ven_1102&dev_0004&cc_0401
#-018 Searching for compatible ID(s): pci\ven_1102&dev_0004&rev_04,pci\ven_1102&dev_0004,pci\ven_1102&cc_040100,pci\ven_1102&cc_0401,pci\ven_1102,pci\cc_040100,pci\cc_0401
#-198 Command line processed: "C:\WINDOWS\system32\setup.exe"  -newsetup
#I022 Found "PCI\VEN_1102&DEV_0004&SUBSYS_20021102" in C:\D\S\CR\1\wdma_emu.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.NTx86]. Rank: 0x00000001. Effective driver date: 10/29/2005.
#I022 Found "PCI\VEN_1102&DEV_0004&SUBSYS_20021102" in C:\D\S\CR\2\wdma_emu.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.NTx86]. Rank: 0x00000001. Effective driver date: 12/08/2005.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [Audigy_Device] in "c:\d\s\cr\2\wdma_emu.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_0004&SUBSYS_20021102&REV_04\4&2E98101C&0&50F0".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [Audigy_Device.NTx86.Interfaces] from "c:\d\s\cr\2\wdma_emu.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "PCI\VEN_1102&DEV_0004&SUBSYS_20021102&REV_04\4&2E98101C&0&50F0".
#I121 Device install of "PCI\VEN_1102&DEV_0004&SUBSYS_20021102&REV_04\4&2E98101C&0&50F0" finished successfully.
[2006/08/23 21:23:54 944.1227 Driver Install]

This means the correct driver got installed, which means something is wrong with this exception in the DPsFnshr.ini. And I've found it now: it lists 'ha10x2k.sys' as a tagfile, while it should have been 'ha10kx2k.sys'. A VERY small typo! You can change it yourself and it'll work, but it will of course be fixed in the next update of the DriverPack Sound B!

Odd!

That's just a very old Realtek AC'97 driver. I'll create a separate .inf file with this HWID listed. That should solve the problem.

From google:

PCI\VEN_14F1&DEV_8800: MSI 8606 Video Capture

What motherboard were you using again?

And neither one is already installed? I mean: none of the drivers are actually installed, but both show up when you scan for driver updates?

Ravennt wrote:

Can it is meaningful Control Center and Control Panel to unite in separate archive???

Nope. But if you want to, you can easily disable the installation of the CCP/CCC by modifying the DPsFnshr.ini wink

1,133

(58 replies, posted in 3rd Party DriverPacks)

It doesn't matter that 'P' was already used by somebody else...

But it would definitely be better if you would create a 'Printer DriverPack' and not a 'Canon Printers DriverPack'. wink Just put them all together. But as I said, you obviously can do it the way you've presented it!

1,134

(5 replies, posted in DriverPack Sound)

@Nakkoush: I've tried to find the drivers for that laptop but I cannot access them without a product code. Could you please download them and then send them to me? Thanks!

@muiz: your driver request was added in the recently updated DriverPack Sound B 6.08! wink

Floppy wrote:

I don't want you to change it....just telle me where the txt is , I can do the "job" myself wink

The text is hardcoded wink I may add this as an option in the future... but not just yet.

Does anyone else have this problem?

See your other topic. It's the same problem.

Topic closed.

Won't be applied. It's good as it is now. And just for your information: there are also motherboards with onboard Creative APU's wink.

Floppy wrote:
Bâshrat the Sneaky wrote:

No picture is used. It's all text wink. What would you like to change precisely?

Just want to give it a norwegian "look" to it!!

Eh? You want to translate 'DriverPacks Finisher'? Sorry, that won't happen any time soon wink

Please post your DPsFnshr.log!

Please post your DPsFnshr.log!

No picture is used. It's all text wink. What would you like to change precisely?

1,143

(6 replies, posted in DriverPack WLAN)

Changelog
new
- another Broadcom Dell driver
- Ralink RT2004 driver (was already supported by other drivers, but this is the official driver)
- U.S. Robotics USR(80)5422 & USR(80)5423 driver

updated
- AVM FRITZ! WLAN USB Stick driver from 04/06/2006,2.0.4.1482 to 04/06/2006,2.0.4.1482 (the included (and necessary) utility was updated, not the driver)
- Broadcom WLAN driver from 12/17/2005, 4.10.40.1 to 06/25/2006, 4.80.28.7
- Intel 2200BG; 2915ABG, 3945ABG driver from 04/04/2006,10.1.1.3 [10.1.1.3] to 07/26/2006,10.5.1.59 [10.1.5.59]
- Ralink RT7xx (RT71 & RT2500USB) driver from 08/13/2004, 1.02.01.0000 to 06/08/2006, 1.01.01.0000 & 10/17/2005, 2.01.00.0000
- Ralink RT6xx (RT61 & RT2500) driver from 01/19/2006, 1.00.04.0000 & 10/20/2005, 3.01.00.0000 to 05/04/2006, 1.01.01.0000 & 06/01/2006, 3.02.00.0000
- Realtek 8185 driver from 08/29/2005,5.103.0829.2005 to 04/13/2006,5.1060.0413.2006
- Realtek 8187L driver from 03/24/2005,5.111.03.0324 to 04/12/2006,5.1221.0412.2006

Known issues
-A certain revision of the D-Link DWL-120+ device is not installed
-The Belkin F5D7011 is instaled as a Dell device: the wrong driver is used

Remarks
-none

Download

Already downloaded smile wink

The driver you linked to is the exact same driver as the one that's already included in D\W\B\6! Also your full HWID is supported by this driver:

    %BCM430G_DeviceDesc% = BCM43XG, PCI\VEN_14E4&DEV_4318&SUBSYS_70111799  ;4318E CardBus

May I ask you which Dell  driver it is using? Since the one in D\W\BR\D does not support your device. Perhaps there's another Broadcom Dell driver, but then I wonder where it's located.

Note that in the new version there's also a universal Broadcom  driver included, which will probably be chosen instead of the Dell driver. That might solve your problem. Please report back after you've used DriverPack WLAN 6.08! (Which will be released within an hour or so from now.)

5418 is supported by the 5417 driver, I've updated the list of supported devices to show this.

5421A is supported by the driver in D\W\U\8. If the driver did not get installed then please post the DPsFnshr.log.

5422/4523 (same driver) is added in the next version. I'll leave this topic open to fix your problem with the 5421A device.

1,147

(19 replies, posted in Other)

fargo wrote:

@Bâshrat the Sneaky:
Will your updated guide install only signed drivers? Or it was only to get rid of Driver Signing Policy popup?

Thank you.

It was only to get rid of the Driver Signing Policy popups!

Perhaps the CCP doesn't support the X1800? Could somebody verify that?

If you want to be sure it works, use the CCC. The CCP is no longer officially supported by ATI so I can't guarantee that the CCP will work...

1,149

(9 replies, posted in Software)

jtdoom wrote:

<Mr Watson frantically looking for Holmes> 8-)

LOL big_smile tongue

Well Ben, I did not support in the past because some parts of the slipstreaming process are slightly different. And handling all of that through batch files is a true PITA. That's why I said "Windows 2000 is not officially supported. The End.".
But the truth is that at least 95% of the included drivers also works for Windows 2000. So it'd be dumb to not support it. The downside is that occasionally these flaws reach the surface. "Occasionally", because few people actually use Windows 2000. If there were more, this error would have been reported months ago.
But the problem is obviously fixable. It'll be fixed in the next update of DriverPack Chipset!

And yes, you can just include the Windows 2000 driver for the SIS AGP controller and it'll work fine! wink