Apache OpenOffice (AOO) Bugzilla – Issue 74867
Windows 2003: Directory mapped diskspace/network drive not detected - install fails
Last modified: 2008-06-17 12:16:58 UTC
Description: With Windows 2003 it is possible to attach network resources or local drives to any location in a directory structure - which would correspond to "mounting a volume" on UNIX. If such a "mounted" volume exists, we do not detect that and thus get incorrect information about the drive capacity which might lead to an installation failure. Example: - There are 200MB of free disk space on drive C: - The volume D: is mapped to "C:\Program files" with a capacity of several GB free. Our installation routine will only report 200MB of free disk space and does not allow installation.
IS -> JSK: The detection of disc capacities is done by the Windows Installer Service. This is not our code. Therefore there is nothing we can do. Perhaps we need an up-to-date version of Windows Installer Service, if we want to support this. Which version of Windows Installer do you have on your system?
Moving target forward to 2.4, this is not going to make it into 2.3. Need time to evaluate again, testing environmant is not available at this time.
Forward to 3.0
it's valid for XP too, can't edit the issue myself as mentioned, free space is checked on the drive not the actual used folder which may on another partition altogether.
Yep, this is correct but it is a problem with the Windows Installer, not the office. Please file an issue against the MSI installer@Microsoft.
Close