I haven't had a chance to play with the pnputil yet.  This was just a variation on the current SAD script.
I'll make it better! smile
The error is from the script trying to delete itself (I think), but nothing to worry about.  The only thing left behind is an empty \D\ directory.

Hmm, I'll need to play with pnputil more.

>pnputil -?
Microsoft PnP Utility
Usage:
------
pnputil.exe [-f | -i] [ -? | -a | -d | -e ] <INF name>
Examples:
pnputil.exe -a a:\usbcam\USBCAM.INF      -> Add package specified by USBCAM.INF
pnputil.exe -a c:\drivers\*.inf          -> Add all packages in c:\drivers\
pnputil.exe -i -a a:\usbcam\USBCAM.INF   -> Add and install driver package
pnputil.exe -e                           -> Enumerate all 3rd party packages
pnputil.exe -d oem0.inf                  -> Delete package oem0.inf
pnputil.exe -f -d oem0.inf               -> Force delete package oem0.inf
pnputil.exe -?                           -> This usage screen

That's already in:
DP_LAN_wnt5_x86-32_10111\D\L\At
DP_LAN_wnt6-x86_1003.7z\x86\L\Atheros\3\Win7_32\
DP_LAN_wnt6-x64_1003.7z\x64\L\Atheros\3\

All current drivers for Atheros are from here: http://partner.atheros.com/Drivers.aspx

1,728

(6 replies, posted in BartPE - UBCD4Win - WinPE)

adrianmarsh wrote:

... but when I try to have it download the drivers in UpdateChecker, I get an error telling me the .7z file is currently unavailable.  I get the same for all of the packages.

That is normal.  Read this news thread: http://forum.driverpacks.net/viewtopic.php?id=4850

Wim Leers wrote:

... And finally, we need to look into ways to generate more income, to be able to continue running this project. A first and obvious step, is to cease the ability to download/update the Windows 2000/XP/2003 DriverPacks from within the DriverPacks BASE for free. In the first phase, the downloads will stop working, thereby increasing our number of visitors.

Just download the DriverPacks, then drop the .7z files in the folder \UBCD4Win\plugin\DriverPacks.net\BASE\DriverPacks\

1,729

(7 replies, posted in Windows 7 Discussion)

x64 SAD install fails, it needs the 64-bit specific version of DPinst.exe to work properly. 
New version now works fine with x64. smile
http://3rdpartydriverpacks.thesneaky.co … -101102.7z

1,730

(7 replies, posted in Windows 7 Discussion)

I have a working script already tested working in x86 Win7,  I need to install x64 Win7 in VM to test the script, but it should work fine.  It'll automatically determine the running system OS arch and extract the correct DriverPacks from the right directory.  Very slick.

If you want to try the work in progress, it's here: http://3rdpartydriverpacks.thesneaky.co … NT6_SAD.7z
Read the "readme.txt"

Ooh, nice tip Rick.  Does that work in both Vista & Win7?

Here is a script developed from the original SAD script.  I'll call it SAD2 smile
It'll automatically determine the running system OS arch and extract the correct DriverPacks from the right directory.  Very slick.
Supports all NT5 (XP/2000/2003) & NT6 (Vista/Win7) OS types.
*To-do:
Add better logging function.
Get DriverPacks Finisher working in NT6.

If you want to try the current work in progress, it's here: http://forum.driverpacks.net/viewtopic.php?id=5336
Older releases:
Download v110505
Download v110504
Download v110503
Download v110502
Download v110501
Download v110312
Download v110213
Download v101203
Read the "readme.txt"

**This post is obsolete**
New thread created here: http://forum.driverpacks.net/viewtopic.php?id=5336

Changelog:
v110505
Fixed code to prevent writing log to read-only disc
Repackaged dpinst* files to prevent accidental deletion.

v110504
Fixed bug where NT6 Method 1 fails prematurely.

v110503
Fixed code to remove extra backslash from path if exist.

v110502
Fixed un7zip code to allow for wildcard file extraction

v110501
Updated to support network shares and UAC elevation for NT6
Fixed CPU detection to allow for 32-bit OS on 64-bit CPU
Fixed un7zip code to allow breakpoints

v110312
Fixed missing NT5\x86\dpinst.* files
Updated to current DriverPack Chipset versions.

v110213
Added NT6 Method 1 functionality.
Added check for UNC (\\server\path\to\file) paths.  Cmd.exe will fail if UNC path is used.
Changed Method 1 COPY function to XCOPY for reliability.
Improved readme.txt instructions.

v101203
Added NT6 functionality (Vista/Win7).

I'm confused.
So do you insert drivers using nlite or DriverPacks BASE (or worse, both)?
I don't get that error during txtmode, but I don't have an AMD chipset either.  All AMD users reported no problems during testing all month.
That file only exists in D\M\AM\ and nowhere else.  That folder hasn't had any updates for a while and there are zero differences between 10.10 and 10.11 for that folder.
Confirm the MD5 hashes of each pack also.
What are your HWIDs and please explain in more detail how you build your source, specifically driver usage?

1,734

(1 replies, posted in DriverPack Sound)

Odd that the driver in DP_Sound_B_wnt5_x86-32_*\D\S\S25 didn't work since it is newer, and supports the identical HWID.
Can you confirm that the driver in DP_Sound_B_wnt5_x86-32_*\D\S\S25\ will work as an UPGRADE using the "have disk" method over the driver you linked to above?
Sometimes not all drivers are loaded when using SAD, and some will not load properly until the chipset drivers are loaded, so it requires a second pass of SAD to load all properly.

