There seems to be some confusion over the use of the program CUT.COM
which is shipped with the current FBB distribution. I will try to
explain how it can be used effectively:-
> CUT.COM can be used when an XMODEM file transfer from an FBB phone
port crashes before the whole file is recovered by the caller.
> After disconnection the caller should save what portion of the
file he has collected and note the size (in this example let us
assume that this section will be called PART1.ZIP and is 252198
bytes long.
> The caller should then reconnect to the sending BBS and again
request the XMODEM download, but must now specify the byte offset
from which the transfer should begin. (In our example this will
be XGET FILENAME.EXT 252198). This will send the remainer of the
file from the point at which disconnection occurred. Let's call
this section which is 64768 bytes long, PART2.ZIP.
> With the transfer completed the caller now has the following in
the download directory:-
PART1.ZIP 252198
PART2.ZIP 64768
CUT.COM
> These two parts can then be stitched together using the following
syntax:-
CUT PART2.ZIP PART1.ZIP 64768 0 /A
> The completed file PART1.ZIP can then be decompressed in the usual
manner; PART2.ZIP can be deleted.
For further information you should refer to the FBB SysOp
documentation section 15.13 on page 97. It is also sometimes
advisable to discard the last few bytes of the first file section as
these can often become corrupt during the carrier loss.
It is likely that this operation will become redundant with the
advent of ZMODEM support in the next general release of FBB.
73 de Andy G1DIL SysOp @ GB7BBS - On-Line +44.746.862531 (>v32/HST)
