Software Deployment

You need to research Custom Actions. There are some good links in this thread http://itninja.com/question/installshield-vs-wise-for-repackaging041

The problem with the example posted on this site is that it was built using a Wise and a wise script. It's a disservice for those who do not have Wise to see how this is accomplished by looking at the msi in Orca.

The problem with the example posted on this site is that it was built using a Wise and a wise script. It's a disservice for those who do not have Wise to see how this is accomplished by looking at the msi in Orca.


Joedown,

Here's something that's microsoft: http://msdn.microsoft.com/en-us/library/aa368268.aspx Also, I think Ian's link contained stuff pointing to A. Stebners blog, which is not Wise specific. Also, I'm pretty sure that WinInstall, which the OP says he has, must have a GUI similar to Wise's where it divides up the custom action and script section into full UI, execution mode and deferred mode.

Thanks for the replies. I am slowly getting somewhere, have figured out where to put the name of the custom action in the AdminExecuteSequence table and have created the custom action. Now I just need to understand where the rest of the information goes (so far none of the links have shown this). A custom action consists of a Name:SETUPADDTOSOURCELISTA Type:DLL Source:??? Target:???, seems logical that the setupapi.dll is either the target or source but no one explains which. I am guessing that the function and parameters belong in a file that is the other (source or target) or maybe just use the driver.inf ?

ORIGINAL: dang574
have figured out where to put the name of the custom action in the AdminExecuteSequence table and have created the custom action. That means that the CA will only run when you use the MSI to create an administrative install point, which is NOT the same thing as installing it using an account with local administrator-level privileges. It needs to be in the InstallExecuteSequence if you want it to run during a normal installation.

Next, get yourself a proper authoring tool.. Although I'm almost certain to get flamed for saying so, only a masochist would use Orca to build an MSI from scratch, particularly a driver install.

Lastly, check out the topic at the top of the forum 'PNP Driver Install Template'.

Thanks VBScab, I am using Wininstall 8, which has a nice little wizard to create a custom action. It starts with entering the name, no problem SETUPADDTOSOURCELISTA then it goes to select the type, again no problem select DLL from the list. Next it wants to know the source (binary table or file table), next it wants either binary entry or table entry, no clue what to put here. Next it asks for the DLL entry point, I'm guessing here but I put [systemfolder]setupapi.dll. Finally it asks for execution type: Always, first sequence, once per process, client repeat or inscript, and a return type: continue or asynchronous, and a do not impersonate checkbox.

I hope you can see how none of this equates to what is in the PNP driver install template that I have read over and over trying to figure out where to put a Function and Parameters. Any help would be greatly appreciated.

ORIGINAL: dang574

Thanks VBScab, I am using Wininstall 8, which has a nice little wizard to create a custom action. It starts with entering the name, no problem SETUPADDTOSOURCELISTA then it goes to select the type, again no problem select DLL from the list. Next it wants to know the source (binary table or file table), next it wants either binary entry or table entry, no clue what to put here. Next it asks for the DLL entry point, I'm guessing here but I put [systemfolder]setupapi.dll. Finally it asks for execution type: Always, first sequence, once per process, client repeat or inscript, and a return type: continue or asynchronous, and a do not impersonate checkbox.

I hope you can see how none of this equates to what is in the PNP driver install template that I have read over and over trying to figure out where to put a Function and Parameters. Any help would be greatly appreciated.



binary or file table refers to where the dll is stored, is it a file in the installation (file table) or a utility you just want to run once (binary).

As for the other choices try the defaults and see how it works. Presumably you do at least know the command line you want to run? If so, then the links Ian sent should help you to get comfortable with custom actions.