Read full article - http://boot-land.net/forums/index.php?showtopic=5213
Driver Import PE (dipe)
from Kare (boot land nick: CD-RW)
__Driver Import PE is a program which runs only in a PE environment (BartPE, UBCD4Win, SherpyaXP, LiveXP, etc). It's intention is to install drivers to the PE so as to get functioning devices be they networking, mass storage, sound, graphics, etc.
Now your PE can still get working devices even if the PE is built without the necessary drivers!
Thanks to: Lancelot to dps support (massstorage controller), Sbond for the nice graphic design, Galapo and dera for testing and giving Sigmatel support
Greetings
-kare-
Thank you again Kare for your hard work in developing Driver Import PE -- it is a real breakthrough!
Drivers may be installed to the PE system from:
- "System (OS) on HD" (ie, the offline system residing on the computer if one exists)
- "Folder (Inf-File)": File "OEM drivers" from specified location (harddisk, usb, network, etc.)
- "Folder (Inf-File)": DriverPacks .7z archives or .zip archives (put 7za.exe to the same folder with dipe) ( DPS packages Web ) ***dps packages not fully supported for now but works nicely in most cases, support will be added in time.
Note: PE must have writable %SystemDrive% which may be achieved by adding FBWF (for CD-based PE) or SDI (for ram-image-based PE).
pebuilder plugin (BartPE, UBCD4win, XPE, SherpyaXPE, ...) may be downloaded from here
WinBuilder script may be downloaded from here
**'Driver Import PE' is now in LiveXP, you can enable it in section: Drivers->5 Others->Driver Import PE
http://www.kare-net.de
http://www.kare-net.de/Plugins.htm
Some features of Driver Import PE (dipe)
--------------------------------
- Support sounddrivers, (includes hdaudio)
- Works with a new device installer, code by myself, now without hwpnp
- globetrotter subdriver (umts driver for lan)
- support to drivers that use "Program Files" folder (Any language %programfiles%)
- check subdriver on manual inf import (ex: hdaudio)
- Driver check (manual) os type, (When "System (OS) on HD" method selected, you see hostoses name(s) on disk(s))
- Coinstaller improved (sigmatel)
- fbwf start support:
if fbwf exists but not started, drvimpe.exe starts fbwf automatically with default %12.5 ram (130MB limited)
if you have fbwf and you want to start dipe with more percent, you can also use dipe with parameter to start:
ex:
drvimpe.exe 40 --> %40 (130MB limited, on a 2GB pc with drvimpe.exe 40 you will get 130MB on %systemdrive%)
- Warning for bus drivers with "driver need busdriver"
- Support for packed files (.7z, .zip)
( ps: Try with DPS packages, Dipe search on .7z packed file is quite fast and works with all manufacturer hwids for now, full support will be added in future)
- Note for frequently asked Nvidia Lan drivers: with "System (OS) on HDD" method you can install at once with selecting Nvidia Lan driver from list. With "Folder inf" method you should first install bus driver than maindriver.
- and many improvements....
How packed file support works:
-----------------------
Driver Import PE needs the commandline tool 7za.exe to decompress the packet.
7za.exe must be in the same folder with dipe.
The install of a dps going in to two steps.
-1st pass decompress the inf-structure and 2nd pass decompress after the choosing the driver.
A temporary folder created and used B:\dps and deleted after process. So using a little memory.
Lancelot Note: DPS forum.driverpacks.net announcement
QUOTE
Driver Forge Boot
It is the 2nd utility to mention to Add driver to livexp after boot ,
Driver Forge Boot wasnt made to install drivers to PE env, but works fine now with LiveXP by greeeaaaat help from dera, and thanks a lot to galapo.
Driver Import PE is more specialized for PE env and have great futures.
please check the links for Driver Forge for additional info.
Driver Forge DPS set scripts - Lancelot
Driver Forge Boot Land
Driver Forge Main Site
Keeping in mind that Driver Forge wasnt made for PE environment, here are some features:
*Uses Device Manager to install driver. So if you can install a driver with device manager, you can install with dforge too.
ps: some other methods added and removed in time
*Easy to use interface
*---Can not add all drivers (especially mass storage) driver to PE (no problem with intel based drivers on PE) (no problem on Windows as windows will reboot)
*---Extracts all .7z archive to search and install drivers (be carelful when used with dps packages, extract to hd in case package is too big)
*---Do not have special features to install drivers for PE so some drivers may eventually fail to install to PE environment
*+++Automatic features can be used with modifying .ini files (which i like most)
I like to use dforge for lan drivers with dps package, i prepare a ini file for that so after clickin dforge it automatically searchs and installs the lan driver.
Also i prepare other dforge packs for my Tv card and GPU (yep it works with nvidia 8500gt) so with one click they are installed.
Also during trials for drivers, i prepare a script so it is easier to make a trial.
ps: Dforge needs right language title when someone use this settings on windows (not on PE). (--Language dependent)
Check_For_Wizard_Title=Found New Hardware Wizard
It is the 2nd utility to mention to Add driver to livexp after boot ,
Driver Forge Boot wasnt made to install drivers to PE env, but works fine now with LiveXP by greeeaaaat help from dera, and thanks a lot to galapo.
Driver Import PE is more specialized for PE env and have great futures.
please check the links for Driver Forge for additional info.
Driver Forge DPS set scripts - Lancelot
Driver Forge Boot Land
Driver Forge Main Site
Keeping in mind that Driver Forge wasnt made for PE environment, here are some features:
*Uses Device Manager to install driver. So if you can install a driver with device manager, you can install with dforge too.
ps: some other methods added and removed in time
*Easy to use interface
*---Can not add all drivers (especially mass storage) driver to PE (no problem with intel based drivers on PE) (no problem on Windows as windows will reboot)
*---Extracts all .7z archive to search and install drivers (be carelful when used with dps packages, extract to hd in case package is too big)
*---Do not have special features to install drivers for PE so some drivers may eventually fail to install to PE environment
*+++Automatic features can be used with modifying .ini files (which i like most)
I like to use dforge for lan drivers with dps package, i prepare a ini file for that so after clickin dforge it automatically searchs and installs the lan driver.
Also i prepare other dforge packs for my Tv card and GPU (yep it works with nvidia 8500gt) so with one click they are installed.
Also during trials for drivers, i prepare a script so it is easier to make a trial.
ps: Dforge needs right language title when someone use this settings on windows (not on PE). (--Language dependent)
Check_For_Wizard_Title=Found New Hardware Wizard
QUOTE
Here is something users pay attention when adding Graphics drivers:
I use DP_Graphics_A_wnt5_x86-32_8102.7z to add my graphics driver
After importing
in display properties color number decreased to 4
http://img357.imageshack.us/img357/8914/20...28081757he1.png
i click Advanced and than OK and OK
http://img98.imageshack.us/img98/326/20081...pressokanf6.png
Than again open display properties,
choose 32bit and resolution 1024x768 (my personal choice)
http://img388.imageshack.us/my.php?image=2...openpropal3.png
And click OK, now GPU working with full power.
ps: Dont forget to increase frequency (if needed), my choice is 85hz (analog monitor)
I hope there will be better solution in next versions of dipe :>. For now this is the manual solution.
ps: Solution added to LiveXP with setresolution script, so all done automatically with LiveXP now
I use DP_Graphics_A_wnt5_x86-32_8102.7z to add my graphics driver
After importing
in display properties color number decreased to 4
http://img357.imageshack.us/img357/8914/20...28081757he1.png
i click Advanced and than OK and OK
http://img98.imageshack.us/img98/326/20081...pressokanf6.png
Than again open display properties,
choose 32bit and resolution 1024x768 (my personal choice)
http://img388.imageshack.us/my.php?image=2...openpropal3.png
And click OK, now GPU working with full power.
ps: Dont forget to increase frequency (if needed), my choice is 85hz (analog monitor)
I hope there will be better solution in next versions of dipe :>. For now this is the manual solution.
ps: Solution added to LiveXP with setresolution script, so all done automatically with LiveXP now
QUOTE
FBWF plugin for BartPE:
download modified plugin from Thuun
I uncomment lines from Thunn plugin, and add AUTORUN0FBWFLDR.CMD for startup.
I set %30 for startup
Put required files to \files\ folder: fbwf.sys and fbwflib.dll (I tested with fbwf.sys 2.0.965.0 and 2.0.965.0)
** WARNING: From experience fbwf cant write more than ~130mb. So if you have 330mb freespace on X:, you can write only 130mb
BartPE:
fbwf plugin is enough alone
UBCD4Win:
fbwf plugin and
you need to copy EMPTYREGDB.DAT (get it from a xp32bit installed computer) to the build of PE \I386\SYSTEM32
download mini EMPTYREGDB_Plugin
SherpyaXPE:
fbwf plugin is enough alone
if you prepare properly (look inside xpe.inf), EMPTYREGDB.DAT comes with sherpya. If not download mini EMPTYREGDB_Plugin
well i use livexp, life is easier with livexp 
download modified plugin from Thuun
I uncomment lines from Thunn plugin, and add AUTORUN0FBWFLDR.CMD for startup.
I set %30 for startup
Put required files to \files\ folder: fbwf.sys and fbwflib.dll (I tested with fbwf.sys 2.0.965.0 and 2.0.965.0)
** WARNING: From experience fbwf cant write more than ~130mb. So if you have 330mb freespace on X:, you can write only 130mb
BartPE:
fbwf plugin is enough alone
UBCD4Win:
fbwf plugin and
you need to copy EMPTYREGDB.DAT (get it from a xp32bit installed computer) to the build of PE \I386\SYSTEM32
download mini EMPTYREGDB_Plugin
SherpyaXPE:
fbwf plugin is enough alone
if you prepare properly (look inside xpe.inf), EMPTYREGDB.DAT comes with sherpya. If not download mini EMPTYREGDB_Plugin
well i use livexp, life is easier with livexp QUOTE
Mini Tutorial from Amalux (post 190) that shows how to test Ethernet driver with dipe:
1)
Run SmartDriverBackup (with your 32bit windows) and select View --> View all drivers and de-select all but the one(s) you need and save these to your to hdd.:
2)
Build LiveXP with enableing DriverImportPE, Than boot cd with LiveXP:
Run Dipe and choose import from folder (.inf) method
3)
Browse to your driver backup and select the .inf
4)
If the driver shows good, just click Import Driver and wait for final result.
After DriverImportPE wraps up, you'll need to run PENetwork and hopefully get an active connection, you can test in Opera. Good luck!
1)
Run SmartDriverBackup (with your 32bit windows) and select View --> View all drivers and de-select all but the one(s) you need and save these to your to hdd.:
2)
Build LiveXP with enableing DriverImportPE, Than boot cd with LiveXP:
Run Dipe and choose import from folder (.inf) method
3)
Browse to your driver backup and select the .inf
4)
If the driver shows good, just click Import Driver and wait for final result.
After DriverImportPE wraps up, you'll need to run PENetwork and hopefully get an active connection, you can test in Opera. Good luck!
QUOTE
User Reports/Demands for Driver Import PE:
Issue:
1) GPU driver adding - set resoulution script features for adding gpu would be nice for dipe too
- Example: post 103 - gpu adding (as reported with trials by Nvidia 8500gt) can be simpler (post 107 galapo offers set resolution script and now issue is fixed automatically with setresolution script)
2) ATI Mobility x1400 cause Bsod with livexp
- post 108 - Installing ATI Mobility x1400 graphics driver from host OS produces bsod (stop 0x000000F4 error)
- post 111 - Installing ATI Mobility x1400 graphics driver from dps produces BSOD with DriverPack Gaphics A. HWID of device is PCI\Ven_1002&Dev_7145
Demand:
1) post 105 - DrvImp.exe shell_to_start [-i optional_driver_locations_to_attempt_installation_from]
1b) (or/and an answer file like driverforge)
2) extract location may be selectable, when there is ramdisk user should be able to use harddisk to extract
2b) or/and when importing files extract directly from 7z to system
Issue:
1) GPU driver adding - set resoulution script features for adding gpu would be nice for dipe too
- Example: post 103 - gpu adding (as reported with trials by Nvidia 8500gt) can be simpler (post 107 galapo offers set resolution script and now issue is fixed automatically with setresolution script)
2) ATI Mobility x1400 cause Bsod with livexp
- post 108 - Installing ATI Mobility x1400 graphics driver from host OS produces bsod (stop 0x000000F4 error)
- post 111 - Installing ATI Mobility x1400 graphics driver from dps produces BSOD with DriverPack Gaphics A. HWID of device is PCI\Ven_1002&Dev_7145
Demand:
1) post 105 - DrvImp.exe shell_to_start [-i optional_driver_locations_to_attempt_installation_from]
1b) (or/and an answer file like driverforge)
2) extract location may be selectable, when there is ramdisk user should be able to use harddisk to extract
2b) or/and when importing files extract directly from 7z to system
