ginormous problem (for me at least)

[gnznroses]

My software is a security app, and one thing that it does is terminate installation programs on sight. I updated Setup Factory to the newest version and now I have the problem that my software doesn't work against my own setup program. When I send a wm_close to the setup program, it shows the Abort? prompt. The problem is that now when I send a wm_close to that window, the setup mysteriously begins running, attempting to install the software. That's not normal operationa nd actually it makes no sense. Even if the close message were interpreted as "No, don't abort" it shouldn't start installing because none of the screens have even been gone through (eg, Select Install Folder, License Agreement, etc). This is a huge problem for me and I don't know what I can do about it. I'd rather not change to a different setup engine just to avoid users seeing this happen (my software still works against other setup apps I try it on).

[Winsteps]

How about sending "TerminateProcess" to that "Abort" Window's process? You already know that things are going wrong .... so a memory leak (or whatever) is probably only a minor concern.

[Lorne]

It sounds to me like your installer may be getting built differently -- perhaps due to different project settings after upgrading to the new version of SF7.

Another possibility is that your software is killing the wrong process. SF7 uses a launcher stub to extract a second executable from its archive, the launcher normally exits as soon as this is completed at the beginning of the setup process. If you terminate the launcher after the actual installer is launched, that won't have any effect on the installation.

Has anything else changed on your system? Have you made any changes to your security software?