Adding Driver after boot (not before), Known utilities - Driver Import PE & Driver Forge & zPNP & External links Rating Options

[CD-RW]

Hi all!

A new version of Driver Import PE is available.

Driver Import PE V1.3.0.7
--------------------------------

Some features of the new version:
--------------------------------
- Support sounddrivers, (includes hdaudio)
- Works with a new device installer, code by myself, now without hwpnp
- Support for DPS packages
- globetrotter subdriver (umts driver for lan)
- and many improvements....

I test it under BartPE + Sherpya XPE and I can install all drivers.

dps support:
-----------------------
Driver Import PE needs the commandline tool 7za.exe to decompress the packet.
7za 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.

Thanks to:
Lancelot to dps support (massstorage controller)
Sbond for the nice graphic design

download on my site:

www.kare-net.de

Greetings
-kare-

[TheHive]

Thanks!

[Lancelot]

Everthing works cool, especially i like dps support with using minimum ramdrive :>:>

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.
Maybe someone out there have a nice idea for a solution

[psc]

I hope there will be better solution in next versions of dipe :>. For now this is the manual solution.
Maybe someone out there have a nice idea for a solution

That is nearly impossible.
Because Kare's app uses information from inf-files, the app cannot know about the possible options of the finally installed driver, and the options the user wants.

I'm afraid that we in future still have to tune the driver after having installed it, if we want to have more than 'standard'.

This is the price you have to pay for the ability ti install 'every driver on an unknown host'

If you have some hosts you frequently use, the better alternity is to include their drivers in the PE. And these can be tuned during build.

BTW: Compared with the rather 'big' old script there now is a very simple app script:

CODE

[variables]
%ProgramTitle%=DrvImp
%ProgramEXE%=DrvImp.exe
%ProgramFolder%=DrvImp

[process]
require_file,expand.exe
Add_Shortcut
unpack

Of course Verify etc of the old script should be added.

Peter

[Galapo]

BTW: Compared with the rather 'big' old script there now is a very simple app script:

I just tested video and mass storage scsi controllers and such a simple script did not work. I still need to use all the 'bigness' of the former script.

Kare, an idea: I wonder if it would be useful to make Driver Import PE be able to run as a shell and start another shell? Here's what I'm thinking. Set DrvImp.exe as shell and supply the shell to be started secondarily, eg explorer.exe. But before starting explorer.exe, Driver Import PE would scan supplied locations and install drivers. After that, explorer.exe would be started, with video adapter already installed etc.

DrvImp.exe shell_to_start [-i optional_driver_locations_to_attempt_installation_from]

Eg: 'DrvImp.exe explorer.exe -i host|$alldrivesroots$\DPs'. Installation of drivers would be attempted from host(s) as well as a folder 'DPs' on any available drives.

Thanks for your great work! This is really exciting.

Regards,
Galapo.

[dera]

Many Thanks Kare!
for this great tool

[Galapo]

I hope there will be better solution in next versions of dipe :>. For now this is the manual solution.
Maybe someone out there have a nice idea for a solution

This will be working in the next version of SetResolution. However, I'm not able to upload it due to ftp issues boot-land has been having (haven't been able to connect all day, although the forum's are still working nicely).

Regards,
Galapo.

[Galapo]

Installing ATI Mobility x1400 graphics driver from host OS produces bsod (stop 0x000000F4 error). Will test DP to see if that's any different.

Regards,
Galapo.

[Galapo]

Unfortunately I also get BSOD with DriverPack Gaphics A. HWID of device is PCI\Ven_1002&Dev_7145.

Any ideas?

Thanks,
Galapo.

[Lancelot]

DrvImp.exe shell_to_start [-i optional_driver_locations_to_attempt_installation_from]

Eg: 'DrvImp.exe explorer.exe -i host|$alldrivesroots$\DPs'. Installation of drivers would be attempted from host(s) as well as a folder 'DPs' on any available drives.

Yes i asked this feature to Kare too, i hope in next version :>.
It will be very easy to add drivers by showing source as .inf/.7z/Folder with such a feature. drforge uses answer file for that which cause me to make 10 scripts to ease .7z trials. (i dont like answer file, reason is obvious). With such a feature dipe can do them all with one script.

This will be working in the next version of SetResolution.

looking forward

Installing ATI Mobility x1400 graphics driver from host OS produces bsod (stop 0x000000F4 error). Will test DP to see if that's any different.

I hope DP have success, i just tested installing nvidia 8500gt graphics driver from host OS (xp32), success. I hope ati problem will be solved soon.
ps: i disable "universal driver script" during trials (i never use it anymore).

@kare:
I put a section in the end of post #1 "User Reports/Demands for Driver Import PE:" for future developments to find/remember things easier.

@galapo:
I copy and paste the defination you made for driver import pe to the beginin of post #1. Native english is better from any english