Choose DriverPacks during (attended) Installation (Page 2 of 2)

WOW KAL fantastic work this is just what we all have been waiting for thank you so much, i am making a new xp right now so i will test this and report back asap. i actually contacted hawk (the first poster) about trying to make this project and we found (after a lot of googling) something called driverpack selector on an unattended xp called LastXP 20

i have been trying to mod/use the driverpack selector thats on lastxp v20, i just acually got it working when i found this post, the driverpack selector on lastxp is amazing, but a little messy to set up, but it does do 3rd party driver packs which i am not sure your version does (downloading yours now  1k a sec wtf) i will put up a mirror when its done.

please please carry on your great work on this project it would be great if we can have a proper official driverpack selector.

here is a screenshot of the dpselector from lastxp ( i can send you the files if you want to take a look at it )

thank you all driver dudes

and admin please make this topic a sticky

mirror for DPsXtrct-0.1.zip
http://uploaded.to/?id=3bnddf

Last edited by sT0n3r (2008-07-07 23:01:40)

Hi sT0n3r!

At least, someone posts to this topic
I'm glad that you like it, and I'm gonna include some changes that you suggest. Unfortunaly, I'm currently on vacation, I'll be back 27th July. So I can code quickly, but I can't test : I just have my laptop.

Well, my program does support any DriverPacks : official & 3rd party. You just need to put the DriverPack in the same directory as DPsXtrct.exe, in 8.3 name format. Then, you give a name for this DriverPack in DPsXtrct.ini, as explained above.

I want to add an option that "DriverPack selector" has : Keed The Drivers. For this, my program needs to edit DPsFnshr.ini when it's copied to %SystemDrive%, and modify "KTD" entry. To be able to do this, DPsFnshr.ini needs to be copied by my program, not by presetup.cmd. So we'll need to modify presetup.cmd to skip the copy of DPsFnshr.ini file. If my DriverPack Extractor becomes an official part of this project, then presetup.cmd won't need extra edits and DPsFnshr.ini will be generated automatically with official DriverPacks names.

Cheer,
Kal

Last edited by Kal (2008-07-08 00:12:21)

as your code was not written in auto it only the inspiration will make it into the base code (i will have to code it again) NP. if you have a working system in place then writing the code to duplicate it will be a breeze. Lets see how popular this is before we get a ton of hours invested in it.

If you are useing this please add your comments to this thread or the thread that will be added in 3rd party DriverPack.

I will suggest that this gets added to the third party DriverPacks forum / downloads
that way it can be made available without the nuisance of say rapid share

Thanks for your generous contributions

ps if you put your program after the copy of the finisher ini then you would only need to edit it (or overwrite it)[or not]
- IE simply move the extraction step to after the finisher step in presetup.cmd... ( I could make this change in base quite easily too. )

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

because it may need to be updated...

IE i cant tell you how many times i wish i had the source code for our setup.exe. I am just SOL on that one.
I am not going to do to someone else what i would not want to be done to me. ( and it has been and i hate it )
If I include something with base then the source code for it will be available to the code team, period.
   ( Wim can of course do as he pleases )
We have no intention of useing more than one language to code DriverPacks.
You and I might both get hit by a truck on the same day

for many reasons... is the reason

yes yes yes... yes and yep.

wouldnt even need a dialog if they select no packs ther is nothing for the finisher to do...
no reason to keep it - so no reason to bother asking...

-------------------------- more

It is quite a bit easier to add it to base than to start from zero and duplicate the many functions that are already included with our programs (75% of it already exists as subroutines)

For example - converting 8.3 pack names to thier full names is an existing function that is built into the code 
You are useing a data file for this. So i would not need to do that i would just call the routine .
this automates a now manual process and eliminates an unneccessary file.
by extension there is no need for you to write a routine to do this since we have one.
I cant give you code bytes or subroutines to use because you did not take the bait when i offered AutoIt as your starting point.

What you have works. It is simple and effective. that is great!

Let's see if what you have already put here generates any interest before you or I sink a bunch of time into it.

If it IS popular then I will make it a feature,

I can add the features you are suggesting with a lot less trouble / code than it would take for you. especially like the pack names and finisher pathing type of stuff that we have existing code for.

It also adds fuel to the attended setup as a supported platform as well. That has become a more popular request but still not a top ten item.

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

Sure, I will publish the source code when I'll be back from vacation. I will cleanup the code and put GPL header. But, IF it becomes a part of DP base, maybe you can let it in Delphi and I'll do the updates needed
Well, we're not yet at this stage, I don't care if it's written in Delphi or AutoIt, I'm just afraid that some functions are not avalaible in AutoIt. I used Delphi because I couldn't find a great gui builder for AutoIt.

