Search options (Page 130 of 213)

Thanks to you both! 

I will get this in the next version

I closed Altan's bugtraker report for you Kenan.

I think he pretty much just agreed with me...

you cant integrate the DriverPacks with nlite...    not and have all the drivers work correctly
(He clearly states this in his post)

If you have a certain machine and you want to integrate just the drivers for that machine - then use nlite.

the DriverPacks are meant to compliment nLite if you simply use them by integrateing with DriverPacks BASE... that works the best !
and you don't have to do anything manually at all
and it doesn't take up a huge amount of space either.

If you were going to use the SAD option there is absolutely no reason to add them with nLite...
(that would be redundant - why would we want to install them twice?)
if you are going to use SAD you would either

integrate mass storage with base
or
integrate only your needed (OEM textmode) mass storage drivers with nlite

then run SAD (to be renamed SoFI) whenever you wish

Thank you debugger -

as you stated - this is well known info
an we should not loose sight of it...

There is no I5 folder in mass 805???

will have to forward that problem to Bâshrat the Sneaky... thanks for reporting!

(i belive that is related to dreamhost which we are migrateing away from )

does it only happen with jaws' app?

you can't...

not useing nLite anyway...

when you are done with nlite (and any other changes you wish to make)

then follow the directions contained in the dp_base tutorial in my signature...

here is a guide for Noobs... http://unattended.msfn.org/unattended.x … 512f1ac37/

and my OLD ones with the big DIN?

you want to keep makepnf for what you do (you do this like i do)

PNF's made simple:
It's a "catalog cache" of the currently available drivers, a table of contents if you will.
windows will check the PNF files first before doing a full blown search or the hardware wizard
if you are old enough you may remember window 98 say building a driver information database I belive this is an extention of that...
this is a speed increase for finding drivers for new hardware  (and possably input reduction)

when you prepare your image don't let the finisher run... !

this will leave the drivers in place and ready to go
(make pnf has been done and so has the PnP search path in the registry)

Run the finisher at deployment on the target machine

this will install any required control panels or other required software
and then remove the driverpacks and clean up reg entries ect...

old method
I used to do this manually after checking device manager...
and then make "per machine type" image if i had some identical machines.

a better idea is to
simply set a runonceex or guirunonce command...
copy the DPINST.exe and DPInst.xml files to the \D\ folder
(they are in the  dp_base\bin\wnt5_x86-32  folder)

1) call dpinst.exe /c /s /sh
2) call the finisher

since most imaging software do compression creating the image haveing the packs extracted is NBD.

You could use the Stand Alone Drivers (SAD) platform feature of base.
This will be a far superior way to do this...
We are still in beta testing on this feature though.
and it has a few rough edges still - but not for long!
(i am going to rename SAD to SoFI  Software First Installer... )

if you choose to use a third party tool always post in that thread...

DriverPacks works (nearly) every time... and doesn't stop for user input at all...

the best thing for you to do is to use DriverPacks "disc" method to integrate your drivers into your source.
(drivers first install)
the next best thing for you to do is to use the Stand Alone Drivers (SAD) feature of base.
(software first install)

you might also have used warm snows app and not jaws app...

The best solution is always to use the tools we provide directly - when you have a choice...

The entire point of jaws tool is to stop for user input (something we do not support)
His idea was " It would be nice to be able to Skip some of the packs for certain machines "
we disagree with this idea because our philosophy is to "Unattendedly Provide All Drivers all the time"

Personally i belive more time is lost waiting for user input or missing a driver (because you really did need that one you skipped) than would ever be gained by skipping a pack

If we ever add attended setup support - then this type of tool may be added - we don't yet support attended setup.

you may also have noticed in the three months it has been posted his thread has only had two posts that are not the team or him and one of those two is you...

Wow...

you're welcome!

have a geat day and i hope we see you around!

It is always nice to hear "it worked"...

thanks a million!