(36 replies, posted in Vista / 7 DriverPack Graphics B)

I completely understand.  Like I said, now I have two drivers that work in 32-bit Windows 7.  The MS one that I downloaded while they offered it, and now this hacked up version of that I put together.  Since the MS driver that I have is signed it will install fine after the fact, or using DISM ahead of time.  I even installed my unsigned driver to my image using DISM /add-driver with the /ForceUnsigned switch and it installed fine on a fresh reload.  I removed it later in favor the MS Driver, but it still worked.  Anyways, I wouldn't waste time on trying to get this into a DriverPack anymore if nobody is supporting the driver.  I would have to think the odds of someone else needing this card to work in Windows 7 in a production environment is pretty slim.  MS obviously took it down for a reason, and the card is pretty old.  The only reason I came across it in the first place was when I testing Windows 7 on some hardware that's probably too old to run Windows 7 well in the first place.  Thanks for your time.


(36 replies, posted in Vista / 7 DriverPack Graphics B)

Here's quick update.  I added my HWID right above the NVS 285 card in the 267.79  driver inf.  Then I tried forcing that driver.  After a restart it said that the driver was disabled because it reported problems.  Then I did the same thing with that with the Dell driver and it loads and appears to work.  Aero works fine as well.  If you want a copy of the MS signed driver I still have it in my collection.  The signed MS driver detects my card as "NVIDIA Quadro PCI-E Series".  Driver date is 10/9/2006 and is driver version  That Dell driver that I put that HWID in has a Driver date of 12/7/2006 and is driver version  In terms of functionality I'm not sure of any differences but I'll let you know if I find any.


(36 replies, posted in Vista / 7 DriverPack Graphics B)

Yeah it looks like Microsoft has pulled that driver from their catalog...  On a fresh install there is no longer a driver offered through Windows Update.  The HWID for this card is as follows.

PCI\VEN_10DE&DEV_00FD&SUBSYS_021510DE&REV_A2\4&E264267&0&0008: Standard VGA Graphics Adapter

I've done some poking around and on Dell's website http://search.dell.com/results.aspx?s=g … mp;cat=sup the second item is for 32-bit Vista, and the description says 64MB PCI-Express Quadro NVS 280, but it doesn't work.  If you open the inf there are no entries for the NVS 280 card in it.  If there is anything you'd like me to try let me know.



(3 replies, posted in Hardware)

bobcat250 wrote:

The page you mentioned, the one with all the model numbers, is one I did find; but I could not locate the 933M unless its known by another number. Guess I'll just have to keep looking.

http://support.gateway.com/support/supi … cprod.html

That should be the link I was talking about with the models.  I also didn't see a 933M machine which leads me to believe that it's some 930 series model.  Good luck!


(3 replies, posted in Hardware)

I'm not sure this is the something that would normally be answered in this forum, but since I've also been affected by MPC's failure I'll try to help.  Underneath their newsletter about the sale it also lists nearly every model that was ever sold in their business line.  It's not as convenient as just typing in the serial number anymore, but I can usually find original everything from Gateway's site just by clicking the actual model of the PC from the list.  Before Gateway re-posted those "as-is" links for the machines they used to sell, I frequently used this site to find drivers http://www.mpcdrivers.com/downloads/driver.html.   I know the domain is mpcdrivers.com but they have drivers and BIOS files that used to be posted on MPC-Corp's website.  Hope this helps.


(19 replies, posted in Other)

Unfortunately I wasn't keeping track of all the various guides and items that I used when I was experimenting. I also didn't find any guides at the time that helped me get everything working in WinPE 3.0.  If I have time in the next few days I'll throw something together to hopefully save everyone who wants to try it some time.  Personally I think everyone that does a bunch of deployments should give it a shot because I don't waste any CD/DVD media anymore.  I have one WinPE 3.0 CD-R that I haven't updated or changed in 4 months, and only have to use it on older machines that aren't capable of booting from a WinPE 3.0 flash drive.  The only time the WinPE evironment needs to change is if some brand spank'n new hdd/raid controller, or network card that isn't supported by DriverPacks comes out.  But if it's that new then booting from USB shouldn't be a problem and you still don't have to burn anymore disks.  Anyways, enough raving about how well it works for me.  Like I said, hopefully I'll have time to put together a guide in the coming days and you can see for yourself smile