Well, as sT0n3r pointed it out, if we remove the finisher, then we will have an error when RunOnceEx/GuiRunOnce/WPI will launch it becomes it won't be present in %SystemDrive%. One solution would be to launch finisher from a .cmd, something like that :

DPsFnshr.cmd

@echo off

:: Run DriverPack finisher ...
IF EXIST "%SystemDrive%\DPsFnshr.exe" start "DPsFnshr" /wait "%SystemDrive%\DPsFnshr.exe"

del /Q "%SystemDrive%\DPsFnshr.cmd"

Well, maybe my explications was confused, but DriverPacks Extractor doesn't convert to 8.3 format. I just say that when someone use a 3rd party DriverPacks, he needs to put it in OEM folder in 8.3 format and modify DPsXtrct.ini.

Thank you
To become popular, maybe we need to move this thread to a place where there's more visitors, or make an announcement or something like that. I don't mind if it's popular or not, I just made this to suit my needs and fill request from others in the thread.

@sT0n3r:
I'm really glad that it worked like a charm for you! It's good news. The bug you found will be solved by the trick I explained above. But it will requires extra files edit...

I will add the Keep The Drivers option when I'll be back

To conclude, Sardena is bellisima

Cheers,
Kal

I am not going to be testing this if this does not add choice for third party and then separate third party.
(and it also has to work in M1.)

no third party are kept track of too. (base creates a txt file that contains the original name when it renames them during the slipstream)

This absolutely won't work with M1 because presetup.cmd is not used -
jaak is correct this will not work with M1 -  but m1 is not very popular anymore either so it is only a minor flaw.

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

Nice work. Works great.

my suggestion for the problem if no drivers are extracted in presetup is...
If nothing extracted then DevPath can't be lauched either.

check if the folder "D" exist. if so run DevPath. if not then don't run it...
IF EXIST %SystemDrive%\D\ %CDDRIVE%\OEM\bin\DevPath.exe %SystemDrive%\D

If folder "D" does not exist the just create the folder...
IF not EXIST %SystemDrive%\D\ md %SystemDrive%\D

That way you still run DPsFnshr without error and you don't need extra batch files or need to modify winnt.sif.

presetup.cmd
http://www.mediafire.com/?wv92kg9czoj

:EDIT:
I've managed to code my own version of a driver Selector. The only thing I haven't figured out yet is the auto install if no user interaction part, which important.
I will post it when finished.

Last edited by jaws1975 (2008-07-21 18:05:47)

I agree.

I really just want to see if I could do it. I figured out the timer thing "on paper". I can't test it yet though.

If you launch mine from presetup with the parameter "presetup" it works like yours. Extraction only.
If launched via double click it will extract and then launch dpinst.exe to install the drivers.

All works perfect but the onMouseOver/Move timer.

I'm building mine more as a learning experience then anything else.

Ok, seeing as this thread is not so much a request anymore but rather offering the once requested features, I'm going to move it to the Software Forum, as I see it fit in there much better.
Also, both your effords should not be in vain so I am granting this a sticky!

It surely will help a lot of users with specific installations.

EDIT: Also, the first post will need some cleanup so new users can easily find those programmes you linked to and aren't being confused by what still looks like a request thread

Unfortunately, I can only delete or edit posts, not split them off the thread.
So, either I ditch Hawk's post putting my own content in or I delete all posts that still deal with the request...
Ideas?

Anyway, Kal, are you the same guy who posted that big pack AddOn over at Wincert.net?
Nice to see you contributing over here, too!

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!

Alright, then I'd say you both get into contact to get things together.
Then, you can post a new thread which will serve as a basis for downloads and possible discussions which I can stick.
Better than cleaning this one up I guess.
A fresh start is always preferred, plus, I do not really trust this Forum software that much to dare any greater editing sessions

Oh, I'm also Helmi over there, in case you haven't guessed yet

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!

we might trim this thread back into a request in Feat Req and link to a new topic here in Software.

we might also start with a good title like
"[Add-on] Select desired DriverPacks from Pop-up Menu list with a time-out feature (M2 only)"

A good Intro sentence like - Ever wished you could skip one or more of the packs during the install (or repair) on a particular machine?

Summarize the Why you Want / Like / Need and invested your personal time in this idea.

How to use and where to get

a reverse link back to the Feature Req topic here so we can keep track of interest in this potential feature.
Features are obviously prioritized by feedback so if we want this to make my to do list... rally the troups

PS since this would be a sub feature of attended installs (AKA 'repair' ) it is also a vote for that platform being added as 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!.