Done in latest testing build.
Very, VERY poor choice in username BTW.

Excellent first post!  Welcome to DriverPacks! smile
Yes, you are doing everything correctly, but unfortunately the mobility chips are hard to support because ATI doesn't release their own unified build for notebooks and we have to modify the desktop drivers to make them work.  But because the integrated graphics chipsets are so tightly integrated with other motherboard components, the desktop drivers are missing something.  I'm just not sure what's missing.
Don't worry if English isn't your native language.  Google translator is a wonderful thing and your English was good enough where I could fully understand everything you meant. smile

ACER_5672 wrote:

In my current install I installed the Catalyst Legacy 10.2 Driver modified with DriverHeaven Mobility Modder 1.2.1.0 and all works fine

10.2 is the current ATI build for legacy hardware.  It's the same version we include in our DriverPack Graphics C.  To be fair, our current DriverPack Graphics C 10.09.1 works fine on my wifes notebook with Radeon 9600.
I'll go back in and see if there's anything that would interupt the normal driver install in an international setting.

1,737

(25 replies, posted in Windows 7 tools)

Technically no. 
We are working on developing our own DriverPacks BASE for Win7 (and possibly Vista) but it's a long way away. 
We have a concept, great ideas, and a very basic framework but nothing worth testing.
We got sidetracked with moving the site/files (twice!) and lost a few of our core DriverPacks developers.  We'll get there in the end, and yes, it will be awesome!

1,738

(9 replies, posted in DriverPack WLAN)

Uploading now...

Well I've heard that sysprep is not that fun to play with.  But Galapo has written a very nice tutorial using his "OfflineSysPrep" utility (your 3rd link) and I intend to follow that path hopefully soon because it has the best results with DriverPacks.
I'm a newbie in this arena also.  So maybe a more experienced person will stop by and offer assistance to us both.

Welcome to DriverPacks!
This is hardly a dumb question!  It's a very good question.  You're correct, there are many methods of making universal images.  I myself use RVMi to integrate an update-pack into XP, then various add-ons to add the functionality I want.  Then add in my own winnt.sif file and DriverPacks (of course) for unattended bliss.  But what's always nagged me is the fact that you have to waste time (every time) to allow the system to "install".  When you could simply have a pre-installed image with a mini-setup and cut the "install" time in half (or more).
I've been tempted on many occasions to begin building images like you suggest and just never find the time to do it.
Perhaps we'll make the journey together. smile

But like you said, there are many who have "been there, done that" and have written very good tutorials (many are stickied in this forum).   So read them carefully, and enjoy.

1,741

(2 replies, posted in DriverPack LAN)

It's already in the current release.
DP_LAN_wnt5_x86-32_10111\D\L\R4\
Are you saying that you've tried using our DriverPacks and it didn't work for you?
If so, please post your DPsFnshr.log and DPs_BASE.log.

1,742

(2 replies, posted in Other)

USB controller drivers were merged into the new DriverPack Chipset 10.11.  Card reader drivers are in the Misc Third Party DriverPack.
The problem you are going to have is that USB 3 drivers are not included in dpms for "textmode" so your Windows setup will not be able to "see" any USB 3 device connected.

USB controller drivers were merged into the new DriverPack Chipset 10.11.  Card reader drivers are in the Misc Third Party DriverPack.
We don't source our drivers from station-drivers.  We prefer to get them from the vendor or OEM themselves.

Yeah, sorry.  I went back and read those posts after I replied.  You have been trying to help. smile
OverFlow has added the pnp interface fix to the "To Do" list for DriverPacks BASE.
Please be patient.

1,745

(8 replies, posted in Other)

OverFlow wrote:
ricky.martin4545 wrote:
gotaker wrote:

no, no antivirus
also that exe is also not in the bin folder.....wher eis it picking the file from
?????

stumped

I guess We'll have to be patient a little longer.

You just responded to a thread that has not had a post in over four years... Either you are a lot more patient than me, or you are really stupid. I have a vote for the latter.

It was a spambot.  It was copying threads and reposting at random.  All 3 of the posts were like that.  No more. wink

theSLug wrote:

not solved in MS 10.10.. sad any other beta DP to try?

mr_smartepants wrote:

Can you try the nvidia test packs in this post?
http://forum.driverpacks.net/viewtopic.php?id=4742
Please report back what works as well as what doesn't work.

Nobody wants to help. neutral
You've got 24-48 hours to test and report back in order to affect a change in 10.11 final.  I'm not waiting.
Start with test-pack #18 then try #15 next.

I have a feeling that in order to fix this nvidia fiasco once and for all we'll need to incorporate cdob's pnpinterface fix into DriverPacks BASE.

I'm in the process of finalizing dpms 10.11 (from 10.11r3). 
Where exactly are you seeing these errors?  As part of my testing, I also use UBCD4win 3.6 and I can't duplicate your errors (with my current build).
Which log file are you looking in?
What concerns me are these two:
Alert: File "SISRAID1.sys" not found
Alert: File "SISRAIDX.sys" not found

Those files are NOT part of dpms 10.09 or newer.  BUT they were present in dpms 10.06.  I suggest you clean out your build folders of any old packs and delete the ..\UBCD4Win\plugin\DriverPacks.net\MassStorage folder
It would also be prudent to start with a fresh source just in case.

1,748

(55 replies, posted in Vista / 7 DriverPack Mass Storage)

Updated to 10.11
Updated first post with "text-mode" instructions.

1,749

(73 replies, posted in Vista / 7 DriverPack Mass Storage)

Updated to 10.11
Updated first post with "text-mode" instructions

1,750

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

Updated to 10.11