Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
ref:fidonet_files [2015/09/07 17:54] – Added section regarding BSO .req files (copied from bt-ref.txt) digital man | ref:fidonet_files [2017/10/09 23:12] – Updated references to SBBSecho packet filenames to reflect v2 and v3 differences. digital man | ||
---|---|---|---|
Line 60: | Line 60: | ||
Packets may contain NetMail or EchoMail messages. | Packets may contain NetMail or EchoMail messages. | ||
- | Packet files have a '' | + | Packet files have a '' |
files "in process" | files "in process" | ||
of a Packet can actually be *anything*, but is usually a | of a Packet can actually be *anything*, but is usually a | ||
- | numeric time stamp of some sort. SBBSecho | + | numeric time stamp of some sort. SBBSecho |
- | (where each pair of letters is a 2-digit zero-padded decimal | + | where each pair of letters is a 2-digit zero-padded decimal |
- | number representing the Day of the month, hour of the day, | + | number representing the day of the month, hour of the day, |
- | minute, and second at the time the packet was created) | + | minute, and second at the time the packet was created |
+ | SBBSecho v3 uses the packet creation time in Unix time_t format | ||
+ | (seconds since Jan-1-1970) represented with hexadecimal digits | ||
as the base file name when creating Packet files. The | as the base file name when creating Packet files. The | ||
important thing is that the Packet files have unique names. | important thing is that the Packet files have unique names. | ||
Line 162: | Line 164: | ||
Flow Files are unique to Binkley/ | Flow Files are unique to Binkley/ | ||
- | BSO) mailers | + | BSO) mailers |
containing plain text (so they can be easily viewed or edited, unlike the | containing plain text (so they can be easily viewed or edited, unlike the | ||
other file types described in this document). | other file types described in this document). | ||
Line 170: | Line 172: | ||
NNNNnnnn.Flo | NNNNnnnn.Flo | ||
- | where " | + | where " |
- | hexadecimal number, and " | + | hexadecimal number, and " |
a 4-digit zero-padded hexadecimal number, and " | a 4-digit zero-padded hexadecimal number, and " | ||
" | " | ||
- | (C)rash, (D)irect/Immediate, (H)old, or F, for " | + | (C)rash, (D)irect/(I)mmediate, (H)old, or F, for " |
- | Another | + | Another |
address is a " | address is a " | ||
is the destination point number as an 8-digit zero-padded hexadecimal | is the destination point number as an 8-digit zero-padded hexadecimal | ||
Line 184: | Line 186: | ||
NNNNnnnn.pnt | NNNNnnnn.pnt | ||
- | where " | + | where " |
- | hexadecimal number, and " | + | hexadecimal number, and " |
for example: | for example: | ||
Line 205: | Line 207: | ||
indicates whether or not to delete or truncate the file after its | indicates whether or not to delete or truncate the file after its | ||
been sent (i.e. '#' | been sent (i.e. '#' | ||
- | |||
==== BT-USER.TXT ==== | ==== BT-USER.TXT ==== | ||