Topic: Drivers on Demand  (Read 1385 times)

Drivers on Demand
« on: January 17, 2020, 04:54:03 AM »

Malok

  • Chef
  • ***
  • Location: Canada
  • Date Registered: Aug 2016
  • Posts: 202
Hi,

Here's my driver pack manager version for XPE.
Read setup info inside Plugin to setup.

*Important: This script rely on Startup_XPE.Script and
must be located in

%BaseDir%\Projects\MyPlugins\Apps\Tweaks

directory In Project for the auto installation to work properly.

Also fixed small errors in interface section that was
causing error in PEBakery... Thanks to APT who brought it
to my attention  :thumbsup: Link is updated.

ila_rendered

Here are links to the x64 driver Packs I made for testing... Use at your own Risks  :wink:

Chips.cab (50.3 Mb - Date: 2020-01-12)
Stor.cab (37.6 Mb - Date: 2020-01-12)
Usb.cab (32.5 Mb - Date: 2020-01-12)
Lan.cab (18.4 Mb - Date: 2020-01-12)
Wifi.cab ( 90.5 Mb - Date: 2020-01-12)
Vendors.cab (97.0 Mb - Date: 2020-01-12)
Reader.cab (56.4 Mb - Date: 2020-01-12)
Video.cab (447 Mb - Date: 2020-01-12)
Sound.cab ( 3.0 Mb - Date: 2020-01-12)

(Downloads are slow to start because Google drive Struggle with scanning cabs for viruses)

All credits goes to the great teams at Forum.ru and drp.su for their wonderful work putting together all these .
« Last Edit: January 23, 2020, 04:23:37 PM by Malok, Reason: Update url »

Re: Drivers on Demand
« Reply #1 on: January 19, 2020, 11:42:52 AM »
  • Location: Israel
  • Date Registered: Dec 2017
  • Posts: 444
Thank you i just want you to know i appreciate you messing with all this stuff. I have no patience to mess with PESE so anything to tweak XPE is amazing.

Re: Drivers on Demand
« Reply #2 on: January 19, 2020, 04:17:35 PM »

Malok

  • Chef
  • ***
  • Location: Canada
  • Date Registered: Aug 2016
  • Posts: 202
Thanks,

This project has a very, very, very, Bright future :great: It's fast and reliable. And can be setup in minutes, So I try to do it carefully because I want it to stay that way.

But adding more complicated tweaks always invokes tempering with configuration files. Because of the model XPE is made it's always done in the egg. for example if you modify XPEStartup.ini with another plugin you need to unpack the one XPE use modify it and repack it where it was. because it will be used next build. but let say you just want to change an autostartup command and make iso directly. now you need to modify in packed version and iso to keep things uniform ect.

And I don't really like tempering with peoples startup files so I always give instructions to do it manually, then the plugins integrates very well. and I try to keep it in the minding of the project also. Give clear instruction and simple plugin to use...

Cheers  :thumbsup:

Re: Drivers on Demand
« Reply #3 on: January 21, 2020, 09:18:42 AM »
  • Location: Israel
  • Date Registered: Dec 2017
  • Posts: 444
@malok

only issue so far is where [Error] ExtractFile - No script in [D:\Oven\Projects\MoPlugins\Apps\Components\Startup_XPE.script] (ExtractFile,%ScriptDir%\Startup_XPE.script,InterfaceEncoded,XPEStartup.ini.txt,%GTemp%\%ProgramFolder%) (Line 161)

i had to move the script.

Re: Drivers on Demand
« Reply #4 on: January 21, 2020, 11:48:15 AM »
  • Location: Israel
  • Date Registered: Dec 2017
  • Posts: 444
so i fixed all the location issues by putting both script under MoPlugins\Tweaks.

[Warning] FileDelete - File [D:\Oven\ISO_x64\Chips.cab] does not exist (if,%CBox1%,equal,false,Filedelete,%Giso%\Chips.cab) (Line 217)

This happened for any ones that are not selected.

Re: Drivers on Demand
« Reply #5 on: January 21, 2020, 01:26:43 PM »

James

  • Grand Chef
  • *****
  • Location: USA
  • Date Registered: Dec 2017
  • Posts: 2272
Best if use > "%BaseDir%\Projects\MyPlugins\Apps\System Tools\Startup_XPE.script"
thus placement location not matter...

also instead of checkbox false
if,%CBox1%,equal,True,filecopy ...
else,if,existfile,%Giso%\Chips.cab,Filedelete,%Giso%\Chips.cab

