> This has happened numerous times in the past and I never can pinpoint
> what caused it. It has to do with Installshield (either a failed
[quoted text clipped - 10 lines]
>
> No one seems to have experienced this weird happening...
As you said, this is normally due to a broken install, and is often
triggered by using the custom controls.
Have a look for the "MSI cleanup utility" and remove the errant install
form the list.

Signature
Dean Earley (dean.earley@icode.co.uk)
i-Catcher Development Team
iCode Systems
Raoul Watson - 10 Jun 2008 01:02 GMT
>> This has happened numerous times in the past and I never can pinpoint
>> what caused it. It has to do with Installshield (either a failed
[quoted text clipped - 16 lines]
> Have a look for the "MSI cleanup utility" and remove the errant install
> form the list.
Thanks Dean.. I appreciate your advice.
I have looked at this utility but got scared because i don't remember half
the things on my PC... didn't want to get rid of something I need.
I was hoping they would make a version that will scan failed installs in the
regitry 9sopme sort of cross referencer)
Dean Earley - 10 Jun 2008 08:52 GMT
>>> This has happened numerous times in the past and I never can pinpoint
>>> what caused it. It has to do with Installshield (either a failed
[quoted text clipped - 22 lines]
> I was hoping they would make a version that will scan failed installs in the
> regitry 9sopme sort of cross referencer)
Surely you know what you use?
Normally, the culprit app is the one listed on the "please insert disk"
dialog, in this case, InstallSheild?
You can always reinstall later.

Signature
Dean Earley (dean.earley@icode.co.uk)
i-Catcher Development Team
iCode Systems
Raoul Watson - 10 Jun 2008 09:59 GMT
..<snip>
> You can always reinstall later.
You are absolutely right.
I'll knock 'em off one at a time starting with the most recent installs and
removals (my previous experience indicated InstallShield Express is just
invoked but the failed app is another one)