Search options (Page 193 of 213)

if drivers are installed during setup then they are cached locally on the machine, without KTD.

(windows\system32\drivers\) and (Windows\inf)
and most notably (WINDOWS\system32\ReinstallBackups)

you may use KTD to keep only the packs you wish, however i don't think you need it if you are aware of
      WINDOWS\system32\ReinstallBackups

mass storage text mode should work alone (without mass storage PnP selected)

can i get some more feedback on the failure -

mass storage textmode should be selectable even if no other packs are to be added... as long as a valid mass storage pack is available.

Yes. The way to just leave them there after we are done is called KTD (Keep The Driver)

DriverPacks does not install drivers through KTD...

In fact KTD is not recomended by me personaly. it is only good for what i call a Test Bed computer. like a technicians machine on his work bench to use for testing customers cards. (quickly identifying if an issue is hardware or software releated.)

In any other environment;
if you are adding hardware you are physically going to be at the machine and have it open anyway. might as well take the latest greatest driver? 

I assume if it is new it won't need hardware added soon. why burn 1.5gig of HDD space on out dated drivers?

Turn KTD off unless you plan on rotating hardware on the machine regularly (like a test machine)
if you are running KTD on a test machine it is likely that you will be reloading it often, and would then be a good DriverPacks tester and have the latest packs all the time.

i will see if i can... not sure what is invoved yet.

sometimes yes and somtimes no...

it falls under "other" for sure
I have to check out the new version now too...

yes it does seem interesting....

That is an excellent question.

The answer is NO... the Joshua plugin will become obsolete when I release DriverPacks LAN.

Be aware that we have not created a plugin for lan yet.
Copying the packs to the network folder is quite a bit different than createing a plugin.
I don't like to type so i will not elaborate on the many reasons.
Just belive me that the problems you are experiencing will not exist in a true plugin.
I didn't bring this up before because you were having fun with it and i saw no need to be a kill joy,
that and it beats a blank by a large margin.

i am codeing my butt off ATM on base
i have fixed the M1 double \d error
the bug where the $OEM$ folder was crerated when only masss storage was selected
the HJW pack is now recognized
SP3 support (beta is out on that)
the page profiles errors (base gets lost when the back button is pressed in gui mode)
removing hardcoded folders in Chipset. (there is a new approach to chipset.)
BartPE gets; new verify path code, chipset and cpu support will now precede LAN since you guys did this.

I hope to post the alpha on this as soon as today, but i won't put it up till i am happy with it and i am tough on myself.

Hello gvasile
Welcome aboard, and thanks for the high praise.

They are already created and have been for years...

Does this mean that we already became the "the most complete and usefull drivers collection in the world"  years ago?

BTW you forgot to ask about printer, monitor, card reader, flash device and TV packs which are also already created.

blue tooth is not a good standard right now and a pack does not seem feasable until the OEMs settle down.
apparently this has been tried with little success.

LOOK ---> http://forum.driverpacks.net/viewforum.php?id=13

the search feature is already included in the forum too

the Joshua plugin for nvidia will probably be teh way to go for nvidia until this is actually coded correctly as a plugin. ( in process atm)

bartpe is - for certain types of drivers - yes