#### Re: Windows 7 x86 & x64 Stand Alone Driverpack utility

Link now fixed, Thankyou (Delete this post if needed)

Last edited by David McMahon (2011-02-03 09:59:41)

#### Re: Windows 7 x86 & x64 Stand Alone Driverpack utility

That's because the *.thesneaky.com domain expired.  I'll update the link in a bit.

#### Re: Windows 7 x86 & x64 Stand Alone Driverpack utility

Thank you, got it just about to do a VHP32, wish me luck!

#### Re: Windows 7 x86 & x64 Stand Alone Driverpack utility

A few things

First, your tool should be in the Vista and 7 tools forums - it's definitely the best standalone tool, but took a while to find.

Second, there's a VBS script available to elevate a batch file (from Microsoft). Here's what I posted at the WSUSOffline forum about it

*edit* I recall that under Vista and 7 with UAC turned on WSUSo didn't work unless you right-clicked and chose "Run as Administrator". Well, I came across that problem in a previous project and I modified a script to elevate the command prompt (so when you double-click on the .cmd or .bat file it will pop up a UAC window then run the script and all sub-scripts elevated. I also made another script which disables UAC. Once I find them (have google desktop indexing my hard drives right now because I don't remember where it is) I can post them with instructions on integrating them into WSUSo. That should make it a little more user friendly.

*edit2* I may or may not still have the files I was looking for, I might have them at work, or Google Desktop might pick them up after I installed an add-on that searches inside rar files. If I can't find it, here's what I based that work on:
http://technet.microsoft.com/en-us/maga … ation.aspx
I used the elevate.cmd and elevate.js
I also referred to the older version of the article http://technet.microsoft.com/en-us/maga … light.aspx
I recall it being a decent amount of work, but I did get it to eventually work automatically and transparently

Got the code for elevation (took forever to find)

Here's the elevate.vbs script: http://pastebin.com/A0sKKj60

And here's the code from elevate.cmd (which calls elevate.vbs):

:: //***************************************************************************
:: // ***** Script Header *****
:: //
:: // File:      Elevate.cmd
:: //
:: // Additional files required:  Elevate.vbs
:: //
:: // Purpose:   To provide a command line method of launching applications that
:: //            prompt for elevation (Run as Administrator) on Windows Vista.
:: //
:: // Usage:     elevate.cmd application <application arguments>
:: //
:: // Version:   1.0.0
:: // Date :     01/02/2007
:: //
:: // History:
:: // 1.0.0   01/02/2007  Created initial version.
:: //
:: // ***** End Header *****
:: //***************************************************************************

@echo off

:: Pass raw command line agruments and first argument to Elevate.vbs
:: through environment variables.
set ELEVATE_CMDLINE=%*
set ELEVATE_APP=%1

start wscript //nologo "elevate.vbs" %*

You should be able to just put the following into update.cmd:

set ELEVATE_CMDLINE=%*
set ELEVATE_APP=%1
start wscript //nologo "cmd\elevate.vbs" %*

Although I'm not sure how important the environment variables are.

Third, I always put an autorun.inf in the DP_Install_Tool.cmd folder (in case I burn it to a disc):

[autorun]
OPEN=DP_Install_Tool.cmd

Last edited by BrentNewland (2011-02-10 05:28:51)

#### Re: Windows 7 x86 & x64 Stand Alone Driverpack utility

Ooh, nice!  I'll have to add that to my "to-do" list.
Yes, I'll have to create it's own thread and sticky it.

#### Re: Windows 7 x86 & x64 Stand Alone Driverpack utility

oh this looks so awesome.

#### Re: Windows 7 x86 & x64 Stand Alone Driverpack utility

I found a bug when using UNC paths such as \\server\path\to\DriverPacks
http://support.microsoft.com/kb/156276
The fix is altering the registry, but changing the affected key may have unwanted side effects.
Hmmm...

#### Re: Windows 7 x86 & x64 Stand Alone Driverpack utility

OK, I've worked in a few improvements to the code.
Now checks for UNC paths and displays error if found.
Added NT6 Method 1 routine (uses xcopy instead of copy).
A few other refinements.  More to come...

#### Re: Windows 7 x86 & x64 Stand Alone Driverpack utility

v11.02.13 online

I'll see if I can get the "privilege elevation" code working auto-magically in the next version.

#### Re: Windows 7 x86 & x64 Stand Alone Driverpack utility

wow Erik 7 MB???

OIC you include a pack for each OS / type for reference...

I like your thinking on the process... however this would be much easier to do in AutoIt. Including the Admin privliges.

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!

