Isolated Program Files

At my company, we have a custom set of scripts for installing and setting up
Windows. We have some Windows XP x64 workstations that we would like to add
to this process. With one exception, all of our applications are 32-bit.

One problem we have run into is with Program Files. All of our applications
are installed with InstallShield and the "-r" and "-s" options. These create
..iss files which are then used for unattended installations. The problem is
that the hard coded path in these files is "C:\Program Files".

Is this going to cause a problem? Can I install 32-bit applications into
the 64-bit Program Files directory? I've been searching for a while now and
have not received a definate yes/no answer.

Advertisements

If there recient installers they should be able to tell the OS is X64 and
put them into the Programs Files (X86) folder but i can't see any issues.
but if they do install into the program files folder they should'nt cause
any issues.

Some apps or games installed into the programs files folder by default and
worked so there should be no issues.

Some i did try to force into the program files once to keep like all the
game series in on folder under the manufucture and still got redirected into
the Programs Files (X86) folder so thats something that could happen.
>
"Stack" <> wrote in message
news:...
> At my company, we have a custom set of scripts for installing and setting
> up
> Windows. We have some Windows XP x64 workstations that we would like to
> add
> to this process. With one exception, all of our applications are 32-bit.
>
> One problem we have run into is with Program Files. All of our
> applications
> are installed with InstallShield and the "-r" and "-s" options. These
> create
> .iss files which are then used for unattended installations. The problem
> is
> that the hard coded path in these files is "C:\Program Files".
>
> Is this going to cause a problem? Can I install 32-bit applications into
> the 64-bit Program Files directory? I've been searching for a while now
> and
> have not received a definate yes/no answer.

Advertisements

"Stack" <> wrote in message
news:...
> At my company, we have a custom set of scripts for installing and setting
> up
> Windows. We have some Windows XP x64 workstations that we would like to
> add
> to this process. With one exception, all of our applications are 32-bit.
>
> One problem we have run into is with Program Files. All of our
> applications
> are installed with InstallShield and the "-r" and "-s" options. These
> create
> .iss files which are then used for unattended installations. The problem
> is
> that the hard coded path in these files is "C:\Program Files".
>
> Is this going to cause a problem? Can I install 32-bit applications into
> the 64-bit Program Files directory? I've been searching for a while now
> and
> have not received a definate yes/no answer.

Well assumeing nearly 100% of the software out there is still 32 bit why
not just change the "C:\Program Files" path to "C:\Program Files (x86)"?
it shouldn't be that hard or am I missing something? I set up unattended
installs all the time.

Stack wrote:
> At my company, we have a custom set of scripts for installing and setting up
> Windows. We have some Windows XP x64 workstations that we would like to add
> to this process. With one exception, all of our applications are 32-bit.
>
> One problem we have run into is with Program Files. All of our applications
> are installed with InstallShield and the "-r" and "-s" options. These create
> .iss files which are then used for unattended installations. The problem is
> that the hard coded path in these files is "C:\Program Files".
>
> Is this going to cause a problem? Can I install 32-bit applications into
> the 64-bit Program Files directory? I've been searching for a while now and
> have not received a definate yes/no answer.

Well, we are trying to do as little rewriting as possible. It's true that
our programs are getting the "Program Files (x86)" directory if we manually
install them, but our original setup for Win2k and XP are set for "Program
Files". When you use these files for the unattended install, the path is
hard coded, so the switch never happens.

"zekolas" wrote:
> Well assumeing nearly 100% of the software out there is still 32 bit why
> not just change the "C:\Program Files" path to "C:\Program Files (x86)"?
> it shouldn't be that hard or am I missing something? I set up unattended
> installs all the time.
>
> Stack wrote:
> > At my company, we have a custom set of scripts for installing and setting up
> > Windows. We have some Windows XP x64 workstations that we would like to add
> > to this process. With one exception, all of our applications are 32-bit.
> >
> > One problem we have run into is with Program Files. All of our applications
> > are installed with InstallShield and the "-r" and "-s" options. These create
> > .iss files which are then used for unattended installations. The problem is
> > that the hard coded path in these files is "C:\Program Files".
> >
> > Is this going to cause a problem? Can I install 32-bit applications into
> > the 64-bit Program Files directory? I've been searching for a while now and
> > have not received a definate yes/no answer.
>

Share This Page

Welcome to Velocity Reviews!

Welcome to the Velocity Reviews, the place to come for the latest tech news and reviews.

Please join our friendly community by clicking the button below - it only takes a few seconds and is totally free. You'll be able to chat with other enthusiasts and get tech help from other members.
Sign up now!