FidoNet message packet
Dan Tobias (Talk | contribs) m (Dan Tobias moved page FidoNet message packets to FidoNet message packet: Be consistent; usually singular is better) |
Dan Tobias (Talk | contribs) (→Sample files) |
||
| (8 intermediate revisions by one user not shown) | |||
| Line 1: | Line 1: | ||
{{FormatInfo | {{FormatInfo | ||
|subcat=E-Mail, newsgroups, and forums | |subcat=E-Mail, newsgroups, and forums | ||
| + | |released=1984 | ||
}} | }} | ||
| − | + | A '''FidoNet message packet''' is used to transfer messages in the FidoNet BBS network. The [[FidoNet nodelist]] is used by systems on FidoNet to find out how to contact other systems to send messages (originally by dialup, but now often by IP or other networking). Originally, all transfers were done during a designated "net hour" in the middle of the night when BBSs were closed to human callers and only called one another, but eventually most software became capable of making network transmissions at any hour (though it was usually done when long-distance rates were cheaper in the days before unlimited calling plans). | |
| − | '''FidoNet message | + | |
The formats used in packet transmission are defined in FidoNet standards documents maintained by the FidoNet Technical Standards Committee (FTSC). | The formats used in packet transmission are defined in FidoNet standards documents maintained by the FidoNet Technical Standards Committee (FTSC). | ||
| + | |||
| + | The packets included some binary information and some plain text. In the plain text portions, line/paragraph breaks were represented with CR (hex 0D), while "soft line breaks" inserted by automatic processors (which were supposed to be ignored in favor of reformatting the text at the recipient end) were stored as hex 8D. Linefeeds (hex 0A) might or might not follow the carriage returns (hard or soft) and were ignored. Long lines were supposed to be wrapped to suit the line length. | ||
| + | |||
| + | Lines starting with Ctrl-A (01) were considered to be control lines intended not to be displayed. | ||
== See also == | == See also == | ||
| − | * [[FidoNet | + | * [[FidoNet nodelist]] |
| + | * [[EMSI/IEMSI]] | ||
== Sample files == | == Sample files == | ||
| − | * [ | + | * [https://www.dan.info/sampledata/BAD_BNDL.007 Sample FidoNet packet] (from 1988; found in an old bunch of archived files, and the filename has "BAD" in it, so it might have been messed up in some way) |
== References == | == References == | ||
* [http://ftsc.org/docs/fts-0001.016 FTS-0001 (revision 16)] - has basic packet format standards | * [http://ftsc.org/docs/fts-0001.016 FTS-0001 (revision 16)] - has basic packet format standards | ||
* [http://ftsc.org/docs/ FidoNet standards documents] | * [http://ftsc.org/docs/ FidoNet standards documents] | ||
| + | * [http://www.textfiles.com/programming/FORMATS/fossil.txt Fundamentals of FOSSIL implementation and use] | ||
| + | |||
| + | [[Category:Bulletin board systems]] | ||
Latest revision as of 00:12, 12 February 2020
A FidoNet message packet is used to transfer messages in the FidoNet BBS network. The FidoNet nodelist is used by systems on FidoNet to find out how to contact other systems to send messages (originally by dialup, but now often by IP or other networking). Originally, all transfers were done during a designated "net hour" in the middle of the night when BBSs were closed to human callers and only called one another, but eventually most software became capable of making network transmissions at any hour (though it was usually done when long-distance rates were cheaper in the days before unlimited calling plans).
The formats used in packet transmission are defined in FidoNet standards documents maintained by the FidoNet Technical Standards Committee (FTSC).
The packets included some binary information and some plain text. In the plain text portions, line/paragraph breaks were represented with CR (hex 0D), while "soft line breaks" inserted by automatic processors (which were supposed to be ignored in favor of reformatting the text at the recipient end) were stored as hex 8D. Linefeeds (hex 0A) might or might not follow the carriage returns (hard or soft) and were ignored. Long lines were supposed to be wrapped to suit the line length.
Lines starting with Ctrl-A (01) were considered to be control lines intended not to be displayed.
[edit] See also
[edit] Sample files
- Sample FidoNet packet (from 1988; found in an old bunch of archived files, and the filename has "BAD" in it, so it might have been messed up in some way)
[edit] References
- FTS-0001 (revision 16) - has basic packet format standards
- FidoNet standards documents
- Fundamentals of FOSSIL implementation and use
