Fossil

• 1. Origins And Acronym

  ›

  The year 1986 marked a turning point for early computer networking. Developers behind FidoNet, Opus-CBCS BBS, and SEAdog met to solve a growing problem. They needed a way for software to talk to serial hardware without knowing the specific machine underneath. This meeting birthed the FOSSIL protocol. The name itself tells the story of its creators. Fido stands for FidoNet. Opus refers to the Opus-CBCS bulletin board system. SEAdog represents a Fidonet compatible mailer. Together they formed the Fido Opus SEAdog Standard Interface Layer. A standards document known as FSC-0015 now defines how this protocol works. The Fidonet Technical Standards Committee maintains that document today.

  1

• 2. Hardware Fragmentation Problem

  ›

  Early Fidonet software struggled to run on different types of machines. Initial development of FidoBBS only worked on one specific type of computer. Programmers realized the software could not spread if every user had unique hardware. A uniform method was required to communicate with serial interface hardware across all platforms. This need became apparent for other communications based software as well. Before this solution existed, developers spent too much time writing code for each new machine. The goal shifted from application logic to hardware compatibility. Software using the standard could use the same interrupt functions regardless of the platform. Developers could then focus on building features instead of fixing connection issues.

• 3. DOS Era Dominance

  ›

  IBM PC compatible machines began to dominate the market in the late 1980s. These systems ran some form of Disk Operating System or DOS. Their built-in BIOS provided very poor support for serial communications. That support fell far short of the needs for any non-trivial task. As MS-DOS and PC DOS became prevalent operating systems, FOSSIL drivers gained importance. PC compatible hardware eventually became the predominant choice for users. The protocol filled a critical gap left by inadequate system-level support. Without it, complex telecommunications programs would have failed on most common computers. The widespread adoption of these machines ensured FOSSIL became essential infrastructure for the era.

  2

• 4. Notable Driver Implementations

  ›

  Specific implementations brought the protocol to life across different operating environments. Two popular DOS based drivers were X00 and BNU. These tools allowed applications to communicate with physical serial ports efficiently. A Windows based driver known as NetFoss later emerged as freeware. SIO served as a popular OS/2-based FOSSIL driver for that specific system. Each driver was written to fit specifically to the serial interface hardware of its platform. This specificity meant software could run smoothly on diverse systems without modification. Users could choose the driver matching their operating environment while maintaining compatibility.

• 5. Non-Serial Hardware Adaptation

  ›

  The protocol expanded beyond traditional serial interfaces to support new technologies. Internal ISDN cards often did not use standard serial ports at all. Developers created FOSSIL drivers to make these cards work with existing software. The goal was to make the hardware look like a modem to the application. This adaptation allowed software originally intended for modem operation only to function correctly. Such extensions proved vital as communication devices evolved past simple serial connections. The flexibility of the specification enabled it to survive changes in hardware design. It remained relevant even when the underlying technology shifted away from basic serial ports.