Drivers Pack Unpacker & Installer by Warm Snow (Page 2 of 9)

thanks . I`ve forgote about this switch

Heh, glad you like it!*

Been using that elsewhere and figured while I am already in the CP, I may just change it.

Next time, maybe I will show you another picture of mine

* Me wearing an old WWII gas mask from my grandpa

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!

Thanks for support. It's goot to have one more mirror

AGAIN new version

Rapidshare - 820 k

Deposit - 820 k

AGAIN new version

Rapidshare - 297 k

Deposit - 297 k

Unpack to the application folder and replace old files

Yes, you are right. Users asked me to give them choice there to store driver packs. Right now application have problems to work thru CD/DVD - because it can`t write settings to the ini file directly on CD/DVD . I`ll fix this today.

Hello WsnoW. Let me tell you beforehand that you were the reason for me registering here.
I have just downloaded the updated driverpacks, and I was thinking about asking if a program like yours could not be created as after all, the concept would be really simple:

1-Get PCI Id's from the system
2-Parse the inf files to get the PCI ID's each driver supports
3-Check which inf files support the PCI ID's from the system
4-Show a list to the user with an install button next to it (to go manually) and also give them a full automated install option.

Someone was asking about the size of the DP's. My question is, do I have to put them compressed or can I uncompress all of them and it'll work?
I'm asking this because extracting them takes a long time even on a fast computer, and I have to work also sometimes with pentium 4 1.4 ghz and old amd durons and athlons so...

Also could you tell us, the correct way of working with the program?

I've opened it now, and it found the DP's (7zipped) on the DP folder (note: I'm not trying to and I do not have them integrated into a windows cd\dvd). I clicked extract and it's extracting, but I don't know where to.

My idea was to burn your app and the extracted dp's, so that when I pop the dvd \ ext. hd into a machine it would simple scan the pci id's from the registry, find the drivers and install them. No extracting needed what so ever. Is it possible?

This tool (together with the excellent job with the DriverPacks of course) will make my job soooo much easier (I fix computers for a living).
Thanks.

PS: I've took a little time to "draw" a concept of what I think would be a good GUI (as my programming skills suck):

1-Clicking would detect the PCI ID's for the installed hardware, maybe just the ones without drivers installed or even better the ones with older drivers.
2-This one would install the drivers for the selected devices on the left.
3-This one would install the drivers for all the devices on the left.
4-Shows up form2
5-This could parse all the inf files on the D\ folder and subfolders and make a "cache file" so that it wouldn't have to look in all .inf folders everytime.
6- Cleans the cache.

I believe there is no need to have all the drivers extracted, since it takes space and most of them would never be needed.
If new hardware is added, then just running this installer again should be enough.

I'd like you to think of this as a suggestion. Even more stuff can be added, but I (and I think many others) like this stuff simple.

Last edited by Xeon3D (2008-04-08 01:47:02)

i meant realize it.

Right now i`m testing the new version , which is unpacking only needed drivers If all be ok , soon i`ll releze it.

thanks . At this stage i think share servers are enough . May be i`m not right.

Last edited by WsnoW (2008-04-10 00:43:21)

soon..
Jeff was coding like mad, and base will include the post install tool we were wanting, and it should be able to run post install driver install, with the exceptions found in the DriverPacks.

Pretty much like the fini.cmd and post install KTD, but this time with the minisetup we never had.

Last edited by Jaak (2008-04-13 11:46:11)

Well, DPinst was the missing tool.

We once had a sticky topic where we tried things like post install finisher and post install KTD, (fini.cmd was in there..) but when we really tested that the result was nada.. we missed minisetup. We had the idea.. we lacked the right tool.
Warmsnow deserves lotsa kudos for looking at the WAIK tools and doing something we had not tried yet..

Here is examples of ini-files prepared by new version of Drivers Pack Unpacker & Installer .

DP_Content.ini

DP_Extract.ini

Utility scans all inf files in selected dp & preparing DP_Content.ini. After all found HWIDs - one by one looked in found INFs. Search results are wrtitten to DP_Extract.ini.

Last stage iz command line

7z x DP_Graphics_A_wnt5_x86-32_802.7z -oc:\ExtractDir @DP_Graphics_A_wnt5_x86-32_802.7z.txt

Soon i`ll post ver.2.0.0 beta1

Last edited by WsnoW (2008-04-13 18:57:58)

@binary64

I don't think the database idea will happen with driverpacks.

the worst part of your idea is what if the NIC driver is the one that is needed?

1)
The program you describe would require us to allow leeching of our files. We block Leeches...
and not just because it's potentialy rude.
We think it is important for people to read the change logs and release notes.

2)
maintaining a database of single drivers and updateing it would require a lot of time for someone.
It is tough for us just to find people who can add drivers let alone keep them syncronized with a database.
the packs include the ability to index the contents (the INI file) but again someone has to populate it.
not to mention the time to recode the base. (are you willing to take on any of these tasks yourself?)

3)
The functionality you require can be had useing existing methods.
extract drivers to a disk (CD - DVD - HDD - Network Share) and run DPinst.exe.
If the space is really an issue for you you can use Base in M1 mode to cab comress them.
(just ignore the xp install and take the $OEM$\$1\ folder for your use.)
the base packs are 300MB 7z or 500MB Cabbed or 1.5GB extracted.
so you can see cabbing is very effective too and windows uses cabbed drivers natively.
the first time you run M1 the QSC needs to be built and it may take a long time.
details and instructions here http://forum.driverpacks.net/viewtopic.php?id=2264

Running dpinst against a local source makes a lot more sense, on many levels not just the NIC issue.
you could run dpinst anytime, even on startup as you suggested.
The obvious advantages of a local repository are numerous starting with
it could be totaly customized to a site or machine type(s). 
(hint: third party packs get cabbed in M1 too)

Jaak is correct that the RC3 version of base includes support for DPInst and is available to the testing team now.

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!.