Subj : Binkley32 on Win2000 Server
To   : Ger Vloothuis
From : Bob Jones
Date : Fri Mar 22 2002 01:36 pm

GV> I am running Binkley32 on a Win2000 Server.  It doesn't
GV> want to write incoming packets to the disk.  It baulks
GV> about disk is full.  There is plenty of space on the
GV> disk and all permissions for Binkley to write there are
GV> set OK.

GV> Anyone came across this before?


You are probably hitting the 4Gb limit on the old DOS API for finding out free
space on a drive.  The maximum amount of space that can be returned via the old
call is 4Gb.  Amounts over 4Gb wrap.  Most software treats this as a signed
instead of an unsigned int, so  if free space is between 2Gb and 4Gb (or 6Gb to
8Gb, or 10Gb to 12Gb, etc.), then when treated as a "signed" int, the value is
negative, and the software thinks you are  out of disk space.

So.... You have a few choices.....

One option is to  eat up free disk space  so that the returned value is under
2Gb free (but at least enough room for the files being  received) on that
partion.

Another option is to place your inbound areas on a disk partition not over 2Gb
in size.

If running "DOS" software in a VDM under OS/2, we have an option to install a
driver that truncates the reported value to a maximum of 2Gb free space.  I
don't know if this is available under Win 2K.  It might come if you access  the
partition as a network mount instead of the direct access via the drive
letter....  I don't know.....

But, what you are hitting is what happens when you have a partition over 2Gb in
size with over 2Gb of free disk space.

Take care.....

Bob Jones, 1:343/41


--- Maximus/2 3.01
* Origin: Top Hat 2 BBS (1:343/41)

You are viewing proxied material from cvs.synchro.net. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.