(My OS is XP professional SP2)
You must update to SP3.
SP3 contains a hotfix that allows ALL HDaudio devices to be detected correctly. They will fail otherwise.
You are not logged in. Please login or register.
DriverPacks.net Forum » Posts by mr_smartepants
(My OS is XP professional SP2)
You must update to SP3.
SP3 contains a hotfix that allows ALL HDaudio devices to be detected correctly. They will fail otherwise.
PS: Have you thought about joining the testing team?
Sure, how do i join?
You just did.
You'll notice that several new forums have been opened to you.
Oops, I'll need to fix that...
Caveat: I don't use Win8 (probably never will...)
I do need to modify the SAD2 code to recognize Win8 for the folder-delete option though.
Maybe in the future, but not now. What we need is a database/index of HWIDs and matching drivers to extract from.
Well, you could always call the utility with the /s (silent) switch.
START %systemdrive%\D\SAD2\DP_Install_Tool.cmd /s
Or just change the line: SET "SILENT=N"
to
SET "SILENT=Y"
And yes, it will work in Win8 Pro. It will NOT work in Win8RT.
Can you post your DPsFnshr.log so we can see?
DOS!?!?! :?
DOS is dead! That notebook comes with Windows7 (or should). It will have an OEM license sticker for Win7...use that!
I don't know what to tell you. I don't get those errors.
******************************************
** Beginning driver injection to index 1
** Index: 1 is Microsoft Windows PE x64
** Using the command: DISM /image:"C:\Output\mount" /Add-Driver /driver:"C:\Input\Drivers\Boot" /recurse /forceunsigned /LogPath:"C:\Output\Logs\Utility.log" /LogLevel:"2"
The operation completed successfully.
******************************************
** Listing all 3rd party drivers in index 1
DISM /image:"C:\Output\mount" /Get-Drivers /Format:Table
Deployment Image Servicing and Management tool
Version: 6.1.7600.16385
Image Version: 6.1.7600.16385
Obtaining list of 3rd party drivers from the driver store...
Driver packages listing:
-------------- | ------------------ | ----- | ----------- | ---------------------------- | ---------- | -------------
Published Name | Original File Name | Inbox | Class Name | Provider Name | Date | Version
-------------- | ------------------ | ----- | ----------- | ---------------------------- | ---------- | -------------
oem0.inf | arcvdev.inf | No | System | Areca Technology Corporation | 11/6/2009 | 6.20.0.19
oem1.inf | oemsetup.inf | No | SCSIAdapter | Areca Technology Corporation | 11/6/2009 | 6.20.0.19
oem10.inf | hptiop.inf | No | SCSIAdapter | HighPoint | 4/28/2009 | 1.2.28.28
oem11.inf | hptrcm.inf | No | System | HighPoint | 4/23/2009 | 1.2.28.23
oem12.inf | hptmv.inf | No | SCSIAdapter | HighPoint | 8/1/2006 | 1.1.9.801
oem13.inf | hptmv6.inf | No | SCSIAdapter | HighPoint | 10/26/2007 | 1.9.7.1026
oem14.inf | 272x_1x.inf | No | SCSIAdapter | HighPoint | 4/24/2012 | 1.2.12.424
oem15.inf | 274x_3x.inf | No | SCSIAdapter | HighPoint | 4/24/2012 | 1.1.12.424
oem16.inf | rr276x.inf | No | SCSIAdapter | HighPoint | 4/24/2012 | 1.1.12.424
oem17.inf | rr278x.inf | No | SCSIAdapter | HighPoint | 4/24/2012 | 1.1.12.424
oem18.inf | rr62x.inf | No | SCSIAdapter | HighPoint | 6/15/2010 | 1.2.10.615
oem19.inf | iaahci.inf | No | hdc | Intel | 11/6/2010 | 10.1.0.1008
oem2.inf | asahci64.inf | No | hdc | Asmedia Technology | 1/5/2012 | 1.3.4.0
oem20.inf | iastor.inf | No | SCSIAdapter | Intel | 11/6/2010 | 10.1.0.1008
oem21.inf | iaahci.inf | No | hdc | Intel | 10/17/2011 | 10.8.0.1003
oem22.inf | iastor.inf | No | SCSIAdapter | Intel | 10/17/2011 | 10.8.0.1003
oem23.inf | iaahcic.inf | No | HDC | Intel Corporation | 9/1/2012 | 11.6.0.1030
oem24.inf | iastorac.inf | No | SCSIAdapter | Intel Corporation | 9/1/2012 | 11.6.0.1030
oem25.inf | iaahci.inf | No | SCSIAdapter | Intel Corporation | 6/20/2012 | 3.2.0.1126
oem26.inf | iastora.inf | No | SCSIAdapter | Intel Corporation | 6/20/2012 | 3.2.0.1126
oem27.inf | iastors.inf | No | SCSIAdapter | Intel Corporation | 6/29/2012 | 3.2.0.1132
oem28.inf | iteraid.inf | No | SCSIAdapter | ITE Tech. Inc. | 9/17/2007 | 1.7.2.9
oem29.inf | iteatapi.inf | No | SCSIAdapter | ITE Tech. Inc. | 5/14/2008 | 1.3.4.3
oem3.inf | rr172x.inf | No | SCSIAdapter | HighPoint | 10/29/2007 | 1.1.7.1029
oem30.inf | jmide.inf | No | hdc | JMicron Technology Corp. | 9/16/2006 | 1.0.0.0
oem31.inf | jraid_f.inf | No | SCSIAdapter | JMicron Technology Corp. | 5/19/2011 | 1.17.63.1
oem32.inf | jraid_i.inf | No | SCSIAdapter | JMicron Technology Corp. | 5/19/2011 | 1.17.63.1
oem33.inf | megasr1.inf | No | SCSIAdapter | LSI | 5/28/2012 | 15.0.528.2012
oem34.inf | nodev.inf | No | System | LSI Corporation. | 5/28/2012 | 15.0.528.2012
oem35.inf | nodev.inf | No | System | LSI Corp. | 11/20/2008 | 3.9.0.64
oem36.inf | oemsetup.inf | No | SCSIAdapter | LSI Corp., | 11/20/2008 | 3.9.0.64
oem37.inf | nodev.inf | No | System | LSI Corp. | 2/14/2008 | 2.20.0.64
oem38.inf | oemsetup.inf | No | SCSIAdapter | LSI Corp., | 2/14/2008 | 2.20.0.64
oem39.inf | lsi_fc.inf | No | SCSIAdapter | LSI Corporation | 8/29/2007 | 1.26.1.0
oem4.inf | rr174x.inf | No | SCSIAdapter | HighPoint | 10/23/2007 | 2.0.7.1023
oem40.inf | mv61xx.inf | No | SCSIAdapter | Marvell Inc. | 5/6/2011 | 1.2.0.8300
oem41.inf | mvnodrv.inf | No | System | Marvell Inc. | 5/6/2011 | 1.2.0.8300
oem42.inf | mv91cons.inf | No | System | Marvell Semiconductor Inc. | 1/19/2012 | 1.2.0.1020
oem43.inf | mvnodrv.inf | No | System | Marvell Inc. | 1/19/2011 | 1.2.0.1020
oem44.inf | mvs91xx.inf | No | SCSIAdapter | Marvell Inc. | 1/19/2012 | 1.2.0.1020
oem45.inf | nvstor64.inf | No | HDC | NVIDIA Corporation | 8/4/2009 | 11.1.0.33
oem46.inf | nvrd64.inf | No | SCSIAdapter | NVIDIA Corporation | 8/4/2009 | 11.1.0.33
oem47.inf | nvstor64.inf | No | HDC | NVIDIA Corporation | 4/9/2010 | 11.1.0.43
oem48.inf | nvrd64.inf | No | SCSIAdapter | NVIDIA Corporation | 4/9/2010 | 11.1.0.43
oem49.inf | megasr.inf | No | SCSIAdapter | LSI Corporation. | 1/20/2009 | 13.4.120.2009
oem5.inf | 2310_00.inf | No | SCSIAdapter | HighPoint | 6/11/2009 | 2.3.9.611
oem50.inf | nodev.inf | No | System | LSI Corporation. | 1/20/2009 | 13.4.120.2009
oem51.inf | si680.inf | No | SCSIAdapter | Silicon Image | 11/13/2007 | 1.2.7.0
oem52.inf | si3112.inf | No | SCSIAdapter | Silicon Image | 4/13/2007 | 1.3.68.2
oem53.inf | si3112.inf | No | SCSIAdapter | Silicon Image | 4/13/2007 | 1.2.14.2
oem54.inf | si3112r.inf | No | SCSIAdapter | Silicon Image | 2/1/2007 | 1.0.12.0
oem55.inf | si3114.inf | No | SCSIAdapter | Silicon Image | 11/10/2006 | 1.2.8.0
oem56.inf | si3114r.inf | No | SCSIAdapter | Silicon Image | 4/10/2007 | 1.0.14.0
oem57.inf | si3124.inf | No | SCSIAdapter | Silicon Image | 8/22/2006 | 1.1.13.0
oem58.inf | si3124r5.inf | No | SCSIAdapter | Silicon Image | 9/20/2006 | 1.5.11.0
oem59.inf | sippd.inf | No | System | Silicon Image | 9/20/2006 | 1.5.11.0
oem6.inf | rr2210.inf | No | SCSIAdapter | HighPoint | 10/17/2007 | 1.3.7.1017
oem60.inf | si3132.inf | No | SCSIAdapter | Silicon Image | 10/3/2007 | 1.0.15.0
oem61.inf | si3132r5.inf | No | SCSIAdapter | Silicon Image | 9/17/2008 | 1.5.19.0
oem62.inf | sippd.inf | No | System | Silicon Image | 9/17/2008 | 1.5.19.0
oem63.inf | si3531.inf | No | SCSIAdapter | Silicon Image | 6/4/2009 | 1.5.20.1
oem64.inf | sippd.inf | No | System | Silicon Image | 6/4/2009 | 1.5.20.1
oem65.inf | vminiide.inf | No | hdc | VIA Technologies, Inc. | 8/13/2009 | 7.0.7000.294
oem66.inf | viamrx64.inf | No | SCSIAdapter | VIA Technologies, Inc. | 11/26/2010 | 6.0.7600.6240
oem67.inf | vmci.inf | No | System | VMware, Inc. | 2/16/2012 | 9.3.51.0
oem68.inf | vmscsi.inf | No | SCSIAdapter | VMware, Inc. | 5/14/2012 | 2.0.3.0
oem69.inf | amd_sata.inf | No | HDC | AMD | 4/11/2012 | 1.2.1.331
oem7.inf | rr232x.inf | No | SCSIAdapter | HighPoint | 4/9/2008 | 1.9.8.409
oem70.inf | ahcix64s.inf | No | SCSIAdapter | Advanced Micro Devices, Inc. | 7/1/2009 | 3.1.1540.151
oem71.inf | nodrv.inf | No | System | Advanced Micro Devices, Inc. | 7/1/2009 | 3.1.1540.151
oem72.inf | ahcix64s.inf | No | SCSIAdapter | Advanced Micro Devices, Inc. | 12/29/2011 | 3.3.1540.29
oem73.inf | megasas2.inf | No | SCSIAdapter | LSI Corp. | 2/22/2012 | 5.2.116.64
oem74.inf | nodev.inf | No | System | LSI Corp. | 2/22/2012 | 5.2.116.64
oem75.inf | lsi_sas.inf | No | SCSIAdapter | LSI Corporation | 12/7/2010 | 1.34.2.0
oem76.inf | lsinodrv.inf | No | System | LSI Corporation | 5/1/2009 | 1.0.7.0
oem77.inf | lsi_sas2.inf | No | SCSIAdapter | LSI Corporation | 3/1/2012 | 2.0.55.1
oem78.inf | lsinodrv.inf | No | System | LSI Corporation | 5/1/2009 | 0.0.4.0
oem8.inf | rr2340.inf | No | SCSIAdapter | HighPoint | 12/31/2009 | 1.7.9.1231
oem9.inf | rr2522.inf | No | SCSIAdapter | HighPoint | 12/31/2009 | 1.2.9.1231
The operation completed successfully.
******************************************
How can i solve this problem??
So the drivers that came with the card didn't work? I'd return it for a refund then.
Which drivers specifically are failing to install?
Are you sure those drivers are meant for Win7 and/or have all the files associated with them?
I integrated the current dpms in my copy of Win7 using the "All" and "Win7" folders without any problems.
Is Drive:E a hard drive or DVD?
The command to inject drivers has the /image flag in the wrong place.
Example: Dism /image:%mount% /Add-Driver /driver:%drivers% /recurse
So you second line sould look like this:
Dism /image:C:\mount /Add-Driver /driver:E:\M /recurse
In the DP_MS 'mod, i would have liked to combine folders as in Chipset. How do i accomplish this in MS.ini?
You'd need to either have all the drivers in a single folder (dupes not allowed) or in sub-folders.
A great example of both storage options can be found in .ini headers [P] and [P-K]/[P-S].
Folder \D\M\P\ has loads of drivers loose in that folder as well as sub-folders \K and \S.
The .ini header [P] has each driver assigned its own subsection.
The .ini headers [P-K] and [P-S] have been separated from the main \P group for Win2k and Server OS. The .ini header includes a dash (-) to indicate a sub-folder. Sub-folders are not ideal as they add additional characters to the folder path for each additional '\'.
So [P-K] in the header would translate to \D\M\P\K\ and [P-K-1-A] in the header would translate to \D\M\P\K\1\A\.
Thanks for all the work on this! I just seem to have zero free time lately.
When using SAD2 to install the DriverPacks...yes.
Provided we have the current drivers needed by that system in our DriverPacks.
Some of our packs haven't been updated in a while.
Some will work while others won't. Windows 8 uses a new Windows Display Driver Model (WDDM) 1.2 which is incompatible with some older drivers.
And yes, DriverPacks will support all OS as best we can.
Nope. But I'm eyeing the Lenovo Yoga...
http://www.lenovo.com/products/us/lapto … 13/?cid=us
It doesn't matter as long as all the drivers are inside the \x64 folder.
For Win7 installations you should keep the "All" folder as well as the "Win7" folder. It's safe to delete the "Vista" and "Server" folders but will cause no problems if you leave them.
After Setup?
You want SAD2.
Yes, AMD has switched their XP releases to quarterly. 12.8 was their last official release for XP. If they follow their "4 times a year" rule, then they may release again in 12.12.
Nvidia is planning something similar, though no official word yet.
DriverPacks support for XP is slowing down considerably.
If you're referring to the autorun.inf file (there is no .hta file) then change the contents to read:
[autorun]
OPEN=DP_Install_Tool.cmd /s
Already in work...downloaded from the main Intel site though (don't trust station-drivers!)
Glad you fixed it. Odd that it was caused by a VMware driver.
For drivers? Yes.
You want SAD2. http://forum.driverpacks.net/viewtopic.php?id=5336
1.If I run this in windows 7 the local drive won't be cleaned? Is that what you mean In to do list by referring the finisher?
2.This script does not include sata drivers like xp's textmode so I won't be able to identify an unknown sata disc or raid with it... Is it true?
3.Can It run itself from a usb flash drive or disk?
1. The local drive WILL be cleaned up after install. All working files are copied to %systemdrive%\D\ and after install the entire \D\ folder is deleted (unless you enabled 'KTD').
2. True (partially). This script does not inject drivers into the disc boot.wim. If your drive/RAID controller is already 'seen' by the system, then this utility will update the drivers for it.
3. Yes. It can be run from anywhere.
Please post the HWIDs of the PC with the problems.
DriverPacks.net Forum » Posts by mr_smartepants
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.092 seconds, 6 queries executed ]