1. Forum
  2. FidoNet
  3. BINKLEY

  • Binkley32 on Win2000 Server

    From Ger Vloothuis@3:633/284 to All on Fri Mar 22 13:33:27 2002
    Hi All!

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

    Anyone came across this before?


    Cheers

    Ger Vloothuis
    ICQ:103-106-035

    --- GoldED/W32 3.0.1
    * Origin: Teletechnique BBS (3:633/284)
  • From Bob Jones@1:343/41 to Ger Vloothuis on Fri Mar 22 13:36:28 2002
    I am running Binkley32 on a Win2000 Server. It doesn't
    want to write incoming packets to the disk. It baulks
    about disk is full. There is plenty of space on the
    disk and all permissions for Binkley to write there are
    set OK.

    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)
  • From David Drummond@3:640/305 to Ger Vloothuis on Sat Mar 23 08:58:58 2002
    Ger

    22 Mar 02 21:33, Ger Vloothuis wrote to All:

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

    Anyone came across this before?

    If it's anything like Binkley for OS/2, it doesn't like free space greater than
    2Gb.

    Regards,
    David

    --- Msged/LNX TE 06 (pre)
    * Origin: Blessed are the geek for they shall inherit the earth. (3:640/305)
  • From Art Johnston@1:103/105 to Ger Vloothuis on Fri Mar 22 23:12:02 2002
    I am running Binkley32 on a Win2000 Server. It doesn't want to write incoming packets to the disk. It baulks about disk is full. There is plenty of space on the disk and all permissions for Binkley to write there are set OK.

    Anyone came across this before?


    Cheers

    You are probably hitting the old DOS Disk Size limit of 4 (?) Gigs. (Can't
    remember exactly been too long). Sizes larger than 4 Gigs, were reported as negative sizes using the *old* DOS API, so the software would think it was out of drive space.

    Try putting Binkley on a Partition less than 4 Gigs in Size.

    Good Luck, keep us posted on your progress!

    Art Johnston

    --- WWIVToss v.1.40 Registered
    * Origin: -*The Abyss Westminster, California USA*- (1:103/105.0)
  • From Jerry Schwartz@1:142/928 to Ger Vloothuis on Sat Mar 23 13:18:21 2002
    Hello, Ger...

    The other messages are all true, but I think the later versions of BTXE have that fixed.

    Regards,

    Jerry Schwartz

    mailto:jerryschwartz@comfortable.com
    http://www.writebynight.com

    --- Msged/NT 6.0.1
    * Origin: Write by Night (1:142/928)