/build/static/layout/Breadcrumb_cap_w.png

install files to specific drive

I have a vendor supplied MSI that I am prepping for delivery. This package has no references to using a different drive that I can see. I run the install manually in my VM and in places files in c:\service\dminstall. My VM has only one drive. On a production device that has two drives, it is installing the files to d:\service\dminstall. How do you specify a drive for the file destinations and how can I fix this to place the files on the correct drive?

Product Details - default dir = Service\DMInstall
Here is what is in the directory table:
Directory Directory_Parent DefaultDir Full Directory
TARGETDIR SOURCEDIR
INSTALLDIR20 TARGETDIR SERVICE SERVICE
INSTALLDIR INSTALLDIR20 DMINST~1|DMInstall SERVICE\DMINSTALL

0 Comments   [ + ] Show comments

Answers (4)

Posted by: cygan 15 years ago
Fifth Degree Brown Belt
0
you will need to use the ROOTDRIVE property


go to the property table

ROOTDRIVE | C:\
Posted by: JimmPanik 15 years ago
Orange Belt
0
I added this row and got an error saying this property is predefined and will be over written during install. Where would the predefined element be?
Posted by: cygan 15 years ago
Fifth Degree Brown Belt
0
thats no problem

ok that and add your property

by default windows installer will install on the drive with bigger space regardless of drive letter

if your have 2 drives on your pc say c and d

if d has more space than c then by default your app will install to d
Posted by: bheers 15 years ago
Second Degree Blue Belt
0
if you have to install appllications to anyother Physical Drive (not network drive) you can do so in the following way.

default INSTALLDIR : C:\Program Files\Dir1
Change to D:\Program Files\Dir1

1. In the MSI Script create a custom action
In "User Interface" just after "Cost Finalize"
"Set Directory" give it a Name , choose the directory by browsing to
ProgramFilesFolder\Dir1 and in the third Blank Space enter "D:\Program Files\Dir1"

2. Create the same Custom action in "Execute Immediate" just after "Cost Finalize" also

This installation works fine as long as D: is a valid Drive, it does not work on drives that were created using "Subst.exe" Command.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
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