Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7) (Page 3 of 22)

OK! So scratch all that again!

Firstly a huge thankyou to mr smarty pants for writing such a wonderful batch file! It's a ripper!

So I've managed to get the driver packs working (wasn't hard once you know how. I was thinking I might make a nice little guide and submit it for smartypants approval that it might stop n00b questions like mine. I really think the SAD2 should be included on the driverpacks.net main site, with some instructions. Would get even more people using it! Which could only be a good thing.

Anyway like I said I can run it no worries from the machine. But now I'm just going to try and get it to work unattended. I was thinking of maybe actually just making an sfx that can install first from fog. Or maybe have the SFX in the image to run on first log on.

Just need to make it unattend..

Ok so right now (9pm at night remoting to my machine via teamviewer ha) I followed the steps outlined to make the batch unattend. Brilliant. And now just compressing to a .7zip archive to make into an SFX!

So this is actually a brilliant way to deploy drivers on large scale using Fog! Because the options out there for sticking drivers into windows 7 are basically non-existent. Most people who use Fog or other imaging software besides MDT just install drivers manually or it's not a problem for them. But for us we have many different models and various ages. I tested this driver packs with a P4 IBM with 512mb ram and win 7 installed beautifully from FOG then I manually did used the batch script from smarty pants and it worked brilliantly for drivers. That said Win 7 pretty much was OK for drivers with that old machine. But I also tested it on a newer dual core Dell, 5400? model. Also worked flawlessly.

So what I was hoping for was to be able to do this unattended! And now I can, I think the best way is what I'm doing now. The install seems to run unattend which is great. I will test the SFX tomorrow. So It will be fairly large (1gb approx) but it will have all win 7 x64 drivers in it for new machines. I will make the SFX delete itself after extraction. So it should be good, will test how long it takes. If it is an old machine I will not bother, but if it is new, I will run the SFX (which I'm calling AbraKaDrivers-SFX (because FOG installs SFX alphabetically), and it will do all drivers first. I think this is better than adding them to the image itself because I can easily update an SFX than the entire image, although realistically it would probably be about the same amount of work..

I was thinking if this works well if anyone else wants the SFX maybe I could upload it somewhere to one of those free hosting sites, I know they are annoying but I can't host this myself.

Anyway will report back if it all goes well.

Hmm well small problem, the SFX extracts OK, everything to the right place, and SFX Maker executes the CMD file, however it seems to close it, I suspect because SFX maker perhaps uses cmd line stuff too, it may cancel the SAD tool before it can run. Maybe I need to tell SFX maker to run a .VBS script to launch the DP_Install_Tool..

I might try running a cmd that will then run the DPinstall cmd.. I'm not too sure about vbs', haven't used them much since high school..

Hmm that didn't work either.. Not sure why it won't let the DPinstall run..? Does anyone know a simple .vbs script that could run a cmd file? In this case the DPInstall.cmd?

Hmm.. No matter what I tried I couldn't get it to run, I thought it was crashing but actually it is failing when launched by SFX maker.. for some reason, it says "Win 7 ultimate 64 bit OS
Install on x86 processor
not currently supported

Please exit the program now!

But I can run this fine from a cmd window. And it runs fine when I double click it.. I wonder what is causing it to fail, because of the way that SFX maker calls it?

Ok So i'm just running this from my "setupcomplete.cmd" file which runs on first boot after the system has been imaged. It works fine, but if anyone has any idea how to get this tool to run as an exe? I looked at converting it to an exe but all of the tools were a bit dodgey.. one reportedly had a trojan..

Last edited by andyroo54 (2012-02-08 12:57:00)

Are you sure you're on x64-bit hardware?
Please open a command-window prompt on the target machine and type the following:
echo %PROCESSOR_ARCHITECTURE%
echo %PROCESSOR_IDENTIFIER%

Then post back here with the responses to each command.  It would be interesting to see what your CPU is reporting.  I may have to alter the code to cope with alternative CPU reporting.
You can over-ride the batch file, but there shouldn't be a reason to.  I wrote those safeguards to ensure the correct packs were installed.

To make the script fully automated, just remove the "set option" line 165:
:KTD-option
set /p option=[Y,N]?

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!

Not all heroes wear capes, some wear Kevlar!

Updated first post to new v120203.  Now packed as a 7-zip self-extracting archive for those without native 7-zip.
To-do: Update code to take advantage of native WinRAR if installed

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!

Not all heroes wear capes, some wear Kevlar!

Hi again,

