Bashrat, I am using string manipulation to isolate specific parts of the filenames of your DP naming convention for presentation reasons. and have a few questions:

1) will the naming  convention remain the same, with underscores etc.

2) I noticed on you naming convention thread that versions were using the "." convention (IE 6.08.2 etc), but some of the "704" releases have an extra digit, eg 7041, I will summize the extra digit is something like an update or bugfix  after the main release etc. Am I correct?

Regards

Les

Update!

I have so far:

1) created the GUI.
2) Provided an output window which lists all the found DP`s automatically, along with filesizes and versions.

To Do:

A)Hook up the compressor and get it to scan for *.inf`s for output to another column in the output window with   totals for each pack


(This seems like a good idea to me at the moment so we can verify the output file totals to the originals for errors, but if you think it is superfluous tell me and I`ll drop it ok)

B) Extract the VID`s etc from the packs and complie into index

C) Get the transforms code from bashrat and hook that in

D)  Redirect the paths in the index to the CD ready for burning

At this stage I plan to test it for conformity and then release it for beta testing (after testing it myself of course)

While that is going on I am planning further sprucing it up by working on the following (among other things):

E) Integrate the update feature into the GUI

F) Tightening up the code

G) Maybe providing an output window as mentioned earlier (vendor, model, version etc) If people want such a thing

BTW The AI help file I printed out was nearly 800 pages! YAY - good job I`m a bookworm smile

There goes another 6m leptons! (he he)

Overflow. If you would care to be a bit more specific with your ini pack query, I may be able to work on it ok

Bashrat, I cannot find an your email address, can you please email the transforms code to me at les95@hotmail.com (you may have done this already but I can`t see it amongst my mail)

Thank you

The first release will just create the index file then I will continue the development to spruce it up ok

And yes I would like the HW transforms code if you would be so kind, you can send it to les95@hotmail.com
cheers

I have read the manual for Autoit and the UDF file and have started building the GUI.

A DP update/comparision function will be builtin along with a download function

apart form the obvious is there any function anyone would like to see on this GUI?

for example output options for various file formats (.xls?)

I am thinking about providing a tabbed area in the GUI for output results for the different packs to provide info such as Vendor, model, version, release date, OS etc along with a save function for each/all etc. Would this be worth providing?

Les

Thanks for the feedback guys, Ive looked at the perl script and it may be useful to us but as Bashrat is using Autoit I may use that instead for integration, compatability and continuity issues.

My brain is in super persuit mode now! in the time it took me to write this sentence I burnt 6m leptons!! (he he)

Will keep you posted with progress reports ok wink

I Am Aware that I would have to write a program to do this but i think such a task is within my capabilities as I am experienced at programing and consider that there is no point burning leptons (and one would have to burn many when it comes to the logic of programing) only to end up with someting that is already availabe on the net, has a confined market or is useless.

I may not have done much programing latlely but logic is logic and never changes - Hey, it`s logical!

This is idea is just up my street! I will start working on it yesterday! (he he) smile

Only thing that remains to decide is which PL do I use? any suggestions anyone?

So if I put the time in to compile the index from the DP`s then setup can just extract the driver it needs from the compressed .7z files yes?

OH pleeeaase say yes!!!! wink

Is it possible to do this:

compare the vendor ID`s /device ID`s /version ID`s etc from those extracted from the hardware by the install routine of windows to those that could be compiled from a list from the driverpacks then just extract the driver for the hardware instead of decompressing and or copying the packs to the hd and searching from there?

I would be quite prepared to help to achieve this if people want

I have been using Method 2 to install drivers up to now. this has achieved my objective and I have backed up the D directory that is put on the hardisk to a dvd for later use on other systems that may need drivers or driver  updates

I have put ALL the driverpacks on the install cd (prior to the latest dp releases as of 16 April) and it works flawlessly - adds about 10 mins to install process - just enough disk space!

If I use method 1 -

A) Will the installation copy the dp`s to the d folder and search from there? OR-

B) Will the installation just scan the $OEM$\$1\ on the cd/dvd for the drivers it needs?

I know this is explaned in the s\s methods window but the mechanics of the two different methods is unclear to me.