Both the ASUS ATK Drivers are in the Chipset DP:
DriverVer=08/23/2007, 1043.2.15.101 (ATK0100)
DriverVer=08/13/2004, 1043.2.15.37 (ATK0110)
ATK100 from Chipset DP works fine, been using it on my old ASUS notebook.
1 2010-07-26 08:23:17
Re: [REQ] Lenovo ACPI - Lenovo Energy Management Driver "ACPI\vpc2004" (14 replies, posted in 3rd Party DriverPacks)
2 2010-06-04 09:40:11
Re: [REL] DP_Bluetooth_wnt5_x86-32_1005b1 (103 replies, posted in 3rd Party DriverPacks)
compstuff wrote:
Thanks for the info but how can I tell about the license? I changed the date on the system to 2011 and it is using the Toshiba BT71012 driver but the Bluetooth seems to still work and no license alerts...
I haven't been doing builds for a long time (changed jobs), and cant remember how the 30day trial works, but on Toshiba download site, they have a disclaimer:
Please note that this TOSHIBA Bluetooth stack is for TOSHIBA
notebooks only!
It will expire on all other Bluetooth hardware after 30 days!3 2010-06-03 19:39:52
Re: [REL] DP_Bluetooth_wnt5_x86-32_1005b1 (103 replies, posted in 3rd Party DriverPacks)
The Toshiba BlueTooth Stack is the same for all hardware, but they have added a licence file which is set per manufacture. Therefore the BT71012 will work on Dell, but will only have a 30Day license.
The original BT61010 I created did not have the hardware license, and was the last version Toshiba released before they locked it down.
Broadcom (WIDCOMM) do the same, so the one in BT driverpack is licensed to IBM machines only, and does not have a trial period.
Hope this helps.
4 2009-09-05 17:27:04
Re: Textmode driver causes bootscreen on Gateway M-285E (tablet notebook) (17 replies, posted in DriverPack Mass Storage)
Slipstreaming the textmode MassStorage only covers the TEXTMODE part, you also need to leave the OEM folder with MassStorage Drivers so the WINDOWS drivers get installed.
Don't remove the OEM folder and all should work fine.
5 2009-06-12 17:09:16
Re: [BUG] possibly with finisher or bluetooth pack WIDCOMM (1 replies, posted in Feedback and Support - DriverPacks Base)
The WIDCOMM bluetooth software in the Bluetooth DriverPack is licensed for IBM machines. Its possible that the licensing is causing the message if its being installed on a non IBM machine.
What hardware are you using, and are the Bluetooth Drivers working once installed?
6 2009-05-15 10:53:44
Re: Wait for network connection in batch file. (6 replies, posted in Universal Imaging)
PING 127.0.0.1 works without an active network 
7 2009-05-12 18:27:55
Re: [SLVD] DriverPack MassStorage 9.01 - ESX VMWare - LSI Adapter, Ultra320 SCSI 2000 series (31 replies, posted in DriverPack Mass Storage)
Hi Guys,
Its been a while since working with ESX, about a year ago I had a similar problem. We were using ESX 3.0 at the time. I no longer work at that company anymore so dont have access to ESX for any testing, but this is what I remember.
Firstly as ESX is a server tool, the Preference is to use SCSI over IDE (at least in our Environment).
I found that the MassStorage Drivers for VM Workstation were in DriverPacks, and were newer than what ESX required, the newer Drivers caused ESX to BSOD. I replaced the 3 VMSCSI files in DriverPacks with the ones from ESX and this fixed the BSOD.
Check the following for the VMSCSI Drivers:
* What version of VMSCSI Driver does Workstation / Server / ESX use
* Are they compatiable
You could try using the older version (from ESX) in DriverPacks and have VMTools upgrade them when its installed. This would allow all VMWare products to work with DriverPacks.
Hope this is helpful
Cheers
7yler
8 2009-01-12 12:53:27
Re: Mult-Boot CD (17 replies, posted in Installation Platforms)
Hi Deadbug,
Multiboot can be very frustrating to setup, make sure you read through the threads over at MSFN.
http://www.msfn.org/board/index.php?showforum=82
flyakite’s guide is good, but it very old now. MSFN forums have more up to date guides. Try this guide:
http://www.msfn.org/board/index.php?showtopic=74862
Drivepacks need to be integrated into your full i386 source, and wont work on the PRAR folder. The PRAR folder needs to be created from you i386 (after Driverpack intergration).
To create the PRAR folder, check out this thread:
http://www.msfn.org/board/index.php?showtopic=58446
Good luck 
9 2008-11-02 15:21:01
Topic: MultiBoot Problem (4 replies, posted in Other)
I've got this strange problem when builting ONE machine using a Multiboot build DVD, It changes the default source location.
It should be <DVD>:\SETUP\XP\Pro3\i386 but at T-39 it starts look for <DVD>:\i386.
I have used the Multiboot build DVD on many machines (VM and physical) without problems, but on the Gigabyle GA-X38-DS5 motherboard this painful problem occurs.
I was wondering if its possible that a Driver could be the cause of the problem?
I will test a few things to look for the root cause, but as this is my main rig, I dont like rebuilding it to often.
As a workaround to get the machine built, I copied <DVD>:\SETUP\XP\Pro3\i386 to <DVD>:\i386.
Any thoughts are welcome
Cheers
7yler
Note to myself: Dont build uber machines configured to the hilt, because they cause nothing but pain ... But when working, how NICE 
===========
PCI Devices
===========
PCI\VEN_104C&DEV_8024&SUBSYS_10001458&REV_00\4&1ADD88A5&0&30F0: Texas Instruments OHCI Compliant IEEE 1394 Host Controller
PCI\VEN_10DE&DEV_0400&SUBSYS_34481458&REV_A1\4&17D528C6&0&0008: NVIDIA GeForce 8600 GTS
PCI\VEN_10EC&DEV_8168&SUBSYS_E0001458&REV_01\4&CF4E44&0&00E5: Realtek RTL8168/8111 PCI-E Gigabit Ethernet NIC
PCI\VEN_1102&DEV_0005&SUBSYS_00211102&REV_00\4&1ADD88A5&0&00F0: Creative SB X-Fi
PCI\VEN_197B&DEV_2363&SUBSYS_B0001458&REV_02\4&24C54F4F&0&00E3: GIGABYTE GBB36X Controller
PCI\VEN_197B&DEV_2363&SUBSYS_B0001458&REV_02\4&24C54F4F&0&01E3: JMB36X Standard Dual Channel PCIE IDE Controller
PCI\VEN_8086&DEV_244E&SUBSYS_00000000&REV_92\3&13C0B0C5&0&F0: Intel(R) 82801 PCI Bridge - 244E
PCI\VEN_8086&DEV_2822&SUBSYS_B0001458&REV_02\3&13C0B0C5&0&FA: Intel(R) ICH8R/ICH9R/ICH10R/DO SATA RAID Controller
PCI\VEN_8086&DEV_2916&SUBSYS_00000000&REV_02\3&13C0B0C5&0&F8: Intel(R) ICH9R LPC Interface Controller - 2916
PCI\VEN_8086&DEV_2930&SUBSYS_50011458&REV_02\3&13C0B0C5&0&FB: Intel(R) ICH9 Family SMBus Controller - 2930
PCI\VEN_8086&DEV_2934&SUBSYS_50041458&REV_02\3&13C0B0C5&0&E8: Intel(R) ICH9 Family USB Universal Host Controller - 2934
PCI\VEN_8086&DEV_2935&SUBSYS_50041458&REV_02\3&13C0B0C5&0&E9: Intel(R) ICH9 Family USB Universal Host Controller - 2935
PCI\VEN_8086&DEV_2936&SUBSYS_50041458&REV_02\3&13C0B0C5&0&EA: Intel(R) ICH9 Family USB Universal Host Controller - 2936
PCI\VEN_8086&DEV_2937&SUBSYS_50041458&REV_02\3&13C0B0C5&0&D0: Intel(R) ICH9 Family USB Universal Host Controller - 2937
PCI\VEN_8086&DEV_2938&SUBSYS_50041458&REV_02\3&13C0B0C5&0&D1: Intel(R) ICH9 Family USB Universal Host Controller - 2938
PCI\VEN_8086&DEV_2939&SUBSYS_50041458&REV_02\3&13C0B0C5&0&D2: Intel(R) ICH9 Family USB Universal Host Controller - 2939
PCI\VEN_8086&DEV_293A&SUBSYS_50061458&REV_02\3&13C0B0C5&0&EF: Intel(R) ICH9 Family USB2 Enhanced Host Controller - 293A
PCI\VEN_8086&DEV_293C&SUBSYS_50061458&REV_02\3&13C0B0C5&0&D7: Intel(R) ICH9 Family USB2 Enhanced Host Controller - 293C
PCI\VEN_8086&DEV_2940&SUBSYS_00000000&REV_02\3&13C0B0C5&0&E0: Intel(R) ICH9 Family PCI Express Root Port 1 - 2940
PCI\VEN_8086&DEV_2946&SUBSYS_00000000&REV_02\3&13C0B0C5&0&E3: Intel(R) ICH9 Family PCI Express Root Port 4 - 2946
PCI\VEN_8086&DEV_294A&SUBSYS_00000000&REV_02\3&13C0B0C5&0&E5: Intel(R) ICH9 Family PCI Express Root Port 6 - 294A
PCI\VEN_8086&DEV_29E0&SUBSYS_00000000&REV_01\3&13C0B0C5&0&00: Intel(R) X38/X48 Express Chipset Processor to I/O Controller - 29E0
PCI\VEN_8086&DEV_29E1&SUBSYS_00000000&REV_01\3&13C0B0C5&0&08: Intel(R) X38/X48 Express Chipset PCI Express Root Port - 29E1
PCI\VEN_8086&DEV_29E9&SUBSYS_00000000&REV_01\3&13C0B0C5&0&30: Intel(R) X38/X48 Express Chipset PCI Express Root Port - 29E9
24 matching device(s) found.
===========
USB Devices
===========
USB\ROOT_HUB\4&26397AB7&0 : USB Root Hub
USB\ROOT_HUB\4&2D364FD6&0 : USB Root Hub
USB\ROOT_HUB\4&30B58B36&0 : USB Root Hub
USB\ROOT_HUB\4&70ACE42&0 : USB Root Hub
USB\ROOT_HUB\4&99F0121&0 : USB Root Hub
USB\ROOT_HUB\4&BD04752&0 : USB Root Hub
USB\ROOT_HUB20\4&269B1DF4&0 : USB Root Hub
USB\ROOT_HUB20\4&88AB043&0 : USB Root Hub
USB\VID_0424&PID_2504\5&278A3C80&0&6 : Generic USB Hub
USB\VID_0451&PID_2036\6&14172609&0&1 : Generic USB Hub
USB\VID_046D&PID_C704\1BF02C : USB Composite Device
USB\VID_046D&PID_C704&MI_00\8&2D9D7C94&0&0000 : USB Human Interface Device
USB\VID_046D&PID_C704&MI_01\8&2D9D7C94&0&0001 : USB Human Interface Device
USB\VID_051D&PID_0002\AB0345141875 : American Power Conversion USB UPS
14 matching device(s) found.
=============
Input Devices
=============
HID\VID_046D&PID_C704&MI_00\9&2D2EB9DB&0&0000 : HID Keyboard Device
HID\VID_046D&PID_C704&MI_01&COL01\9&9577C19&0&0000 : HID-compliant mouse
HID\VID_046D&PID_C704&MI_01&COL02\9&9577C19&0&0001 : HID-compliant consumer control device
HID\VID_046D&PID_C704&MI_01&COL03\9&9577C19&0&0002 : HID-compliant device
HID\VID_046D&PID_C704&MI_01&COL04\9&9577C19&0&0003 : HID-compliant device
HID\VID_046D&PID_C704&MI_01&COL05\9&9577C19&0&0004 : HID-compliant device
HID\VID_051D&PID_0002\6&EFA6D90&0&0000 : HID UPS Battery
7 matching device(s) found.
============
ACPI Devices
============
ACPI\FIXEDBUTTON\2&DABA3FF&0 : ACPI Fixed Feature Button
ACPI\GENUINEINTEL_-_X86_FAMILY_6_MODEL_23\_0 : Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz
ACPI\GENUINEINTEL_-_X86_FAMILY_6_MODEL_23\_1 : Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz
ACPI\GENUINEINTEL_-_X86_FAMILY_6_MODEL_23\_2 : Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz
ACPI\GENUINEINTEL_-_X86_FAMILY_6_MODEL_23\_3 : Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz
ACPI\INT0800\2&DABA3FF&0 : Intel(R) 82802 Firmware Hub Device
ACPI\PNP0000\4&1E850C4&0 : Programmable interrupt controller
ACPI\PNP0100\4&1E850C4&0 : System timer
ACPI\PNP0103\4&1E850C4&0 : High Precision Event Timer
ACPI\PNP0200\4&1E850C4&0 : Direct memory access controller
ACPI\PNP0501\1 : Communications Port (COM1)
ACPI\PNP0700\4&1E850C4&0 : Standard floppy disk controller
ACPI\PNP0800\4&1E850C4&0 : System speaker
ACPI\PNP0A03\1 : PCI bus
ACPI\PNP0A06\3&473F1A46&0 : Extended IO Bus
ACPI\PNP0B00\4&1E850C4&0 : System CMOS/real time clock
ACPI\PNP0C01\2&DABA3FF&0 : System board
ACPI\PNP0C02\1 : Motherboard resources
ACPI\PNP0C02\2 : Motherboard resources
ACPI\PNP0C02\4 : Motherboard resources
ACPI\PNP0C04\4&1E850C4&0 : Numeric data processor
ACPI\PNP0C0C\2&DABA3FF&0 : ACPI Power Button
ACPI_HAL\PNP0C08\0 : Microsoft ACPI-Compliant System
ROOT\ACPI_HAL\0000 : ACPI Multiprocessor PC
ROOT\ARPC_CLASS\0000 : MS ArACPI Driver
25 matching device(s) found.10 2008-11-02 14:47:01
Topic: [BUG] JMicron shows twice in Device Manager with yellow (5 replies, posted in DriverPack Mass Storage)
I just rebuilt my main machine that has a Gigabyte GA-X38-DS5 motherboard, and the JRAID drivers did not install correctly.
DriverPack - DP_MassStorage_wnt5_x86-32_810H.7z
JRAID 1.17.42.08 installs, but shows twice in Device Manager with yellow(!). The only way to fix was to install JRAID 1.17.39.7 from Gigabyte.
http://www.gigabyte.com.tw/Support/Moth … ileID=2733
Same problem happen with older DriverPack when I rebuilt machine a few months ago. (most likely DP 8.05).
I remember reading the same problem here somewhere, think it was from Jaak. Sorry, I cant find the post.
I dont think its a version problem, Maybe Gigabyte mods the default JRAID drivers.
===========
PCI Devices
===========
PCI\VEN_104C&DEV_8024&SUBSYS_10001458&REV_00\4&1ADD88A5&0&30F0: Texas Instruments OHCI Compliant IEEE 1394 Host Controller
PCI\VEN_10DE&DEV_0400&SUBSYS_34481458&REV_A1\4&17D528C6&0&0008: NVIDIA GeForce 8600 GTS
PCI\VEN_10EC&DEV_8168&SUBSYS_E0001458&REV_01\4&CF4E44&0&00E5: Realtek RTL8168/8111 PCI-E Gigabit Ethernet NIC
PCI\VEN_1102&DEV_0005&SUBSYS_00211102&REV_00\4&1ADD88A5&0&00F0: Creative SB X-Fi
PCI\VEN_197B&DEV_2363&SUBSYS_B0001458&REV_02\4&24C54F4F&0&00E3: GIGABYTE GBB36X Controller
PCI\VEN_197B&DEV_2363&SUBSYS_B0001458&REV_02\4&24C54F4F&0&01E3: JMB36X Standard Dual Channel PCIE IDE Controller
PCI\VEN_8086&DEV_244E&SUBSYS_00000000&REV_92\3&13C0B0C5&0&F0: Intel(R) 82801 PCI Bridge - 244E
PCI\VEN_8086&DEV_2822&SUBSYS_B0001458&REV_02\3&13C0B0C5&0&FA: Intel(R) ICH8R/ICH9R/ICH10R/DO SATA RAID Controller
PCI\VEN_8086&DEV_2916&SUBSYS_00000000&REV_02\3&13C0B0C5&0&F8: Intel(R) ICH9R LPC Interface Controller - 2916
PCI\VEN_8086&DEV_2930&SUBSYS_50011458&REV_02\3&13C0B0C5&0&FB: Intel(R) ICH9 Family SMBus Controller - 2930
PCI\VEN_8086&DEV_2934&SUBSYS_50041458&REV_02\3&13C0B0C5&0&E8: Intel(R) ICH9 Family USB Universal Host Controller - 2934
PCI\VEN_8086&DEV_2935&SUBSYS_50041458&REV_02\3&13C0B0C5&0&E9: Intel(R) ICH9 Family USB Universal Host Controller - 2935
PCI\VEN_8086&DEV_2936&SUBSYS_50041458&REV_02\3&13C0B0C5&0&EA: Intel(R) ICH9 Family USB Universal Host Controller - 2936
PCI\VEN_8086&DEV_2937&SUBSYS_50041458&REV_02\3&13C0B0C5&0&D0: Intel(R) ICH9 Family USB Universal Host Controller - 2937
PCI\VEN_8086&DEV_2938&SUBSYS_50041458&REV_02\3&13C0B0C5&0&D1: Intel(R) ICH9 Family USB Universal Host Controller - 2938
PCI\VEN_8086&DEV_2939&SUBSYS_50041458&REV_02\3&13C0B0C5&0&D2: Intel(R) ICH9 Family USB Universal Host Controller - 2939
PCI\VEN_8086&DEV_293A&SUBSYS_50061458&REV_02\3&13C0B0C5&0&EF: Intel(R) ICH9 Family USB2 Enhanced Host Controller - 293A
PCI\VEN_8086&DEV_293C&SUBSYS_50061458&REV_02\3&13C0B0C5&0&D7: Intel(R) ICH9 Family USB2 Enhanced Host Controller - 293C
PCI\VEN_8086&DEV_2940&SUBSYS_00000000&REV_02\3&13C0B0C5&0&E0: Intel(R) ICH9 Family PCI Express Root Port 1 - 2940
PCI\VEN_8086&DEV_2946&SUBSYS_00000000&REV_02\3&13C0B0C5&0&E3: Intel(R) ICH9 Family PCI Express Root Port 4 - 2946
PCI\VEN_8086&DEV_294A&SUBSYS_00000000&REV_02\3&13C0B0C5&0&E5: Intel(R) ICH9 Family PCI Express Root Port 6 - 294A
PCI\VEN_8086&DEV_29E0&SUBSYS_00000000&REV_01\3&13C0B0C5&0&00: Intel(R) X38/X48 Express Chipset Processor to I/O Controller - 29E0
PCI\VEN_8086&DEV_29E1&SUBSYS_00000000&REV_01\3&13C0B0C5&0&08: Intel(R) X38/X48 Express Chipset PCI Express Root Port - 29E1
PCI\VEN_8086&DEV_29E9&SUBSYS_00000000&REV_01\3&13C0B0C5&0&30: Intel(R) X38/X48 Express Chipset PCI Express Root Port - 29E9
24 matching device(s) found.
===========
USB Devices
===========
USB\ROOT_HUB\4&26397AB7&0 : USB Root Hub
USB\ROOT_HUB\4&2D364FD6&0 : USB Root Hub
USB\ROOT_HUB\4&30B58B36&0 : USB Root Hub
USB\ROOT_HUB\4&70ACE42&0 : USB Root Hub
USB\ROOT_HUB\4&99F0121&0 : USB Root Hub
USB\ROOT_HUB\4&BD04752&0 : USB Root Hub
USB\ROOT_HUB20\4&269B1DF4&0 : USB Root Hub
USB\ROOT_HUB20\4&88AB043&0 : USB Root Hub
USB\VID_0424&PID_2504\5&278A3C80&0&6 : Generic USB Hub
USB\VID_0451&PID_2036\6&14172609&0&1 : Generic USB Hub
USB\VID_046D&PID_C704\1BF02C : USB Composite Device
USB\VID_046D&PID_C704&MI_00\8&2D9D7C94&0&0000 : USB Human Interface Device
USB\VID_046D&PID_C704&MI_01\8&2D9D7C94&0&0001 : USB Human Interface Device
USB\VID_051D&PID_0002\AB0345141875 : American Power Conversion USB UPS
14 matching device(s) found.
=============
Input Devices
=============
HID\VID_046D&PID_C704&MI_00\9&2D2EB9DB&0&0000 : HID Keyboard Device
HID\VID_046D&PID_C704&MI_01&COL01\9&9577C19&0&0000 : HID-compliant mouse
HID\VID_046D&PID_C704&MI_01&COL02\9&9577C19&0&0001 : HID-compliant consumer control device
HID\VID_046D&PID_C704&MI_01&COL03\9&9577C19&0&0002 : HID-compliant device
HID\VID_046D&PID_C704&MI_01&COL04\9&9577C19&0&0003 : HID-compliant device
HID\VID_046D&PID_C704&MI_01&COL05\9&9577C19&0&0004 : HID-compliant device
HID\VID_051D&PID_0002\6&EFA6D90&0&0000 : HID UPS Battery
7 matching device(s) found.
============
ACPI Devices
============
ACPI\FIXEDBUTTON\2&DABA3FF&0 : ACPI Fixed Feature Button
ACPI\GENUINEINTEL_-_X86_FAMILY_6_MODEL_23\_0 : Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz
ACPI\GENUINEINTEL_-_X86_FAMILY_6_MODEL_23\_1 : Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz
ACPI\GENUINEINTEL_-_X86_FAMILY_6_MODEL_23\_2 : Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz
ACPI\GENUINEINTEL_-_X86_FAMILY_6_MODEL_23\_3 : Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz
ACPI\INT0800\2&DABA3FF&0 : Intel(R) 82802 Firmware Hub Device
ACPI\PNP0000\4&1E850C4&0 : Programmable interrupt controller
ACPI\PNP0100\4&1E850C4&0 : System timer
ACPI\PNP0103\4&1E850C4&0 : High Precision Event Timer
ACPI\PNP0200\4&1E850C4&0 : Direct memory access controller
ACPI\PNP0501\1 : Communications Port (COM1)
ACPI\PNP0700\4&1E850C4&0 : Standard floppy disk controller
ACPI\PNP0800\4&1E850C4&0 : System speaker
ACPI\PNP0A03\1 : PCI bus
ACPI\PNP0A06\3&473F1A46&0 : Extended IO Bus
ACPI\PNP0B00\4&1E850C4&0 : System CMOS/real time clock
ACPI\PNP0C01\2&DABA3FF&0 : System board
ACPI\PNP0C02\1 : Motherboard resources
ACPI\PNP0C02\2 : Motherboard resources
ACPI\PNP0C02\4 : Motherboard resources
ACPI\PNP0C04\4&1E850C4&0 : Numeric data processor
ACPI\PNP0C0C\2&DABA3FF&0 : ACPI Power Button
ACPI_HAL\PNP0C08\0 : Microsoft ACPI-Compliant System
ROOT\ACPI_HAL\0000 : ACPI Multiprocessor PC
ROOT\ARPC_CLASS\0000 : MS ArACPI Driver
25 matching device(s) found.11 2008-11-02 14:19:41
Re: [REL] DP_Bluetooth_wnt5_x86-32_1005b1 (103 replies, posted in 3rd Party DriverPacks)
Thanks RogueSpear,
Now things make sense. That explains why license.dat is required and the installer complains if it is not there, maybe a hardware vendor key.
Interestingly I can install it on a machine without Bluetooth hardware. Skeptik also confirmed it installed when running it manually, dont no what hardware, or if BT was working after the install.
Looks like I will have to remove the Widcomm drivers 
RogueSpear wrote:
It would seem from what I have read here that adapters using the Toshiba stack seem to all work with the same install set (or am I missing something here?).
Your not missing anything Toshiba Stack is straight from the link in the first post, the only change a AS.INI change to make it silent.
At least the Toshiba Stack looks to work well. The HWID for bluetooth in Toshiba notebooks is ACPI\TOS6205 (but they changed it for the lastest model I tested - USB\VID_....). Other vendors like ASUS also have HWIDs of USB\VID_.....
From what I can tell, the Toshiba Stack is generic and works for all vendors. Well at least no problems yet.
12 2008-10-31 19:58:33
Re: [REL] DP_Bluetooth_wnt5_x86-32_1005b1 (103 replies, posted in 3rd Party DriverPacks)
Skeptik, Thanks again for your feedback.
Its good to here that Toshiba Bluetooth is working for you
I not sure what to do about Broadcom Bluetooth, the problem is with the installer, but everything looks good from a packaging point of view. It would be good If someone else could confirm the problem, I might PM Grunger86 and see if he can test again.
Couple of things to check
* Check EventViewer and see if anything stands out as a problem (MSI version / errors / etc)
* Run installer after build has complete, and see if it errors, or installs and BT is working
If installer works after first loggon, as a workaround I could make it install as a RunOnce
13 2008-10-30 10:42:42
Re: Is there a nightly that supports the X-Fi titanium? (PCIe) (5 replies, posted in DriverPack Sound)
I can confirm that the X-Fi PCI version works fine and the control panel installs without a problem, DP805 sound A.
If you need a X-Fi PCI tester I'm happy to help out.
14 2008-10-28 21:49:25
Re: [REL] DP_Bluetooth_wnt5_x86-32_1005b1 (103 replies, posted in 3rd Party DriverPacks)
Skeptik, thanks for your patience and testing out the Bluetooth Driverpacks.
I have redone the installer, which I hope will fix the error.
15 2008-10-27 20:30:18
Re: [REL] DP_Bluetooth_wnt5_x86-32_1005b1 (103 replies, posted in 3rd Party DriverPacks)
Skeptik
Ok. The HWID weren't really need as the installer is running
I dont think DPsFnshr.log would really be helpful either
The installer (BT5504300.exe) is causing the error, Reading the error "Adminstrator Error" it maybe a problem with your setup.
The only other thing I can think of is two installers (DP exceptions) are trying to run at the same time. I was having this problem with Toshiba Bluetooth.
You could try the following:
* Unpack DP_Bluetooth_wnt5_x86-32_081021.7z
* Edit DriverPack_Bluetooth_wnt5_x86-32.ini and change these lines:
From:
exc_1_commands = 1
exc_1_command1 = "%DPSROOT%\D\3\BT\B\BT5504300.exe"To:
exc_1_commands = 3
exc_1_command1 = "PING -n 30 127.0.0.1 >NUL"
exc_1_command2 = "%DPSROOT%\D\3\BT\B\BT5504300.exe"
exc_1_command3 = "PING -n 30 127.0.0.1 >NUL"* Compress DP_Bluetooth_wnt5_x86-32_081021.7z
* Retry and let us know how you go
This will put a large pause before and after the installer.
Good Luck.
16 2008-10-25 15:29:45
Re: [REL] DP_Bluetooth_wnt5_x86-32_1005b1 (103 replies, posted in 3rd Party DriverPacks)
Hi Skeptik,
Thanks for the feedback, not sure why you would be getting that error. please check a few things:
* Make sure you are using DP_Bluetooth_wnt5_x86-32_081021.7z (Not DP_Bluetooth_wnt5_x86-32_081022.7z - this is no good)
* Post your HWID list
* Post your DP Finisher Log (DPsFnshr.log)
* Extract D\3\BT\B\BT5504300.exe from DP_Bluetooth_wnt5_x86-32_081021.7z and run it manually. See if that works, or errors.
17 2008-10-23 04:49:57
Re: [REL] DP_Bluetooth_wnt5_x86-32_1005b1 (103 replies, posted in 3rd Party DriverPacks)
Removed DP_Bluetooth_wnt5_x86-32_081022.7z rolled back to DP_Bluetooth_wnt5_x86-32_081021.7z
Including both Broadcom Bluetooth Stacks (5.1.0.4700 and 5.5.0.4300) was not required.
18 2008-10-22 19:15:06
Re: [REL] DP_Bluetooth_wnt5_x86-32_1005b1 (103 replies, posted in 3rd Party DriverPacks)
Added 5.1.0.4700, but USB\Vid_0a5c&Pid_2110&Rev_0100 should be covered by 5.5.0.4300 driver.
1. You need to have Bluetooth/WiFi hardware switch on for the Drivers to install.
2. If you have KTD enable and switch Bluetooth on after build, the Drivers will install but the Bluetooth Stack will not be installed.
Do a rebuild and let me know which driver gets installed, 5.1.0.4700 or 5.5.0.4300. (if any )
If 5.5.0.4300 installs, I will remove 5.1.0.4700 again because I don't think its needed.
19 2008-10-21 21:00:35
Re: [REL] DP_Bluetooth_wnt5_x86-32_1005b1 (103 replies, posted in 3rd Party DriverPacks)
Updated to include Broadcom(WIDCOMM) Bluetooth Stack, see first post.
I used the same approach as the Toshiba Drivers. It was a lot easier than Toshiba, and hopefully it will work.
I used version 5.5.0.4300 to cover more hardware, the drivers used are located here:
http://www-307.ibm.com/pc/support/site. … MIGR-70450
If they don't work i can use 5.1.0.4700 that you linked to.
Hope they help, let us know how you go.
7yler
20 2008-10-21 09:36:57
Re: [REL] DP_Bluetooth_wnt5_x86-32_1005b1 (103 replies, posted in 3rd Party DriverPacks)
Hi Grunger86,
I only have access to a hand full of machines and they all have the Toshiba Bluetooth Stack.
I haven't seen or work with the Broadcom Bluetooth Stack. If you can provide a link to the Drivers I will have a look, but can't promise anything.
Cheers
7yler
21 2008-10-17 23:16:06
Topic: DriverPack_reference_wnt5_x86-32.ini Document (1 replies, posted in Feedback and Support - DriverPacks Base)
While checking the DriverPack_reference_wnt5_x86-32.ini I noticed multiple references to '-hwid'.
shouldn't these 2 lines read as:
exc_1_+hwid2 = "<idem, will not be required if one of the previous '+hwid' requirements is already fulfilled>"
exc_1_+infFile2 = "<idem, will not be required if one of the previous '+infFile' requirements is already fulfilled>"
Not as:
exc_1_+hwid2 = "<idem, will not be required if one of the previous '-hwid' requirements is already fulfilled>"
exc_1_+infFile2 = "<idem, will not be required if one of the previous '-hwid' requirements is already fulfilled>"
While on DPsFnshr exceptions, is there any more information on how exc_1_+infFiles works, as I'd like to use it in the Bluetooth DriverPack, but I'm having problems getting it to use the HWIDs in the INF File.
Also, is there any chance of getting access to the Testing thread
Thanks
7yler
22 2008-10-17 23:04:26
Topic: [REQ] [GUI] DP_Base - MultiBoot Platform Profile (3 replies, posted in Feature Requests)
Original Title: Multi Boot - "Select the settings files" Page
While using the DriverPack BASE with the Multi Boot options, I noticed a few minor things that could be changed to make the BASE better.
1. The width of the "settings file" is not long enough and I have to resize it all the time. It would be nice if is was expanded to the full width by default.
2. Also when adding or deleting INI files you can only select one at time. It would be convenient if you could use Shift/Ctrl to select multiple INI's at a time.
I use Multi Boot all the time, as its a great feature. I do a lot of testing with HFSLIP/nLite/RyanVM and find I'm constantly changing settings. I hope its not to much to implement these minor changes.
Cheers
7yler
23 2008-10-17 23:02:42
Topic: [SOLVED] - Multi Boot with 3rd Party DriverPacks (2 replies, posted in Feedback and Support - DriverPacks Base)
I was testing on 8.10rc3 BASE, but have noticed this in previous releases.
When using the Multi Boot Option and having 3rd Party DriverPacks (like PhysX) they get processed multipy times. Causing multiple copies with different names to be added to the OEM folder.
1st Pass DP_Graph.7z
2nd Pass DP3P0001.7z
3rd Pass DP_Graphics_A_PhysX_wnt5_x86-32_810.7z
24 2008-10-14 23:21:38
Re: [IMPL] Intel Application Accelerator 2.3 (15 replies, posted in DriverPack Chipset)
JakeLD,
Thanks for your time and researh into this.
I had no broken install caused by nlite, I just enjoy playing around with windows builds on different hardware. At times I will use DriverAgent.com and other tools to check for Driver updates and noticed this was listed as requiring an update. As DriverPacks includes all the old Intel ICH Drivers I thought I would mention this one.
If as newsposter reports, it causes issues with newer hardware/software, leave it out.
Out of interest, I did a test on the old rig:
Hardware: Pent III, 512Mb, 82801BA (PCI\VEN_8086&DEV_244B)
Software: Windows XP SP3
Default Windows XP SP3 Install
--------------------------------------------------
Intel(R) 82801BA Ultra ATA Storage Controller - 244B
Driver Provider: Microsoft Corporation
Driver Date: 1/07/2001
Driver Version: 5.1.2600.5512
files: atapi.sys, intelide.sys, pciidex.sys
After Installing Intel Application Accelerator 2.3
----------------------------------------------------
Intel(R) 82801BA Ultra ATA Storage Controller - 244B
Driver Provider: Intel
Driver Date: 1/10/2002
Driver Version: 2.3.0.2160
files: ideBusDr.sys, ideChnDr.sys, IPrtCntst.dll
While here, I would just like to give a big thumbs up to all you guys, for all your hard work, I know how time consuming and frustrating drivers can be. I wasted many hours until I found DriverPacks. You do a fantastic job.
Damn ... I just re-read that and it sound like I just found GOD ... Well maybe I did ... The Driver Mecca
Cheers
7yler
25 2008-10-14 22:27:58
Re: [IMPL] ATK0100 ACPI utility 1043.2.15.101 (10 replies, posted in DriverPack Chipset)
I just done a build with the testpack DP_Chipset_wnt5_x86-32_810C.7z and all worked fine.
Driver 1043.2.15.101 installed, and all Fn HotKeys worked.
As expected with the INF change, driver signing was broken.
Thanks for the update. 7yler