MFM removed unnecessary clock pulses.

Then the storage ministries looked at the same magnetic surface and asked the traditional question:

Can it be made to confess more?

The answer was RLL.

Officially: Run-Length Limited.

Unofficially: a reminder that magnetic media is governed by spacing rules, not optimism.

I. What RLL Means

RLL is not a connector. It is not a controller card. It is not a hard-disk interface.

It is a family of line coding schemes.

The basic idea is simple: when recording data onto magnetic media, you must control the spacing between flux transitions.

• transitions too close together become hard to distinguish
• transitions too far apart make clock recovery difficult

So an RLL code limits the minimum and maximum run length between transitions.

Term	Meaning
minimum run length	how close transitions may appear
maximum run length	how far apart transitions may appear
RLL code	a code that enforces those limits

The Supreme Leader notes that even magnetic domains require zoning laws.

II. MFM Was Already A Kind Of RLL

Here is where the naming becomes treasonous.

MFM itself can be described as an RLL-style code. In that formal sense, MFM is part of the same family.

But in the PC hard-disk marketplace, people usually used RLL to mean something more specific: controllers and drives using denser schemes such as 2,7 RLL, which were marketed as an improvement over ordinary MFM hard-disk systems.

Name people used	What they usually meant
MFM	conventional modified frequency modulation hard-disk encoding
RLL	denser run-length-limited encoding, often 2,7 RLL

This is historically sloppy. It is also how people actually spoke.

The Republic records both the truth and the propaganda.

III. The 2,7 Promise

The most famous PC hard-disk version was 2,7 RLL.

The numbers mean the code controls transition spacing:

• at least 2 zero bit times between transition markers
• at most 7 zero bit times between transition markers

In practical PC storage terms, 2,7 RLL was commonly sold as offering roughly 50 percent more capacity than MFM on suitable media.

That is why old drive tables looked like this:

MFM format	RLL-style marketing promise
20 MB	about 30 MB
30 MB	about 45 MB
40 MB	about 60 MB

This was not magic. It was encoding.

But Western marketing prefers miracle language because it sells controller cards.

IV. The Same Drive? Maybe. The Same Consequences? No.

Many users learned a dangerous lesson:

“If I attach an RLL controller to my MFM drive, I get more capacity.”

Sometimes this worked. Sometimes it worked briefly. Sometimes it turned the disk into a quiet archive of future disappointment.

The reason is physical: not every drive that tolerated MFM recording had enough media quality, head precision, and signal margin for denser RLL encoding.

Situation	Outcome
RLL-rated drive with RLL controller	correct use
good MFM drive reformatted as RLL	may work, may not age well
weak drive forced into RLL	data corruption wearing a promotion uniform

RLL asked the medium to store transitions more efficiently. The medium was not always patriotic enough.

V. Why It Needed Better Electronics

RLL placed heavier demands on the controller and data separator.

The controller had to:

• encode input data into legal RLL patterns
• write the denser pattern reliably
• recover timing from a more constrained transition stream
• decode the pattern back into user data

Conceptually:

Host data
  -> RLL encoder
  -> write precompensation / disk channel
  -> magnetic media
  -> read amplifier / data separator
  -> RLL decoder
  -> host data

The drive and controller had to agree with the physics.

This is always the difficult treaty.

VI. Why It Appeared At The Right Moment

RLL arrived in the PC market at the exact historical moment when users wanted more storage but the industry had not yet fully moved the controller intelligence into the drive.

That made it tempting:

• same broad ST-506/ST-412 world
• more capacity from similar mechanisms
• a controller upgrade that looked cheaper than a full platform rethink

It was a density squeeze before the interface revolution.

VII. Why It Did Not Become The Final Regime

RLL was clever, but it did not solve the larger architectural problem.

The drive was still not a complete intelligent storage subsystem. The controller still mattered too much. Geometry still mattered. Formatting still mattered. Compatibility remained a field of mines.

Then IDE/ATA took the next political step:

put the controller logic on the drive, standardize the host command path, and stop making every PC owner understand the recording channel.

Stage	What improved
MFM	better density than FM
RLL	more density from controlled transition spacing
ESDI	more drive-side intelligence and faster transfer paths
IDE / ATA	integrated drive electronics become normal

RLL was not wrong. It was intermediate.

VIII. The Real Story (Suppressed)

Officially, RLL means Run-Length Limited.

This is the version printed in documentation.

The internal name was Regime Length Limited, because every flux transition had to obey spacing rules issued by the Ministry of Magnetic Affairs.

No transition too soon. No silence too long. No unauthorized clustering.

Even the oxide had to file a movement plan.

This was later shortened to RLL after a junior engineer asked whether “regime length” sounded politically unstable. The engineer was reassigned to floppy calibration.

IX. The Lesson

RLL matters because it shows that storage progress was not only mechanical.

It was mathematical.

More capacity did not always require a new platter, a new spindle, or a new interface. Sometimes it required a stricter code and a controller confident enough to enforce it.

That confidence was sometimes deserved. Sometimes it was retail packaging.

Next: ESDI, the transitional storage interface that tried to improve ST-506 without becoming IDE, and therefore occupied the historical territory where good ideas go before mass adoption ignores them.

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