Here is an example
Scenerio is this:
imagine i prepare a cd by using DP_MassStorage_wnt5_x86-32_805.7z - DPs_BASE_805.exe --> plugin for bartpe, livexp ... etc.
and imagine i went to a unbootable pc
and put my PE cd, and boot.
Than i get a surprise, i can not access the harddisk!
so i go do driverpacks.net to get a new DP_MassStorage_wnt5_x86-32_XXX.7z (which support the controllers of this pc) and put it on usb-stick
go to same pc, boot with same cd
with "Driver Import PE" i import new DP_MassStorage_wnt5_x86-32_XXX.7z
and valaaaa, i can access the harddisk!
OR can i,
with the current problem i can not be sure!
But i can be sure if i use "Driver Import PE" with manufacturer drivers. But wouldnt it be better to go our lovely trustable source DriverPacks which in first place created (as far as i read) for that reason.
"Driver Import PE" Scenerio's can be increased,
Ex: for now with "Driver Import PE" i can install my Geforce 8500 GT by using DP_Graphics_A_wnt5_x86-32_8102.7z on cd. .
So the PE i prepare can support all drivers DP_Graphics_A support without loosing much space.
Ex: adding a general support for ethernet driver to PE by .7z file dont loose much space (7mb - 41mb)
Ex: In all scenerios core files to bootup decrease which is especially very important for utilized .img methods (ex: livexp bootsdi method with wim)
etc etc etc......
So it is a very helpful tool. beta already works now with DriverPacks packages, but with current jmicron problem we can not be %100 sure.
I hope i could write more clearly now. Sorry for bad english.