Hi,

This maybe a stupid question to most of you but I'm breaking my brains over this one. I've snapped an app and this app installs itself on the D:\ of the machine.

What is the best way to let it install to the C:\ of my mahine ?

Regards,

Peter.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
The best way is to install the app to C: in the first place. If it doesn't let you, then you can try changing the INSTALLDIR property. But if the software itself won't install to C, you might find stom hardcoded references to D:. If that's the case, it won't work.
Answered 03/03/2005 by: VikingLoki
Second Degree Brown Belt

Please log in to comment
0
Set the ROOTDRIVE public property in the MSI to C:\
Answered 03/03/2005 by: brenthunter2005
Fifth Degree Brown Belt

Please log in to comment
0
I have a similar problem . this app installs to C:\ drive but i have to copy a folder to D:\ drive. all computers have both drives and the D drive was included in my snap shot . But it is not being captured Is there a work around for this. Help greatly appreciated.
Answered 08/18/2005 by: Willo
Yellow Belt

Please log in to comment
0
ORIGINAL: Willo

I have a similar problem . this app installs to C:\ drive but i have to copy a folder to D:\ drive. all computers have both drives and the D drive was included in my snap shot . But it is not being captured Is there a work around for this. Help greatly appreciated.

You have to add the D: Drive into the Directories to Watch as C: is the only directory added by default.
Answered 08/18/2005 by: AngelD
Red Belt

Please log in to comment
0
I would recapture the application when it's installed to C:\ then create a MST if you want to redirect the ROOTDIR to D: or INSTALLDIR to D:\<path>.
As default path variables are defined by the env. variables and if the applications are installed on D: they will be hardcoded.
Answered 08/18/2005 by: AngelD
Red Belt

Please log in to comment
0
I would agree with Viking, if there are certain files of that application that needs to be executed only from the secondary partition that is D: in your case than changing the installdir will have certain problems.
Answered 08/24/2005 by: wiseapp
Second Degree Green Belt

Please log in to comment
0
I usually add a set directory custom action to install particular directories to particular drives, and include the Rootdrive property, so the app gets installed to c: even if D: has more space available.
Answered 08/24/2005 by: DuncanPaul
Orange Belt

Please log in to comment
0
When I piece a package together with Wise for Windows Installer, I use a template that has our common properties (ROOTDRIVE, LIMITUI, ALLUSERS) pre-set. But I like AngelD's idea of .mst too.
Answered 08/25/2005 by: revizor
Third Degree Blue Belt

Please log in to comment
Answer this question or Comment on this question for clarity