[Add-on] Select desired DriverPacks during M2 install or after install (Page 1 of 3)

there was some forum group effort behind this, I suppose.
Is this open source?
Is this in alpha stage? (the topic title may have to be changed.)

As an aside; and FWIW, I think that releases of WAIK and DPinSt and inhouse/published tools to work with 2008 made developments like this possible.

I figure our admins want to know this up front.
Is this in autoIT?
will you help us improve it (not jut plug it).

I know this Sounds like a Cold shoulder, but I would LOVE this functionality.
I just don't know how DriverPacks will grow and what turns we'll have to take.

we have a few developments going and they would go to x64.
but XP x64 was not in the picture. (vista x64 is)

@DriverPacks, we was hounded by people craving for space on their CDR and x64 drivers were pruned out.
And, imho, there is nobody here who has access to all original drivers (we often do not know if there ever were x64 present in a set.)

The consent (in my point of view)  to date is that 64 for vista is definately not pruned, and x64 for XP shall not be edited out when we update.
(which would bring back X64 for XP whenever there is a review of a driver that had it.)

RE:  it downloads them and installs them with dpinst

um if chipset and LAN drivers are not installed hoiw will you access the net?

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!

The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Yes, please do Helmi!

--- do that voo-doo that you-do so well! ---

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!

The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Updated to v0.3.1

I eliminated un7zip.exe and use 7za.exe directly for extraction. DriverUpdater would wait for un7zip which would wait for 7za. In some cases 7za.eze could freeze up causing everything to become unresponsive and hidden at the same time.
also fixed a potential problem with spaces in the path.

update at first post.

Last edited by jaws1975 (2008-07-30 14:49:43)

Re: I propose

It will ultimately make the most sense to bundle them in the same manner as the OEM's provide them.

i like the idea of seperation where it will not cause extra work to maintain the packs. we would not use such long file names though.

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!

The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Updated to v0.3.4

a few changes...

DPsFnshr.exe is not used when installing drivers. DriverUpdater.exe will remove all temporary and driver files after installation. This eliminates errors for unsupported systems.
DPsFnshr.exe is kept in the x86 archive because it is still used during an OS install using presetup.cmd.
I moved presetup.cmd to the bin folder. You must use it in your install disc replacing the one in your i386 folder.

If installing XP drivers they can be named as downloaded or as base renames them.
XP x64 drivers must be named starting "x64DP" and the root folder must be "x64DP" also.
for Vista driverpacks they must be as Muiz has created them.

it will only allow drivers intended for your Operating System to be shown and installed.

It is compatible with XP, 2000, 2003, Vista and 2008. x86 or x64. Windows 2008 will show as being Vista. (difficult to differentiate the two)

tested in Vista x64 and XP x86 only.

update at first post.
updated info at first post as well.

has anybody tried these??????????
zero feedback so far.
am I wasting my time?

Last edited by jaws1975 (2008-07-31 15:55:51)

Nah, certainly not.
In the other thread, you could see there was a demand.
Thing is probably just that folks may have forgotten over time.

You may want to PM the requester so that he knows of you programme.

Also, I think we have many lurkers here and folks that have not registered.
This will follow the link and use the software but do not tell about it (unfortunately).
Maybe you can monitor thread acces figures to get an idea for popularity.

It definately is on my testing list (though I see no direct need for myself), but as with the other tests, it will have to wait a while...

Coming up next - useful links:
• If you like this project, please support it with your donation!      • Grab your HW info (HWIDs) here!     
• If you are a newbie, be sure to check out the DriverPacks tutorial!     • Here's how to create your own DP!

jaws1975 - Have you figured out how to include a countdown timer for your version?  I'd really like to have that option, so it could keep the Windows install unattended if the user doesn't deselect certain DriverPacks within the given amount of time.

Last edited by Echo_Platoon (2008-08-01 07:22:34)

I haven't gotten a chance to test it just yet.  I just wanted to make sure it had that feature, as that is an important feature to have in my builds.  I will test this out first chance I get.  Thanks.

Sorry. I made a bunch of changes last update and I didn't test "presetup".

It's fixed now!

update at first post.

I also changed the presetup timeout from 60 seconds to 30 seconds. The timer will stop if user interaction detected.

Last edited by jaws1975 (2008-08-04 10:18:55)

Wow you seem to have made a good job jaws, congrat !

Here is my source, I didn't have time to add functions you were requesting, but feel free to do so :
RapidShare |ADrive

That would be good to merge our work and do only one DriverPacks extprctor.

Last edited by Kal (2008-08-08 01:25:37)

Good teamwork guys... That is the spirit that "drives" us

LOL    (sorry...) Rofl...

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!

The DriverPacks, the DP_Base program, and Support Forum are FREE!.