Not sure how to do this... Install appication pending driver install

this is a feature of DriverPacks.

you can create a driverpack (or modify an existing) and
use the INI in the DriverPack to launch an application
based on the presence of a specific HWID. or specific File name (like its driver file name).

the entry in the ini may look like this

[CR2]
; REQUIRED
exc_count    = 1
; OPTIONAL
exc_1_tagFiles    = 2
exc_1_tagFile1    = "%SystemRoot%\system32\drivers\P17.sys"
exc_1_tagFile2    = "%DPSROOT%\D\S\CR2\Ctzapxx.ini"
exc_1_+hwids    = 0
exc_1_-hwids    = 0
exc_1_+infFiles    = 1
exc_1_+infFile1    = "%DPSROOT%\D\S\CR2\Win2k_xp\*.inf"
exc_1_-infFiles    = 0
exc_1_commands    = 1
exc_1_command1    = "%DPSROOT%\D\S\CR2\ctzapxx.exe /S"

this says that if the file "%SystemRoot%\system32\drivers\P17.sys" is found
execute --> ctzapxx.exe /S

explained...
P17.sys will only exist if the device is present and its driver was successfully installed in the machine
if both of these things are true then we need to run the devices installer
to provide control panels and other features that compliment but are not part of the actual driver.

there is quite a bit of info already documented here on this topic -

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

Glad we could help...

well you would have had a tough time searching like that...

it is actually documented in the docs\ folder of the DriverPacks base program folder it is called

DriverPack_reference_wnt5_x86-32.ini

you can use the terms in the reference file to find search keywords if you still have questions...

sorry that our documentation is not well documented ;D

Jaak may even steal some of this and use it for .INI University training...
and then U & I 2 could be a graduate of INIU - LOL

It really is not well documented and not surprizeingly therefore that it is also not well understood.
I am always eager to take opportunity to explain how powerful Bâshrat the Sneaky's INI / DP_finisher combo is.
It is a very versitile system and was well implemented.

the drivers get installed during setup
then the finisher checks what was installed and runs appropriate programs
based on installed hardware and the INI settings associated with that hardware.

Please ask questions as it does tend to lead to documentation that benifits many.

ps
the Finisher was often in the past plagued by people who had gotten the idea that it would install drivers - it doesn't  -

We are Now able to offer a redistributable MS tool 'DPinst.exe' which does install drivers... ty ty ty
- this is for people who need a SAD disk
- (since base ver 8.*)

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

there is a rumor over in 3rd party DriverPack forum that the blue-tooth have multiple standards and were tempermental
and were abandoned as eligeble for a pack...

you should be able to get a single driver in a custom pack though... hmmm

are you sure the exe is getting called?

did you try it without the command line switches?  IE "%DPSROOT%\D\3\BT\setup.exe"
to see if it launched in attended mode?

did you try running      "c:\D\3\BT\setup.exe" /S /v/qn        from a command line?
did you try "%DPSROOT%\D\3\BT\setup.exe" /S /v/qn       from the finisher?
or """%DPSROOT%\D\3\BT\setup.exe"" /S /v/qn" ?
or ""%DPSROOT%\D\3\BT\setup.exe" /S /v/qn" ?
or """%DPSROOT%\D\3\BT\setup.exe"" /S /v/qn" ?

you might add the log switch 
           Logging Options 
                /le <LogFile>
    e - All error messages

IE "%DPSROOT%\D\3\BT\setup.exe" /S /v/qn /le %SystemRoot%\BTinst.log ?

you can run the finisher over and over - simply use the directions for a SAD disk and only put your BT 3rd party DriverPack in the OEM folder instead of all the packs

IE copy your OEM folder to the Local HDD (creating C:\OEM\) delete the main packs... except your BT Pack
and run the DP_Install_Tool.cmd as many times as neccessary till you got it workin

how about that for a shortcut to test the finisher ?

INI University - classes starting daily!

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

I've created a DP for the Toshiba Bluetooth stack a while ago, which I have tested on a few machines, ASUS R1F, Toshiba S3, S4, S5, and it looks to work fine. I was planing on uploading it earlier, but got side tracked.

Info: I installed on a machine and extracted all the drivers, as installing directly from the installer caused me problems. Therefore the drivers install first, and the applications runs if the drivers are detected.

I have uploaded it to RapidShare (DP_BT_wnt5_x86-32_080722.7z) - 28534 KB:

http://rapidshare.com/files/135965710/D … 22.7z.html

If its works and its useful, you can move it to 3rd party packs, and modify to your liking.

While here, I would just like to say a big thanks for the fantasic work you guys are doing, its much appreciated, and saved me a great deal of work, as drivers can be a big pain.

PS. Heres the main Toshiba link, to check for updates: http://aps2.toshiba-tro.de/bluetooth/?page=download

Last edited by 7yler (2008-08-09 16:16:25)

Well, no, I'm not.  I don't know if msiexec is available to the operating system at that point during install...  and I don't know if setup.exe just calls msiexec, and subsequently fails.

lol good idea.  Noob moment, I suppose.  I've got a build going with that right now, and I'll see what happens.

Er..  Yes, first one does work (and installs the software).

2nd one (from the finisher) fails - and maybe I am in the wrong place to test, because %DPSROOT% isn't set when I am finally at a point where I can use a command line.

Fantastic   I didn't know.  I keep going back to this post because, so far, its the best page for consolidated information on the finisher.  You guys need a wiki or something...

It's not, but that's how Setup.exe wants to see it...

7yler - Thanks!  I will gladly try it out, but I have my doubts - this is a Dell laptop...  my experience with Dell so far is that they tend to "brand" their stuff somehow so you need to use their device drivers.  A bit of a pain, but thanks to the flexibility of AutoImage and DriverPacks, its eeeeaaaasyyyy.  I will certainly give the pack a shot.  And I completely agree with you on the simplifying work - I'm in a shop with AMD, Intels from PIII to Core 2 Duo's and all the peripherals in between..  and boy does deploying a machine go nice n easy and hardly any issues.  Its just these silly laptops that have their custom stuff on them!

Agree, Its notebooks and all the apps that sit on top of the drivers, Bluetooth, finger readers, Hotkeys, TPM, Mouse Pads, etc, etc, the list goes on ...

I use the default DriverPacks for the core components, and create custom driver packs, a pack for each hardware model. This is so I can add/remove full driver pack support when hardware models come into the business or when  fully decommissioned.

The Toshiba Bluetooth stack should work, I have'nt seen any vendors customise this yet (but I'm shore they will :-)).

If my pack does not work, let me know and i can help to customise. There is a file AS.INI that needs to be modified to make this into a silent installation. Then run:

START /WAIT MSIEXEC.EXE /I "%DPSROOT%\D\3\BT\BtSwInst.msi" /QB REBOOT=R ALLUSERS=1

The files are extracted from the SETUP.EXE first, so AS.INI can be changed and the MSI can be run.