Software Deployment

The Guide in App Deploy, packages, describes how you should disable the "custom actions" and that should disable the Registration screen and the xetensions ergistration, but I have found that simply disabling the custom actions or deleting them in "Custom Actions" the Table has no effect. I am going to try a Setupcapture to see what changes between a registered and non registered Paintshop.[8|]

If Paintshop is an MSI, have you tried creating an Administrative Install Point? It's basically an extracted and patchable MSI & folder structure that usually includes licensing data in it so it doesn't have to be entered every time.

If they do registering by a custom action, I usually have good results by pre-populating whatever properties are passed to the CA and modifying the MSI Script and CA's conditions to keep the dialog from displaying, going directly to the CA.

Yes. An install from the Administrative installation point results in three screens being displayed when Paintshop Pro 7 being opened for the first time only. The First is the registrstion screen which runs an executable within the INSTALLDIR of Painshop called "Register.exe". The second screen displays the File Associations screen, and the third displays the "Hints and Tips" screen. I cannot locate custom actions for these events in the Wise script . The Setupcapture I did has captured a large number of registry changes that occur when you pass through these first three screens, but nothing that is clearly changeable to disable these first three screens. Do you know of a way that the application might be calling these screens in this Custom action like way? [&:]