Unistalling with Installshield 7.02
Posted 06 May 2002 - 10:37
Please help. How do I uninstall my applications.
Posted 10 May 2002 - 19:51
But that should never happen when you use Add/Remove Programs. That picks up the version from c:\Windows\Installer which must be the same as the one you installed...
... unless you've somehow updated it in between?
Posted 16 May 2002 - 15:58
I also get the same error message when i try to use add/remove programs. I have basically locked up 2 PC's right now because i am unable to un-install the program and therefore am unable to re-install over top of it.
Any comments on this would be very helpful.
Remember not to name the lambs...
It only makes the chops harder to swallow
Posted 20 May 2002 - 08:48
Did you both create the project using the VB import wizard? Which version of Developer are you using? 7.03 or an older version?
Posted 21 May 2002 - 16:23
I installed with the setup.exe. I missed a few things so tried to un-install right away with the exact same setup.exe, but it told me that there was already another version installed.
Oh I forgot, It's Developer 7.0.2
Posted 21 May 2002 - 16:28
Posted 21 May 2002 - 16:38
Do you have any suggestions for removing the previously installed version?
Posted 21 May 2002 - 17:08
To fix the test machine you'll install the new release as a minor update (same product code, new package code). For this you open the setup.ini of the new release, and modify the CmdLine entry as documented for minor updates:
Now start the new setup (using setup.exe) on the test machine.
BTW I strongly suggest you use a tool like DriveImage, Ghost, VMWare or something similar. This will make it easy to restore your test machine to a clean state.
P.S. that bug is documented in the ISD 7.03 release notes, and will be added to the Bugs Bulletin here on InstallSite shortly. I didn't know about this myself until a few days ago.
Posted 21 May 2002 - 20:19
Thanks so much for your help Stefan.
I actaully just re-imaged both the Test and Development PC's from a Ghost image I had of them. But I will know for next time how to correct that problem should it happen again.
P.S. Here is the response from IS, regarding this.
This behavior happens if there is no package code for the product which you are installing. There is a bug in the InstallShield Developer 7.0 product that causes there to be no package code generated for a project created by using the Import Visual Basic Project wizard. I would suggest you to refer the article Q105823 using the link: