Floppy Disks and DOS: Command Line Childhood

C:\>_

The cursor blinked, waiting. No icons. No mouse. Just text, and the expectation that you knew what to type.

The Floppy Disk

5.25-inch disks were actually floppy bendable plastic squares with exposed magnetic media. You could ruin them with a careless touch, a magnet, or direct sunlight. They held 360KB. Later, 1.2MB on the high-density versions.

The 3.5-inch disks that followed were rigid, encased in hard plastic with a sliding metal cover. More durable, smaller, but we still called them floppies. 720KB, then 1.44MB.

Every program came on floppies. Multiple floppies. Install software meant swapping disks when prompted:

Please insert Disk 2 of 7
Press any key to continue...

By disk 5, you questioned your life choices.

DOS: The Interface

MS-DOS (Microsoft Disk Operating System) was a text environment. You typed commands. The computer responded. There was no other option.

Basic navigation:

DIR          - List directory contents
CD           - Change directory
COPY         - Copy files
DEL          - Delete files
FORMAT       - Prepare a disk (and destroy everything on it)

The path structure made sense once you understood it:

C:\GAMES\SIERRA\SQ3\SQ3.EXE

Drive C, directory GAMES, subdirectory SIERRA, sub-subdirectory SQ3, file SQ3.EXE.

You learned to navigate without seeing. Mental maps of directory structures. The entire computer existed as text, and you held it in your head.

CONFIG.SYS and AUTOEXEC.BAT

These two files controlled your computer's soul.

CONFIG.SYS loaded device drivers and set memory configuration:

DEVICE=C:\DOS\HIMEM.SYS
DEVICE=C:\DOS\EMM386.EXE NOEMS
DOS=HIGH,UMB
FILES=40
BUFFERS=20

AUTOEXEC.BAT ran commands at startup:

@ECHO OFF
PATH C:\DOS;C:\WINDOWS;C:\GAMES
SET BLASTER=A220 I5 D1
PROMPT $P$G

Getting these wrong meant the computer wouldn't work right. Getting them right was an art.

The Memory Problem

DOS could only use 640KB of RAM directly. This was "conventional memory." Games needed as much of it as possible.

MEM /C

This showed your memory map. A good setup had 600KB+ free. A bad setup had 550KB, and your game wouldn't run.

The solution: memory managers. Loading drivers into "upper memory" or "high memory" to free the precious 640KB. Hours of tweaking for a few extra kilobytes.

Boot disks became essential. A floppy with a custom CONFIG.SYS and AUTOEXEC.BAT optimized for a specific game. Different games needed different configurations.

This was insane. We accepted it as normal.

The Games

Installing a game meant running INSTALL.EXE and answering questions:

Select your sound card:
1. Sound Blaster
2. Adlib
3. Roland MT-32
4. PC Speaker
5. None

Wrong choice meant no sound, or worse, crashes. You learned your hardware specifications by necessity.

Then the IRQ and DMA settings:

Sound Blaster IRQ: 5
Sound Blaster DMA: 1

These had to match your actual hardware configuration. Conflicts with other devices meant troubleshooting. Sometimes for hours.

When it finally worked when the game actually ran, with sound, without crashing the satisfaction was immense. You'd earned it.

Batch Files

You could automate commands by writing batch files:

@ECHO OFF
CD \GAMES\DOOM
DOOM.EXE
CD \

Save as DOOM.BAT, and now typing DOOM at any prompt would launch the game.

This was programming, in a practical sense. You learned that computers do exactly what you tell them, in order. Sequencing. Logic. The building blocks.

The Boot Process

Turn on the computer. Watch text scroll:

Starting MS-DOS...

HIMEM is testing extended memory...done.

C:\>_

That cursor appearing meant success. Every startup was a minor victory.

Sometimes it didn't work. Error messages. Hangs. The dread of potential hardware failure.

You learned troubleshooting. Step by step, ruling out possibilities. What changed? What's different? Where's the error coming from?

The Upgrade Treadmill

Every new game pushed the limits. You needed more RAM. A better sound card. A faster processor. A bigger hard drive.

20MB hard drives gave way to 40MB, then 80MB, then (unimaginably) hundreds of megabytes. We couldn't conceive of filling such space.

Each upgrade meant reinstalling everything. Reconfiguring everything. The ritual of optimization, repeated.

The Windows Transition

Windows 3.1 arrived, and suddenly there were icons and a mouse. But Windows sat on top of DOS. You exited Windows to run games. You still needed to understand the underlying system.

Windows 95 changed everything. DOS became hidden. The command line became optional. Most people never saw it again.

Those of us who grew up with the blinking cursor felt both relief and loss. Computers became easier. They also became less comprehensible.

The Legacy

I still use command lines. Terminal on Mac, PowerShell on Windows. The skills transfer.

But more than skills: it's a mindset. Computers aren't magic. They're systems. Systems can be understood. Commands can be learned. Problems can be solved.

That blinking cursor taught patience, precision, and the satisfaction of figuring things out. When it finally worked when the game loaded, when the program ran, when the system bent to your will you knew you'd earned it.

C:\>_

Still waiting. Still ready. What do you want to do?