Please wait while Windows configures <ProductName>
First, on a personal note, I notice no one from Acresso has bothered to reply to many of the posts. Chandima used to be very prompt in replying to posts for Macrovision/Installshield. Is she still around?
The issue:
Our customer gets this message every time she goes into our application now. This started after she downloaded an updated EXE of our application via the web. If she puts her original cd in, it lets her in. If not, she continues to get this message. The new features added to our application via the updated exe are available once she is in the program.
Exe is installed on same machine as the original installation. Downloaded from web and pasted the exe to the existing program folder, overwriting the previous exe. Customer was logged on as the same user as in the original install.
EXE is written in VB6, machine is XP
2008/12/02
Looks like the culprit is Axdist.exe, a now obsolete redistributable that was inadvertently carried over from InstallShield2.12 when we upgraded InstallShield versions.
Some of the registration process in Axdist.exe is not completed until the machine is restarted - which explains why rebooting helped, and, it gets clobbered anytime a user clears out their temporary files - which explains why the issue crops up again.
We intend to remove Axdist.exe from future CD updates and installations since MS advises not to run Axdist.exe on systems that have Internet Explorer 3.0 or higher installed.
The question is should we advise current users to uninstall the existing installation first, before running the CD update? Vista seems to require uninstallation of existing version automatically, XP and earlier do not.
We have numerous ISE 2.12 installations out.
If we issue issue an update of our product using ISE 2008, will the ISE 2008 install recognize that the preexisting ISE 2.12 installation is the same product?
Would there be any issues if the customer installed over the ISE 2.12 installation?
