Does Anyone Here own Installshield Product

I've posted this in many newsgroups. Please know this is not just Netscape communicator related.

Hello Programmers,
1st I'm not a programmer so if you reply please know if you speak
"programmese", I'll probably not understand.
I troubleshoot at, a Q@A site. We have been
seeing a lot of problems lately with
installations [THE DECOMPRESSION OF %S FAILED] using "Installshield".
It's hard for me to think that after reading and trying most of the
solutions recommended; most are changing the 'temp' and or "tmp", i.e;
SET TEMP=C:\TMP and variations of that, along with very good
optimization of the questioners system, including:
1. Turn off CD-ROM caching.

2. Make approximately 45 MB of hard drive space available at
minimum, as Installshield (depending on the parameters set by
the software writer) will look at the minimum set when the
file(s) are compressed. This makes room for the program files
(38 MB base parameter) and extra working space for cleanup if
that parameter has been chosen. Compressed drives only estimate
the amount of free space available and may need even more than
the amount being reported as available (Installshield parameter
minimum as against acutal free space plus cleanup). If this has
been left at default values in Installshield, a program with
15MB of files could be calling for 40MB plus another 40MB for

3. Free up memory. Installshield requires 8 MB of physical RAM,
with approximately 5,500k free.

NOTE: In addition to the foregoing, if QEMM or Stacker are
running in the background, the probability of failure increases
progressively in a linear fashion, eg: the lower the amount of
installed ram, the higher the probability of a failure.

We still are not solving this.
I'm beginning to think it's more hardware related that software or
envirernment setting.
The [THE DECOMPRESSION OF %S FAILED] is mostly with Netscape
Communicator, however, if a person has trouble
with that he or she also has the identical problem with ALL other
DECOMPRESSION installations.
Can anyone help me understand why, [other than a corrupted file], this
occurs and hopefully how to fix it.
A lot of people now simply can't install programs.

NOTE: In all cases the questioner reports a certain % where the istallation fails. This varies,
i.e.; 38% then fails, or 78% then fails.

Please refere to
for related conversation.

LVL 14
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

I know it's not much of an answer, but have you contacted InstallShield and/or Netscape tech support? (I'd try the former first)

The line "THE DECOMPRESSION OF %S FAILED" sounds like part of a C language printf statement where '%S' is supposed to be replaced with some text which, for some reason, is not.

If you can get ahold of a good tech support person and give them that line, perhaps they can pass it to a programmer who can figure out what would cause the error.
smeebudAuthor Commented:
I 1st posted in the C Language area, and was told it was a Visual Basic call???

