Software Deployment

From your description, any reasonable person would conclude that the dialog in question is produced by the application, not the installer.

Most such dialogs have a check-box on them somewhere, something to the effect of 'Don't show this again'. You should start a capture when the dialog is displayed (don't bother with a full-blown snapshot - use a lightweight snapshotter like Ziff-Davis's 'In Control' - or use a file/registry monitor) and conclude it after selecting that check-box. If there's no such check-box, I'd wager that there will be a 'Preferences' or 'Options' menu which will control whether or not that dialog is displayed.

Thanks for your answer VBScab.
Its right, there is a check box as you describe.

But I still have a few questions.
You mention that I can do a snapshot. I am useing Wise so what should I choose to not do a "full-blown" snapshot?
Or should I use another application for that? And when its done I assume that I get a new MSI? So I should use the new MSI..? Can I use the old MST or do I have to make a new one?

Thanks!

You can use resplendence registrar. Easy to use to see what key you need to change to hide the dialog box showing the first time

Software can downloaded from here
http://www.resplendence.com/downloads

ORIGINAL: aXz
You mention that I can do a snapshot. For simple, small changes such as a check-box might make, using Wise (or any of the full-blown tools) is over-the-top. As I suggested, In Control is a tool I've used since it first appeared in PC Magazine x years ago (I was playing with Delphi and the app came with source). Search the web for 'InCtrl5.ZIP'.

Alternatively, you could use a registry monitor, as Bankeralle suggests. RR is shareware, though, whereas ProcMon is free and can selectively filter file and registry access, as well as processes.

ORIGINAL: VBScab

ORIGINAL: aXz
You mention that I can do a snapshot. For simple, small changes such as a check-box might make, using Wise (or any of the full-blown tools) is over-the-top. As I suggested, In Control is a tool I've used since it first appeared in PC Magazine x years ago (I was playing with Delphi and the app came with source). Search the web for 'InCtrl5.ZIP'.

Alternatively, you could use a registry monitor, as Bankeralle suggests. RR is shareware, though, whereas ProcMon is free and can selectively filter file and registry access, as well as processes.



Thansk. I downloaded Process Monitor and filter on spss.exe and it let me know that spss creates a registry key named "show_welcome_dialog" with the value 1 under "\HKEY_CURRENT_USER\Software\JavaSoft\Prefs\com\spss\/S/P/S/S for /Windows\16.0\en\ui\dialog_settings\welcome_page"
I added the key in my mst but gave it the value 0 and its works perfect.

Thansk all!

Ha ha! Where are all the ProcMon knockers now, eh? :) LOL...

Glad it worked out for you. You may want to post a note about this into AppDeploy's 'Package KB'.

ORIGINAL: VBScab

Ha ha! Where are all the ProcMon knockers now, eh? :) LOL...

Glad it worked out for you. You may want to post a note about this into AppDeploy's 'Package KB'.



Yes I will do that. BUT I get one more problem when I started to test the package. The registry key I added in my MST is under the current user. So when I install the package with the command "msiexec /i [MSI package] TRANSFORMS= [MST File] /qn" its works fine. But when i deploy the package over the network with CA's Software Delivery it will be installed with another useraccount so the changes in the registry dosent matter for the user that will logon.
How do I manage this?

- Create a new feature in your transform. Most of us would probably call this feature 'CurrentUser'
- Add a new component containing the relevant HKCU registry entry. Ensure you set the entry to be the component's key path
- Optionally, you can set the new feature to always be installed and/or hidden.
- Ensure that the shortcuts are advertised.

by the way why are you trying to do all of this, spss 16 is a msi already and can but deployed with /qb! or you can create a wrapper and do setup.exe /s /qb! i don't see why you are doing all of that. and to activate you can run spssactivator.exe with the serial number.

Im doing an MST because I want to tweek the MSI in some places. For example, I want to point on the licens that is on a specified server during installation, remove some shortcuts etc....
Thats what I learn on the course I went to anyway....

Did you read the whole thread (a failing of mine lately!)? The first post says:

I have done a MST to the MSI file for SPSS 16.0 and it works fine

My later responses have been connected with getting the OP's install to write entries to HKCU.