Yes it's a bit strange, 100% certain on x64 architecture, when i run the script "manually" by double clicking it, it detects fine and then installs x64 win 7 drivers.

When I get it to run on first log on it also runs fine.

But if I try to run it from an SFX, for whatever reason, it fails with that error..

So strange.. I wish I could just skip the scan so it would auto install x64 drivers.

Last edited by andyroo54 (2012-02-09 10:49:16)

Hi,

Well the reason I want it as an SFX is so that if I have to update the drivers packs I can just update the SFX and no need to manually distribute them or have to having to update the image.

Yes I suspect like you said it is being confused by the SFX maker when it is being commanded to run. That's why I asked what I could remove to force it to go x64 x64.

Thanks anyway!

I'd still like to post my guide somewhere here when finished. Maybe I'll pm it to you. The readme is very good, but as I mentioned for someone new to all this it might be difficult to figure out. I'm going to make one this weekend.

Thanks, Andrew

It would probably make more sense if you use FOG.

The direction these recent posts are heading is detracting from the original post.
To answer the question: Yes, I can rip the guts out of the script to enforce x64 installation, but I won't.  It does everything I need it to do and does it safely.
Please create a new thread to discuss the relative merits of the FOG utility.

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!

Not all heroes wear capes, some wear Kevlar!

Sorry Erik, please feel free to relocate any and all of my distracting posts to the appropriate thread.  I agree it would be better.

Cheers and Regards

And how did we get off on THIS tangent?

Cheers and Regards

i'm no lawyer, either; i have banned myself from the 'bar' for malpractice!  I do see that you do observe & respect such licenses.  Compliance isn't that difficult.  One would have to go out of one's way to violate such terms.

Were someone to 'bundle' your app with a toolbar, or other SW, section 4b & 7a would likely be in effect:

Just thought you might bring the aforementioned non-compliance to I.P.'s attention; with a request to consider to author a 'special' command-line unzipper for DP's (incl. SAD2 & BASE), should maxximum not respond.  I would post to the 7-zip forum, yet i wouldn't know exactly what to request.  This would need to be AutoIT compatible?

Thinking (The Box).

Last edited by TechDud (2012-02-13 16:04:35)

Forum Rules & Guidelines   HWID's tool   Unknown Devices (Win7-max) LatencyMon - NT6.x
MemTest86+    Video Memory Stress Test    D-P-C Driver Latency Tester (Win7-max)

We already have un7zip, and it is our "special" unzipper.  It was created for us to use and distribute with DriverPacks BASE and we use it with SAD2.  But it is old (based on the 4.* version of 7z.dll) and doesn't support a lot of the newer functions of the 9.* series 7z.dll.  The cool thing about un7zip is that it is portable and does not need 7-zip to be installed to use.
Igor does make a standalone "command-line" version here: http://downloads.sourceforge.net/sevenzip/7za920.zip
But from what I understand after reading the readme.txt is that it doesn't support LZMA2 either.
As to letting Igor know about the license infractions, if someone has a sourceforge account then by all means contact him and link to this thread.  He doesn't have a publicly available email address.

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!

Not all heroes wear capes, some wear Kevlar!

I will be glad to have this post copied to where it was suggested, but would also prefer to leave a copy here since I feel it is a direct continuation of the conversation I began in post #44 - http://forum.driverpacks.net/viewtopic. … 516#p47516 - therefore directly associated with the latest update, unlike most of the posts from #52 - #70 which I agree are mostly OT - FOG etc.

Erik, while the standalone version you referenced, the 9.20 "7za" version, seems to be the latest available, you could also use the 7z console version, the "7z" version.  The 9.22 version is available here - http://sourceforge.net/projects/sevenzi … -Zip/9.22/.  To get them, you can install the version you want and copy the files out, either the x86 or x64, or just extract the files you need, using 7-zip of course.   The only files you need are "7z.exe" and "7z.dll", you just need to have them both from the x86  and/or x64 version.  They do not have to be installed or registered.  Put the .exe and the .dll in the same folder and you're good to go.  The 7z.exe is command line driven, which you can see the main command options by opening a command box in that folder and simply typing "7z" without the quotes.

The "7z.exe" plus "7z.dll" are larger than the 7za.exe standalone, but they are available in both x86 and x64 versions and they fully support LZMA2.

EDIT: Also, to be clear, the "7z.exe" plus "7z.dll" combination is fully capable of handling both compression and decompression chores.

Cheers and Regards

Last edited by bphlpt (2012-02-15 09:41:59)