20 replies to this topic

[maanu]

The following Graphical Tutorial will show you how to able to let Live XP choose and install LAN and WLAN drivers right after Desktop appears in completely Automated Way ./


here we go ,

Requirements :

1. zPNP Script by Nikzzzzz ( Post # 14 and 15 of below page )
( http://www.boot-land...?...=8846&st=10 )

2. LAN and WLAN latest Drivers Packs .
( http://driverpacks.n...verpacks/latest )

3. idx2.exe ( by Nikzzzz )
( see attachment below by me )

4.ANY tool that can pack a folder into WIM file .like GimageX etc .


now lets start it , ( ONLY PICTURES) ,
























Link to IDX2.EXE and above pictures packed in 7z.

http://ifile.it/tjbav6w

SERVICE POST :

zPNP author Nikzzzz just updated the script along with drivers too . see below ,

http://www.boot-land...?showtopic=8846

[MedEvil]

maanu, do you know if this methode will also work with those pesky drivers which always use the same names for the inf and sys files, like nvidia?

[maanu]

maanu, do you know if this methode will also work with those pesky drivers which always use the same names for the inf and sys files, like nvidia?

i dont have nividia drivers , so i can not answer . practially it should install . because in driver.idx file , there are basically hardware id's stored of the drivers included in Driver packs . it is kind of database .

nikzzzz can answer it in detail i guess if you will ask him . but i have tested the above method on about 10 to 12 systems , and in all of them LAN and WLAN drivers were installed automatically .

[MedEvil]

maanu, two more questions.
The way i understand it %systemroot% does not need to be writable with zPnP, or does it?
Does the wim get unmounted after the driver installing or is it still needed?

[maanu]

maanu, two more questions.
The way i understand it %systemroot% does not need to be writable with zPnP, or does it?
Does the wim get unmounted after the driver installing or is it still needed?

sorry i have not yet tested it without ram based (BootSdi + Wimboot ) so i dont know .
and AFAIK wim file obviously gets mounted and unmounted and ofcourse it will need ram .
but truly , i am not sure about either of above. sorry

[nikzzzz]

maanu, do you know if this methode will also work with those pesky drivers which always use the same names for the inf and sys files, like nvidia?

It should not call problems, zPNP will establish the first found on ID the driver, after performance the carrier with DriversPack can be removed.
%systemroot% should be rewritten. (Bootsdi,WimBoot or standart CD+FBWF)
Packing in Wim is not necessary if it is used, support of mount ssembling Wim of images is necessary.
Creation of an index file (Drivers.idx) is unessential, but accelerates job.
Regards,
Nikzzzz.

[Rootman]

I am confused on the 2 part RAR file for the zPNP script. The first one epands fine the second one give me a "file is broken" error.

What do we do with the 2 parts of the RAR file?

[maanu]

I am confused on the 2 part RAR file for the zPNP script. The first one epands fine the second one give me a "file is broken" error.

What do we do with the 2 parts of the RAR file?

here you go ,

http://ifile.it/jim8ncz

[Rootman]

I can't seem to get this to work. I've got the Drivers folder in the root of the build, in it is the ~75MB drivers.wim. Inside the wim is the LAN and WLAN folders and the driver.idx. When I boot to it I see the drivers folder and the driver.wim there on the SDI boot drive.

on boot I can see zPnp run for about 2 seconds and exit. PENetwork says there is no card installed. I manually ran zPnp (the AUTO link), it runs again for about 2 seconds and the same results - no net card. I have all the stock "project" net card driver deselected..

Any ideas what is wrong?

[amalux]

Hi maanu

You show a zPNP version 14 in your first pic, I can only find 13. What difference? Where to get? Thanks for nice tut

p.s. There is often problem in forum these days where some posts are 'missing'
 post13.jpg   252.74KB   135 downloads
(no post 14 & 15)

[maanu]

Hi maanu

You show a zPNP version 14 in your first pic, I can only find 13. What difference? Where to get? Thanks for nice tut

p.s. There is often problem in forum these days where some posts are 'missing'
 post13.jpg   252.74KB   135 downloads
(no post 14 & 15)

it was in post # 14 and 15 . but anyways i will upload it tonight for you ,

[maanu]

here you go ,

http://ifile.it/jim8ncz

[amalux]

here you go ,

http://ifile.it/jim8ncz

Thanks mannu

Everything seems to work I guess but the results are disappointing

I packed the wim with a batch  DPx_LAN.rar   376bytes   133 downloads and got zPNP.exe to autorun (script option didn't work for me); there should be some kind of progress message because it wasn't clear that it was doing anything until the tray notifications started popping up. When finished I was presented with this dialog:
 zpnp_err.jpg   55.94KB   146 downloads
All point to inf files located on the host's system drive or in the build folder which seems very odd. The result is that the installs failed even though the drivers are present in PE.

The devices found are comparable to DIPE:
 vsdipe.jpg   57.39KB   127 downloads
but dipe is much easier, faster and the installs are successful

Did you have better results with zPNP? Am I doing something wrong?

[Lancelot]

Hi amalux,

can you also test dipe with command line switches to get more "automagic" installation routine (required info is at right-up info button on script)

[amalux]

Hi amalux,

can you also test dipe with command line switches to get more "automagic" installation routine (required info is at right-up info button on script)

Yes, I'll test and add some options to the script if it works

[nikzzzz]

All point to inf files located on the host's system drive or in the build folder which seems very odd. The result is that the installs failed even though the drivers are present in PE.

Hi,amalux
You have specified path SystemDrive, it is necessary SystemDrive\Windows.
zPnp does not understand path "i386" and "MiniNt", "Windows" only.
It is easy for correcting, but it is necessary?

Regards,
Nikzzzz.

[amalux]

Hi,amalux
You have specified path SystemDrive, it is necessary SystemDrive\Windows.
zPnp does not understand path "i386" and "MiniNt", "Windows" only.
It is easy for correcting, but it is necessary?

Regards,
Nikzzzz.

Thanks nikzzzz

Don't know yet, I'm still playing with different approaches; I'll let you know if I need help

[maanu]

@ Amalux

here is what i did for my own pe .

1. i took latest version of zPNP (14) .and added to apps folder . LEFT IT UNTOUCHED THERE,
2. i made a wim packed file with GimageX gui . rename it to Drivers.wim file and put it in Drivers folder and saved it to root of usb drive .

i have checked the above with followed methods and success so far.

wimboot + wimpack ( regfactory enabled or disabled )
Bootsdi + wimpack (both system32 packed or not) ( regfactory enabled or disabled both )

now every time i boot from my pe on ANY system as of now , a message at system tray shows the found driver and report its successful installation . and this all process completes in under 5 to 8 seconds .

can you repeat the above procedure please ?

and as far as dipe is concerned , no doubt it is a great tool , but it has some limitations ,

1. command line method (automation) is not as easy as zPNP .
2. it needs host OS to be NT5 based only. (zPNP installs drivers from the root of booting device so no excessive load )
3. it needs human interaction most of the time ( not the case with zPNP )
4. zPNP is much much faster then dipe ( at least when we talk about automated installation of WLAN +LAN )

i would love to be corrected by someone .

[Lancelot]

i would love to be corrected by someone .

Why not.
But I have disappointment to see a good user like you commenting on things without first understanding how to use an application.

and as far as dipe is concerned , no doubt it is a great tool , but it has some limitations ,

1. command line method (automation) is not as easy as zPNP .
2. it needs host OS to be NT5 based only. (zPNP installs drivers from the root of booting device so no excessive load )
3. it needs human interaction most of the time ( not the case with zPNP )
4. zPNP is much much faster then dipe ( at least when we talk about automated installation of WLAN +LAN )

1. wrong --> you can not achive does not mean it is not easy.
2. wrong --> I assume with hostos you mean the os on disk. If so it is NOT mandatory for dipe to require hostos to be NT5 based (it is only optional), ready files or packages can also be used either at cd or on disk (or ufd).
3. wrong --> you did not check parameters carelfully.
4. no comment --> but i do not think there will be a lot difference. (+- 1 or 2 seconds)

moreover:
I can not find time to add an option to current dipe script to ease the configuration of dipe-autoinstall-lan/wan. Besides It is very easy and can be achived by various ways.
Anyway, I am happy to have 3 applications (dipe, dforge, zpnp) available for such tasks. I remember old days of having no application . Personally I do not like the idea of "autoinstalling" drivers at boot but I understand that this can be required for some tasks. That is the reason dipe have command line parameters and dforge have ini file configuration and we have zpnp for the ones who spend time to learn and use. Comparision of these 3 applications should be made by the ones who tested (and understand) all. It is NOT a nice attitute to make a comment on any application without knowing it well.

[MedEvil]

If someone's up for the task, i would be very interested in a comparison of dipe, dforge, zpnp.

[Shibby]

@maanu
I'm trying since yesterday to make it work on my HP notebook.
I have a build wich works with everything, but it seems not to find, or not running the Drivers.wim file in my CD root.

I'm using a cd to mount the image and boot in my own hp/vmware.

Could you give me a hand?
I don't know what else to do