Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
ref:fidonet_files [2010/03/16 12:54] – digitalman | ref:fidonet_files [2015/09/07 17:54] – Added section regarding BSO .req files (copied from bt-ref.txt) digital man | ||
---|---|---|---|
Line 350: | Line 350: | ||
===== BT-REF.TXT ===== | ===== BT-REF.TXT ===== | ||
- | Snippet | + | Snippets |
+ | |||
+ | ==== Outgoing file requests ==== | ||
+ | These can be generated by BinkleyTerm or by using one of the many | ||
+ | utilities designed for the purpose, such as Amax, Bonk, Please, | ||
+ | etc. Any Opus-compatible file request builder can be used with | ||
+ | BinkleyTerm. | ||
+ | a single-line flat ASCII text file, and are named in the same | ||
+ | manner as packets (refer to the User Manual section "How | ||
+ | BinkleyTerm Handles Mail" for information on the naming convention) | ||
+ | and have a file extension of .REQ. Outgoing requests should NEVER | ||
+ | have a drive and path designation; | ||
+ | system handles the drives and paths. | ||
+ | |||
+ | The '' | ||
+ | |||
+ | BinkleyTerm will not place calls for a stand-alone .REQ file. In | ||
+ | order for a call to be placed, a packet or file attach of the | ||
+ | proper flavor must also exist (this will be prepared, along with | ||
+ | the .REQ file, by utilities such as Bonk and Amax). | ||
+ | manually poll to send the request immediately. | ||
==== Points ==== | ==== Points ==== | ||
Line 365: | Line 385: | ||
C: | C: | ||
+ | |||
===== See Also ===== | ===== See Also ===== |