(19 replies, posted in Other)

I've had extremely good success with deploying XP using WIM images along with OfflineSysprep so if you did decide to go down that road and ran into any snags I can probably assist you.  That combined with DriverPacks allows me reload oem-specific or VLK XP machines in 10-15 minutes.  Anyways, if you do give is a whirl and get stuck let me know and I'm sure I could help you.


(36 replies, posted in Vista / 7 DriverPack Graphics B)



(36 replies, posted in Vista / 7 DriverPack Graphics B)

Hey guys, I had created a Windows 7 image with DP_A, DP_B, and DP-Mobile Vista/7 packs and I my graphics driver wouldn't load.  With further research I discovered it's a card that isn't supported by nVidia for Vista or 7 (Quadro NVS 280).  The driver that I ended up using was found on Microsoft Update on the link below.  I created a test pack based on the 1007 release with the driver found below and it loaded without error and I was just wondering if these kinds of drivers are typically left out of DriverPacks or is Microsoft a good enough source for some drivers?  Let me know.  Thanks for everything guys.

http://catalog.update.microsoft.com/v7/ … 9276aa5f58

yeik wrote:

I can comfirm this issue. The issue showed up for me with LAN pack V. 10.04 but 10.0411 from mr_smartepants fixed the issue.

What he said ^

Hey guys.  I haven't done much testing besides what I'll layout here but there seems to be a bug in the latest DP_LAN pack when loading into BartPE.  I'm using the DriverPacks Base 10.04.01rc and and when I use the DP_LAN_wnt5_x86-32_1004 pack I receive a message in BartPE with a title of "winlogon.exe - Entry Point Not Found"  The message itself says "The procedure entry point StrRetToBSTR could not be located in the dynamic link library SHLWAPI.dll."  When I revert the LAN driverpack back to the DP_LAN_wnt5_x86-32_100313 nightly it seems to work fine.  Is there something that I'm missing or need to change?



(41 replies, posted in Universal Imaging)

eethball wrote:

I appreciate the reply.  I'm not sure what exactly fixed that registry issue I was having, but after starting with a fresh xp load to be imaged, and without checking the "Don't reset the grace period" checkbox I have a working universal image.  The only sort of weird hang up thing that I'm assumed is caused by the Update HAL on First Boot option is the first time the machine boots it says It is now safe to shutdown your computer".  I power the machines off and then back on and the mini setup begins.  Is this normal?

Alright, I saw that it was normal for the PC to shut down after the HAL is updated, but does anyone know if there is a way to turn that into a reboot instead of a shutdown?  Obviously it's not too big of a deal, but I was just wondering.  Thanks to everyone for their time.


(41 replies, posted in Universal Imaging)

I appreciate the reply.  I'm not sure what exactly fixed that registry issue I was having, but after starting with a fresh xp load to be imaged, and without checking the "Don't reset the grace period" checkbox I have a working universal image.  The only sort of weird hang up thing that I'm assumed is caused by the Update HAL on First Boot option is the first time the machine boots it says It is now safe to shutdown your computer".  I power the machines off and then back on and the mini setup begins.  Is this normal?


(41 replies, posted in Universal Imaging)

Hey guys.  I've been trying to work out a universal image myself and was running into an issue.  2 or 3 days ago I posted this same question at 911cd.net (http://www.911cd.net/forums//index.php? … amp;st=740) but hadn't received any responses.  I was hoping someone here that has had success with his OfflineSysPrep program might be able to point out something I'm doing wrong so hopefully I can correct it.  If it's frowned upon that I post this question in more than one spot let me know and I'll remove the post.  Thanks ahead of time guys.  I appreciate everything you guys do.

Here's the original message.

