Update; fixed it!

So I'm trying to get DP_Install_Tool.cmd to start (post-install) on my Windows 8.1 unattended ISO and for the life of me I just can't. I realized early on that I was incorrectly using the win7 setupcomplete.cmd when in fact this is now called firstlogon.cmd for Win8 in the dvd\...\scripts folder. Still no dice. When I run the DP cmd manually in the DVD $OEM$ location after I reach a freshly installed 8.1 desktop it runs (of course) perfectly.

Help me here, completely stumped. The tool works great, I just want the tool's DP cmd to automatically launch after an 8.1 installation completes.

The lone text in the firstlogon.cmd is;
@echo off
START %systemdrive%\DP_Install_Tool.cmd /S
DEL %0

Fix; reverted back to setupcomplete.cmd (not sure what the difference is between this and firstlogon, I think setupcomplete is guaranteed to work under system account before oobe), just made a simple set %DVD% and start the DP cmd tool from a folder at the root of the iso. So I guess the problem before was having all the driverpack stuff in the $OEM$ folder (which copies to C:). In fact I prefer the tool launch from the ISO anyway.

What do I need to do to get this to run in Win 8.1 x64? I see references to the script supporting Windows 8.1, but upon running, I get a "windows 8.1 Pro - which uses DriverPacks - not currently supported - please the exit program now" and prompt to exit

Edit; using the latest version available on the 1st page link SAD3-130627


(88 replies, posted in DriverPack LAN)


http://downloadcenter.intel.com/Detail_ … ldID=21228


(88 replies, posted in DriverPack LAN)

ChiefZeke wrote:

Version 17.1 released: XP Pro and Win7 32/64 bit versions

http://downloadcenter.intel.com/Detail_ … ldID=18717


(88 replies, posted in DriverPack LAN)

mr_smartepants wrote:

Already in work. wink

- At\ Atheros AR813X/AR815X Series PCI-E Ethernet Controller DriverVer = 12/23/2011,
- I\ Intel from 17.0 CD (3/23/2012)
- M\ Marvell Yukon Ethernet Controller to DriverVer = 03/23/2012,
- R4\ Realtek 10/100/1000 PCI-E NIC Family NDIS XP DriverVer = 02/22/2012,5.794.0222.2012

Oh neat, you have a URL for that nightly?

Updated request to include 3rd generation HD gfx support
http://downloadcenter.intel.com/Detail_ … ldID=21134


(88 replies, posted in DriverPack LAN)


http://downloadcenter.intel.com/Detail_ … ldID=18717

Saw this on station-drivers, not on intel just yet but Samsung is using them on their latest laptop images

http://www.samsung.com/us/support/downl … 0X3A-A03US
Drivers tab


(88 replies, posted in DriverPack LAN)

Just for posterity, I'll update REQ to 16.8.1 wink

http://downloadcenter.intel.com/Detail_ … ldID=20739

And wow, read the release notes!

If you installed software version 16.8, you must remove the software before you can install version 16.8.1.
- The version 16.8.1 software has replaced the version 16.8 software package.
- The version 16.8.1 software package contains a bug fix to the Windows driver for the Intel(R) 82579V Gigabit Network Connection.

Updated request to v14.46.9.5394

Updated request to

http://downloadcenter.intel.com/Detail_ … ldID=20792

How would I invoke this to run unattended? Say for example I want to bypass all Y/N prompts because I just want this to run in SetupComplete.cmd in a Windows 7 x64 install?


(88 replies, posted in DriverPack LAN)

16.8 http://downloadmirror.intel.com/20739/eng/V16_8_CD.zip

http://downloadcenter.intel.com/Detail_ … ldID=21594


(88 replies, posted in DriverPack LAN)



The 11.071 beta:


(88 replies, posted in DriverPack LAN)

http://downloadcenter.intel.com/Detail_ … ldID=20232


http://support.lenovo.com/en_US/downloa … MIGR-77009

Finally saw this on a big OEM website today outside of station drivers.

Station drivers has had their intel drivers segmented between HD 1st generation and 2nd for a while now, the latest 2nd appears to be version (package 14.46.5), which lenovo now officially uses.

mr_smartepants wrote:

Well, if you add the drivers to the install.wim with DISM then you're going to have all the drivers remain even after install...significant bloat.
The method I prefer (to minimize the driverstore bloat) is to only integrate dpms & Chipset and use my SAD2 script post-install.  Using dpinst.exe ensures that only the drivers that are needed are installed and the script cleans up after itself.  I'm still planning on getting DriverPacks Finisher to work in an NT6 environment.

Ok, cool! Before I start here with your SAD2 package - is it ready for testing on 7 x64 installs? Or is DriverPacks Finisher required to get this working?

Time to revisit this question - how to have a completely unattended *UNIVERSAL* install that has all driver packs available to install but at the end of the day results in the particular PC having only the drivers it needs stored in the filerepository? As in, just like we do so easily with UA XP installs.


(85 replies, posted in Vista / 7 DriverPack Chipset)

mr_smartepants wrote:

Ah, that's because I stupidly deleted the i386 folder.  Fixed in my local copy of DriverPack Chipset 11.06

No worries friend! All in all, the latest DP releases are pretty slick. As you can tell by my flurry of posts, I was doing a few updates to my integration base, so thought I'd report which folders had gremlins. smile


(21 replies, posted in 3rd Party Vista / 7 DriverPacks)

FYI: Logitech folder "2" and Philips folder "1" fail to integrate with DISM on Windows 7 x64. The rest integrate fine (code = '0')


(85 replies, posted in Vista / 7 DriverPack Chipset)

FYI: The FTDI folder with ftdibus.inf fails to integrate via DISM on Windows 7 x64, all the rest integrate fine (code = '0')


(78 replies, posted in Vista / 7 DriverPack Audio)

FYI: Creative folder "6" fails to integrate via DISM (has SBXF and XFHX folders) for Windows 7 x64, all others integrate fine (code '0')