Rebuilding the Windows 98 Disk Defragmenter in Pure JavaScript: The Art of Watching Blocks March

If you grew up using a personal computer in the late 1990s, you remember the sound.

It was the rhythmic, metallic crunch-crunch-thwip of a 4.3 GB Quantum Fireball hard drive mounted inside a beige steel tower. It was the faint phosphor warmth radiating off a 15-inch CRT monitor at 1:00 AM, illuminating a darkened bedroom with a saturated #008080 teal glow.

And on that screen was an application that captivated an entire generation: The Windows 98 Disk Defragmenter (defrag.exe).

There were no algorithmic feeds, no smartphone notifications, and dial-up internet cost real money by the minute. So we sat there, chin rested on palms, mesmerized by a grid of colored squares slowly consolidating toward the front of the drive:

• Unoptimized light-blue clusters would suddenly flash radioactive green as they were read into memory.
• The disk head would seek across the platter, and destination blocks at the front would strobe alert red as data was written.
• With a quiet mechanical sigh, those cells settled into a soothing, solid navy blue.

1. Decoding the Sacred 6-Color Palette

Before writing any logic, the visual language had to be exact. The original utility didn’t use random primaries; it used an intentional palette designed for 8-bit and 16-bit CRT monitors.

The legend dialog listed a mysterious sixth state: “Data that will not be moved”. These were the locked page files (win386.swp), system files, or bad sectors that marked out boundaries the defragmenter was forced to work around.

2. Why Naive Defrag Looked “Fake” (The Chunk Secret)

When you first try to simulate defragmentation, the obvious approach is to find the first empty space, find the last used cluster, and move it one single cell at a time.

If you ever watched the real Windows 98 utility, that is not how it worked. Real disk controllers read and write contiguous sectors in batches.

By grouping adjacent cluster moves into contiguous runs, entire 3-block and 4-block sequences flash green at the tail, vanish into free space, and strobe red at the head—recreating the authentic mechanical cadence of a real drive head seeking across platters.

3. Period-Accurate 3D Chrome: Bevels & Progress Bricks

In Windows 98, every button and status bar was an illusion rendered using dual 1px and 2px border bevels simulating an overhead light source:

The Segmented Progress Bar

Remember how progress bars back then weren’t smooth gradients, but discrete little vertical blue rectangular bricks?

4. The Retro Easter Egg: “Under Construction” Mode

While building this simulator, we realized it had a wonderfully nostalgic second life. Remember the animated GIF construction workers with yellow tape from the GeoCities era?

With a single URL parameter, the simulator turns into an interactive, animated “Under Construction” page for modern websites:

5. Try It Live & Play With Presets

You can run and customize the simulator right now without installing anything:

6. Frequently Asked Questions

Epilogue: What We Lost When Things Got Fast

Modern NVMe solid-state drives don’t need defragmentation. Today, files are scattered across billions of silicon gates in nanoseconds, invisible and silent.

Software today is faster, smoother, and vastly more powerful. But there was something deeply comforting about the old world.

You could see the entropy of your operating system. You could watch chaos turn into order, block by block, cluster by cluster, until the drive was a clean, contiguous wall of navy blue.

Sometimes, in an industry obsessed with milliseconds, it’s worth taking two minutes to just sit back, relax, and watch the blocks march.