Hey there Galapo. First I just wanted to say thanks for all your time on this project. Now I’m asking out of desperation since I can’t seem to get my universal XP image working and I hoping that you (or someone in this forum) had a second to look at what I’m doing and see where I’m going wrong. Basically I have the vmware machine that I’d like to image. Since I have a very large amount of different hardware I’d like to use this image on I’ve been creating the DriverPack-MassStorage folder using the CreateMassStorageData.exe and I’ve replaced the ntldr with that of the XP x64 system to avoid the ntfs.sys error. Now I’ve tried different versions of sysprep, and my last test was with sysprep.exe version 5.2.3790.1830 with no pre-configured sysprep.inf added to the sysprep folder on my BartPE disk. When running OFP I selected do nothing from the HAL options (just to rule that out as causing the problem), and the only thing that I selected from the advanced options is say “Install all DriverPacks non-IDE Mass Storage Device(s)”. When sysprep opens I selected “Don’t reset grace period for activation” (since I’m using VLK OS), Use Mini-Setup, and set the shutdown mode to quit. Then I clicked reseal, and when sysprep closes I shutdown the machine from BartPE. Then I try to boot machine I always seem to get the error message saying An error has been encountered that prevents Setup from continuing. Windows is unable to start because the registry could not be updated… I’ve seen other people in the forums mentioning they’ve received this error, but almost everyone says it has something to do with their sysprep.inf, but since I deleted mine for testing and still receive the error message I seem to be stuck. Any help would be appreciated.

Glad to be part of the team.  You guys have saved me soooo much time over the last few years so I'm glad to be of assistance to you guys.

Found another HWID that seems to have a problem as well.  If I used the latest nightly and not my repackaged driverpack it loads the driver in the I7 folder and gets the Code 10 device could not start error.  If I used my repacked driverpack where I added the I20 folder, setupapi says it loaded the driver in my I20 folder, but also gives the device could not start error.  So I went into my I20 folder and I7 folder and pruned the hwid below from both infs, and added an I21 folder with the driver found here http://support.gateway.com/support/driv … =257757934 and then reloaded the machine and it worked just fine...

Edit.. Forgot to list the HWID for this second system...

HDAUDIO\FUNC_01&VEN_8384&DEV_7634&SUBSYS_107B0461&REV_1001\4&34AF940E&0&0001: SigmaTel High Definition Audio CODEC

Hey guys.  I don't know if the testing team has come across this yet, but I figured I would post my findings.  Using dp_base 8.12.25, Disk integration, on Windows XP SP3 I get a blue screen right after the text-mode setup says "Starting Windows" when using the nightly driverpack DP_MassStorage_wnt5_x86-32_909r6.7z.  I reverted back to the DP_MassStorage_wnt5_x86-32_901.7z driverpack and then the reload went just fine.  The HWIDs for the machine are as follows.

