Subj : FLO file specifications
To   : Nick Andre
From : mark lewis
Date : Tue Nov 06 2012 05:14 pm


 NA> Can someone please Netmail me or post the complete specifications
 NA> for the  contents of the Binkley FLO file format?

here's the info from the binkleyterm v2.60 documentation, pages 21 and 22, 
concerning BSO ?UT and ?LO files... ?UTs are RAW PKT files just a different 
name to tell binkley what to do with it... binkley will rename them to PKT when 
sending them... ?LO files are "file attached" files like archived mail and 
such...

==== snip ====

     The file names of the packets tell BinkleyTerm how to treat the
     different packets. Here's a typical packet name:
     00680024.OUT

     That says that the packet is for 0068/0024 (in hexadecimal) or
     104/36 in more familiar terms. The ".OUT" means it is a Normal
     packet.

     Other packet extensions include:
                  .HUT          Hold this packet for pickup by the
                                remote system.
                  .CUT          The other system can receive
                                Continuous Mail.
                  .DUT          Direct, meaning the other system
                                can NOT receive Continuous Mail.
<pgbrk>
     One nice thing is that you can manually change the file extension
     if you need to, or you can use fancy utilities such as AMAX or BONK
     to do this sort of thing for you on your command.

     For the remainder of this section, we'll assume that you'll be
     using oMMM as your mail packer. As mentioned previously, you
     probably will be using another program that has oMMM-like
     functionality; it depends on your environment.

     The oMMM program knows about these extensions and creates them
     based on information you put into the oMMM control file. You'll
     have statements like this:

     NormHold 124/102

     Any messages you enter to 124/102 would be turned into a .HUT
     packet file, placed into the outbound area, and BinkleyTerm would
     hold that packet for 124/102 to call and pick it up.
     Files are also sent through FidoNet compatible networks. oMMM
     builds and maintains a file that tells BinkleyTerm what files to
     send (or hold) for whom. A typical 'file attach' file might be
     named:

     00680024.FLO

     This would designate a that there is a file waiting to be sent to
     0068/0024 (in hexadecimal) or 104/36 in more familiar terms. The
     ".FLO" says it is a Normal file attach. File attach files are also
     called 'flow files' - named after the .FLO file extension.

     Other flow file extensions are:

         .HLO             Hold these files for pickup by the
                          remote system.
         .CLO             The other system can receive
                          Continuous Mail.
         .DLO             Direct, meaning the other system
                          can NOT receive Continuous Mail.

    A flow file is just a text file. It contains a list of files that
    are to be sent to another system:

    #c:\binkley\outbound\0000fc9c.mo1
    ^c:\myfiles\wizzle.doc
    c:\pascal\notes.doc

    The '#' prior to a flow file entry says to truncate the file to
    zero-length after successfully sending the file to the remote
    system. This is normally only employed when sending compressed mail
    (archived mail) to the remote. The '^' prior to a flow file entry
    says to delete the file after sending.

==== snip ====

you can FREQ the binkleyterm docs from my system if you like...

     BDOC_260.ZIP   289200 23-Jul-1999

don't let that 1999 date fool you... the internal files are 1995 and 1996... i 
must have grabbed the file via FTP in 1999 and failed to redate it according to 
the contents :/

)\/(ark

 
* Origin:  (1:3634/12)

.