Re: Drivers on Demand
« Reply #6 on: January 21, 2020, 01:41:54 PM »

James

  • Grand Chef
  • *****
  • Location: USA
  • Date Registered: Dec 2017
  • Posts: 2272
also as a protection DOD should be run after XPEStartup...
and then check if XPEstartup.ini exists
else extract a default XPEStartup.ini from within DOD...

this way you do not need to manipulate XPEStartup.ini contained in XPEStartup script
it would also allow DOD to run without selecting/enabling XPEStartup



« Last Edit: January 21, 2020, 01:48:24 PM by James »

Re: Drivers on Demand
« Reply #7 on: January 21, 2020, 02:16:03 PM »

Malok

  • Chef
  • ***
  • Location: Canada
  • Date Registered: Aug 2016
  • Posts: 202
thanks, for the feedback,

@james, Will correct the script following your suggestions. Also will check out for the XPEStartup.

@Bigbadmoshe, I updated OP to precise the script location. I erased all temporary file and run the scripts multiple times I also manually tried to reproduce the problem on line 217, I'm not getting the error you mentioned. But I can see inconsistent entries in my log... I'm going to check it out. something is not correct in my project....

My logs shows

Code: [Select]
FileDelete - Sucessfully deleted [%BaseDir%\ISO\Chips.cab]

Even when the file is not there !?! loll...
« Last Edit: January 21, 2020, 02:20:09 PM by Malok »

Re: Drivers on Demand
« Reply #8 on: January 21, 2020, 03:41:52 PM »

James

  • Grand Chef
  • *****
  • Location: USA
  • Date Registered: Dec 2017
  • Posts: 2272
Some Error messages are not present when using winbuilder - but are presented when using PEBakery..
Thus we try to avoid by using if,exist

Re: Drivers on Demand
« Reply #9 on: January 21, 2020, 07:03:24 PM »

Malok

  • Chef
  • ***
  • Location: Canada
  • Date Registered: Aug 2016
  • Posts: 202
Some Error messages are not present when using winbuilder - but are presented when using PEBakery..
Thus we try to avoid by using if,exist

Got that.. Is there a way to enable logging of all errors and Warnings in XPE ?

also as a protection DOD should be run after XPEStartup...
and then check if XPEstartup.ini exists
else extract a default XPEStartup.ini from within DOD...

this way you do not need to manipulate XPEStartup.ini contained in XPEStartup script
it would also allow DOD to run without selecting/enabling XPEStartup

I'm still not sure if I want to have more than one plugin that installs XPEStartup.ini
This could end up with settings made being replaced by other plugins. It's why I used that way.

I think Next Version will start from PEcmd.ini and load it's own DriverSod.ini from the usb Drive
instead. This will also get rid of the TXTReplace commands and leave XPEStartup.ini untouched.

I Updated the script to fix the errors in PEBakery. should be ok now.

I want to integrate the universal version as well, so it can be used to install x86/x64 drivers from any build.
to any Windows NT. and I also want to clean the root of the usb drive and put everything in the program directory.
for a cleaner finish.

Thanks for your inputs without it I would have never known that PEBakery was trowing errors because I don't use it.
« Last Edit: January 21, 2020, 07:03:39 PM by Malok »

Re: Drivers on Demand
« Reply #10 on: January 21, 2020, 08:56:51 PM »

APT

  • Grand Chef
  • *****
  • winpe enthusiast
  • Location: UK
  • Date Registered: Nov 2012
  • Posts: 1150
Hi Malok

just confirming DoD PEBakery warnings resolved
regards and thanks


ps. using PEB 0.9.7b7
« Last Edit: January 21, 2020, 08:59:15 PM by APT »

Re: Drivers on Demand
« Reply #11 on: January 21, 2020, 11:22:42 PM »

James

  • Grand Chef
  • *****
  • Location: USA
  • Date Registered: Dec 2017
  • Posts: 2272
Quote
I think Next Version will start from PEcmd.ini and load it's own DriverSod.ini from the usb Drive
instead. This will also get rid of the TXTReplace commands and leave XPEStartup.ini untouched.
:great:

With a simple addition in default Pecmd.ini - with same reference as XPEStartup.ini
Is a doable project addition - for Next release... I'll make Note:

For Now - It would have to be manually added to pecmd.ini

Code: [Select]
// Load external Autorun.cmd or PecmdStartup.ini to run program, Install external drivers, keyboard,...
IFEX Y:\DriverSod.ini,LOAD Y:\DriverSod.ini