PCI Devices 
PCI\VEN_104C&DEV_8039&SUBSYS_0461107B&REV_00\4&6B16D5B&0&48F0: Generic CardBus Controller
PCI\VEN_104C&DEV_803A&SUBSYS_0461107B&REV_00\4&6B16D5B&0&49F0: Texas Instruments OHCI Compliant IEEE 1394 Host Controller
PCI\VEN_104C&DEV_803B&SUBSYS_0461107B&REV_00\4&6B16D5B&0&4AF0: Mass Storage Controller
PCI\VEN_8086&DEV_109A&SUBSYS_0461107B&REV_00\4&192AC53F&0&00E0: Intel(R) PRO/1000 PL Network Connection
PCI\VEN_8086&DEV_2448&SUBSYS_00000000&REV_E2\3&B1BFB68&0&F0 : Intel(R) 82801 PCI Bridge - 2448
PCI\VEN_8086&DEV_27A0&SUBSYS_00000000&REV_03\3&B1BFB68&0&00 : Mobile Intel(R) 945GM/GU/PM/GMS/940GML/943GML and Intel(R) 945GT Express Processor to DRAM Controller - 27A0
PCI\VEN_8086&DEV_27A2&SUBSYS_0461107B&REV_03\3&B1BFB68&0&10 : Mobile Intel(R) 945 Express Chipset Family
PCI\VEN_8086&DEV_27A6&SUBSYS_0461107B&REV_03\3&B1BFB68&0&11 : Mobile Intel(R) 945 Express Chipset Family
PCI\VEN_8086&DEV_27B9&SUBSYS_00000000&REV_02\3&B1BFB68&0&F8 : Intel(R) ICH7M/U LPC Interface Controller - 27B9
PCI\VEN_8086&DEV_27C5&SUBSYS_0461107B&REV_02\3&B1BFB68&0&FA : Intel(R) ICH7M/MDH SATA AHCI Controller
PCI\VEN_8086&DEV_27C8&SUBSYS_0461107B&REV_02\3&B1BFB68&0&E8 : Intel(R) N10/ICH7 Family USB Universal Host Controller - 27C8
PCI\VEN_8086&DEV_27C9&SUBSYS_0461107B&REV_02\3&B1BFB68&0&E9 : Intel(R) N10/ICH7 Family USB Universal Host Controller - 27C9
PCI\VEN_8086&DEV_27CA&SUBSYS_0461107B&REV_02\3&B1BFB68&0&EA : Intel(R) N10/ICH7 Family USB Universal Host Controller - 27CA
PCI\VEN_8086&DEV_27CB&SUBSYS_0461107B&REV_02\3&B1BFB68&0&EB : Intel(R) N10/ICH7 Family USB Universal Host Controller - 27CB
PCI\VEN_8086&DEV_27CC&SUBSYS_0461107B&REV_02\3&B1BFB68&0&EF : Intel(R) N10/ICH7 Family USB2 Enhanced Host Controller - 27CC
PCI\VEN_8086&DEV_27D0&SUBSYS_00000000&REV_02\3&B1BFB68&0&E0 : Intel(R) N10/ICH7 Family PCI Express Root Port - 27D0
PCI\VEN_8086&DEV_27D2&SUBSYS_00000000&REV_02\3&B1BFB68&0&E1 : Intel(R) N10/ICH7 Family PCI Express Root Port - 27D2
PCI\VEN_8086&DEV_27D8&SUBSYS_0461107B&REV_02\3&B1BFB68&0&D8 : Microsoft UAA Bus Driver for High Definition Audio
PCI\VEN_8086&DEV_27DA&SUBSYS_0461107B&REV_02\3&B1BFB68&0&FB : Intel(R) N10/ICH7 Family SMBus Controller - 27DA
PCI\VEN_8086&DEV_27DF&SUBSYS_0461107B&REV_02\3&B1BFB68&0&F9 : Intel(R) 82801G (ICH7 Family) Ultra ATA Storage Controllers - 27DF
PCI\VEN_8086&DEV_4222&SUBSYS_10008086&REV_02\4&20975680&0&00E1: Intel(R) PRO/Wireless 3945ABG Network Connection
21 matching device(s) found.
USB Devices 
USB\ROOT_HUB\4&1C154916&0                                   : USB Root Hub
USB\ROOT_HUB\4&1C6C53DE&0                                   : USB Root Hub
USB\ROOT_HUB\4&2D9F71CD&0                                   : USB Root Hub
USB\ROOT_HUB\4&2DF67C95&0                                   : USB Root Hub
USB\ROOT_HUB20\4&25C00A81&0                                 : USB Root Hub
5 matching device(s) found.
Input Devices 
No matching devices found.
ACPI Devices 
ACPI\ACPI0003\2&DABA3FF&0                                   : Microsoft AC Adapter
ACPI\FIXEDBUTTON\2&DABA3FF&0                                : ACPI Fixed Feature Button
ACPI\GENUINEINTEL_-_X86_FAMILY_6_MODEL_15\_0                : Intel(R) Core(TM)2 CPU         T7200  @ 2.00GHz
ACPI\GENUINEINTEL_-_X86_FAMILY_6_MODEL_15\_1                : Intel(R) Core(TM)2 CPU         T7200  @ 2.00GHz
ACPI\PNP0000\4&38462492&0                                   : Programmable interrupt controller
ACPI\PNP0100\4&38462492&0                                   : System timer
ACPI\PNP0103\4&38462492&0                                   : High Precision Event Timer
ACPI\PNP0200\4&38462492&0                                   : Direct memory access controller
ACPI\PNP0303\4&38462492&0                                   : Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
ACPI\PNP0A06\3&473F1A46&0                                   : Extended IO Bus
ACPI\PNP0A08\2&DABA3FF&0                                    : PCI bus
ACPI\PNP0B00\4&38462492&0                                   : System CMOS/real time clock
ACPI\PNP0C02\1                                              : Motherboard resources
ACPI\PNP0C02\2                                              : Motherboard resources
ACPI\PNP0C04\4&38462492&0                                   : Numeric data processor
ACPI\PNP0C09\1                                              : Microsoft ACPI-Compliant Embedded Controller
ACPI\PNP0C0A\1                                              : Microsoft ACPI-Compliant Control Method Battery
ACPI\PNP0C0A\2                                              : Microsoft ACPI-Compliant Control Method Battery
ACPI\PNP0C0C\2&DABA3FF&0                                    : ACPI Power Button
ACPI\PNP0C0D\2&DABA3FF&0                                    : ACPI Lid
ACPI\PNP0C0E\2&DABA3FF&0                                    : ACPI Sleep Button
ACPI\SYN0402\4&38462492&0                                   : PS/2 Compatible Mouse
ACPI\THERMALZONE\TZ00                                       : ACPI Thermal Zone
ACPI_HAL\PNP0C08\0                                          : Microsoft ACPI-Compliant System
ROOT\ACPI_HAL\0000                                          : ACPI Multiprocessor PC
25 matching device(s) found.
 HDA Audio 
