1

(19 replies, posted in DriverPack Sound)

if we were centrally located, yes, unfortunately its across ~30 locations over the entire US, that much traffic over the WAN doesn't work out well

2

(19 replies, posted in DriverPack Sound)

awesome, working as intended.  mr_smartepants, Major, thank you both for your assistance, now to spend about 5 hours burning DVD's to distribute to the other sites and schedule a deployment timeline for 4000 pc's lol

3

(19 replies, posted in DriverPack Sound)

sorry if I was being unclear, I don't do things that way, I'm modifying the original image source(reimaging my pre-sysprepped build onto the original machine, making the changes to the driverbase, putting paths in registry, taking a new ghost image of the steps up to this new point, sysprepping it, and taking a ghost image of the new sysprepped machine) I don't use nlite or slipstream anything in.  My build gets shipped out on DVD's and external harddrives to multiple locations from here and used on the company machines nationwide.  I've found its just easier and saves typing to say rebuilding sources and image.

I apologize if I was unclear, but most of what I'm doing is well within the "best practices" as I know them, but thank you for trying to prevent me from making a mistake beyond the one I already made!

4

(19 replies, posted in DriverPack Sound)

ok, let me rebuild sources and the image, I'll re-sysprep and package everything up and report back

5

(19 replies, posted in DriverPack Sound)

http://rapidshare.com/files/360832064/s … 0.log.html

6

(19 replies, posted in DriverPack Sound)

file is too big to post, for some reason it's not finding the I9 folder as a match for the hardware, if an admin or whoever wants to email me with their email I can ship the file off to you

7

(19 replies, posted in DriverPack Sound)

Windows finds the device and installs the driver, but I still get a "device cannot start".  I'll keep playing with it and monitor the forums for any updates

-edit
found part of the issue was the revision in question, the new revision of E6400's use a different driver

ftp.us.dell.com/audio/IDT_92HDXXX-HD-Audio_A06_R213367.exe

from previous places on the forum it seems that the 21366 revision was used, and trying a manual install, that didnt work on this notebook.  Using the current install it worked fine.  Dell service for corporate systems is great... but their hardware stability sucks.

8

(19 replies, posted in DriverPack Sound)

let me slip it into my presysprep image and repackage it, I'll report back tomorrow with a yea or nay

9

(19 replies, posted in DriverPack Sound)

I'm working on pushing a ghosted XP SP3, fully updated build out to very diverse machines, and have traditionally had no issues whatsoever with drivers, but this one just keeps popping up.  I saw a thread that mentioned this HWID, that pointed to the "nightly builds" and seeing as how I'm not a tester I don't have access to this unless someone posts a link.  Anyone know if this ever got integrated and how I could get a copy?


SOURCE XP SP3 X32
HWID HDAUDIO\FUNC_01&VEN_111D&DEV_76B2&SUBSYS_10280233&REV_1003\4&380800DF&0&0001  - IDT High Definition Audio Codec
SoundA - 805
SoundB - tried 805 and 906b(found link somewhere and couldnt get A to download)