Not applicable

Running the java SDK inataller (v1.3.0) on an NT4 machine produced an error
message stating there was not enough free space on the disk, please free up
(can't remember how much) and try again.

Looking in the NT explorer showed that drive C had just over 10 Gig free.
Creating some large dummy files to reduce the free disk space to 7 Gig allowed
the installer to run successfully.

Looks like an overflow in the free space check to me.

Please note, I do not expect a reply - this is just for your information.
(Review ID: 115236) 
======================================================================




java -version none

Double-clicked the install for jdk 1.3.1, and got the following message:

Java 2 SDK <in title bar>
There is not enough space on drive c:\ to extract this package.
Please free up 35.75 MB and click Retry.

I have 52.0 GB free on C:(Review ID: 124998)
======================================================================




I have 8GB free on c:\ but whenever I try to install the SDK it says "Out of
disk space, free 35.75MB and click on retry to continue installation".
Obviously, it has an issue with the way it reads available disk space.
(Review ID: 125218)
======================================================================

Creating some large dummy files to reduce the free disk space to 7 Gig allowed
the installer to run successfully.
======================================================================




Stop installation, drop available space to <8GB, restart installation.

It worked for me with 7.7GB available.
(Review ID: 125218)
======================================================================

I believe this bug is present on all win32 platforms.  See also bugs 4415692, 4362393 and 4400299
 xxxxx@xxxxx  2001-05-22

I've tried to reproduce this on Win2k for our jre131fcs.exe with 4GB, 4.3GB, 7GB, and 8GB of free space on the C: drive.  Unfortunately I did not see the error message.  Clearly this is a package for the web problem.  Even if we could reproduce it is not something we could fix, because it is install shield specific.  Hopefully, with our upgrade to Package for the Web 3.0 for Merlin beta3, this problem won't occur anymore.  I did not see anything about this bug or a fix at install shield's support web site.  However, I read the following line in the Package for the Web 3.0 release notes:

Fix - Free disk space check works correctly 
Previously, the disk space check would fail if disk space less than the size of the package was available. 

It appears that they have changed the disk space check code, so hopefully this problem got fixed.  I am closing this as not reproducible.
 xxxxx@xxxxx  2001-09-07

This is fixed in Merlin beta3 and subsequent releases.  At this point, 1.3 releases may still run into this problem.  We may merge this fix back to 1.3 releases in the near future.
 xxxxx@xxxxx  2001-12-03

sdk 1.4.0 Beta works fine

I have 30 Gb of free space. Is creating a large dummy 
file/s the ony solution ?.

This is very reproducible. Check if you have service packs
applied:
I run Windows 2000 Professional, 5.00.2195 Service Pack 2
x86 Family 5 Model 4 Stepping 3, 128 Megs of memory.
Does it for me with JDK 1.3.1 and 1.4.0beta2. I had 9 Gig
free, now I started to fill up the disk with garbage and at
5 gigs it still does it.
jkl@osc.edu

I had 12GB free on C: on Windows 2K and JDK 1.3.1 broke on 
install. Same message as above. My workaround was to go 
into the System Applet and increase Virtual memory to 
4095MB (the maximum) to shrink the disk down to 8GB and it 
worked.

This problem seemed to occur because of using the non-DOS7.x
code for free disk space checking. To answer maugil's
question, yes - creating large dummy file(s) is the only
solution, because:
Assume the installer uses a method called e.g. freespace(),
then freespace() returns a number between 0 and 2G (good old
DOS era, remember?). That's why this bug occurs every time
you have less than ((n*2G)+install_space) free hard disk
space left (with n>=0).
Solution: Shrink your free space to a value that is a little
bit smaller than a 2G factor.
I wonder why jlabanow had problems although having an
odd-gigabyte amount of frere space. Could anyone explain?

My workaround was to use the winzip program to extact the 
j2sdk-1_3_1_01-win.exe file and run setup.exe in the \disk1 
directory created.

Using WinZip to open the .EXE as a ZIP archive and 
extracting the contents to a temporary directory works 
great.  The self-extractor has the bug, not the install 
program itself.  <SOAPBOX>Since almost every new 
developer's computer has gobs of memory, why doesn't Sun 
put a note on the download page on how to work around this 
problem until a real fix is made?  Just closing it and 
saying it's not reproducible is like sticking your head in 
the sand.</SOAPBOX>

I have the same problem.  I have windows XP home edition.  
I have 32GB of free space but it says I need to free up 
50.53 mb of space.