Using US Windows 98, 6.01 DE or FR installs, installer issues a "not enough disk space" message when 349MB are available on c: drive. Then, it does not fail very gracefully, but must be terminated with Ctrl-Alt-Del.
Does this happen with a recent Mozilla build? This is probably fixed; please use bugscape.mcom.com for Netscape 6 bugs.
is there happen to be a path mentioned in the error message, or just "c:"? ps. yes, if this does not happen with the mozilla builds, pleave move this bug to bugscape.
Moved to Bugscape 4372--do not yet know if this happens with 6.5 builds on my system. If it does, I'll file a Bugzilla bug. Sorry for my lapse of Bugzilla ettiquette.
Getting a similar message when attempting to install 6.5 daily build for 03.20 This message might be more helpful, because it is in English: 123: Could not determine available disk space for c:\Program Files\Netscape\Nscp6.5.03.21 Got this message with 377MB available space, right after running a Scan Disk that found no bad sectors.
nominating... this is not widespread, so what is different about your system? One difference is that you're using DE and FR builds, perhaps the disk-space amounts were incorrectly updated when those installs were generated. Can you reproduce this problem in English builds on the same system? *when* do you get this message? before or after the downloads? Please CC the folks who built the DE and FR installs because I strongly suspect that is where the problem lies, unless you can reproduce this in an English build. Where can we get a copy of the translated installers to inspect?
my initial guess (without looking at the code) would be the funny path name: Nscp6.5.03.21 I'll have to look at it more closely to know for sure.
If it's the path name then the English version would also fail when Linda tries to install to a similarly funny path name. I'm suspecting that the archive sizes built into the translated config.ini files are wrong.
good point. I be the file sizes don't get recalculated at translation time. But it should be off by that much. 349MB is a lot of disk space.
Fabulous. Changing the path name to one *without* any punctuation made the problem go away. The "funny path name" problem was a problem for EN, DE, FR builds--all of them. Seems to me like Nscp 6.x should either accept a path name with punctuation or reject it with a proper error message.
uhm, yes. it's a bug :)
Can I have an example of the pathname used so I can be sure to duplicate this? Thanks, syd
Path name which caused the problem is in comment from 03.22
*** Bug 54926 has been marked as a duplicate of this bug. ***
*** Bug 88677 has been marked as a duplicate of this bug. ***
*** Bug 90542 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 88410 ***
sure is dupe...