Irresolvable Background Window Problem?

[csd214]

My project uses a background window for both the installer and the uninstaller. I’m going to change the installer procedure to perform a silent uninstall before installing the new version (instead of installing on top). Unfortunately the uninstaller’s background window pops up during the install. Of course I can remove the background in the NEW uninstaller but not in the existing uninstaller used be the end user’s uninstaller string. There is nothing to be modified in the existing configuration file, I guess.

Any workarounds?

My suggestion: By default the background window should NOT be used when the uninstaller is running in silent mode.

[Adam]

This looks like a bug to me. The background window should not show if the uninstall is run silently.

Ref: 11024

Adam Kapilik

[Eagle]

just thinking out load here:

if you used an 'image' for the background window..could you delete
from the end users uninstall dir before running the existing uninistall ?
(not sure if would raise an error message)

alternatively:

if the background window has a title or can be detected via window handle,
you may be able to do the window titles -handle stuff and -window.hide...

[csd214]

It’s always a pleasure with brainstorming Aus.-NO; so far away, but still so near…

“Unfortunately” I used a gradient coloured background for the uninstaller so, accordingly there is no IRIMGn.jpg. I had no success with the window handle. There seems to be only one handle; the installer and the uninstaller have the same title (%ProdiuctName% Setup). The Window.Hide() command made the uninstaller visible!

Of course, I should NEVER ask whether the next service release is going to be published before MY release date (October 1st)……….

[Eagle]

hey CSD if ya wanna try this 'tricky dicky' workaround.

when your 'new installer' is run on end user's box, copy irsetup.exe
to the uninstall folder in Windoz folder..renamed to 'uninstall.exe'

you should then be able run it 'silent'

get the current location from the uninstall reg key..change the run command arg
to /U /S ..... or probably just /S

worth a try ?

[csd214]

Of course, I should NEVER ask whether the next service release is going to be published before MY release date (October 1st)……….

3 hours later; v7.0.4.0 is released. “My” bug is fixed (and others) & several new features.

Unbelievable. Now also my “main” project can use the automated “delete on reboot” solution based on brainstorming with Eagle in February, and the silent uninstall during “While Installing.On Progress”.

X 2

[Eagle]

How's that for 'customer support' , extra