/build/static/layout/Breadcrumb_cap_w.png

Wrong drive.

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

Answers (8)

Posted by: VikingLoki 19 years ago
Second Degree Brown Belt
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.
Posted by: brenthunter2005 19 years ago
Fifth Degree Brown Belt
0
Set the ROOTDRIVE public property in the MSI to C:\
Posted by: Willo 18 years ago
Yellow Belt
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.
Posted by: AngelD 18 years ago
Red Belt
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.
Posted by: AngelD 18 years ago
Red Belt
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.
Posted by: wiseapp 18 years ago
Second Degree Green Belt
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.
Posted by: DuncanPaul 18 years ago
Orange Belt
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.
Posted by: revizor 18 years ago
Third Degree Blue Belt
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.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