People say “MFM drive” as if MFM were the whole machine.

It was not.

MFM means Modified Frequency Modulation.

It is an encoding scheme. Not a cable. Not a controller. Not a BIOS service. Not a drive family.

And yet it became so influential in floppy and early hard-disk systems that an entire generation started using the encoding name as shorthand for the whole storage arrangement.

This is exactly the sort of conceptual sloppiness history rewards.

I. What MFM Does

Magnetic media stores data as flux reversals over time. The controller must decide how binary data is turned into those reversals while still preserving enough timing information for the read side to know where the bit cells are.

That is what an encoding scheme is for.

National Semiconductor’s disk interface guide lays out the tradeoff clearly:

• efficient codes want fewer flux reversals
• self-clocking codes want more timing cues

You do not get both for free.

MFM was the compromise that won a large part of the microcomputer era.

II. FM Before MFM

Earlier FM encoding wrote a clock transition at the beginning of every bit cell, then added a data transition for a 1 in the middle of the cell.

That was easy to decode. It was also wasteful.

MFM improved density by removing many of those clock transitions.

National’s guide states it plainly: MFM doubles the data capacity over FM by eliminating the clock transitions used in FM when they are not needed.

Encoding	Clock behavior	Practical consequence
FM	clock every bit cell	simpler, lower density
MFM	clock only when needed	denser, more efficient

This is how storage progressed for years: by deciding which pulses were truly necessary and then purging the rest.

III. The Rule

In MFM:

• data bits are written in the middle of the bit cell
• clock bits appear at the beginning of the bit cell only when there is no data bit in both the previous and current cell

The result, again in National’s description, is that there is a maximum of one flux change per bit cell.

That means higher density than FM without abandoning practical recovery.

Bit cells:   |  0  |  1  |  0  |  0  |  1  |

FM idea:     C     CD    C     C     CD
MFM idea:    C      D          C      D

C = clock transition at cell boundary
D = data transition at cell center

The exact waveform matters to the controller. The political lesson is simpler: MFM stopped writing timing markers where the medium could infer them anyway.

This is austerity in magnetic form.

IV. Why It Was Popular

National’s guide calls MFM “by far the most popular” encoding for floppy drives of the era and notes that it was used in double-density controller chips. It was also a natural fit for early hard-disk regimes like the ST-506/ST-412 world.

That popularity came from a favorable balance:

• much better density than FM
• feasible electronics
• manageable data separation

Property	MFM’s position
density vs FM	much better
decoding complexity	higher than FM, still practical
historical popularity	enormous

It was not the densest code imaginable. It was the code the industry could live with.

V. Why Controllers Mattered So Much

MFM is where old storage reminds you that “just read the bits” was never the whole job.

The National guide explains that MFM decoding requires a data separator to keep data and clock windows synchronized even though not every bit cell contains a clock pulse. In ST-506-class systems, that separator often lived on the controller side.

That is why an early hard-disk controller board was not just a passive adapter. It had to:

• receive MFM read data
• separate timing from data
• decode the stream to NRZ data for the host logic
• perform the reverse on writes

This is one reason old drive/controller combinations were so temperamental. The drive spun the media, but the controller had to be clever enough to understand what the media was saying.

VI. Why People Called Whole Drives “MFM”

Because language rots toward convenience.

If a hard disk used the ST-506-style interface and relied on MFM encoding, people called it an “MFM drive.” This was imprecise but understandable.

What people said	What they often meant
MFM drive	ST-506/ST-412-class hard disk using MFM encoding
MFM controller	controller handling MFM encode/decode and data separation

This confusion persisted because the encoding and the interface were entangled in real products.

Historians may object. Repair technicians know exactly what was meant.

VII. Why RLL Showed Up Next

MFM was good. Then density pressure returned, as it always does.

National’s guide notes that RLL schemes offered substantially better encoding efficiency than MFM, though at the cost of more complexity, better data separation requirements, and greater sensitivity to wider error bursts.

That is the next step in the story:

• FM was simpler and wasteful
• MFM was denser and practical
• RLL pushed density further and demanded more sophistication

Storage history is just repeated attempts to make the same square inch of oxide confess more bits.

VIII. The Real Story (Suppressed)

Officially, MFM stands for Modified Frequency Modulation.

This was almost MLM, but the committee decided the storage industry should not resemble a pyramid scheme until much later, when it discovered cloud billing and enterprise subscriptions.

So MFM survived:

• technical enough to sound respectable
• obscure enough to intimidate civilians
• efficient enough to matter

The naming process was not noble. It was merely less embarrassing than the alternative.

IX. The Lesson

MFM matters because it reminds us that storage progress was not only about better motors, better heads, or larger platters.

It was also about encoding discipline:

• fewer unnecessary transitions
• enough timing to decode safely
• more data from the same magnetic surface

That is how density moved forward before the interface itself changed.

Next: RLL, the next attempt to squeeze more truth out of the same magnetic territory with less patience and more mathematics.

— Kim Jong Rails, Supreme Leader of the Republic of Derails