Drivers on Demand

V0.92
-----------------------------------------------------------------------------
The command now enables users to have very simple syntax to remember and
Powerful tools easy to use. for example: You can now use DriverSod from any
drive letter to export drivers from an host. (/exp) in a booted Windows.
Then use them at will in your PE With (/Imp) to load the saved drivers.
You can cleanup those and create cabinet with cabPack for later uses (/inst).
The command can also be used to install drivers to standard windows NT
installations (/inst /load /imp). You can also create a cmd with
@DriverSod /exp %ComputerName% save it and double click it from usb drive on any
machine to automatically backup Hosts drivers to Folder ..\Drivers_x??\Computername.
Then use them right away in PE (/imp).The command can also generate batch command
to install up to 8 packs at once (/gen). And also create full cmd and ini to use
in projects (/genx). On a Running host Browse to the DriverSod folder in your
usb drive and start the cmd shortcut to have quick access to DriverSod prompt in
program folder. Or use start menu in PE for quick access to most useful commands.
Use plugin Automation or edit DriverSod.ini to enable / Disable packs installation
at PE Startup.
-----------------------------------------------------------------------------
*** Remove all traces of previous installation before installing this one ***

*** Follow Setup info in Plugin to setup auto installation at startup ***
-----------------------------------------------------------------------------
If you have any problem with your compiler please let me know... So i can fix it.
I've been using it every occasions 'I have since last week. It does a good job.

V0.92
-----------------------------------------------------------------------------
The command now enables users to have very simple syntax to remember and
Powerful tools easy to use. for example: You can now use DriverSod from any
drive letter to export drivers from an host. (/exp) in a booted Windows.
Then use them at will in your PE With (/Imp) to load the saved drivers.
You can cleanup those and create cabinet with cabPack for later uses (/inst).
The command can also be used to install drivers to standard windows NT
installations (/inst /load /imp). You can also create a cmd with
@DriverSod /exp %ComputerName% save it and double click it from usb drive on any
machine to automatically backup Hosts drivers to Folder ..\Drivers_x??\Computername.
Then use them right away in PE (/imp).The command can also generate batch command
to install up to 8 packs at once (/gen). And also create full cmd and ini to use
in projects (/genx). On a Running host Browse to the DriverSod folder in your
usb drive and start the cmd shortcut to have quick access to DriverSod prompt in
program folder. Or use start menu in PE for quick access to most useful commands.
Use plugin Automation or edit DriverSod.ini to enable / Disable packs installation
at PE Startup.
-----------------------------------------------------------------------------
*** Remove all traces of previous installation before installing this one ***

*** Follow Setup info in Plugin to setup auto installation at startup ***
-----------------------------------------------------------------------------
If you have any problem with your compiler please let me know... So i can fix it.
I've been using it every occasions 'I have since last week. It does a good job.

Amazing. thank you for this.

If PE is x64 do you need to have any files 32 in them? and what about all the .exe .vp .bin. Do those need to be in the cab?

Yes only if your PE is not pure x64 then it would need the wow3264 files...  To make sure your pack is compatible with all PE build it is advised to include both architecture in your pack, intel video drivers only needs user mode drivers, Kernel mode driver and Unified Shader compiler to basically work,

Intel drivers use a naming scheme that is easy to understand once you identified the Files of one driver it is basically the same for other similar products  but the beginning of the name differs a little  (igd...igx...igf...) then you can eliminate all other files and remove them from inf... the latest I have done are running 150 to 200 mo each. so they are not really practical for PE. If you take a look to the already stripped drivers you can basically find those just by how they are named.  then If you're a bit on the maniac side you can use infVerif to check your inf for errors.

A simple trick to get started fast, put files in detail view in explorer then sort by size, start by the biggest check detail in properties grab all user mode and shader  related dlls all sys and cat and inf files remove the rest and test in a live PE Most of the time the user mode drivers need 3-4 files for each architecture. example if igd10xxxx igd12xxxx igd14xxxx  ending ium32/64 are part of user mode for 3 different line of products. All the other files SDK, runtime, com object, Ressources, jit, openCL, openGL, filters, even the codecs and decoders are not needed. also there is nothing more needed to have DirectX working. To start with an already reduced file set, grab them from the drivers store of an installed windows 10.

hth

v0.93
-----------------------------------------------------------------------------
New Routine to Extract and install Offline host drivers in Live PE.

Extract Drivers, Remove doppelgangers, Show extracted drivers
for cleanup Before continuing. Or with /go extract, Remove, install
directly.With no interruption.

DriverSod /off <Path_to_offline_Windows> <Path_to_Tmp_Folder> [/go]

DriverSod /off c:\Windows c:\DrvTmp
-----------------------------------------------------------------------------
I have read that this would need Switch to admin. But as far as I
Have tested this. It works without it as long PE has read access.
-----------------------------------------------------------------------------

PEBuilder Giving me errors. Tried a few Versions.

Error in script [DriverSod] (Win10XPE\Apps\Tweaks\DriverSod_XPE.Script)
[Error] Error - Syntax error (Line 345)

Hi Bigbadmoshe

as you know, those errors show up when using PEBakery as your builder (for those who don't !)
try attached file and check it still works correctly

regards APT

It works find not PEBakery was just giving you a heads up.

Thanks for your help.

 Hi

It works find not PEBakery was just giving you a heads up.

mmm. so did the modified script fix the PEB errors for you or not ?

Hi
Please excuse my atrocious English.

I did not understand that the script you posted was a fix. I will test it out tomorrow.

Thank you for the quick fix.

It works find not PEBakery was just giving you a heads up.

mmm. so did the modified script fix the PEB errors for you or not ?

Hi Bigbadmoshe

as you know, those errors show up when using PEBakery as your builder (for those who don't !)
try attached file and check it still works correctly

regards APT

Works great thanks.