My apologies for the long delay. An answer may be here --> http://forum.driverpacks.net/viewtopic.php?id=6720
551 2013-06-03 02:14:29
Re: [REQ] I need to integrated my ahci driver into winxp disc (56 replies, posted in DriverPack Mass Storage)
552 2013-06-03 02:09:57
Topic: USB-CD/DVD & USB-Floppy textmode support (0 replies, posted in DriverPack Mass Storage)
Edit your ..\i386\txtsetup.sif and add these entries in XP SP2 or SP3 for extra USB support in textmode.
This way, Windows can setup from these extra devices, as long as BIOS allows it to boot.
add to TXTSETUP.SIF after line:
USB\VID_55AA&PID_1234 = "usbstor"
these:
USB\VID_03F0&PID_2001 = "usbstor" ; xtra USB-Floppy begins
USB\VID_0409&PID_0040 = "usbstor"
USB\VID_0424&PID_0FDC = "usbstor"
USB\VID_054C&PID_002C = "usbstor"
USB\VID_055D&PID_2020 = "usbstor"
USB\VID_057B&PID_0001 = "usbstor"
USB\VID_08BD&PID_1100 = "usbstor" ; xtra USB-floppy ends
USB\VID_03EE&PID_7500 = "usbstor" ; xtra CD begins
USB\VID_03F0&PID_0207 = "usbstor"
USB\VID_03F0&PID_0307 = "usbstor"
USB\VID_0471&PID_080E = "usbstor"
USB\VID_0471&PID_0811 = "usbstor"
USB\VID_0499&PID_6001 = "usbstor"
USB\VID_04B4&PID_0000 = "usbstor"
USB\VID_04B4&PID_5A9B = "usbstor"
USB\VID_04DA&PID_0D01 = "usbstor"
USB\VID_04DA&PID_0D09 = "usbstor"
USB\VID_04DA&PID_0D0A = "usbstor"
USB\VID_054C&PID_0073 = "usbstor"
USB\VID_056F&PID_CD00 = "usbstor"
USB\VID_059B&PID_0050 = "usbstor"
USB\VID_059B&PID_0053 = "usbstor"
USB\VID_059B&PID_0056 = "usbstor"
USB\VID_05AB&PID_0CDA = "usbstor"
USB\VID_0644&PID_D001 = "usbstor"
USB\VID_0644&PID_D002 = "usbstor"
USB\VID_0718&PID_D000 = "usbstor"
USB\VID_07E5&PID_5C01 = "usbstor"
USB\VID_093B&PID_0011 = "usbstor"
USB\VID_0AC9&PID_0000 = "usbstor"
USB\VID_0B0D&PID_0000 = "usbstor"
USB\VID_0ECD&PID_1400 = "usbstor"
; USB\VID_1005&PID_B223 = "usbstor" ; xtra CD ends
USB\VID_03F0&PID_0507 = "usbstor" ; xtra DVD begins
USB\VID_045E&PID_029C = "usbstor"
USB\VID_045E&PID_029D = "usbstor"
USB\VID_04BB&PID_0204 = "usbstor"
USB\VID_04BB&PID_0206 = "usbstor"
USB\VID_04DA&PID_0D0E = "usbstor"
USB\VID_04E6&PID_0702 = "usbstor"
USB\VID_050D&PID_0210 = "usbstor"
USB\VID_054C&PID_01D0 = "usbstor"
USB\VID_054C&PID_023B = "usbstor"
USB\VID_054C&PID_02D1 = "usbstor"
USB\VID_059B&PID_015D = "usbstor"
USB\VID_059B&PID_1052 = "usbstor"
USB\VID_0644&PID_D010 = "usbstor"
USB\VID_0789&PID_0033 = "usbstor"
USB\VID_0789&PID_00B3 = "usbstor"
USB\VID_093B&PID_0041 = "usbstor"
USB\VID_093B&PID_0042 = "usbstor"
USB\VID_0E8D&PID_1836 = "usbstor"
USB\VID_0ECD&PID_A100 = "usbstor"
USB\VID_13FD&PID_0841 = "usbstor"
USB\VID_13FD&PID_1640 = "usbstor"
USB\VID_152E&PID_E001 = "usbstor"
USB\VID_1C6B&PID_A222 = "usbstor" ; xtra DVD ends
USB\VID_04B4&PID_4611 = "usbstor" ; xtra USB Storage Adapters begins
USB\VID_04B4&PID_6830 = "usbstor"
USB\VID_04B4&PID_6831 = "usbstor"
USB\VID_04C5&PID_102C = "usbstor"
USB\VID_04C5&PID_1039 = "usbstor"
USB\VID_04CE&PID_0002 = "usbstor"
USB\VID_0547&PID_2810 = "usbstor"
USB\VID_054C&PID_0022 = "usbstor"
USB\VID_054C&PID_002B = "usbstor"
USB\VID_054C&PID_0030 = "usbstor"
USB\VID_054C&PID_0076 = "usbstor"
USB\VID_05AB&PID_0030 = "usbstor"
USB\VID_05AB&PID_0060 = "usbstor"
USB\VID_05AB&PID_0061 = "usbstor"
USB\VID_05AB&PID_0101 = "usbstor"
USB\VID_05AB&PID_0201 = "usbstor"
USB\VID_05AB&PID_0301 = "usbstor"
USB\VID_05AB&PID_0351 = "usbstor"
USB\VID_05AB&PID_5700 = "usbstor"
USB\VID_05AB&PID_5701 = "usbstor"
USB\VID_05AB&PID_5A01 = "usbstor"
USB\VID_081B&PID_0600 = "usbstor"
USB\VID_081B&PID_0601 = "usbstor"
USB\VID_093B&PID_0000 = "usbstor"
USB\VID_093B&PID_0010 = "usbstor"
USB\VID_0BC2&PID_2000 = "usbstor"
; USB\VID_0BF6&PID_A000 = "usbstor" ; Addonics USB Cable 205 (TPP)
; USB\VID_0BF6&PID_A001 = "usbstor" ; Addonics USB Cable 205 (TPP)
USB\VID_14C2&PID_0250 = "usbstor"
USB\VID_14C2&PID_0350 = "usbstor" ; xtra USB Storage Adapters endsnote that F6 support is still possible as long as the following entry is set in your unattend file:
[Unattended]
OemPreinstall=No ; controls $OEM$ Distribution Folders and set to Yes prevents F6 floppy drivers
Worked with DP_BASE - Method2
edit:
Note that this method may vary by region.
If your XP-SP3 txtsetup.sif differs, please reply in this topic.
553 2013-05-31 22:42:46
Re: [Nightlies] DP_Misc_wnt5_x86-32_1303-1501 - Public (30 replies, posted in 3rd Party DriverPacks)
updated --> DP_Misc_wnt5_x86-32_1305301.7z 
edit: link removed - latest nightly in last post of this topic
554 2013-05-31 22:41:57
Re: [Nightlies] DP_Chipset_wnt5_x86-32_1304-1501 - Public (75 replies, posted in DriverPack Chipset)
updated here --> DP_Chipset_wnt5_x86-32_1305301.7z edit: link removed - updated
555 2013-05-31 22:41:14
Re: [Nightlies] DP_LAN_wnt5_x86-32_1303-1501 - Public (51 replies, posted in DriverPack LAN)
here's something a little more up-to-date
here --> DP_LAN_wnt5_x86-32_1305301.7z edit: link removed - updated in first post
556 2013-05-30 01:06:34
Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7) (525 replies, posted in Windows 7 tools)
Dat is cool. Leuk!
557 2013-05-29 16:25:06
Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7) (525 replies, posted in Windows 7 tools)
Have you room for a DP_Graphics_PhysX-Legacy_wnt5_x86-32_1305xxx.7z pack & it's lone file,
..\D\G\N03\PhysX\PhysX-9.12.1031-SystemSoftware-Legacy.msi?
[off-topic] ... "this crust is so unyielding & tasteless, it reminds me of a Type 5 Chassis!"
- The Unknown Geek. [/off-topic]
558 2013-05-26 21:47:50
Re: "Satellite-Debris"; misc news (12 replies, posted in Other)
It's old news, yet something new to me maybe you too.
virtuOS wrote:
"Sue on Gorbachev!"
I think that could have been translated "Sue Gorbachev!". From SamLab's forum:
http://translate.googleusercontent.com/ … Y0jjO3iLCA
virtuOS wrote:
" It is no coincidence that a man so loved in London and Washington, and do not like in St. Petersburg and Moscow. "
Where have we heard that kind of talk before?
"Mr. Gorbachev, tear down this wall". - Fmr. President Ronald Reagan
Now tear this wall down. No, THIS wall.
On this side of the ocean, criticism of leadership is taking on ominous tones. Try these comments. Not for young readers. It can't be easy to be a "political pinata" these days.
Double Whammy… Police Ticket Torched Cars in Stockholm
& I Had To Share This Poster "Sometimes a picture speaks more clearly than an essay."
Poignant for Memorial day.
559 2013-05-26 20:46:05
Topic: [REQ] Creative Labs Updates for XP (0 replies, posted in DriverPack Sound)
Audigy, etc.
Who would have imagined that Creative would continue support for this venerated series of products?
Thanks to Truth Unknown for mentioning it.Note daniel_k's reaction.
daniel_k wrote:
"Completely unexpected from Creative.
Did some preliminar tests and this driver works just fine (ASIO, OpenAL, Decoder, Microphone and WhatUHear recording) even without the 64-bit address registry setting.
Unfortunately there are issues with the Windows audio subsystem.
If you set the default format to anything other than 16-bit 44.1k or 48k, sound skips, crackles and disappears.
Even so, IMHO this driver is much better than the previous one."
...
"I'm about to release a final version of Support Pack and a complete installation CD in some days.
This final release uses a smarter approach so no safe mode during install is required anymore."
Quoted from: http://forums.creative.com/showthread.p … post541314
I haven't tested it yet. I'm waiting for daniel_k's updated Audigy SupportPack, myself (not for integration, at least not without his expressed permission & admin's). 
{DriverVer=03/04/2013, 6.0.01.1377} WHQL'ed for NT6 yet allegedly includes NT5 support.
here --> http://ccfiles.creative.com/manualdn/Dr … 8_0019.exe 
Suck lemons, station-drivers! 
Sucer les citrons, les stations-pilotes!
Creative Labs wrote:
wdma_emu.inf
"; Creative Technology Ltd.
; Copyright (c) Creative Technology Ltd, 1994-2007.
;
; Description
; This inf file contains the following device for Creative's audio card.
;
; Audio Device
; - PCI\VEN_1102&DEV_0008&CC_040100
; - PCI\VEN_1102&DEV_0004&CC_040100
;
; Modified Date: 4 January 2013
; Version: 2.18.0017.19"
...
[Creative]
; Audigy, Audigy 2
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_00401102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_00411102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_00421102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_00431102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_005A1102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_005B1102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_005C1102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_00511102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_00521102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_00531102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_00541102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_00551102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_00561102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_00571102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_00581102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_00591102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_10021102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_10031102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_10041102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_10051102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_10061102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_10071102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_10081102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_10091102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_100A1102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_20011102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_20021102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_20031102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_20041102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_20051102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_20061102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_20071102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0008&SUBSYS_10001102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0008&SUBSYS_10011102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0008&SUBSYS_10211102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0008&SUBSYS_10221102
;Audigy2 LS SB0612
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0008&SUBSYS_10231102
;Audigy 2 SA
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0008&SUBSYS_11011102
; Audigy 4 PCMCIA
%AudigyPCMCIA.DeviceDesc%=Audigy2PCMCIA_Device,PCI\VEN_1102&DEV_0008&SUBSYS_20011102
; Audigy 4 PCMCIA
%AudigyPCMCIA.DeviceDesc%=Audigy4PCMCIA_Device,PCI\VEN_1102&DEV_0008&SUBSYS_20211102
[Creative.NTX86]
; Audigy, Audigy 2
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_00401102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_00411102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_00421102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_00431102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_005A1102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_005B1102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_005C1102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_00511102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_00521102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_00531102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_00541102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_00551102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_00561102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_00571102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_00581102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_00591102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_10021102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_10031102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_10041102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_10051102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_10061102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_10071102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_10081102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_10091102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_100A1102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_20011102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_20021102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_20031102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_20041102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_20051102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_20061102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_20071102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0008&SUBSYS_10001102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0008&SUBSYS_10011102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0008&SUBSYS_10211102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0008&SUBSYS_10221102
;Audigy2 LS SB0612
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0008&SUBSYS_10231102
;Audigy 2 SA
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0008&SUBSYS_11011102
; Audigy 2 PCMCIA
%AudigyPCMCIA.DeviceDesc%=Audigy2PCMCIA_Device,PCI\VEN_1102&DEV_0008&SUBSYS_20011102
; Audigy 4 PCMCIA
%AudigyPCMCIA.DeviceDesc%=Audigy4PCMCIA_Device,PCI\VEN_1102&DEV_0008&SUBSYS_20211102
[Creative.NTAMD64]
; Audigy, Audigy 2
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_00401102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_00411102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_00421102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_00431102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_005A1102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_005B1102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_005C1102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_00511102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_00521102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_00531102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_00541102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_00551102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_00561102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_00571102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_00581102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_00591102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_10021102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_10031102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_10041102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_10051102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_10061102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_10071102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_10081102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_10091102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_100A1102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_20011102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_20021102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_20031102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_20041102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_20051102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_20061102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0004&SUBSYS_20071102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0008&SUBSYS_10001102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0008&SUBSYS_10011102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0008&SUBSYS_10211102
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0008&SUBSYS_10221102
;Audigy2 LS SB0612
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0008&SUBSYS_10231102
;Audigy 2 SA
%Audigy.DeviceDesc%=Audigy_Device,PCI\VEN_1102&DEV_0008&SUBSYS_11011102
; Audigy 2 PCMCIA
%AudigyPCMCIA.DeviceDesc%=Audigy2PCMCIA_Device,PCI\VEN_1102&DEV_0008&SUBSYS_20011102
; Audigy 4 PCMCIA
%AudigyPCMCIA.DeviceDesc%=Audigy4PCMCIA_Device,PCI\VEN_1102&DEV_0008&SUBSYS_20211102...
[Strings]
CREAF="Creative"
StrDisk="Creative Installer CD-ROM"
CLMfgName="Creative Technology, Ltd."
EMU10K1.DeviceDesc="Creative EMU10K1 Audio Processor (WDM)"
Audigy.DeviceDesc="Creative Audigy Audio Processor (WDM)"
AudigyPCMCIA.DeviceDesc="Creative Audigy Audio Processor (WDM)"
Live2K.Wave.szPname="Creative Audio"
Live2K.Topology.szPname="Creative Mixer"
Live2K.SpdifWave.szPname="Creative SpdifOut Audio"
Live2K.SpdifTopo.szPname="Creative SpdifOut"
Live2K.Synth.szPname="Creative Synth"
Live2K.SynthA.szPname="Creative Synth A"
Live2K.SynthB.szPname="Creative Synth B"
Live2K.SwSynth.szPname="Creative Sw Synth"
Live2K.UART1.szPname="Creative MIDI Port"
Live2K.UART2.szPname="Creative MIDI Port II"
Live2K.MidiAutoFx.szPname="Creative MIDI AutoFx"
Live2K.DmUart1.szPname="Creative DirectMusic MIDI Port"
Live2K.DmUart2.szPname="Creative DirectMusic MIDI Port II"
Live2K.DmAutoFx.szPname="Creative DirectMusic AutoFx"
Live2K.DmSynth.szPname="Creative DirectMusic Synthesizer"
OSSRV.SvcDesc = "Creative OS Services Driver"
HA10KX.SvcDesc = "Creative Hardware Abstract Layer Driver"
EMUPIA.SvcDesc = "E-mu Plug-in Architecture Driver"
CTAUD2K.SvcDesc = "Creative Audio Driver (WDM)"
CTAC32K.SvcDesc = "Creative AC3 Software Decoder"
CTPRXY2K.SvcDesc = "Creative Proxy Driver"
CTSFM2K.SvcDesc = "Creative SoundFont Management Device Driver"
HAP16V2K.SvcDesc = "Creative P16V HAL Driver"
HAP17V2K.SvcDesc = "Creative P17V HAL Driver"
CTDVDA2K.SvcDesc = "Creative DVD-Audio Device Driver"
CTMMFILT.SvcDesc = "Audio Filter Driver"
CT0531FL.SvcDesc = "Audio Filter Driver CT0531FL"
CTFXBASE.SvcDesc = "Base"560 2013-05-18 16:53:09
Re: [REQ] CP210x USB to UART Bridge VCP Drivers (1 replies, posted in 3rd Party DriverPacks)
... already "in the system". Actually, in the Chipset latest nightly, or release candidate.
561 2013-05-17 15:07:48
Topic: Security Vulnerability - nVidia Display Driver Service (0 replies, posted in DriverPack Graphics)
Apparently, there is a Security Vulnerability concerning nVidia display drivers, at least those released prior to 2013.
Jimboc wrote:
..." once you have configured the Nvidia Control Panel settings to your liking please set the Nvidia Display Driver Service to the Disabled start-up type since driver 310.70 and prior versions have a security vulnerability. Further details are available at the following link (see the posts written by nvtweakman and myself):
https://forums.geforce.com/default/topi … gtx-690/2/"
Quoted from: https://forums.geforce.com/default/topi … 2/#3732522
Jimboc wrote:
"I chose the thread I linked to about the security vulnerability since it was short and to the point. It was also discussed in the following threads (there is probably more threads available than these few):
https://forums.geforce.com/default/topi … a-drivers/
https://forums.geforce.com/default/topi … e-needed-/
https://forums.geforce.com/default/topi … le-310-70/
https://forums.geforce.com/default/topi … be-hacked/
Since the 310 drivers no longer support the old GeForce 6 and 7 series (from 2004 - 2005) Nvidia will be releasing a driver for them that contains the fix for the security vulnerability in the coming weeks. This was mentioned by ManuelG in the following thread:
https://forums.geforce.com/default/topi … 7-series-/"
Quoted from: https://forums.geforce.com/default/topi … 0/#3732560
562 2013-05-17 14:22:16
Re: [Nightlies] DP_Modem_wnt5_x86-32_1305-1411 - Public (9 replies, posted in 3rd Party DriverPacks)
updated here --> DP_Modem_wnt5_x86-32_1305151.7z
added driver requested by matyibuta --> http://forum.driverpacks.net/viewtopic. … 503#p49503
edit: link removed - latest nightly in last post of this topic
(27 downloads for 1305051 & 1305151)
563 2013-05-16 12:25:49
Re: Driverspack Solution (4 replies, posted in Other)
Does this indicate that the following list of download sites is now irrelevant?
http://driverpacks.net/docs/DriverPack% … -first-run
564 2013-05-15 22:11:34
Re: Driverspack Solution (4 replies, posted in Other)
Huh? Say what? Data base? Offline? Confused?
565 2013-05-15 15:14:08
Re: VEN_10de&DEV_1049 (GeForce GT 620) Missing (10 replies, posted in DriverPack Graphics)
If one was to chide you for a mistake, it might be not reading the stickied topic "STOP ATI / NVIDIA REQUESTS please" by muiz, but i will let that pass. There are extenuating circumstances.
I note that v307.83 seemingly supports the widest range of devices. There exists a desktop & notebook release and for Quadro/Tesla.
http://us.download.nvidia.com/Windows/3 … l-whql.exe
http://us.download.nvidia.com/Windows/3 … l-whql.exe
http://us.download.nvidia.com/Windows/Q … l-whql.exe
http://us.download.nvidia.com/Windows/Q … l-whql.exe
nV wrote:
"Legacy Support Notification: GeForce 6-series and GeForce 7-series GPUs will be moved to legacy support after GeForce R304 drivers (304.xx to 309.xx). GeForce R310 drivers will not support these products."
Quoted from: http://www.nvidia.com/object/notebook-w … river.html
No promises, just information here, so far. 
566 2013-05-13 16:00:50
Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7) (525 replies, posted in Windows 7 tools)
Just an update. Looked up OEM's driver page for that particular model, and it has listed Alps only. Synaptics "Pressure Graph" app states that the program requires a Synaptics TouchPad. That would explain why the control panel & Animated SystemTray icon don't work right. Driver v16.2.10.20 was installed. Mind you, these are results with legacy hardware, NT5 & DP_HID, so maybe it's not of issue to NT6 DP_TouchPad_Mouse users.
I'll do what i can to test with NT6 & report back.
Would a touchpad mfg possibly be listed in acpi, for instance?
567 2013-05-13 14:45:42
Re: devPath.EXE problem (18 replies, posted in Feedback and Support - DriverPacks Base)
That's not your fault, OverFlow. I know that you are being sarcastic.
It sure does help to not waste our time when critical information is included.
We are volunteers, not profiteers.
ikbeneenlul wrote:
"I did not read the forum rules and guidelines"
Give it a go. Even i have to re-read the rules, once in a while.
ikbeneenlul wrote:
... "because fewer systems seem to accept SP3"
I have yet to see an ATAPI Setup with at least a P-II or Athlon & 256MB that could not fully Setup Windows from my own slipstreamed XP SP3 disc, other than faulty units. I have seen exceptions to that, yet those had issues with a CD/DVD drive (sometimes specific models) being on the same controller, or simply reading a scratched disc or poorly-supported media.
When i have encountered Setups that could not complete, or spat out errors, there was either a problem with the update packs i include with RVMi, my source, or a genuine hardware issue (not considering DP's development). This includes the AMD chips that were an original issue with SP3.
I consider XP-SP3 Setup to be a genuine hardware test, other than for the newest and where NT5 drivers do not exist, or the oldest where memory limits patience.
At any rate i deduce from your comments regarding 4MB that you are likely using nLite. This can corrupt one's source. Remember that if you have copied your disc to a folder, you have copied it onto R/W hardware. It can and will be changed eventually, if you do not monitor changes to that folder &/or refresh it's contents. This has been noted and repeated on occasion elsewhere in this forum.
Oh, yes. I would replace the coin-cell in any that show those infamous crystalline residual signs of leakage for any vintage to antique computing hardware.
568 2013-05-13 10:22:47
Re: Touchpad Mouse x86 (31 replies, posted in 3rd Party Vista / 7 DriverPacks)
Ra wrote:
"DP_Touchpad_Mouse_wnt6-x86_1203
Causes ThinkCentre M57 computers to run the fan at full speed and then reboot after 30 seconds continuously. It boots then fan comes on full and 30 seconds later instant reboot."
... see Ra's topic here --> [BUG] DP Touchpad Mouse wnt6-x86 1203 ThinkCentre reboot loop
Can anyone reproduce this issue?
Be prepared for possible thermal-runaway, though. 
569 2013-05-13 10:10:57
Re: [BUG] DP Touchpad Mouse wnt6-x86 1203 ThinkCentre reboot loop (10 replies, posted in 3rd Party Vista / 7 DriverPacks)
[off-topic] Oh, it's a wind instrument relying upon one's lips for production of those soothing sounds. A "bong-style" cooler, which relies upon "phase-change" for cooling, could not reproduce those sounds. Add to that the fact that additional humidity in some climates could encourage mold & mildew growth inside a dwelling. It seemed like a novel idea at the time. 
[/off-topic]
On a "risk" machine, disable "Automatic Restart" upon system failure to view a bluescreen code and the offending file (if applicable).
Also, please mention some models other than the "ThinkCentre M57" so that others have a better chance of reproducing this undesired and potentially harmful effect.
Also, does this same effect occur with "SAD3"? Is the 64-bit pack effected, too?
570 2013-05-13 09:50:31
Re: devPath.EXE problem (18 replies, posted in Feedback and Support - DriverPacks Base)
ikbeneenlul wrote:
"In the old days, machines were not build to be replaced, they were build to last
I agree. In addition, some components used real gold, not the alloys used as of late which are more prone to oxidization and bi-metallic corrosion. (I would have to double-check my half-cell electrochemical tables to confirm that last part concerning "bi-metallic corrosion"; call it an observation, not necessarily fact.) Also, they used leaded solder, which is not as prone to thermal, whiskering or other inclusive phenomenon as the early and or inexpensive unleaded crap.
OverFlow wrote:
... "people throw away far better equipment than this"
I rely upon this fact. Often it is only a lack of cleanliness, or blown capacitors in a P/S (stored charge in such can kill; beware), that prevent stable operation.
If only you could plunk an AMD K6-2/500 & another 64MB or so in there. Although as OverFlow hinted, those CPU's performed better with a 16-bit OS.
ikbeneenlul wrote:
"My P1 has 64MB of ram ( I verified XP requires an i386 with 4MB of ram or better )"
That doesn't seem accurate, so here's some info from Wikipedia:
" Minimum
Processor 233 MHz[1]
Memory 64 MB of RAM[2]^1 Even though this is Microsoft's stated minimum processor speed for Windows XP, it is possible to install and run the operating system on early IA-32 processors such as a P5 Pentium without MMX instructions. Windows XP is not compatible with processors older than Pentium (such as 486) because it requires CMPXCHG8B instructions.[94]
^2 A Microsoft TechNet paper from Summer 2001 (before Windows XP's actual release), states that: "A computer with 64 MB of RAM will have sufficient resources to run Windows XP and a few applications with moderate memory requirements." (Emphasis added.) These were said to be office productivity applications, e-mail programs, and web browsers (of the time). With such a configuration, user interface enhancements and fast user switching are turned off by default.
For comparable workloads, 64 MB of RAM was then regarded as providing an equal or better user experience on Windows XP with similar settings than it would with Windows ME on the same hardware. In a later section of the paper, superior performance over Windows ME was noted with 128 MB of RAM or more, and with computers that exceed the minimum hardware requirements.[95]
Quoted from: http://en.wikipedia.org/wiki/Windows_XP … quirements
additional reference: http://support.gateway.com/s/software/m … u136.shtml"
There you have it. Although that processor doesn't appear to meet minimum speed requirements (effecting timing in some cases?), it can "work", yet with that, yet with a minimum of memory some features will be disabled. Does that effect DEVPATH? OverFlow would know better than me. I thought some of this info would be relevant and/or helpful.
As a parting thought, an Apple I motherboard (no case) recently sold at auction in December for $640,000!
http://appleinsider.com/articles/12/12/ … an-auction
& http://www.zdnet.com/apple-i-to-be-sold … 000015200/
That "Pascaline" seems to have that "steampunk" look, yet it would seem that an abacus would be more "user-friendly"!
Just because it is a "dinosaur" doesn't necessarily mean that it is worthless. After all, those that ignore history are oft doomed to repeat it or at least "rhyme" with it.
I do admire your courage and patience in working on this vintage hardware.
edit: post a small image or two, or link to downloadable pic, to show off hardware that endures. What brand is that?
571 2013-05-11 13:22:55
Re: [BUG] DP Touchpad Mouse wnt6-x86 1203 ThinkCentre reboot loop (10 replies, posted in 3rd Party Vista / 7 DriverPacks)
So, what it does is to run-up the CPU usage, maybe throwing Page Faults faster than newsprint through a press, as well? Then, after running near full-throttle for sometime derating it's ability to efficiently deliver rated current, that is increasing resistance, leading to thermal runaway and an auto-shutdown, perhaps even internal to the CPU!
30 seconds, eh? Power-packs likely match the rating of the portable.
At any rate, maybe it would be best to monitor temperatures, Wattage, fan speeds; whatever practical during testing, if you agree. Decline the usage of a mercury thermometer (naturally).
That is indeed a noteworthy issue, imho.
It could risk possibly permanently ruining marginal (more likely unmaintained) ThinkCenters, perhaps even portables by other manufacturers.
This could be hobbling to some.
It would seem a priority for the community to isolate what that it is that causes these issues, perhaps even pull current packs for now.
That is, if observation and deduction align concerning this topic. Ra? Admin?
Does a previous pack function properly with a couple of non-critical models? (elevate the back with a rubber ball safely cut in half, or a stick, pair of erasers, oversize pencils, tiny-didgeridoo, or what-have-you - whatever keeps fans clear!) Digeridoo H2O "Bong-Style" CPU/GPU cooler; ooo! Need good waterflow to get sound, though, i garner. Not for apartment-dwellers! Sorry, back to topic.
Remove the battery on a test-unit, especially if not fully-charged. Remove all-but one memory stick, disable HT, reduce FSB, remove WiFi card if practical. Sticky-tape antennae, or otherwise insulate.
These techniques can limit some damage from thermal-runaway, or make more power available for thermal-runaway to ramp in less time. That is where monitoring a parameter or two can guide.
What is uncovered when you boot into Safe Mode? I hope that it is possible. Double check the Keyboard, Mouse Control Panel apps as well as DEVMGMT.MSC versus OEM Specification data & Driver availability concerning the actual TouchPad in each test-case. If any must undergo disassembly, those would make great test-candidates if TouchPad manufacturer can be visually verified from a logo on-chip, or printed on TP board. Avoid removing factory laminate from the fragile modules. Sticky-tape is OK to remove, just be careful with the ribbon-cables (if applicable).
Thank you again, for pointing out those issues!
What is progress without feedback? It is unconfirmed.
572 2013-05-10 23:02:40
Re: Driverpacks structure question (2 replies, posted in Other)
You are correct.
The folder structure for NT5.x DriverPacks is indeed totally different from that of the NT6.x packs.
You all-but answered that fro yoself.
573 2013-05-10 22:53:25
Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7) (525 replies, posted in Windows 7 tools)
That HID pack can be a bit of a briar patch, neh?
Here's an oddball i found in a Satellite A70.
Installed along with the proper Synaptics TouchPad software (with the icon nicely disabled, thank you - how can i do that with ATi? 
) mistakenly was Elan Microlelectronics's "ETDWare PS/2-x86 v11.6.4.001_WHQL. In addition, it added a new tab in "Control Panel\Mouse" which had all options greyed out.
PS/2 Keyboard - ACPI\PNP0303\4&102A0DBB&0
Logicool was listed as manufacturer, SynTP was the upper-filter's name, and i8042prt being the service name.
I was able to uninstall the utility via A&RProgs., yet had to "roll-back" the PS/2 Mouse driver from the unexpected plain-jane MS driver, to the previously installed Synaptics driver (v16.2). The Control Panel\Mouse extension was missing.
To add to that, there were 23 files dated Sept 5th 2007 from DP_HID\D\3\H\A\ installed in my Program Files folder, including an Alps utility. In another Satellite A70, i see an Alps TouchPad installed. I will check with Toshiba Support's Drivers page to see if both Alps & Synaptics are listed &/or included on support page.
Not a complaint, just observation. Wondering if other models may be effected as this one was on XP?
Also, wondering if SAD3 would better discriminate Sound drivers better than Setup/DPfinisher11.09.012?
574 2013-05-10 14:35:50
Re: [Nightlies] DP_Misc_wnt5_x86-32_1303-1501 - Public (30 replies, posted in 3rd Party DriverPacks)
One would have to insert many BitCoins to continue...
So, why should it be ruled out, if someone were to fund the research?
It would become the "very legacy" branch for NT6.x_x64 ...
575 2013-05-10 14:20:50
Re: [SLVD] Lost keyboard and mouse after deploying image to laptops (3 replies, posted in Universal Imaging)
Bear with me, my Sysprep skills are non-existent.
With that in mind, i would probably try a simplified approach with the included packs.
The devices causing issue are HID devices; therefore, it may be an idea to leave that pack out for now.
It can be installed post-setup via SAD2.
The latest version, SAD3, is here --> http://forum.driverpacks.net/viewtopic. … 586#p51586
If you do decide to use SAD3, you need a replacement for DP_HID meant to weed out known problem devices. --> http://forum.driverpacks.net/viewtopic. … 563#p51563
Also, it is possibly wise to install the Webcam pack that way, too. It has potential path-length issues.
I note that the drivers in the Bluetooth pack are at least 4 years old now. This is probably insecure. You might want to get the latest from a manufacturer, as there is no updated Bluetooth pack here.
WLAN is something else that i avoid including with setup as some devices are more "chatty" than others and have potential to negatively impact security.
In addition, is it wise to include DP_LAN-RIS_wnt5_x86-32_1011.7z with DP_LAN_wnt5_x86-32_1205.7z ? I am uncertain myself. Perhaps someone more familiar with RIS integrations could add some comments.
Also noting that you have not DP_Graphics_ATI_runtimes to go with the DP_Graphics packs. That must mean that none of those appliances previously mentioned have AMD/ATi Graphics or you do not desire the Catalyst Control Center installed with .Net2SP2 & latest VisualC++ runtimes.
One recommendation that i can make is to use my latest nightly for DP_Modem, as it removes some drivers meant for Vista. http://forum.driverpacks.net/viewtopic.php?id=6704
Also, the latest nightly for DP_Sound_A updates the Realtek & VIA lines of HD Audio devices including HDMI, if applicable.
http://forum.driverpacks.net/viewtopic.php?id=6701
Now, if you have a need for the latest drivers, here are some updated packs that so-far have proven themselves in testing:
DP_Chipset_wnt5_x86-32_1305071.7z * Know your TPM's brand first (if applicable) or risk data
DP_Graphics_ATI_Runtimes_wnt5_x86-32_1305051.7z
DP_Graphics_A_wnt5_x86-32_1305041.7z
DP_Graphics_B_wnt5_x86-32_1305061.7z
DP_Graphics_C_wnt5_x86-32_1305042.7z
DP_LAN_wnt5_x86-32_1304271.7z
DP_MassStorage_wnt5_x86-32_1305061.7z
DP_Modem_wnt5_x86-32_1305051.7z
DP_Misc_wnt5_x86-32_1305042.7z
DP_Biometric_wnt5_x86-32_1304rc1 * use with DP_Misc; no utilities - just drivers incl.
3GKid wrote:
"The strange thing is that I did a similar image earlier in the year and I did not get this issue on the laptops."
This indicates to me that you used the same packs earlier this year.
It may have been that you made your previous image earlier this year on a laptop, perhaps?
If i am totally off-target, then i sincerely apologize.
Welcome to DriverPacks.net & may good fortune be yours!