or text-replace in pecmd.ini with above
Code: [Select]
//EXEC @!%WinDir%\System32\pnputil.exe /add-driver Y:\Drivers\*.inf /subdirs
« Last Edit: January 21, 2020, 11:32:33 PM by James »

Re: Drivers on Demand
« Reply #12 on: January 21, 2020, 11:45:49 PM »

James

  • Grand Chef
  • *****
  • Location: USA
  • Date Registered: Dec 2017
  • Posts: 2272
I seen when first posted - but refrained from feedback until others did...
I did not want to come off as being somewhat critical of your work...

Feedback is important, so that the development works for everybody...
 :wink:

Re: Drivers on Demand
« Reply #13 on: January 22, 2020, 12:37:55 AM »

Malok

  • Chef
  • ***
  • Location: Canada
  • Date Registered: Aug 2016
  • Posts: 202
Code: [Select]
// Load external Autorun.cmd or PecmdStartup.ini to run program, Install external drivers, keyboard,...
IFEX Y:\DriverSod.ini,LOAD Y:\DriverSod.ini

Yes, Right what I've done. But I written it under the "//Load Users Drivers from Y before shell in background" location instead...
I added a command /gen that automatically creates cmd and ini file for given packs. from cmd prompt. In next release.

Code: [Select]
DriverSod /gen New_Loader lan wifi vendors video

Will create New_Loader.cmd and New_Loader.ini for given driver packs. Then just double click cmd to install at will.
Also added a bit of syntax error checking, so if you make typos the cmd will echo an error or bring help screen.

It's starting to feel good and reliable.. Thanks @all for your inputs.


Re: Drivers on Demand
« Reply #14 on: January 22, 2020, 01:43:52 AM »

James

  • Grand Chef
  • *****
  • Location: USA
  • Date Registered: Dec 2017
  • Posts: 2272
Just don't go over-thinking things and make it over complicated..
keep it simple and just to the basics.. (Only as required)

Re: Drivers on Demand
« Reply #15 on: January 22, 2020, 02:04:46 AM »

RoyM

  • Jr. Chef
  • **
  • Date Registered: Aug 2017
  • Posts: 80

https://en.wikipedia.org/wiki/KISS_principle

'I was not Navy', but this principle permeated all other branches.
To this day, I find that it still holds true.

Regards.
RoyM


Re: Drivers on Demand
« Reply #16 on: January 22, 2020, 04:26:53 AM »

James

  • Grand Chef
  • *****
  • Location: USA
  • Date Registered: Dec 2017
  • Posts: 2272
Hello All,
I would like to first say hello and introduce myself, my name is jimmy and I have been doing a little scripting as of late..
I was scripting programs that I could use with winpe - diskpart scripts - dism scripts - apply wim scripts - image prep and so on..
A member from eight forums sent me a stand alone program that ran from my desktop, when it finished I had a bootable disk that booted into ram (X) and had a windows type interface with a bunch of programs on the desktop..
Well after a little searching,, I'M HERE..
Been reading the forum, and wow is there a lot of knowledge here to learn for a beginner.. And I Thank You..
But, Need a little scripting help..

Thank You in Advance
kyhi

We all start out somewhere...
« Last Edit: January 22, 2020, 04:27:47 AM by James »

Re: Drivers on Demand
« Reply #17 on: January 23, 2020, 11:34:28 AM »
  • Location: Israel
  • Date Registered: Dec 2017
  • Posts: 444
@malok how you choose what files to include in the cab? i want to add drivers for more intel graphics.

Re: Drivers on Demand
« Reply #18 on: January 23, 2020, 01:06:47 PM »

Malok

  • Chef
  • ***
  • Location: Canada
  • Date Registered: Aug 2016
  • Posts: 202
Hi, Bigbadmoshe

To add more drivers Extract the cab on your machine with 7zip, Add as many drivers as you want respecting the structure and repack using Cabpack.

You will find drivers required files are listed in inf file [SourceDisksNames] and [SourceDisksFiles] sections. Copy cat file also.

hth.

Re: Drivers on Demand
« Reply #19 on: January 23, 2020, 01:26:50 PM »
  • Location: Israel
  • Date Registered: Dec 2017
  • Posts: 444
You will find drivers required files are listed in inf file [SourceDisksNames] and [SourceDisksFiles] sections. Copy cat file also.

This is what i needed thank you.

 

Powered by EzPortal