You are not logged in. Please login or register.
Active topics Unanswered topics
Search options
OverFlow wrote:if you have time check to see if there is a newer driver for that device... If so we can update the pack and see if that fixes it!
be sure to test it and make sure it works or no sense in adding it to the pack 
its 2 different hardware devices though. Sigmatel and Realtek HD Audio. I wonder if anyone else is able to test/replicate 
going back to my original problem (namely having to remove and readd the sound driver)
Is this likely to be a problem with SAD or the driver pack itself? I have a work around, but I'd prefer that i didn't have to (because scripting a reboot after the "automagic" driver install after a devcon rescan is a pita).
mallen wrote:I am at the point where every driver is good except the sound on one of the two machines. The crazy part is, is that it says it is installed correctly (Device manager shows the correct driver - SigmaTel High Definition Audio Codec - is installed and "is working correctly". However it's not. No sound is produced from either headphones or internal speakers. If I go to start->programs->accessories->entertainment->volume control, Windows exclaims that there is no active mixer devices available.
I tried using both SP2 with the KB88811 fix (microsoft HD audio driver) installed and also I tried using a base image of SP3. Both times, one model works fine (the one with RealTek sound), and the older model (with Sigmatel audio) unexplainably doesn't work.
I have this exact problem - see http://forum.driverpacks.net/viewtopic.php?id=4449
I believe the answer in the short term will be in the form of a DEVCON device "uninstall", then a DEVCON Scan for new hardware. Long term, hopefully the problem can be resolved without post-driver scripts.
(This is the Sigmatel HD Audio Codec as per a Dell D630 Laptop - get the actual code from devcon driverfiles HDAUDIO*)
devcon remove HDAUDIO\FUNC_01*VEN_8384*DEV_76A0*
devcon rescan
Im going to try nightlies of the affected drivers (as well as DP_Base) as i have other wierd issues on my 2 test platforms;
1. Dell D630 Intel 965 Express driver installs, but leaves a second entry under display adapters - "Update Driver automagically" fixes this.
2. Acer TM6493 laptop has an "!" on its Built-in IR Port.
It also might sort my sound problems out (fingers crossed), I also have a problem with Intel Mass Storage not working right (BSOD on boot in AHCI mode) - trying DriverPack MS Nightly.
OverFlow wrote:alternately you could try running SAD twice... IE sometimes certain drivers will depend on others, hda depends on hdabus (hdabus=KB888111), hdabus depends on pcibus, no hdabus then no hda this would require two / three passes Test: run SAD reboot run SAD agian... does it work now?
Twice = no go. (specifically run SAD, reboot, run SAD again).
Will try adding chipset to OEMPNPDriversPath, then reimaging.
Uninstall, Scan and then Windows "automagics" it works fine however (no online connectivity, i'd assume its pulling it from the driver cache after SAD puts it there), no reboot required.
http://users.on.net/~randomtask/DPsFnshr-tm6493-2.log
http://users.on.net/~randomtask/DPINST-tm6493-2.LOG
http://users.on.net/~randomtask/setupapi-tm6493-2.log
*edit*
Same again with OEMPNPDrivers for Chipset.
The driver works - I just think its installing wrong or something.
OverFlow wrote:My impression was the limit of a DevicePath reg entry was the limit of any single reg entry one megabyte?
We have been having an issue with no drivers being installed when too many 3rd party DriverPack were used...
Can you show me where you found it documented that the devpath limit was 64k? that would really help us!
Source was here - http://blog.remyservices.net/2007/09/28 … -image-pc/
further reading tells me that its not quite that long...
http://support.microsoft.com/kb/256986
The following table lists the data types that are currently defined and that are used by Windows. The maximum size of a value name is as follows:
* Windows Server 2003, Windows XP, and Windows Vista: 16,383 characters
* Windows 2000: 260 ANSI characters or 16,383 Unicode characters
* Windows Millennium Edition/Windows 98/Windows 95: 255 characters
Long values (more than 2,048 bytes) must be stored as files with the file names stored in the registry. This helps the registry perform efficiently. The maximum size of a value is as follows:
* Windows NT 4.0/Windows 2000/Windows XP/Windows Server 2003/Windows Vista: Available memory
* Windows Millennium Edition/Windows 98/Windows 95: 16,300 bytes
Note There is a 64K limit for the total size of all values of a key.
Either way its more than 4096/2048. - my programmer friend tells me its 16k, unlimited if you point to a file somewhere (although i am unsure if you can do that for this particular key).
I also found these tools helpful - http://technet.microsoft.com/en-au/maga … light.aspx - specifically PNPPath.vbs (which can apply both the registry and an .inf file).
Thanks, will look into this
OverFlow wrote:OEMPNPDriversPath has a limit of 4096 in normal windows installation, and half that in SysPrep. If you exceed a path length of 2048 in sysprep then either nothing is installed or only the first 2048, usually nothing .
I suggest you include chipset in OEMPNPDriversPath, that may cure your issue.
What about using the reg entry? HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\DevicePath
My understanding was you were allowed 64,000 there? (I tried both)
OverFlow wrote:Also I highly recomend you take a long hard look at OLSP (Off Line SysPrep by Galapo).
I looked at that, I couldn't really find much in the way of a tutorial (or even a base idea). Is the idea you build an image to be sysprepped, then shutdown, boot BartPE with OLSP and do it that way? Any further info on a good starting point with OLSP would be nice.
OverFlow wrote:alternately you could try running SAD twice... IE sometimes certain drivers will depend on others, hda depends on hdabus (hdabus=KB888111), hdabus depends on pcibus, no hdabus then no hda this would require two / three passes Test: run SAD reboot run SAD agian... does it work now?
Will test this before doing below.
OverFlow wrote:Let me know if the issue still persists after you add chipset to your base install.
Will try doing this next run (S.A.D is missing a few things from our images, trying to add them via OEMPNPDriversPath - if that works, then I'll try add chipset).
Thanks for the help.
Ahh ok.
Essentially what i'm doing is
Sysprepped image with only f6 mass storage applied (we only have intel to worry about), single boot then dump a local copy of S.A.D over the top for drivers. I tried to do the whole lot in OEMPNPDriversPath - ended up with Zero drivers.
Base image is a slipstreamed SP3 install, patched to the hilt (or wednesday last week).
here is the setupapi.log file - http://users.on.net/~randomtask/setupapi-tm6493.log
Test machines are a Dell D630 laptop and an Acer Travelmate 6493.
So I have built a SAD disk with DP_Base 8.12.5 and DP_Sound_A_wnt5_x86-32_1003, DP_Sound_B_wnt5_x86-32_1003 and I'm having a bit of a problem.
When applied to a fresh install of XP, the sound driver installs - but doesn't work until I remove the HD Audio driver (both Sigmatel HD Audio Codec and Realtek HD Audio - 2 machine types doing it) then re-add it via "scan for new hardware".
Any thoughts as to why? Or if i can script removing the driver (uninstall) then re-adding them?
Posts found [ 9 ]
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.014 seconds, 5 queries executed ]