6 replies to this topic

[dtieuf]

Our setup is a basic InstallShield setup (setup.exe + cab files + ini files and such) that is packaged using Microsoft's IExpress to be a single "ourproduct.exe" file.

When some of our users launch this exe, it seems to extract but then nothing happens, the included setup.exe is not launched.

Somehow, the users having this problem have XP systems.

Anyone knows how this extraction/setup would break ?
Any pointers on how to troubleshoot this would also be appreciated
We would like to avoid the manual extraction workaround as much as possible...

[Before using cab files, the package was shipped as a self-extracting zip file, and this would happen as well...]

Thank you,

Sophie

Edited by dtieuf, 19 January 2005 - 18:13.

[Stefan Krueger]

If you are using an old InstallShield version it may be the problem described here:
http://www.installsi...s_is5.htm#isp5x

Does the same setup work properly if it's not packed using IExpress?

[dtieuf]

I am using InstallShield DevStudio 9 + VBuild 2.1.

For these users, the setup doesn't hang, it just doesn't run at all...

Our current workaround is to tell the users to extract the files manually, using WinZip for instance, and then launch setup.exe. It then works fine.

Before using IExpress, we were using WinZip's self-extractor tool and the same problem would occur.

[Stefan Krueger]

I guess these self extractors fails to wait until your setup has finished.

[Stefan Krueger]

BTW I wonder why you are using a separate tool to buld a self extracting exe. Why don't you build a single file setup.exe in InstallShield?

[dtieuf]

We're using IS9 + VBuild + IExpress because it makes the exe about 25% smaller than using IS alone for a full-version setup.

[Stefan Krueger]

I thought that vBuild could generate such an exe for you. But I may be wrong (I've never really used vBuild)