Injecting Drivers

Hi again

OK! Said I would have more questions.......lol

I don't seem to be able to inject any drivers.... I have unpacked all the drivers that you can download from driverpacks and created directories for each of them....I point winbuilder to them and the script seems to run for a few seconds and then stops?!

Logically one doesn't want to inject to much into the actual wim file because of that loading into ram, but it would be nice to have extras on the cd/usb etc.

What am I missing here......

Can one inject the important drivers into the wim and have the others on the cd? And how do I go about that?

Sorry for beginner questions.....lol


bookie56

bookie56

Hi bookie56,


Most Windows 7 drivers are already available in Win7PE_SE  .
you can of course added some specific drivers (eg: LAN, WLAN) in your Win7Pe and also integrated driversPacks (eg: chipsets, mass storage) with the Driver Integration script.

But as you said, careful not to inject too many drivers for keeping an acceptable wim file size, for the starting time and the size occupied in RAM.

You can also use the script "Driver Package Installer" which uses DPInst to add drivers to your running PE
This one allows to copy or unpack drivers packages onto your media to the outside of the wim file (Not in Ram).
and load them, if needed, in your running PE.

These 2 scripts allows you to control which ones you want integrated into the WIM and which are available after booting the PE.
This is a personal choice depending on which machine you want to run your PE and your Win7PE use.
Remembering that most Win7 drivers are already included.


Regarding your error, difficult to help you without log.
You can run "Driver Integration" by selecting the "Pause (win7)" checkBox with the "Show process". 
With this, you will have a break at the end of the integration for better see what happens.

Regards,

Hi ChrisR!
Ok! I will have a look at that as soon I get a moment.

bookie56

Yeah, this can give you a hard time, and not just beginners.
I'm currently busy with some really crappy driver injection tasks...

Two things that come into my mind:

• Make sure your driver stuff is complete and you're using a current release. I noticed differences between Double Driver 4.1 and Driver Magician 3.68 (the latter being shareware seems to work better) trying to sort the relevant files out.
• I tried out several driver scripts, but wasn't content until I was notified of amalux' Auto Driver Import W7 script. I use it for a few (w)lan drivers, it works perfectly. You'll find it in the latest amalux Win7PESE release.

I just built my first Win7PE last night and I love it!! I am having the same issue. I am using extracted driver pack files (Lan and Mass only) but my Asus laptop lan driver did not load. It wasn't until I used DISM to inject the drivers into the Win7pe wim did I get a working lan on bootup. I am missing something? The folder on my Winpe iso says DriverPacks and inside that folder lan and Mass. Should there be something else in that folder? Also if I use device manger to manual  point to that DriverPacks\Lan folder, the driver installs fine. So I know it's not my machine but the drivers are not getting loaded on bootup.

For Lan, WLan, Mass, I think that it is better to use Driver Integration (dism) for that it is loaded automatically at startup. I use this way for few lan wlan drivers.
I have not tried amalux' Auto Driver Import W7 script, which certainly makes the job.

That's what I did and it works great. Question, what index number is the boot.wim? I tried to mount the PE wim with DISM with index 2 and DISM says that index is not in that wim. I mount it with wintoolkit and then use DISM in a command to inject the drivers. I would rather mount, inject and commit unmout in the same cmd.

To mount Target PE, you can use Mount script in Utils folder.

Without rebuilding your PE: 
If you have a Win7 SP0 as source, you can use MountPoint=%targetDir% and use also MountSource to use then "Driver Integration script"

With Win7 SP1 source, use MountPoint=%BaseDir%\Mount\%ProjectName%\Target then integrates your driver manually before unmount.