I got the errror myself lately, I just cleared out my /temp and al was OK (I'm on an NT4 server)
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

I've used InstallShield and another install package called WISE, I think basicly there're 2 scenarios for your problems:

1. out of disk space.
2. if you're installing from a CD, the CD is bad. Try it on another CD drive (different brand).
The times installation failed, have you tried copying the CD to the HD and installing from there? I've had troubles lots of times due to driver failures, which didn't occur when copying to the HD.
Searching DejaNews and some other sites gave several solutions. Maybe you've already tried them, but in a nutshell, here they are (I quote):

"In addition and in some cases, the video driver may have caused a problem during initial stages of setup. You may want to switch to VGA video driver for the duration of setup."

"I suddenly started encountering this problem as well.....I then found out that this was happening because of some device driver that was installed...what I suggest is that you identify what you installed recently...then uninstall that and try the self extracting file luck, then try uninstalling another software that you my case it was ZipFolders that was the culprit!"

"This error is very common in WINOS/2 when the partitions are HPFS because the Win API is not capable for determine the amount of free space available in large partitions (>2Gb). In old Win (Fat16) applications is possible a similar behavior with FAT32." (if this is the case, I don't know of any solution...)

And from
"Search the hard disc for uninst*.exe; if you find files that fit, make sure they are not Read-Only."

Some other documentation stated that it could be due to driver failure and/or hardware failure. Try the "copying to HD" I first stated, or try to install in "Save Mode".
If I understood you correctly, there was enough room on your HD and the TMP and TEMP settings were correct and the TMP/TEMP directories are empty when starting the installation.

Hope some of these options apply to your problem,

Regards, Abel
It certainly is NOT a Visual Basic call.  We don't use anything that even remotely looks like that (the '%s', I mean).

Apparently, from the last two postings it seems your problem is drive space (or lack there of).
BTW, I have InstallShield 5 Free Edition which comes with Visual Studio. In the documentation supplied with it, there's no mention of this error.
BTW2, you'll have to excuse me, but I'm going on holiday. If you want any reply from me to a reply of you, it'll be in about 10 days....
smeebudAuthor Commented:
Hello all,
Well, 1st Abel. All you information is good. But I already had that documented.

2nd, I looked at my question and realized I left out a important part.
I said, "The [THE DECOMPRESSION OF %S FAILED] is mostly with Netscape     Communicator, however, if a person has trouble  with that he or she also has the identical problem with ALL other  DECOMPRESSION installations. Can anyone help me understand why, [other than a corrupted file], this occurs and hopefully how to fix it.
A lot of people now simply can't install programs.".

What I left out was that the  [THE DECOMPRESSION OF %S FAILED] message occures with netscape. Other installation will not flash the [THE DECOMPRESSION OF %S FAILED], but rather asorted other messages, or simply lockup the systems.

I have not seen and error of that nature yet when installing from a CD.

Is what everyone telling me that the [THE DECOMPRESSION OF %S FAILED] message
is not from installshield??

Yes, it IS from InstallShield.  Extstub.exe contains that message.
A bit more on extstub.exe.  It's used in self extracting setups (single file installs and, I believe, install from web).

There is no delimiter between these two lines in the executable, so they are probably related:
The decompression of %s failed. There may not be enough free disk space available in the TEMP directory.

I would be willing to bet that you don't have enough space in your TEMP directory (or your TEMP directory doesn't exists) and InstallShield is having a failure in displaying the error.

Make sure you have enough space in temp (both Windows\temp and \temp)

smeebudAuthor Commented:
Adide from creating a permenent swapfile, 80mg, and a having gobs of mgs left on the HDD, how would I allocate Space to a temp file.

Temp directories exist, Veriations do to different systems, but I always have them;
Try, in this order:
Search the hard disc for uninst*.exe; if you find files that fit, make sure
they are not Read-Only.
Create the directory C:\Temp and add to autoexec.bat the lines


and reboot. (Optional - also create c:\tmp and use SET TMP=C:\tmp)
Before and after, delete any files in C:\Temp and \Windows\Temp.

It has noting to do with RAM.  I have found out that if you change the
location of the TEMP directory, it takes care of this error in some cases.
Just edit your autoexec.bat file and change the line:
to point to another location.


You don't allocate space to a temp directory, you just make sure that the drive which contains your temp directory has enough space.

If you're running on NT or 95, setting your Temp environment in autoexec.bat shouldn't have any effect.  This value is in the registry. (\HKEY_CURRENT_USER\Environment)

InstallShield may, or may not, use the temp directory the os wants it to use.  Possibly it creates it's own temp directory on the fly (as pkzip does).  In this case, the temp directory would be on the drive that's running the install.

But at the very least, I have found for you the fact that your error message exists in InstallShield (rather than Netscape).
smeebudAuthor Commented:
At last some progress. The only "Environment" I have is in
Which to me is better as it does not get re-written as does HKEY_CURRENT_USER.

Can I get you to do two things before I grade.
1. Tell me where to read about "extstub.exe"
2. Write InstallShield asking the question I asked. I wrote them but not having any of thier products, they said they would not answer.

Thanks for your efforts. This has been driving me crazy.

Good news, bad news...

Good news:
I can do the second thing you ask.
1. I don't know where you can "read" about extstub.exe.  The information I got was from looking at the hex code using an app called FileView.  You would be surprised at what doesn't get compiled!

Bad news:
Four day weekend.  I won't be able to call InstallShield until Tuesday.

I will post an answer as information I get from InstallShield.

If another expert can call InstallShield before I can get to it, then let them answer.
smeebudAuthor Commented:
Ok, clif.
I think you're on the train of thought I'm on so if you want to answer this go ahead.
i can wait for the installshield feedback.

I Don't think you have to call. They answer thier tech mail pretty fast.

Ok, smeebud.  Installshield verified that it was indeed their error message.  What I got from them was a stock answer about making sure the temp directory existed.  

I told them it did then they said to make sure I had enough space available.  I told then I had tonnes.  They said Windows limits the size of the TEMP directory and it may be full even though I have ample free space available on your hard disk.

I told them I'd check that part out, but to limit call backs, was there anything else.  They said that occasionally there was a conflict with the video drivers and I might switch to standard VGA (or boot in safe mode).  I said "Thanks a lot" as sarcastically as I could (I didn't really but would have liked to).  And that was it.

I'm going to submit this as an answer, but I'm an honorable sort.  If this doesn't do it, you should reject the answer.

I'm sorry I could do more.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
smeebudAuthor Commented:
That's what I needed to know. you did what i asked as I could not get feedback from them.
I don't believe them when they say that temp's have limits, as you said above.
You've done a fine job and I thank you.

If you can find out per your statement, "InstallShield may, or may not, use the temp directory the os wants it to use.  Possibly it creates it's own temp directory on the fly (as pkzip does).  In this case, the temp directory would be on the drive that's running the install."
That InstallShield uses it's own temp directory, that would be helpful.


I think I have a solution/explanation.

When the decompression occurs the files are written to a tempory directory (probably c:\temp or c:\windows\temp).  This much is known already.

If ANY file being decompressed already exists in this tempory directory it will be overwritten UNLESS IT IS READONLY.  Ie. if there is already a setup.exe which is read-only, the decompression will fail.  So the % completed will vary depending on which file already exists as read-only.  If it is setup.exe then it fails VERY quickly, whereas if it is a dll that it gets to later then the %completed will be higher of course.

I found out a) from everyone elses suggestions re UNINST*.EXE, and b) because my 'client' had a SETUP.EXE pre-loaded from a CD-ROM (which of course copies as READONLY).

Solution is CLEAR OUT all temp directories before decompressing, however the problem lies with InstallShield's decompression and should really be tackled there by them.


smeebudAuthor Commented:
Thanks Cmoore,
I'll add thatto my database.

smeebudAuthor Commented:
Please see:

a typical example.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.