Search options (Page 4 of 159)

Report it!
http://windows.microsoft.com/en-us/wind … -microsoft

Those are for Windows 7.  This thread is for NT5.
Moved text to this thread: http://forum.driverpacks.net/viewtopic. … 261#p50261

Welcome to DriverPacks.net!
We support DriverPacks and their usage in Windows.
Please post details of what you did to inject DriverPacks into your Windows and how DriverPacks did not work for you.
Specifically we need your HWID list (use the tool linked in my signature), and the log files for the tool you used to integrate DriverPacks into your Windows 7 OS (DISM, SAD, WinToolkit, etc.)
If you didn't use any tools, and are simply looking for information, we have several stickied posts in this section for users like you.
http://forum.driverpacks.net/viewforum.php?id=45
http://forum.driverpacks.net/viewforum.php?id=47

Interesting...The above files have been removed and the link is dead.
Using the below link, looks like RST 12.5 is the current version.
https://downloadcenter.intel.com/Search … C2%AE+RST)

There are only two instances and they are in the same section.

FOR %%i IN (3 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z) DO (DIR %%i: && IF /I EXIST "%D_DPSLocation%\%%i\" (SET "F_Method=1" & GOTO Message2))
ECHO Searching Root folders since DriverPacks were not found in current folder...
FOR %%i IN (C D E F G H I J K L M N O P Q R S T U V W X Y) DO (
 DIR %%i:
 IF /I EXIST "%%i:\OEM\bin\un7zip.exe" (SET "F_Method=2")
 IF /I EXIST "%%i:\$OEM$\$1\D\" (SET "D_DPSLocation=%%i:\$OEM$\$1" & SET "F_Method=1" & %%i)
 IF "%F_Method%" GEQ "1" GOTO Message2
 )

I'll try and find time to upload the whole package when I get home from work.

Please read the Read BEFORE you post. link in my signature and upload your HWID list and log files so we can figure out what is going wrong.
Think about this; can we reproduce the scenario which caused your problem by the information you provided?  No.
Please help us to help you.

DriverPacks BASE is only for older Windows (2000, XP, 2003).  For newer Windows you need to use DISM (built-in tool).
Here's a post on how to do it manually.
http://forum.driverpacks.net/viewtopic.php?id=3716

More info:
http://forum.driverpacks.net/viewtopic.php?id=4725

I wrote some simple scripts to take care of it all.  They can be found here:
http://forum.driverpacks.net/viewtopic.php?id=5199

If you want a tool that can hold your hand for the entire process, then check out WinToolkit over at the Wincert forums.
We don't directly support their tool though.
http://www.wincert.net/forum/forum/179-win-toolkit/

Actually the latest is in this post: http://forum.driverpacks.net/viewtopic. … 586#p51586

Through a stupid accident on my part, I lost the source code of my working copy. 
I'm rebuilding it from v130507.

:: v130627 v3.0 (Erik Hansen)
:: Added 7zip switch -aoa to enable auto-overwrite mode.
:: Removed Win8 leaked build numbers and added Win8.1 preview build number to detection array.
:: Added DIR to CDROM detection array to prevent errors with card readers in system.

Testing within a VM will always have pitfalls with drivers because the hardware is not always presented to the virtual environment in the correct way.
One way to isolate the VM as the source of the problem is to try your build on a live-metal machine using a spare HDD (all other HDD disconnected).
If it works on live-metal but crashes in VM then you know the source of the problem.

In my opinion, VMware is a much better VM than VirtualBox.  I used to use VB exclusively but eventually moved to VMware for speed/compatibility.
When building DriverPacks releases, I always test in VM first but test installs on live-metal as a final check.  To say dpms is "incorrect" is not true, my older tower system had a 2829 HWID and it worked fine with dpms 1209 before I sold it.

You're using DriverPacks in an unsupported way.  We're in uncharted waters here, so be patient with us.

Glad you got it sorted out.
A couple of notes to help you out:
You should remove DP_LAN-RIS_wnt5_x86-32_1011.7z it is not needed (nor desirable).  It's intended specifically for RIS-server deployments (non-desktop builds).

We encourage you to include the following optional Third Party DriverPacks in your build since the DPsFnshr.ini will utilize these only if present.
DP_Graphics_Languages_wnt5_x86-32_1206.7z (only needed for non-English installs)
DP_Graphics_PhysX_wnt5_x86-32_1206.7z (only for matching nvidia hardware)
DP_Runtimes_wnt5_x86-32_1206.7z (only for ATI graphics cards)

Well, I guess I'm done.  I haven't done anything with it for a while.  I haven't done any coding for detecting laptops at all and I don't have a lot of time either.
I really need to find some time to update the first post though, it's way out of date.

Does your SAD2 folder exist on the install media or on the %systemdrive% (C:\D\SAD2\...)???
If you're installing to a clean hard drive, then the C:\D\ folder won't exist unless you have it injected into the install.wim image or use the $OEM$ folders method: http://unattended.msfn.org/unattended.x … f57c0ae2b/