http://wiki.synchro.net/ 2026-04-10T08:18:34+00:00 http://wiki.synchro.net/ http://wiki.synchro.net/_media/wiki:logo.png text/html 2024-02-08T00:23:44+00:00 Anonymous (anonymous@undisclosed.example.com) http://wiki.synchro.net/ref:ansi?rev=1707351824&do=diff ANSI ANSI stands for “American National Standards Institute”, but in the context of BBSing, it usually is used in reference to the ANSI X3.64 Terminal Emulation standard, or the subset of which was supported by the Microsoft MS-DOS ANSI.SYS console driver. text/html 2021-02-27T12:42:25+00:00 Anonymous (anonymous@undisclosed.example.com) http://wiki.synchro.net/ref:callinfo.bbs?rev=1614429745&do=diff Callinfo.bbs External Program Data File (a.k.a. drop file), CALLINFO.BBS format from the RBBS software. This file should normally be created in the current node's directory (example: C:\sbbs\node1). The current node's directory can be easily passed to external programs via command line (using the %n command line specifier in text/html 2021-02-27T13:13:42+00:00 Anonymous (anonymous@undisclosed.example.com) http://wiki.synchro.net/ref:chain.txt?rev=1614431622&do=diff Chain.txt External Program Data File (a.k.a. drop file), CHAIN.TXT format. This file should normally be created in the current node's directory (example: C:\sbbs\node1). The current node's directory can be easily passed to external programs via command line (using the %n command line specifier in text/html 2024-09-26T06:16:23+00:00 Anonymous (anonymous@undisclosed.example.com) http://wiki.synchro.net/ref:cterm?rev=1727331383&do=diff CTerm CTerm is the ANSI parsing code maintained as part of ciolib (and used by SyncTERM). The documentation is available at the SyncTERM website. See Also * ANSI References * ECMA-48 Standard * XTerm Control Sequences * VT100.net * Banana ANSI text/html 2019-07-19T08:49:13+00:00 Anonymous (anonymous@undisclosed.example.com) http://wiki.synchro.net/ref:dirs.txt?rev=1563526153&do=diff DIRS.TXT DIRS.TXT is an a file format used by synchronet to import and export file areas. Each flie area claims 20 lines in a flat file, with the terminator: ***END-OF-DIR*** Line descriptions 1. Area Long Name 2. Area Short Name 3. Area code without prefix (eg: MAIN) 4. data directory (eg /sbbs/data or wherever the subdirectories for this area are stored blank for default) 5. Access Requirements (eg: LEVEL 30 or blank for default) 6. Upload Requirements (eg: LEVEL 30 or blank for default) … text/html 2022-04-25T01:35:19+00:00 Anonymous (anonymous@undisclosed.example.com) http://wiki.synchro.net/ref:door.sys?rev=1650850519&do=diff DOOR.SYS External Program Data File (a.k.a. drop file), DOOR.SYS file format, initially introduced by GAP BBS Software from Kenny Gardner. This file should normally be created in the current node's directory (example: C:\sbbs\node1). The current node's directory can be easily passed to external programs via command line (using the text/html 2021-02-27T11:18:09+00:00 Anonymous (anonymous@undisclosed.example.com) http://wiki.synchro.net/ref:dorinfo1.def?rev=1614424689&do=diff Dorinfo1.def External Program Data File (a.k.a. drop file), Dorinfo#.def format from the RBBS software. This file should normally be created in the current node's directory (example: C:\sbbs\node1). The current node's directory can be easily passed to external programs via command line (using the %n command line specifier in text/html 2019-07-23T10:58:01+00:00 Anonymous (anonymous@undisclosed.example.com) http://wiki.synchro.net/ref:editor.inf?rev=1563879481&do=diff EDITOR.INF The EDITOR.INF file is a drop file that can be created by BBS software to pass information to an external message editor. Format The original EDITOR.INF file format comes from WWIV BBS software and its related message editors (e.g. WWIVedit). text/html 2025-05-09T03:19:44+00:00 Anonymous (anonymous@undisclosed.example.com) http://wiki.synchro.net/ref:fidonet?rev=1746760784&do=diff FidoNet Extensions Control Paragraphs FidoNet control paragraphs (a.k.a. “kludge lines”) are how extensible message metadata is shared among FidoNet nodes. Synchronet and SBBSecho have extended FidoNet messages with the following control paragraphs: Control Tag Description text/html 2020-12-25T01:23:01+00:00 Anonymous (anonymous@undisclosed.example.com) http://wiki.synchro.net/ref:fidonet_files?rev=1608859381&do=diff FidoNet Files This page contains details regarding the names and contents of files used in FidoNet networking (netmail and echomail). Background One of the most confusing aspects of FidoNet Technology Networks is the various files involved and their naming schemes. text/html 2024-08-09T20:17:29+00:00 Anonymous (anonymous@undisclosed.example.com) http://wiki.synchro.net/ref:fidonet_glossary?rev=1723234649&do=diff FidoNet Glossary This is the Synchronet glossary of technical terms specific to FidoNet. AKA AKAs are additional/alias addresses for an FTN node. Some times you'll see the Main/Primary address also referred to as an “AKA”, but just know this just means an text/html 2018-11-06T06:32:56+00:00 Anonymous (anonymous@undisclosed.example.com) http://wiki.synchro.net/ref:fidonet_packets?rev=1541485976&do=diff FidoNet Packets FidoNet packets are all somewhat based on the “Type-2” packet format defined in Section F (Network Layer) of FTS-1, a.k.a. FTS-0001 which contains: * A single 58-byte “Packet Header” * Zero or more “Packed Messages” (each with its own header and body text, null terminated) text/html 2024-10-15T22:33:51+00:00 Anonymous (anonymous@undisclosed.example.com) http://wiki.synchro.net/ref:files?rev=1729031631&do=diff Synchronet Files The format of most files created and used by Synchronet can be identified by the filename extension / suffix. This page is your guide to quickly identifying these files and links to format references, where available: Encoding Each of the file formats listed here will have an identified encoding: text/html 2022-03-27T17:03:59+00:00 Anonymous (anonymous@undisclosed.example.com) http://wiki.synchro.net/ref:fossil?rev=1648400639&do=diff FOSSIL In the context of BBSing, FOSSIL (Fido Opus Seadog Serial Interface Layer) is a standards protocol for creating an 8086/8088-compatible serial driver interface. It was primarily used to replace poor COM port support in the PC BIOS but used a similar (INT 14h) interface. text/html 2019-01-21T21:54:17+00:00 Anonymous (anonymous@undisclosed.example.com) http://wiki.synchro.net/ref:index?rev=1548107657&do=diff Reference Library Synchronet-related specifications: ref index External References * Synchronet JavaScript Object Model text/html 2024-01-29T05:04:13+00:00 Anonymous (anonymous@undisclosed.example.com) http://wiki.synchro.net/ref:markup?rev=1706504653&do=diff Synchronet Message Markup Synchronet can optionally recognize and apply simple text “style codes” to displayed messages. These markup codes are called 'StyleCodes' in GoldEd, 'Rich Text' in SemPoint, 'Structured Text' in Mozilla/Thunderbird, and 'Synchronet Message Markup' in Synchronet. text/html 2024-02-14T04:49:08+00:00 Anonymous (anonymous@undisclosed.example.com) http://wiki.synchro.net/ref:msginf?rev=1707886148&do=diff MSGINF The MSGINF file is a drop file that can be created by BBS software to pass information to an external message editor. Format The original MSGINF file format comes from QuickBBS and Remote Access BBS Software. The file is just a simple text file with CRLF-terminated lines: text/html 2020-11-24T23:29:56+00:00 Anonymous (anonymous@undisclosed.example.com) http://wiki.synchro.net/ref:node_status?rev=1606260596&do=diff Synchronet Node Status The current state of Synchronet terminal server (BBS) nodes are tracked in the shared file: ctrl/node.dab. The node status can be displayed through various methods: * NodeList module (Ctrl-U key handler) * Node utility * Synchronet Control Panel (for Windows) Usually each node is displayed on its own line of the form: text/html 2021-02-27T13:10:19+00:00 Anonymous (anonymous@undisclosed.example.com) http://wiki.synchro.net/ref:pcboard.sys?rev=1614431419&do=diff PCBOARD.SYS External Program Data File (a.k.a. drop file), PCBOARD.SYS format. This is a binary file written in 128 byte blocks This file should be pre-filled with spaces inside the first 128 bytes so that any field not written is filled with spaces instead of zeroes or other characters. Typically this only really matters when a caller is not online at which time only the first four fields inside of the 128 byte block are valid. The rest of the fields outside of the 128 byte block may conta… text/html 2025-05-05T00:54:42+00:00 Anonymous (anonymous@undisclosed.example.com) http://wiki.synchro.net/ref:qwk?rev=1746406482&do=diff QWK Format QWK packets and their closely related Reply (REP) packets are single-file archives (usually in PKZIP format) containing one or more data files. QWK packets are filenames with a .QWK suffix/extension, while Reply packet filenames have a .REP text/html 2021-06-28T16:53:48+00:00 Anonymous (anonymous@undisclosed.example.com) http://wiki.synchro.net/ref:qwknet?rev=1624899228&do=diff Synchronet QWK Network Extensions Imported from the old SYNCQNET.DOC file, dated 03/23/95, on July-19-2012: This document is intended for developers of QWK off-line readers or mail doors for non-Synchronet BBS packages. Synchronet multi-node BBS software has never had a QWK door written for it, because it has had extensive internal QWK off-line reader and network support since version 1 (1992). Since QWK networking is such an integrated component of Synchronet, it is extremely easy to setup a… text/html 2024-03-13T03:47:05+00:00 Anonymous (anonymous@undisclosed.example.com) http://wiki.synchro.net/ref:qwk_cmds?rev=1710301625&do=diff QWK Remote Commands Synchronet BBS users and QWKnet node sysops can perform various control functions remotely by sending QWK reply (REP) packets with specially formatted messages. Note that some of these functions are intended only for users who are using QWK offline readers to retrieve their messages from the text/html 2019-07-19T08:58:55+00:00 Anonymous (anonymous@undisclosed.example.com) http://wiki.synchro.net/ref:result.ed?rev=1563526735&do=diff RESULT.ED RESULT.ED is the name of a drop file that an external text editor may leave for the BBS to read and use after the editor has completed creating or editing a text file (typically a message). The filename is traditionally all-caps, but Synchronet supports text/html 2020-04-24T04:08:40+00:00 Anonymous (anonymous@undisclosed.example.com) http://wiki.synchro.net/ref:smb?rev=1587701320&do=diff Synchronet Message Base FIXME The SMB format and library specification v1.21, circa 1993: <http://synchro.net/docs/smb.html> Header Fields RECIPIENT * The RECIPIENT header field contains a single name or full-address of the message recipient, in US-ASCII or UTF-8 characters * text/html 2024-03-05T21:37:48+00:00 Anonymous (anonymous@undisclosed.example.com) http://wiki.synchro.net/ref:uifc?rev=1709674668&do=diff UIFC Background UIFC (User InterFaCe) is the text mode full-screen user interface library used by SCFG, echocfg, and others. It was originally inspired by the text mode user interface for NetWare 2.x server management utilities for DOS (e.g. SYSCON), and was written from scratch by text/html 2025-10-09T12:30:43+00:00 Anonymous (anonymous@undisclosed.example.com) http://wiki.synchro.net/ref:xbin?rev=1760013043&do=diff XBin XBin (.xb) is an ANSI/block art file format created by Tasmaniac of ACiD. The main “image data” portion of the file is identical in format to that of a “Binary Text” (.bin) file: an IBM CGA text mode memory dump consisting of pairs of 8-bit character (e.g. text/html 2011-07-14T06:49:12+00:00 Anonymous (anonymous@undisclosed.example.com) http://wiki.synchro.net/ref:xmodem?rev=1310626152&do=diff XMODEM, CRC XMODEM, WXMODEM File Transfer Protocols Please circulate this document anyway that you see fit without alteration except on the page at the end titled: "Notes and Comments". It is requested that anyone using these protocols within a commer- cial product not charge for them as an option or surcharge, but include XMODEM and its derivations as part of the basic product. Peter Boswell … text/html 2021-02-27T18:26:24+00:00 Anonymous (anonymous@undisclosed.example.com) http://wiki.synchro.net/ref:xtrn.dat?rev=1614450384&do=diff XTRN.DAT The Synchronet v2 External Program Data File (a.k.a. drop file), xtrn.dat format. In DOS and OS/2 versions of Synchronet, this file was named XTRN.DAT but later (in Synchronet v3), the case of the created file was configurable (either all upper or all lower case). text/html 2011-07-14T05:02:00+00:00 Anonymous (anonymous@undisclosed.example.com) http://wiki.synchro.net/ref:ymodem?rev=1310619720&do=diff XMODEM/YMODEM Protocol Reference A compendium of documents describing the XMODEM and YMODEM File Transfer Protocols. This document was originally edited and formatted (by Chuck Forsberg) 10-27-87. This document was formatted for Wiki syntax by Rob Swindell on July-13-2011. text/html 2025-09-26T21:13:21+00:00 Anonymous (anonymous@undisclosed.example.com) http://wiki.synchro.net/ref:zmodem?rev=1758921201&do=diff ZMODEM zmodem.doc !copyrighted by MCS 1994 use it anyway you like but don't complain this file should be accompanied by a readme which contains some background information on implementing zmodem. GENERAL Documentation about the zmodem protocol internals; should be sufficient to implement a completely functional zmodem protocol suite.