[wix-users] Installation directory must be on a local hard drive

[Bob Arnson]

Visual Studio hasn't supported Windows 2000 since VS2008. XP support requires SP2.

-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Schooley, Ron
Sent: Wednesday, 22 March, 2017 20:06
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Subject: Re: [wix-users] Installation directory must be on a local hard drive

After more testing, I have found this failure occurs with even new operating system versions.

Here are the results of some additional tests:

1. Windows 2000 (Gold) - FAILS
2. Windows 2000 w/ SP1 - FAILS
3. Windows 2000 w/ SP2 - FAILS
4. Windows 2000 w/ SP3 - FAILS
5. Windows 2000 w/ SP4 - FAILS
6. Windows XP (Gold) - FAILS
7. Windows XP w/ SP1 - FAILS
8. Windows XP w/ SP2 - PASSES

Needless to say, it seems like *something* got added to make this start working in SP2 of Windows XP.

Any thoughts?

-Ron

-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Schooley, Ron
Sent: Wednesday, March 22, 2017 4:25 PM
To: wix-users at lists.wixtoolset.org
Subject: [wix-users] Installation directory must be on a local hard drive

I have recently started switching some of my program install packages to use WiX (which is a fantastic product, by the way). Just out of curiosity, I decided to see if the install packages being built could run under an ancient operating system version like Windows 2000 (5.0.2195). While running the install, I got the "Installation directory must be on a local hard drive" error message. I am using the WixUI_installDir WiXUIExtension from WiX 3.11.0.1507.

Although I understand very few if any people are still running Windows 2000, I was a little surprised by this failure. I can work around this issue by using the well-documented quiet (non-GUI) install option or by setting the WIXUI_DONTVALIDATEPATH Property. Given how simple the path validation code seems to be while briefly skimming it over (and as a matter of simple principle), it seems like this issue should be able to be eliminated.

Please find below a snippet of the trace log. Is it simply the case that the custom action is not getting run for some reason? Why would this be the case?

-Ron

Action start 16:11:47: WelcomeDlg.
Action 16:11:47: WelcomeDlg. Dialog created Internal Error 2898. WixUI_Font_Title, Tahoma, 0 Action 16:11:49: LicenseAgreementDlg. Dialog created Action 16:11:51: InstallDirDlg. Dialog created Action start 16:11:53: WixUIValidatePath.
Internal Error 2737. WixUIValidatePath, C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\MSI42.tmp, ValidatePath Action ended 16:11:53: WixUIValidatePath. Return value 1.
Action 16:11:53: InvalidDirDlg. Dialog created Action 16:11:55: BrowseDlg. Dialog created Action start 16:11:57: WixUIValidatePath.
Internal Error 2737. WixUIValidatePath, C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\MSI43.tmp, ValidatePath Action ended 16:11:57: WixUIValidatePath. Return value 1.
Action 16:11:57: InvalidDirDlg. Dialog created Action 16:12:00: CancelDlg. Dialog created Action ended 16:12:01: WelcomeDlg. Return value 2.
MSI (c) (70:B0): Doing action: UserExit
MSI (c) (70:B0): Note: 1: 2205 2:  3: ActionText Action start 16:12:01: UserExit.


____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/