This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Product installs on wrong hard disk partition
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 04, 2008
12:22 PM
Product installs on wrong hard disk partition
Hi,
I currently have 2 partitions (C: and D:) on my machine, and for some reason the installer installs onto the 😧 by default, but when I specify the installer to install on C:, not all the folders are copied over. I did some more testing, and found that if the 😧 partition is not formatted, there are no problems - all the folders are copied over correctly. If I then run a uninstall, format the 😧 to NTFS file system, and run the install again, I run into the same problem as before. Does anyone know why this is happening? or where I can specify the default location for the files/folders that are copied over? Thanks in advance!
-Sean
I currently have 2 partitions (C: and D:) on my machine, and for some reason the installer installs onto the 😧 by default, but when I specify the installer to install on C:, not all the folders are copied over. I did some more testing, and found that if the 😧 partition is not formatted, there are no problems - all the folders are copied over correctly. If I then run a uninstall, format the 😧 to NTFS file system, and run the install again, I run into the same problem as before. Does anyone know why this is happening? or where I can specify the default location for the files/folders that are copied over? Thanks in advance!
-Sean
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 05, 2008
02:24 AM
I have experienced this before. I think it has to do with how windows installer tries to find a drive with enough space where to copy the files - if your C drive didn't have enough space it decided to copy the files in D drive instead.
I think you'll need to set property ROOTDRIVE with value C:\ in your package to avoid this.
http://msdn2.microsoft.com/en-us/library/aa371372(VS.85).aspx
Though I haven't experienced this with installshield packages I've done - only packages I've run.
I think you'll need to set property ROOTDRIVE with value C:\ in your package to avoid this.
http://msdn2.microsoft.com/en-us/library/aa371372(VS.85).aspx
Though I haven't experienced this with installshield packages I've done - only packages I've run.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 05, 2008
02:50 PM
arsirantala wrote:
I have experienced this before. I think it has to do with how windows installer tries to find a drive with enough space where to copy the files - if your C drive didn't have enough space it decided to copy the files in D drive instead.
I think you'll need to set property ROOTDRIVE with value C:\ in your package to avoid this.
http://msdn2.microsoft.com/en-us/library/aa371372(VS.85).aspx
Though I haven't experienced this with installshield packages I've done - only packages I've run.
You're close, with 3.x Microsoft has the drive with the most available space as the default.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 05, 2008
03:19 PM
Fantastic! It worked like a charm! You guys are great! Thanks!:D 😄 😄
![](/skins/images/A5EADE085F77DE82FB3B14D6B307AE6A/responsive_peak/images/icon_anonymous_message.png)