PDA

View Full Version : Problems with InstallShield Express Pro V1.11a and Microsoft SMS



NewsArchive
03-28-1997, 01:00 AM
I have created a package to install a VB4 16 bit application. An express
extension EXE is called prior to the progress indicator.
All of the necessary files for the extension EXE (which is a VB3 app) are
included on the first diskette uncompressed. The target platform is Windows
for Workgroups 3.11.

The installation works okay when launched from diskette or from a network
drive (either UNC path or mapped).

When sent as a workstation install package from SMS, the express extension
EXE does not run, and the main program EXE is not copied to the target PC.

SMS is setting up the package correctly on the distribution server. I can
verify this by mapping the SMS_PKGD share and running setup from the
appropriate subdirectory.

If anybody has any ideas, clues, or experience with InstallShield Express
Pro and SMS please respond ASAP via email as this package is an urgent
upgrade to a critical corporate application (and my butt is on the line).

Thanks

--
Dougal Ingram
Technical Development Specialist
ACTEW Corporation
Canberra Australia
mailto:Dougal.Ingram@actew.com.au

NewsArchive
03-28-1997, 01:00 AM
Hi Dougal

> All of the necessary files for the extension EXE (which is a VB3 app) are
> included on the first diskette uncompressed. The target platform is
Windows
> for Workgroups 3.11.

It seems ISX Pro gets a bit confused about the current working directory.
So far the only way I've been able to guarantee an Express Extension will
find all its component files is put them in <SUPPORTDIR> - ie copy them
into the TEMP files section of Disk Builder. I've had strange effects
running EXEs and DLLs from elsewhere - even effects varying on different
machines :-?

Since everything in <SUPPORTDIR> gets compressed and it currently fits
uncompressed on your disk 1, there should be no problem. Another
alternative is to write a small EXE in <SUPPORTDIR> that changes directory,
then calls your app.

I'm not that familiar with SMS, but it's more likely that ISX is where the
problem is :-(

Hope this helps
Chris Nash
Auto-Graph C.D.S. Inc.

NewsArchive
03-28-1997, 01:00 AM
Hi Dougal

> All of the necessary files for the extension EXE (which is a VB3 app) are
> included on the first diskette uncompressed. The target platform is
Windows
> for Workgroups 3.11.

It seems ISX Pro gets a bit confused about the current working directory.
So far the only way I've been able to guarantee an Express Extension will
find all its component files is put them in <SUPPORTDIR> - ie copy them
into the TEMP files section of Disk Builder. I've had strange effects
running EXEs and DLLs from elsewhere - even effects varying on different
machines :-?

Since everything in <SUPPORTDIR> gets compressed and it currently fits
uncompressed on your disk 1, there should be no problem. Another
alternative is to write a small EXE in <SUPPORTDIR> that changes directory,
then calls your app.

I'm not that familiar with SMS, but it's more likely that ISX is where the
problem is :-(

Hope this helps
Chris Nash
Auto-Graph C.D.S. Inc.

NewsArchive
04-29-1997, 12:00 AM
Dougal,

SMS might have a problem running the EXE-file if the path and filename
exceeds 32 characters (in the SMS package definition). To resolve this
problem use less than 32 chars, or use the SMS-program NTENCAP.EXE (in the
MSTEST directory).

Asbjørn Kvalheim
asbjorn.kvalheim@delfi-data.msmail.telemax.no


Dougal Ingram <Dougal.Ingram@actew.com.au> skrev i artikkelen
<01bc3b57$1272d3c0$fb06000a@pc1>...
> I have created a package to install a VB4 16 bit application. An express
> extension EXE is called prior to the progress indicator.
> All of the necessary files for the extension EXE (which is a VB3 app) are
> included on the first diskette uncompressed. The target platform is
Windows
> for Workgroups 3.11.
>
> The installation works okay when launched from diskette or from a network
> drive (either UNC path or mapped).
>
> When sent as a workstation install package from SMS, the express
extension
> EXE does not run, and the main program EXE is not copied to the target
PC.
>
> SMS is setting up the package correctly on the distribution server. I can
> verify this by mapping the SMS_PKGD share and running setup from the
> appropriate subdirectory.
>
> If anybody has any ideas, clues, or experience with InstallShield Express
> Pro and SMS please respond ASAP via email as this package is an urgent
> upgrade to a critical corporate application (and my butt is on the line).
>
> Thanks
>
> --
> Dougal Ingram
> Technical Development Specialist
> ACTEW Corporation
> Canberra Australia
> mailto:Dougal.Ingram@actew.com.au
>
>

NewsArchive
04-29-1997, 12:00 AM
Dougal,

SMS might have a problem running the EXE-file if the path and filename
exceeds 32 characters (in the SMS package definition). To resolve this
problem use less than 32 chars, or use the SMS-program NTENCAP.EXE (in the
MSTEST directory).

Asbjørn Kvalheim
asbjorn.kvalheim@delfi-data.msmail.telemax.no


Dougal Ingram <Dougal.Ingram@actew.com.au> skrev i artikkelen
<01bc3b57$1272d3c0$fb06000a@pc1>...
> I have created a package to install a VB4 16 bit application. An express
> extension EXE is called prior to the progress indicator.
> All of the necessary files for the extension EXE (which is a VB3 app) are
> included on the first diskette uncompressed. The target platform is
Windows
> for Workgroups 3.11.
>
> The installation works okay when launched from diskette or from a network
> drive (either UNC path or mapped).
>
> When sent as a workstation install package from SMS, the express
extension
> EXE does not run, and the main program EXE is not copied to the target
PC.
>
> SMS is setting up the package correctly on the distribution server. I can
> verify this by mapping the SMS_PKGD share and running setup from the
> appropriate subdirectory.
>
> If anybody has any ideas, clues, or experience with InstallShield Express
> Pro and SMS please respond ASAP via email as this package is an urgent
> upgrade to a critical corporate application (and my butt is on the line).
>
> Thanks
>
> --
> Dougal Ingram
> Technical Development Specialist
> ACTEW Corporation
> Canberra Australia
> mailto:Dougal.Ingram@actew.com.au
>
>