Search options (Page 156 of 213)

if you were going to spend some time on this you could even write your GUI so that you could select from multiple versions of a pack too...

I see real potential to this being a cool feature of an attended install.
and I have been considering adding attended setup as a platform.
We have had several requests for attended support, for various different reasons.
It does seem to be a logical extention of what we do and you have added yet another reason to support it.
When I add attended installation platform it seem resonable that multiboot should also be addressed (attended or not boot option)

Bâshrat the Sneaky's long term goals include adding a make ISO option from the GUI.
if that were added and attended installs were suported then a multiboot option would be the next logical step...

Thanks for your feedback.
From your original post is was not clear what was needed or why it was needed.
Now it is crystal clear on both What and Why and I agree that this could be very helpful.
although i must say i would rather fixe the packs so that this feature is not ever necessary

thanks a million
Jeff

1 third party driver packs - you are a third party therefore you are the author. (or could be)

2 you posted a driver - Implied, you want it supported... Yes you asked...

3 I am sorry... We want you to feel welcome. Jake was just trying to help you...
   Feedback makes DriverPacks better and you provided that. Thank You for participating.

Jakes attitude is understandable
- you gave the impression that you think your time is somehow more valuable than his.

This would require editing presetup.cmd.

to accept user input and branch you could add a

SET /p Variable=

help yourself...

PS since we support unattended installs, adding a stop for user input is not in keeping with our goals.
This will not be a feature - unless we add attended installs as a platform in the future.

Drivers are only installed for devices that exist in the machine...

If you dont have any wireless adapters in your machine then no WLAN drivers will be installed...
all of the drivers are not installed, they are just made available to windows setup.
only the drivers that are neccessary for a machine are used the rest are ignored.

So it would seem that DriverPacks does exactly what you want right out of the box.

now i have at least one reason to get a newer version than 8.3...

text like an egyptian... wasn't that a soneg by that all girl band... ;P

Thanks for reporting!

see you guys always compalining about wanting the latest drivers in the packs then they cause instability.

that is why we say dont ask for them. We must test them first

i will take stable over current every time...  
which is not to say we don't want to be current. We do.
just let some other poor shlub work out the bugs for us first ;P 
Then we add them... after they are tested and known good .

this is the same reason we do not include beta or leaked drivers.

let us know what you did to resolve this so we can update the packs for everyone.

Thanks for reporting the issues it makes DriverPacks better for everone.
you guys are DriverPacks heros of the day...

this would be quite easy for you to do yourself

just write a script that edits or swaps the finisher ini file after it is copied to %systemdrive%

IE put your script right before the call to the finisher (ROE or GUIrunonce).

Welcome to DriverPacks

can you belive hammer actually posted a request right below my post about not requesting intel drivers.

banned for a month... (for not being able to read)

hmmm well it is not that then... gut perhaps newsposter is still correct

try adding the monitor pack ?

i belive you can accomplish this quite easily by useing svcpack.inf

svcpack.inf runs at t-13 (right after cmdlines.txt normaly would at t-12)
You can call a script from svcpack.inf as long as that script is in \I386\svcpack\
so... add a script or exe before any other existing entries IE

[SetupHotfixesToRun]
MyScript.cmd

assumeing that \I386\svcpack\MyScript.cmd exists you could parse the commands that would normaly be in cmdlines.txt at approximately the same time during setup.