Vista RC2 hates InstallSheld 5.5 install sets? Beta 2 was OK

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Under Vista RC2 when you try to run an InstallShield v5.53 built installation
package you get the error message:
"This program has known compatibility issues
Program My Talk Fax Pro 7
Publisher inter COM
Location C:\Users\steven\AppData\Local\Temp\_ISTMP1.DIR\_INs5576._MP"

Vista is identifying the worng file(s) as the source of the problem with My
Talk Fax Pro. This file is a temp file used by ALL InstallSheld 5.5
installers and Vista RC2 now has a problem with all of my lagacy apps!!!

This was not a problem in Vista Beta2 and if Vista is released with this
problem I will miss my January release schedule because I will have redo the
installers for the legacy components.

....Steven
 
We had people using InstallShield 5.x and I made them cease and desist.
I'm surprised it still works for you on anything... You can get a version
of the latest InstallShield (12 I think) for the price of 2 copies of Vista
Ultimate I think. Your users will thank you...

Why do you say that's the wrong file as the source of the problem? Does
it still run? I occasionally have something tell me that under XP and still
it works...

Rich

StevenAtInfoProd wrote,
 
Under Vista RC2 when you try to run an InstallShield v5.53 built
installation
package you get the error message:
"This program has known compatibility issues
Program My Talk Fax Pro 7
Publisher inter COM
Location C:\Users\steven\AppData\Local\Temp\_ISTMP1.DIR\_INs5576._MP"

Vista is identifying the worng file(s) as the source of the problem with
My
Talk Fax Pro. This file is a temp file used by ALL InstallSheld 5.5
installers and Vista RC2 now has a problem with all of my lagacy apps!!!

This was not a problem in Vista Beta2 and if Vista is released with this
problem I will miss my January release schedule because I will have redo
the
installers for the legacy components.

...Steven
Click to expand...

Surpised anything works with InstallShield, it really is the worst install
product on the market... Absolutly horrendous, from a developers and
users point of view...
 
The file being identified is a tmp file created by that version of the
InstallShield installer during the initiall decompression stage before the
installation acutally starts. As such it affects any and every install set
built with this version InstallShield no matter what is actually being
installed.

Regarding your comments, we also own recent versions of InstallShield.
There is no economic reason to upgrade the installer technology used on these
particular applications. We've never used the default look for any of our
installers so they don't look like crap, so the users don't & wont care.
Given the choice of a new feature or bug fix vs porting the application to a
new installer - which would you choose?

Meanwhile I've got production milestones to meet and having to redirect
energies from focusing on new products and technologies to instead
repackaging applications that work fine in Vista, just to the replace the
installer technology - is at best frustrating. As I mentioned in my earlier
post, the apps (and their installers) worked just fine in Vista Beta2.

....Steven
 
StevenAtInfoProd said:
Under Vista RC2 when you try to run an InstallShield v5.53 built installation
package you get the error message:
"This program has known compatibility issues
Program My Talk Fax Pro 7
Publisher inter COM
Location C:\Users\steven\AppData\Local\Temp\_ISTMP1.DIR\_INs5576._MP"

Vista is identifying the worng file(s) as the source of the problem with My
Talk Fax Pro. This file is a temp file used by ALL InstallSheld 5.5
installers and Vista RC2 now has a problem with all of my lagacy apps!!!

This was not a problem in Vista Beta2 and if Vista is released with this
problem I will miss my January release schedule because I will have redo the
installers for the legacy components.

...Steven
Click to expand...

Steven:

If you don't have to use the Windows Installer, I would strongly
recommend Inno Setup. It's free, and the author has done a lot of work
to get it working smoothly on Vista.

The only downside (for me) is that any customization has to use
Pascal/Delphi.

Actually, I am currently using an old version of InstallShield Express
(IE), which I always disliked, and decided to move to Inno to take care
of Vista and 64-bit issues (IE is 16-bit).

The IE installer worked on Vista x86, though I'm not sure I tried it on
RC2. My app ran also, but only with the dreaded virtualization. Frankly
I would be happier if it would not install/run on Vista, because then
existing customers would come to my web site and get the Vista-friendly
version (free upgrade).

David Wilkinson
 
Hello StevenAtInfoProd,
good points. I wonder if there is a way to counter that message somewhere?
There must be a database/file somewhere... Or it may be that RTM won't have
that problem. If you have an MSDN subscription you could find out on Friday.
There may be other ways to find out but I don't condone them for obvious
reasons.

Rich
 
David,

Thanks for the reply. I have tested an Inno Setup (someone else's app) on
RC2 and it works fine.

Unless Microsoft fixes this before they ship the release, I'm limited in my
options.
I either rebuild all the old installers or have a bogus warning message
upset my customers.
For the simpler install sets I definitely will check out Inno, using a newer
version of InstallShield for these apps will make them HUGH compared to what
they were before. I'm familiar with Delphi, but have never used Inno before,
hopefully the learning curve is short.
Several of the apps have a lot of script and will be painful to port
regardless of what I change to. Sigh...

....Steven
 
David,

Thanks for the reply. I have tested an Inno Setup (someone else's app)
on
RC2 and it works fine.
Click to expand...

Personally, I prefer NSIS (http://nsis.sf.net), I did evaluate Inno when
we moved from the Installshield nightmare we had a few years back, and
NSIS came out on-top, mainly due to it's open-source nature, as we wanted
to make some engine tweaks to it.

Either way you go, NSIS or INNO, I promise you will never look back, and
your customers will thank you for it. Nobody likes massive downloads to
deploy small files...

Our deployments shrank from 200MB to 130MB just by switching to NSIS, and
we had complete control over what was happening during install and
uninstall, rather than Installshields higher level launguage, where
myserious things happen (the annoying to sometimes suicidal Repair mode
for example). In addition, NSIS allows you to write your own plugins to
the installer, to extend it's functioality to do whatever you wish. Very
handy for what we wanted. I suspect INNO can also do this.

Good discussion about NSIS vs INNO here:
http://forums.indiegamer.com/archive/index.php/t-2540.html

(Ignore the last comment about the uninstaller not being able to remove
folders of files, the poster didn't see the RM -R RMDIR commands from the
manual).
 
Back
Top