HDAUDIO\FUNC_01&VEN_8384&DEV_7634&SUBSYS_107B0461&REV_1001\4&34AF940E&0&0001: SigmaTel High Definition Audio CODEC
HDAUDIO\FUNC_02&VEN_1057&DEV_3057&SUBSYS_00010001&REV_1001\4&34AF940E&0&0101: Modem Device on High Definition Audio Bus
2 matching device(s) found.
RAID Devices 
    Name: Mass Storage Controller
    Hardware ID's:
    Compatible ID's:
    Name: Intel(R) ICH7M/MDH SATA AHCI Controller
    Hardware ID's:
    Compatible ID's:
    Name: Intel(R) 82801G (ICH7 Family) Ultra ATA Storage Controllers - 27DF
    Hardware ID's:
    Compatible ID's:
3 matching device(s) found.

I just verified that it also happens with the DP_Sound_A_wnt5_x86-32_1001b1.7z nightly pack as well.  Let me know if you'd like me to try anything else.

I was using the DriverPack Sound A nightly to do a test on a machine and ran into an interesting issue.  Using base 8.12.5, Disk Integration for Windows XP SP3 with only DP_Sound_A_wnt5_x86-32_911b1.7z and DP_Sound_B_wnt5_x86-32_91204.7z loaded the sound didn't work.

I checked device manager and the Realtek High Definition Audio said it was installed fine "This is working properly" under Device status (on the general tab).  I went into control panel under Sounds and Audio Devices and it said at the Top "No Audio Device" and all the buttons were grayed out.

I downloaded the driver from Gateway's site using the link below, and it worked.  It's unsigned, but seems to work just fine.

http://support.gateway.com/support/driv … =257743752

The HWID for the sound card is as follows.

HDAUDIO\FUNC_01&VEN_10EC&DEV_0880&SUBSYS_08600000&REV_0900\4&15631FDD&0&0201: Realtek High Definition Audio

I can do some testing like I did in this post http://forum.driverpacks.net/viewtopic.php?id=4290 with HWID pruning, and creating a new folder if you'd like, but just thought I'd report the issue.

In my own testing, I commented out the line from STHDA.INF in the I10 folder as shown below.  Then I created an I20 folder and copied the contents of the WDM folder in the driver I posted in the first post to it.  Finally repackaged the driverpack, reloaded the machine and the driver in I20 loaded perfectly.


Alright, I reloaded the machine again with DP_Sound_B_wnt5_x86-32_91204.7z to get the information you requested.

Here's the entry in the setupapi.log for the sound card.

#-019 Searching for hardware ID(s): hdaudio\func_01&ven_8384&dev_7618&subsys_107b5058&rev_1002,hdaudio\func_01&ven_8384&dev_7618&subsys_107b5058
#-018 Searching for compatible ID(s): hdaudio\func_01&ven_8384&dev_7618&rev_1002,hdaudio\func_01&ven_8384&dev_7618,hdaudio\func_01&ven_8384,hdaudio\func_01
#-198 Command line processed: "C:\WINDOWS\system32\setup.exe"  -newsetup
#I022 Found "HDAUDIO\FUNC_01&VEN_8384&DEV_7618&SUBSYS_107B5058" in C:\D\S\I10\sthda.inf; Device: "IDT High Definition Audio CODEC"; Driver: "IDT High Definition Audio CODEC"; Provider: "IDT"; Mfg: "IDT"; Section name: "STHDA".
#I023 Actual install section: [STHDA]. Rank: 0x00000001. Effective driver date: 03/12/2009.
#I022 Found "HDAUDIO\FUNC_01&VEN_8384&DEV_7618" in C:\D\S\I7\sthda.inf; Device: "IDT High Definition Audio CODEC"; Driver: "IDT High Definition Audio CODEC"; Provider: "IDT"; Mfg: "IDT"; Section name: "STHDA".
#I087 Driver node not trusted, rank changed from 0x00002001 to 0x0000e001.
#I023 Actual install section: [STHDA]. Rank: 0x0000e001. Effective driver date: 02/27/2008.
#I022 Found "HDAUDIO\FUNC_01&VEN_8384" in C:\D\S\I7\sthda.inf; Device: "IDT High Definition Audio CODEC"; Driver: "IDT High Definition Audio CODEC"; Provider: "IDT"; Mfg: "IDT"; Section name: "STHDA".
#I087 Driver node not trusted, rank changed from 0x00002002 to 0x0000e002.
#I023 Actual install section: [STHDA]. Rank: 0x0000e002. Effective driver date: 02/27/2008.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [STHDA] in "c:\d\s\i10\sthda.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 "HDAUDIO\FUNC_01&VEN_8384&DEV_7618&SUBSYS_107B5058&REV_1002\4&22347350&0&0201".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [STHDA.Interfaces] from "c:\d\s\i10\sthda.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "HDAUDIO\FUNC_01&VEN_8384&DEV_7618&SUBSYS_107B5058&REV_1002\4&22347350&0&0201".
#I163 Device not started: Device has problem: 0x0a: CM_PROB_FAILED_START.
#I121 Device install of "HDAUDIO\FUNC_01&VEN_8384&DEV_7618&SUBSYS_107B5058&REV_1002\4&22347350&0&0201" finished successfully.

Here's the rather uneventful entry in the DPsFnshr.log for the card.

PCI\VEN_8086&DEV_284B&SUBSYS_5058107B&REV_02\3&61AAA01&0&D8 : Microsoft UAA Bus Driver for High Definition Audio
PCI\VEN_8086&DEV_2990&SUBSYS_00000000&REV_02\3&61AAA01&0&00 : Intel(R) Q963/Q965 Processor to I/O Controller - 2990
PCI\VEN_8086&DEV_2991&SUBSYS_00000000&REV_02\3&61AAA01&0&08 : Intel(R) Q963/Q965 PCI Express Root Port - 2991
PCI\VEN_8086&DEV_2994&SUBSYS_5058107B&REV_02\3&61AAA01&0&18 : Intel(R) Management Engine Interface
PCI\VEN_8086&DEV_2996&SUBSYS_5058107B&REV_02\3&61AAA01&0&1A : Standard Dual Channel PCI IDE Controller
PCI\VEN_8086&DEV_2997&SUBSYS_5058107B&REV_02\3&61AAA01&0&1B : Intel(R) Active Management Technology - SOL (COM3)
26 matching device(s) found.