The DriverPacks, the DP_Base program, and Support Forum are FREE!.

#### Re: Windows 7 x86 & x64 Stand Alone Driverpack utility

LOL, I guess I could have included "dummy packs" instead eh?

#### Re: Windows 7 x86 & x64 Stand Alone Driverpack utility

mr_smartepants wrote:

OK, I've worked in a few improvements to the code.
Now checks for UNC paths and displays error if found.
Added NT6 Method 1 routine (uses xcopy instead of copy).
A few other refinements.  More to come...

You can use pushd/popd. It will automatically map a network drive.

Check out the full post I made at WSUSOffline (the same one as the elevation script): http://forums.wsusoffline.net/viewtopic … =381#p1512

pushd %~dp0
set cur=%cd%

at the beginning of the script will change the command prompt to the current directory (and if it's a network share, it will map it to a drive first). Setting "cur" to %cd% will set the cur variable to the current directory AFTER the pushd has been performed.

At the end of the script put in a popd and it will close the network share (or do nothing if not over the network).

#### Re: Windows 7 x86 & x64 Stand Alone Driverpack utility

Oooh, nice.  I'm adding that to my to-do list.

#### Re: Windows 7 x86 & x64 Stand Alone Driverpack utility

hello,i think this window 7 is great.

SPAM link removed by moderator!

#### Re: Windows 7 x86 & x64 Stand Alone Driverpack utility

hello,i will support this great forum.

check this site aed batteries

#### Re: Windows 7 x86 & x64 Stand Alone Driverpack utility

hair, I would first like to thank you for creating this very useful tool that helps me (in my case) to create the windows I need.
Now I will tell my problem, which I do not understand and run .... cmd I get the blue he says about cuetna administrator, press any key and close the cmd there and hanging remains in doubt, someone could tell me in detail how to use this tool as well please?

From already thank you very much for all your help, I salute you.

Last edited by Aleksey09 (2011-03-10 09:00:20)

#### Re: Windows 7 x86 & x64 Stand Alone Driverpack utility

For Vista & Win7, the tool will fail if you run the batch file as a normal user.  The warning is just to remind you to run as an administrator.

** Caution **
The below caution is for Vista/Win7 users only.
User Account Control will ask you to confirm each action the tool tries to complete.  Very annoying.
For best results, right-click the DP_Install_Tool.cmd file and select "Run as Administrator" from the menu.

#### Re: Windows 7 x86 & x64 Stand Alone Driverpack utility

I am running the program on windows xp sp3

#### Re: Windows 7 x86 & x64 Stand Alone Driverpack utility

Then as long as you execute the batch file from within an administrator account, you'll be fine.  Don't worry.

#### Re: Windows 7 x86 & x64 Stand Alone Driverpack utility

Gentlemen, I say that because I understood how to include drivers in the folder for the program. But now when I run the cmd, I have to press any key on 2 occasions (using method 2) telling in the final stage (in addition to the legend that self-close the window in 30 seconds) the Spanish legend not been able to find the selected file.
Even now I do not understand how the program works, nor how I can include it in the nlite to run the cmd in the first start of assignment (in the installation of windows xp sp3).

Already thanks for help, I salute you.

Last edited by Aleksey09 (2011-03-11 04:50:21)

#### Re: Windows 7 x86 & x64 Stand Alone Driverpack utility

If you don't want to see the messages, just remove the word "pause" from the batch file.
To run the batch file automatically (not recommended), just add it to the cmdlines.txt file for inclusion in the RunOnce phase.

#### Re: Windows 7 x86 & x64 Stand Alone Driverpack utility

excuse my ignorance, but I do not understand how I can use it in the nlite, or as if it works ... and this is the only method I found to include the drivers to my Windwos modified without losing the ability to repair

#### Re: Windows 7 x86 & x64 Stand Alone Driverpack utility

No, you cannot integrate SAD with nlite.  SAD is a Stand Alone Driver-disc.  It's meant to stand alone (to be run by itself).
Because it is a batch file (command script) it can be called at any time after windows is installed.

#### Re: Windows 7 x86 & x64 Stand Alone Driverpack utility

you could use nlite to launch sad as a runonceex command ...

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!

The DriverPacks, the DP_Base program, and Support Forum are FREE!.

#### Re: Windows 7 x86 & x64 Stand Alone Driverpack utility

Well ... if I can not in a conventional manner to include the modified SAD my windows, I need to tell me what the steps because I can not update the drivers with this program.
When can I switch images to see if they can tell me what happens ... because if it goes well this part of the driver, I will have done the windows changed.