PDA

View Full Version : Hard coded Directories



NewsArchive
11-02-1997, 01:00 AM
I haven't found any easy answer to how to restrict the user to only
changing drives and the last directory in the path.

In other words, I want to have a specific path (a requirement by the
customer) but allow the user to put it on any drive. They can also change
the last subdirectory in the installation path. The company has mutliple
products and wants them all off the same directory structure.

Example (items in <> are user customizable):
Desired outcome <drive>:\my-company\this-one-product\<customer picked
directory to install in>
Other products would then install to:
<drive>:\my-company\different-product\<customer picked directory name>

Finally, they start in a different directory off the hard-coded path but
call the EXE from the cusomer picked install directory.

The product is in VB3 and previous installs without IS accomodated this
structure. We are trying to standardize on IS but I haven't been able to
recreate the install above.

Am I missing something obvious in the use of Groups that will allow this?

NewsArchive
11-08-1997, 01:00 AM
This functionality is not supported with Express. Express was designed as
a very quick and easy installation tool. Because it has no scripting, it
does not have all the extensibility or functionality you require.
InstallShield 5 provides scripting and provides a lot of the functionality
you want.

Kent
InstallShield Technical Support

dk <rdower@sky.net> wrote in article
<01bce73d$5f0c6380$eaa5e6ce@skynet.sky.net>...
> I haven't found any easy answer to how to restrict the user to only
> changing drives and the last directory in the path.
>
> In other words, I want to have a specific path (a requirement by the
> customer) but allow the user to put it on any drive. They can also
change
> the last subdirectory in the installation path. The company has mutliple
> products and wants them all off the same directory structure.
>
> Example (items in <> are user customizable):
> Desired outcome <drive>:\my-company\this-one-product\<customer picked
> directory to install in>
> Other products would then install to:
> <drive>:\my-company\different-product\<customer picked directory
name>
>
> Finally, they start in a different directory off the hard-coded path but
> call the EXE from the cusomer picked install directory.
>
> The product is in VB3 and previous installs without IS accomodated this
> structure. We are trying to standardize on IS but I haven't been able to
> recreate the install above.
>
> Am I missing something obvious in the use of Groups that will allow this?
>