History is made of facts: dates, standards, speeds, companies. But the dial-up era was also made of experiences — the specific texture of what it felt like to be online when being online was still a novelty. The sound of a modem connecting. The decision to stay on just a little longer. The morning after a night of downloads. These stories try to capture that texture.
If you are of a certain age, you do not need to be told what the dial-up handshake sounded like. You remember it. The dial tone. The beeping of the number. A pause. Then — the screech.
It started with a high, pure tone, like a telephone that had decided to become an instrument. Then a lower tone replied. Then both began to modulate, to warble, to slide across frequencies in patterns that sounded almost musical if you were in the right mood and almost maddening if you were in a hurry. Bursts of static. A kind of rhythmic chuffing. Another screech. A negotiating silence. And then, if the gods were willing, the word CONNECT appeared on your screen, followed by a number: 28800, or 33600, or — on a good day, on a clean line, with the wind behind you — 52000.
What you were hearing was two machines introducing themselves. The opening high tone was the ANSam signal: the answering modem announcing its presence and capabilities. The warbling that followed was the line-probing phase: each modem sending test tones across the frequency spectrum, measuring how the wire responded, building a map of where the noise was and where it was not. The chuffing was the equaliser training: known bit patterns sent and analysed, filter coefficients adjusted, until the channel model was good enough to begin. The whole sequence lasted between 20 and 40 seconds and represented, in compressed acoustic form, a remarkable feat of real-time signal processing.
Nobody explained any of this to the people listening. They just knew that the sound meant it is working, and the absence of the sound — the dreaded silence followed by NO CARRIER — meant try again. Over time, experienced users learned to read the sound. A handshake that sounded different than usual often meant a noisier line and a lower connect speed. A very short handshake was suspicious: either a fast connection or a failed one that hadn't reported the failure yet.
The sound became so embedded in the culture of the era that it has survived long after the technology that produced it. It has been sampled and released as music. It appears in films whenever a director wants to signal "the 1990s internet." Websites play it as a nostalgic greeting. A generation that grew up with it reports a complex emotional response upon hearing it again: something between warmth and mild anxiety, which is perhaps exactly the right emotional register for those years.
It probably went something like this.
Someone — a friend, a colleague, a magazine article — had told you that you needed to get on the internet. This was 1995 or 1996. You had a computer, probably a Pentium or a 486, running Windows 95. You had a modem — 14.4k if you'd bought it a year ago, 28.8k if you'd bought it recently. You had signed up for an account with an ISP: a local one, or CompuServe, or one of the regional services that were proliferating at the time.
The setup took an afternoon. There was a floppy disk. There was a phone number to dial. There were fields to fill in: username, password, DNS server addresses written on a card the ISP had mailed you. There was a moment when it all seemed to be configured correctly and you double-clicked the dialup icon and listened to the modem dial and negotiate and then — you were connected. The little icon in the system tray showed two computers exchanging data, their lights blinking in a pantomime of activity.
You opened a browser. Netscape Navigator, almost certainly. The default home page loaded — slowly, a progress bar inching across the bottom of the screen, the image arriving in chunks from top to bottom as the data trickled down the line. You typed an address someone had given you, or you went to Yahoo! and looked at the directory of websites organised by category, and you clicked on something, and a page loaded, and it had text and some images and maybe a MIDI file that started playing automatically and you could not figure out how to turn it off.
You stayed online for an hour, maybe two. You were aware, the entire time, of the ticking clock: the phone line was occupied, the bill was running, someone might need to make a call. When you finally disconnected, you sat for a moment looking at the screen. Something had shifted. You weren't sure what it was yet. You would figure it out over the next several years, along with everyone else.
Before the World Wide Web, before AOL, before any of the things that most people mean when they say "the internet," there were the BBSs. And they were run, for the most part, by individuals who had decided to give up a phone line, some disk space, and a significant portion of their sleeping hours so that strangers could call in at 2 a.m. and argue about Star Trek.
The sysop — system operator — was a specific type of person. Not necessarily a programmer, though many were. What they shared was a certain compulsion: the belief that a computer connected to a phone line was a thing worth maintaining, worth upgrading, worth losing sleep over. They named their boards with a kind of earnest creativity: The Twilight Zone, Shadow Realm, The Dragon's Den, Caffeine Dreams. They wrote the welcome screens themselves, often in ANSI art — a form of text-based graphics using IBM's extended character set and escape codes for colour — that could be genuinely beautiful in a blocky, neon-on-black kind of way.
The experience of calling a BBS was ritualised. You dialled the number. If the line was busy — and on popular boards, it often was — you redialled, manually, until you got through. A good terminal program could automate the redialling, cycling until the line was free. You were greeted by the welcome screen, asked to log in or register, and then presented with a menu: Messages, Files, Doors, Chat, Bulletins. You read the messages in the forums you followed. You checked the file sections for new uploads. If the sysop was online, you might get a private chat message: "Hey, you're the person who uploaded that utility last week — is there a newer version?"
There was a social hierarchy. New users were guests; regular users had higher download ratios; contributors who uploaded files or helped new users had status. The sysop's word was law — they could delete your account with a keystroke, and on their board, they were absolute sovereigns. Most were benevolent. Some were eccentric. A few were tyrants whose boards were nonetheless worth calling because they had the best files.
FidoNet connected these islands. Starting in 1984, BBSs could forward messages to each other in nightly batch transfers — one board calling another in the small hours, exchanging accumulated messages, then hanging up. A message posted in Chicago on Monday evening might arrive in London by Wednesday. This was called "netmail" and it was, for many users, their first experience of international electronic communication. The FidoNet backbone at its peak in the early 1990s carried more message traffic than the internet.
The BBSs did not die of old age. They were killed by the internet — specifically, by the combination of graphical browsers, flat-rate internet access, and the sudden availability of a global network that made the local BBS feel small. The transition happened fast: between 1994 and 1997, most BBSs either shut down or transformed into internet service providers. The sysops who had run them went various ways: some became early web developers, some became network administrators, some simply went back to sleep.
There is a calculation that anyone who used dial-up internet in the 1990s performed constantly, usually in their head, sometimes on paper. It went: file size divided by connection speed, adjusted for the gap between theoretical and actual throughput, multiplied by the cost per minute of the phone call, compared against the urgency of having the file. The result was a number in minutes and pence (or cents), and the decision was whether that number was acceptable.
For small files — a web page, a short text document, a small program — the calculation was easy and the answer was yes. For large files, the calculation became genuinely agonising. A 1.44 MB floppy-disk image at 28.8 kbps took about seven minutes to download, assuming a clean line and no retransmissions. A CD image was out of the question. A game demo of 20 MB, which became common in the mid-1990s, took roughly 90 minutes. You could start it, go to bed, and hope.
Hoping was the operative word. Dial-up connections dropped. Phone lines crackled. The ISP's server went down. The download manager — if you had one, and many early users did not — might support resuming an interrupted download; many servers did not support the HTTP range request header that made resuming possible. A dropped connection after 85 minutes of a 90-minute download meant starting over. This happened. It happened more than once to most people who downloaded large files in that era, and the memory of it still produces a specific kind of low-grade fury that has no modern equivalent.
The solution, for those who figured it out, was the overnight download. You started the download before going to bed. You configured your download manager to dial automatically if the connection dropped and resume from where it left off. You set the screen saver. You went to sleep to the faint sounds of the modem renegotiating from the other room. In the morning, either the file was there — complete, verified, intact — or it wasn't, and you started again.
The phone line being occupied was a separate problem. In households with a single line and more than one person, a two-hour evening download was a domestic negotiation. Parents who needed to make phone calls, flatmates who were expecting a call, anyone who wanted to use the telephone for its original purpose — all of them were blocked by the modem's occupation of the line. This produced a specific type of household tension that ended, abruptly and completely, the day broadband was installed and the phone line was free again regardless of internet activity.
At some point in the 1990s, it became impossible to open a magazine, receive a piece of post, buy a box of cereal, or rent a video without finding an AOL disc inside. The discs — first floppy, then CD-ROM — offered a free trial: ten hours, then thirty hours, then a hundred hours, then a month, then two months of America Online, free, just install this disc and you're online. They arrived in the post unsolicited. They fell out of magazines. They were handed out at trade shows, tucked into shopping bags, bundled with computer purchases. At the peak of AOL's direct mail campaign in the mid-to-late 1990s, the company was spending an estimated $300 million per year on disc distribution.
The strategy was, by any measure, extraordinarily effective. AOL grew from 200,000 subscribers in 1992 to 2.5 million in 1995 to 10 million in 1997 to a peak of 26.7 million in 2002. The discs converted browsers into subscribers at rates that justified the cost. Steve Case, AOL's CEO, understood something that many technology companies have since rediscovered: that the barrier to trying something new is friction, and if you could put the thing directly in people's hands — physically, literally, through their letterbox — a certain percentage of them would try it, and a certain percentage of those would stay.
The discs themselves accumulated. Nobody threw them away, at least not immediately. They stacked up in drawers and on shelves. They were used as coasters, as frisbees, as reflectors for garden pests. Artists collected them and made installations. An Oregon man named Jim Kimball collected over 1 million AOL discs. The discs became a symbol — of the era's excess, of a company's extraordinary confidence, of a moment when the internet was still new enough that giving it away was a viable business strategy.
AOL itself was more than a service. For most of its subscribers, it was the internet — not a gateway to the wider web, but a complete online world: email, instant messaging (AIM, which was a separate cultural phenomenon), chat rooms, news, entertainment, shopping, all within AOL's walled garden. The famous "You've got mail" notification, spoken in a warm American voice whenever new email arrived, became one of the most recognised audio signatures of the decade. A 1998 romantic comedy was named after it. For a brief but remarkable period, AOL was the internet, and the internet was AOL.
In early 1997, the modem industry presented its customers with a choice they had not asked for and did not want. US Robotics had X2. Rockwell had K56flex. Both promised 56 kilobits per second downstream. They were incompatible. Your modem had to match your ISP's equipment, or you got V.34 speeds regardless. Pick a side.
Most people did not know they had picked a side until after they had. You bought a modem — a USR Sportster, say, because USR had a good reputation — and then you called your ISP and asked if they supported 56k, and they said yes, and you said great, and you got home and plugged in the modem and the connection speed was 33,600 bps. The ISP had K56flex equipment. Your modem was X2. The protocol negotiation had sensibly fallen back to V.34 rather than attempt an incompatible 56k handshake.
The forums and newsgroups of the era were full of this. Threads with titles like "X2 vs K56flex — WHICH IS FASTER??" and "My ISP uses K56flex but I bought X2 — am I stuck??" People posted their CONNECT speeds the way other people post gym results. 44,000 was decent. 49,333 was good. 52,000 was cause for celebration. 56,000 was technically impossible under FCC regulations and therefore a source of some dispute when anyone claimed to have achieved it.
US Robotics argued, with some justification, that X2 was technically superior. Rockwell argued, with equal justification, that K56flex had broader industry support. Neither was entirely right. Both had real limitations, and the real-world performance of either standard depended far more on the quality of your local loop — the copper wire from your house to the exchange — than on which protocol you were using.
The ITU ratified V.90 in September 1998 and the war ended. Both sides issued firmware updates. Users applied them. The CONNECT speeds did not change dramatically — V.90 was largely a diplomatic reconciliation between two technologies that were more similar than either company had cared to admit. But the anxiety of having chosen wrong, of being on the losing side of a standards war, was over. For a few more years, until broadband arrived and made the whole discussion irrelevant, everyone was speaking the same language.
The day broadband arrived was not, for most people, a dramatic event. There was a engineer visit, or a self-install kit, or a router that arrived in the post with instructions. You plugged in a cable. You configured something, or the router configured itself. A light turned green. You opened a browser and typed a web address and the page appeared. Not slowly, not in chunks, not with a progress bar crawling across the bottom of the screen. It appeared, essentially instantly, as if it had always been there.
You tried another page. Then another. You downloaded something — a file you had been putting off downloading because it was too large for a sensible dial-up session. You watched it complete in minutes. Then you tried streaming audio, which you had heard about but never seriously attempted because a streaming audio connection at 28.8k involved more buffering than music. It worked. It just worked, without drama, without dropped connections, without the specific held-breath tension of a dial-up session in progress.
The most immediately noticeable thing was not the speed. It was the silence. The modem was not dialling. There was no handshake, no CONNECT message, no occupied phone line. The internet was simply there, as a condition of the house, like electricity or running water. You could pick up the telephone and make a call while simultaneously downloading a file — two things that had been mutually exclusive for the past several years of your life. This felt, in a way that was disproportionate to its actual significance, extraordinary.
Something had ended. The rituals of dial-up — the dialling, the waiting, the managing of connection time, the overnight queues, the disconnecting before someone needed the phone — were simply gone. The texture of going online had changed completely, and with it, gradually, everything else: how you consumed media, how you communicated, how you worked, what you expected. The always-on internet was not just faster dial-up. It was a different thing entirely.
And the modem? It was still there, technically. The ADSL router under the desk contained a modem, running DMT modulation across 256 sub-carriers on the copper wire, adapting continuously to line conditions, sustaining a connection that never dropped and never needed to announce itself with a sound. It had become infrastructure — invisible, essential, no longer worthy of notice. Which is, perhaps, the highest compliment technology can receive.