problem making msi package with d:\documents and settings

If you install to a folder that is not part of a shell-folder (ex. ProgramFilesFolder) then the drive (partition) with most free diskspace will be used, in your case D:\.
To prevent this you will need to use the ROOTDRIVE property to "hard-code" which drive to use (ex. ROOTDRIVE="C:\")

In addition to AngelD comments you may also need a Set Directory CA to allow deploying to both c:\ and d:\

Thanks a lot for the reply.

But where do I set ROOTDRIVE ?

is it a Wise option ?

Thanks in advance.

Well, I think "ROOTDRIVE property" gives you a hint; a property is set in the Property table.

ok found public properties in windows installer editor

thanks for all !

It's me again !

I'm still aplying rootdrive=c:\ to the public properties of y msi package, but the the package is continuing deploy to d: !

Any idea ?
Thanks in advance !

Have you ensured that you used all upper-case for the property name? If it's not all upper-case, it's not a Public property.

As ever, a verbose log will show you all properties and what they're resolved to.

Hi,

I would again suggest you the method I suggested sometime back as well to someone. The solution for your problem can be found in my post here:
www-secure.symantec.com/connect/blogs/installing-files-multiple-drives  
Hope it helps.

1. Set ROOTDRIVE=C:\ in property table
2. Check for any custom actions which is setting ROOTDRIVE to D:\ ( just go to MSI Script and search for ROOTDRIVE)  if found replace its value with C:\

If this doesnt work create a log by Msiexec /i <MSI path> /l*v <path to created log file> and search for ROOTDRIVE in this log file.

The correct spelling is IMPOSSIBLE.

You will find that something called a DICTIONARY will help you to find the correct spelling of words you are unsure of.

Er, I think it's meant to be humorous, Ed...

@Umara, you need to do some reading. Just because the install targets the D: drive doesn't mean that there is a CA setting the ROOTDRIVE property. In the absence of that property, the engine will choose the local drive with the most free space as the target drive. Still, as you say, setting it explicitly will force installation to the chosen drive.

Looks like me sense of humour transplant is being rejected (again).
Must be contamination from all the Charlie Romeo Alpha Papa  I have to shovel.....

well well
Thanks friends;

      @VBScab thanks for adding some valuable information in my very little knowledge bank. But when i wrote CA thing I didnt say its a solution. it may be one of the reasons that package is going to D:\ . I guess even fresher in packaging field would know what happens when ROOTDRIVE is not set.
     Any troubleshooter will check for CA if he founds ROOTDRIVE is set and still package is installing on D:\ . That is why in the first point i wrote set property and in second point I wrote check for Custom Action.

    @EdT What to do mate; I have a modernised copy of Napolean's dictionary, it doesnt have that word in it and I like this dictionary so much that I dont want to change it.
 
:-)

If your dictionary includes the word "modernized", I'd throw it away, as it's a US English one. The word is "modernised". LOL :)

I was ready for this reply as soon as I clicked on save :) :) :) let me edit it first :) :) :)

congrats

"msiexec /i c:\topxr.msi TARGETDIR=C:\"
Make sure to trigger a repair and uninstallation during test-phase as properties added through commandline are not "remembered".

looks like i m appearing for spell test :) :) :) (word Napolean changes as per your location on the earth). Do I need to go back to my schools again