Bug 77016 - UI: Installer does not allow installing to a drive other than drive C.
Summary: UI: Installer does not allow installing to a drive other than drive C.
Status: RESOLVED DUPLICATE of bug 52169
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Installation (show other bugs)
Version:
(earliest affected)
4.2.2.1 release
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-03 16:25 UTC by Kohei Yoshida
Modified: 2014-04-06 19:01 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kohei Yoshida 2014-04-03 16:25:48 UTC 
Background.
I only have 98MB of free space in drive C, but 98GB of free space in drive D.  I tried it under Oracle Virtual Box.

1. Download the msi installer and launch it to install.
2. Choose "Custom" and click Next.
3. Change the installation path to D:\Program Files (x86)\LibreOffice 4\ (I have drive D mapped to additional hard disk with lots of free space), and click OK.
4. Click Next.
5. The installer says "Disk out of space", and the drive C is still highlighted even though I have selected drive D as the installation destination.


Operating System: Windows 7
Version: 4.2.2.1 release
Comment 1 tommy27 2014-04-06 11:22:51 UTC 
(In reply to comment #0)
> Background.
> I only have 98MB of free space in drive C

kinda short of MB...

> 5. The installer says "Disk out of space", and the drive C is still
> highlighted even though I have selected drive D as the installation
> destination.

my guess is that even if you choose D: as the final install destination, during the installation process stuff is extracted under some temporary folder under C: which in your case is short of space.

what do you think about it?
Comment 2 Maxim Monastirsky 2014-04-06 19:01:40 UTC 
It's a known limitation of Windows Installer.

*** This bug has been marked as a duplicate of bug 52169 ***