2010-01-20 10:54:09 : <INIT> 3. HDAUDIO devices

HDAUDIO\FUNC_01&VEN_8384&DEV_7618&SUBSYS_107B5058&REV_1002\4&22347350&0&0201: IDT High Definition Audio CODEC
1 matching device(s) found.

The Windows Event Viewer only has one entry that happens a few times and its Event ID 7000 Source: Service Control Manager saying "The Audio Service service failed to start due to the following error:
The system cannot find the path specified. "

Hope this is helpful.

I wiped the machine prior to being able to look at the event viewer but I'd be happy to reload the machine again and see what I get.  Are you talking about the Windows Event Viewer or is the info you're looking for something that could be found in one of the driverpacks logs like DPsFnshr.log?  Either way, let me know and I'll get the information you're looking for.

First off I'm just going to say thanks for all your continued efforts on these packs.  I'm using a not so normal way of loading Windows XP Pro on these machines so it's not really a true "Disk" method integration, but I don't think that's the issue.

After driverpacks failed to install the driver (which is very rare) I went to gateway's site and loaded driver from their website.  I posted the link below to that driver.  After it was successfully loaded I ran FindHWIDs.exe and got the HWID for the sound card.  I extracted the DriverPack Sound B nightly pack and used Agent Ransack to search within that folder for the HWID, and found it in the D\S\I10 folder.  I uninstalled the working driver and tried to manually install the driver in the I10 folder but it failed just like the original item.  I'm not sure if that means you need to change that driver, or prune that HWID and add the driver that I posted, but whatever you guys decide to attempt I'll be more than happy to test any nightly pack you put together and report back.  Thanks again guys for all your time.

Base - 8.12.5
DriverPack - DP_Sound_B_wnt5_x86-32_91204.7z (nightly)
Problems HWID - HDAUDIO\FUNC_01&VEN_8384&DEV_7618&SUBSYS_107B5058&REV_1002\4&22347350&0&0201: SigmaTel High Definition Audio CODEC
Working Driver - http://support.gateway.com/support/driv … =257560544

Thanks to everyone in this forum for working so diligently on these packs.  I’ve been testing the Graphics B 911rc9 and 911rc10 driverpacks because I noticed they included the FireMV series cards and noticed one thing missing.  I originally had the same problem when I made a 3rd party pack for these cards.  You seem to have one file missing from your AE\B_76015 folder and that’s atiicdxx.dat.  If I extract those RC driverpacks and manually try to install the driver in the AE folder you receive a message saying “Setup cannot copy the file atiicdxx.dat.”  When you extract the FirePro_8.583_XP32_77157.exe (or whatever version you’re working with) that file is found in the \$HWNDPARENT\BIN folder.  I changed nothing with the DPGPB rc10 pack except adding that file to the B_76015 folder and then the driver loads perfectly on a FireMV 2250, FireGL V7100, and FirePro V5700.

Nice work on all the new driverpacks.  For the 4 nVidia Quadro Cards we have all the drivers work flawlessly, as do all the Intel integrated graphics controllers I've tested on so far.  I did run into the same problem that I had a few months ago with the DriverPacks C pack.   Here is the previous post.  http://forum.driverpacks.net/viewtopic.php?id=3223  Basically again because the driver signing is broken in the N4 folder by default Windows XP uses the driver that Windows XP has natively instead of the newer one in the N4 folder.  Just like before if I rename the nv4_dispinf.bak and re-package the driverpack it works fine for me.  Thanks to everyone involved with these driverpacks.  Oh, also I'm using DP_Graphics_C_wnt5_x86-32_8121.7z

Nevermind, I guess I'm just bad at reading.  I see you broke driver signing on purpose to avoid the hwid overlap.  I guess until I run into a problem with using the original inf I'll just leave it this way for myself....