LabVIEW Idea Exchange

About LabVIEW Idea Exchange

Have a LabVIEW Idea?

  1. Browse by label or search in the LabVIEW Idea Exchange to see if your idea has previously been submitted. If your idea exists be sure to vote for the idea by giving it kudos to indicate your approval!
  2. If your idea has not been submitted click Post New Idea to submit a product idea to the LabVIEW Idea Exchange. Be sure to submit a separate post for each idea.
  3. Watch as the community gives your idea kudos and adds their input.
  4. As NI R&D considers the idea, they will change the idea status.
  5. Give kudos to other ideas that you would like to see in a future version of LabVIEW!
cancel
Showing results for 
Search instead for 
Did you mean: 
matt.baker

Stop using removable drives as a temporary location for installation

Status: Declined

Any idea that has received less than 2 kudos within 2 years after posting will be automatically declined.

Please can the installer be changed to stop using removable drives as a temporary location for installation files. I had a 2TB drive attached when I started the install and "safely removed" it part way through. The install then failed Smiley Frustrated

I assume it uses the largest attached drive available. If possible could it check for the fastest drive instead. My main drive is an SSD with an HDD as the secondary drive which is larger. The SSD would have been the best choice in this instance.



Using LV2018 32 bit

Highly recommended open source screen capture software (useful for bug reports).

https://getsharex.com/
4 Comments
Rich_Y.
Member

Hi Matt--Can you attach an installation log for the case you mention?  From the command line, run "setup.exe /log "C:\customdir\mylog.txt"".  Thanks.

matt.baker
Active Participant

I ran the install again with the log option and it generated a 110 MB file, so I don't think it would be wise uploading that!

 

However, I think I now know why it is using the drive - yet again it's down to Microsoft Smiley Mad.

Windows Installer Package/Database files (msi) use the largest available drive unless ROOTDRIVE has been specified when executing the installer:

http://serverfault.com/questions/372789/keep-windows-installer-from-using-largest-drive-for-temporar...

http://superuser.com/questions/71325/windows-installer-using-usb-drive-for-temp-purposes

 

Therefore, could the installer be tweaked to pass the ROOTDRIVE parameter when launching said msi files? Or manually extract before launching the contents?

 

I know it's not a massive issue, but it just seems like poor design (on Microsoft's part).

 

Log file extract:

Action 14:54:11: CostInitialize. Computing space requirements...
Action start 14:54:11: CostInitialize.
MSI (c) (EC:F4) [14:54:11:130]: Machine policy value 'MaxPatchCacheSize' is 10
MSI (c) (EC:F4) [14:54:11:400]: PROPERTY CHANGE: Adding ROOTDRIVE property. Its value is 'E:\'.
MSI (c) (EC:F4) [14:54:11:400]: Note: 1: 1325 2: templates 
MSI (c) (EC:F4) [14:54:11:400]: Note: 1: 1324 2: _Legal Information 3: 1 
MSI (c) (EC:F4) [14:54:11:400]: Note: 1: 1325 2: U~Service 
MSI (c) (EC:F4) [14:54:11:400]: Note: 1: 1325 2: ExtComSu~ 
MSI (c) (EC:F4) [14:54:11:400]: Note: 1: 1324 2: Driver Deployment 3: 1 
MSI (c) (EC:F4) [14:54:11:400]: Note: 1: 1325 2: templates 
MSI (c) (EC:F4) [14:54:11:410]: PROPERTY CHANGE: Adding CostingComplete property. Its value is '0'.
MetaInstaller: ***Progress Info*** End: Calling action CostInitialize. Mon Aug 08 14:54:11 2016
MetaInstaller: ***Progress Info*** Start: CDistribution::NIComponentCostTable::LoadTable. Mon Aug 08 14:54:11 2016
MetaInstaller: ***Progress Info*** End: CDistribution::NIComponentCostTable::LoadTable. Mon Aug 08 14:54:11 2016
MetaInstaller: ***Progress Info*** Start: Calling action FileCost. Mon Aug 08 14:54:11 2016
Action ended 14:54:11: CostInitialize. Return value 1.

And another section:

Action start 14:54:11: CostFinalize.
MSI (c) (EC:F4) [14:54:11:711]: PROPERTY CHANGE: Adding OutOfDiskSpace property. Its value is '0'.
MSI (c) (EC:F4) [14:54:11:711]: PROPERTY CHANGE: Adding OutOfNoRbDiskSpace property. Its value is '0'.
MSI (c) (EC:F4) [14:54:11:711]: PROPERTY CHANGE: Adding PrimaryVolumeSpaceAvailable property. Its value is '0'.
MSI (c) (EC:F4) [14:54:11:711]: PROPERTY CHANGE: Adding PrimaryVolumeSpaceRequired property. Its value is '0'.
MSI (c) (EC:F4) [14:54:11:711]: PROPERTY CHANGE: Adding PrimaryVolumeSpaceRemaining property. Its value is '0'.
MSI (c) (EC:F4) [14:54:11:711]: Note: 1: 2262 2: Patch 3: -2147287038 
MSI (c) (EC:F4) [14:54:11:721]: PROPERTY CHANGE: Adding TARGETDIR property. Its value is 'E:\'.
MSI (c) (EC:F4) [14:54:11:721]: PROPERTY CHANGE: Adding WWWROOT.LVCINT.10000 property. Its value is 'E:\'.
MSI (c) (EC:F4) [14:54:11:721]: PROPERTY CHANGE: Adding INSTALLDIR.DN462W property. Its value is 'E:\'.
MSI (c) (EC:F4) [14:54:11:721]: PROPERTY CHANGE: Adding WWWROOT.MSTINTRP071 property. Its value is 'E:\'.
MSI (c) (EC:F4) [14:54:11:721]: PROPERTY CHANGE: Adding GAC property. Its value is 'E:\'.

Where E:\ was a large removable drive in this instance.



Using LV2018 32 bit

Highly recommended open source screen capture software (useful for bug reports).

https://getsharex.com/
Rich_Y.
Member

Try the following optional command-line switch:

setup.exe [/prop <property name>=<property value>,<property name>=<property value>,...]

 

For example:

setup.exe /prop ROOTDRIVE=C:\

 

This switch can be combined with the log switch to see if you get the change desired.

 

If this switch doesn't work, then I recommend searching for an option within the OS itself.  Best wishes.

Darren
Proven Zealot
Status changed to: Declined

Any idea that has received less than 2 kudos within 2 years after posting will be automatically declined.

DNatt, NI