Life behind the SysOp prompt

The word SysOp — system operator — could sound glamorous on a title screen. In practice, it often meant buying a second phone line, feeding disks into a stubborn computer, answering questions about forgotten passwords and trying to understand why the board had stopped accepting calls while you were asleep.

Every BBS had an operator. For thousands of small, personal systems, this was one individual who provided the hardware, software, storage, electricity, telephone service and, most importantly, the time. You could admire a board's animated ANSI welcome or its enormous collection of shareware. Behind it was somebody arranging file directories, setting up message conferences, troubleshooting a modem, and making decisions about the culture of the community.

The nightly checklist

A responsible SysOp checked the call log, looked for failed transfers, reviewed messages and answered private notes. New users might need authorization. Uploaded files might need virus scanning and description updates. A door game could require maintenance, reset schedules or new configuration files. If the system exchanged FidoNet messages, its mailer and message-tossing software had their own schedules and potential failure points.

Large boards could run multiple nodes, with each node handling a concurrent caller. That offered breathing room but added considerable complexity: extra lines or connectivity, multitasking software, hardware expenses and the possibility of corrupted data when several callers wrote to the same storage.

Being a host, not merely an administrator

SysOps established tone. Some boards were deliberately strict: use your real name, keep on topic, no duplicate uploads, read the rules. Others were anarchic, creative places full of absurd handles, elaborate ANSI menus and fierce door-game rivalries. Moderation and judgement were essential. A small community could be transformed by one abrasive caller, and the person who paid the telephone bill often had to make the hard decision.

A good BBS felt like a room someone had prepared for you before you arrived.

On many systems, pressing a key to page the SysOp could ring a bell at the host computer. If the operator was home and available, the screen could suddenly split into a two-way chat. For a new caller, that moment was startling: the person who ran the computer was actually there.

The economics of generosity

Most hobby boards were not lucrative businesses. A SysOp paid for a PC, modem, hard drive and line rental, plus replacement parts and sometimes long-distance network calls. A particularly popular board could become expensive to expand. Some sought voluntary donations or subscription fees, particularly if they offered extensive file libraries or multiple simultaneous lines.

None of that work showed up in the welcome banner. But it determined whether a board felt reliable and safe. People returning each night often had no idea how many failed modem handshakes and midnight resets had occurred since yesterday's visit.

A good question for every surviving SysOp

Ask what the board was called. Ask about its area code, software, hardware, welcome ANSI, most popular door and the quirks of its callers. Ask when it started and when it stopped — or whether it never stopped at all. Above all, ask why they decided that other people deserved a place to call.

Every answer is a small piece of community history that rarely appears in the formal history of computing.