New program kicks off old program's installer

I'm not sure whether this is a VB question, OS question, Windows installer question or Installshield question, but i'll go for it anyway.


I have a program that I made in VB and created an installshield project for.  This program got distributed and installed by some reps.

I made another program, completely seperate of the first, the only thing in common is the signiture it uses (that box that comes up if you run a program off the web).

This only seems to happen for people running XP service pack 2, but when they run the new app from our website, it kicks off the old app's installer!  Furthermore, after that has happened, the old app kicks off the installer too!!!

I've seen this happen with office premier before, where any MS program you run kicks off the premiere install, and after cancelling it a number of times, you're program eventually runs.

Firstly, how can I stop this happening in the future?

Secondly how can I stop it happening on peoples machines that already have it happening?

This is quite urgent as I know i'm going to have a load of reps phoning me first thing monday morning, so ANY clues at all would be much appreciated.
LVL 2
kintonAsked:
Who is Participating?
 
moduloConnect With a Mentor Commented:
Closed, 500 points refunded.

modulo
Community Support Moderator
Experts Exchange
0
 
kintonAuthor Commented:
I seem to have fixed the problem.  By using the kill command to delete 2 files, the MSI noticed their disappearance and launched the installer whenever the .exe was launched.
I didnt realise that using the wininet ftp download overwrites files automatically, so losing the kill command wasnt an issue and solved the problem.


Not sure how to mark questions as answered when I managed to solve it, so if admin see this - QUESTION ANSWERED!

Thanks.
0
All Courses

From novice to tech pro — start learning today.