The Unix Revolution Begins

The shock of losing a document you had been working on—especially with the American Dream deadline breathing down your neck—could linger for a very long time.

“In truth, Android Alpha was never part of ID Group’s official development roadmap. It began as a DOS-compatible system capable of running ID Office stably, with the Ribbon Interface layered on top. The enthusiastic support from PC users allowed us to release multiple version patches, eventually bringing it all the way to the final release.”

To be exact, it had all started because of a phone call from Microsoft. When the company openly threatened compatibility issues with DOS 4.0, Android Alpha was born in a blaze of defiance. Of course Yoo Jae-won had always planned to create a proper graphical operating system, but without Microsoft’s provocation the timetable would have stretched far beyond its current date.

“The final patch maximized stability and security, yet it was impossible to eradicate the underlying instability at its root.”

Yoo Jae-won’s expression turned solemn.

“As everyone here knows, the cause lies in DOS’s fundamental limitations. That is why I made a critical decision. Let us abandon DOS. Yes—that is correct. What I am about to show you today is a completely new operating system, rebuilt from zero.”

The moment his words ended, thunderous applause erupted. The people gathered in this hall loved PCs and made their living in PC-related businesses. They understood DOS’s limitations better than anyone. They also knew it had to be discarded. Yet the immense burden of breaking compatibility with countless existing applications had stopped every one of them.

Yoo Jae-won was different. Having swallowed Microsoft whole, the life or death of DOS now rested entirely in his hands.

Because of this, endless speculation had swirled before the Android 1.0 preview appeared. Opinion had split between those who insisted the core would be completely rebuilt and those who believed the DOS framework would continue. Once the preview leaked to the public, however, every voice claiming DOS would survive vanished overnight.

The screen transformed dramatically as the Android 1.0 boot sequence appeared. The tin-can robot from Alpha had evolved into a sleek twenty-first-century android.

“Unix-level stability, performance that devotes every resource of the PC to the user, and a rich library of applications. Android 1.0 will guide you into a new world of personal computing unlike anything you have experienced before.”

As Yoo Jae-won spoke, the demonstration screen shifted dynamically. When he mentioned stability, it displayed a PC that had remained powered on for an entire month. When he spoke of performance, multiple IDW documents opened simultaneously. When he reached applications, a cascade of titles appeared—ID Technology and ID Software products alongside diverse programs from partners such as Electronic Arts and other developers collaborating with ID Group.

“In Korea we have a proverb: seeing once is better than hearing a hundred times. So from this moment on, I will demonstrate every aspect of Android 1.0 by using the computer myself. President Remington!”

Once again Yoo Jae-won called for him. True to form, Remington appeared on stage pushing a lavish cart—the same kind used for room service in luxury hotels. Something large ‍‍‌‌⁠​​⁠‌​​‍​​‍​‌​⁠‍‌‍⁠⁠‌⁠‌‍‌‍‌‌‌‍⁠​‌​‌​‌‍‌‌‌⁠‍​​‌‍⁠‌‌⁠⁠rested upon it, concealed beneath white velvet. It would have made a delightful picture if Remington had worn a maid uniform, but he had politely yet firmly refused.

Dressed in his usual roomy suit, Remington pulled the cart forward, exchanged a brief handshake with Yoo Jae-won, and withdrew behind the stage.

“Ah, yes—one more thing. For this completely new Android 1.0, Sambo TriGem has produced a new Egg PC.”

Yoo Jae-won swept the white velvet away in one dramatic motion. Pre-positioned spotlights converged on the cart, fully revealing the new machine to the audience.

A collective gasp of admiration swept the hall. Many elements had changed, yet the unmistakable lineage of the Egg PC design remained. The sophisticated aluminum-alloy case with its subtle polycarbonate accents made the word “refined” feel utterly perfect.

“Introducing the new Egg PC—the New Egg. You may now order it from ID Flagship Stores and TriGem dealerships worldwide. Naturally, the New Egg ships with Android 1.0 pre-installed. I will now demonstrate the entire process—from installation to daily use—on this very machine.”

Yoo Jae-won’s live demonstration began in earnest.

“As you can see, the New Egg currently has the entirely incompatible MS-DOS 4.0 installed. Unfortunately, ID Group has no plans to continue supporting the DOS architecture. Support for version 4.0 therefore ends this year, and we strongly recommend that users migrate to Android 1.0.”

Yoo Jae-won was openly mocking the ill-fated MS-DOS 4.0. No one remained in a position to object. Moreover, Chairman Gates’ impatience had left the OS riddled with incomplete features, earning far more criticism than praise.

“Android 1.0 is distributed on twelve 3.5-inch diskettes. A full installation occupying every function requires twenty-six megabytes of hard-disk space.”

Compared to DOS 4.0’s single diskette, the capacity was enormous. High-resolution graphics, high-quality sound resources, and numerous bundled applications had driven the size upward. Users with limited hard-drive space would certainly exist; therefore Yoo Jae-won had included an option to exclude non-essential components such as bundled programs and sound files. Installing only the core files required roughly ten megabytes.

“We are not limited to the diskette version.”

Yoo Jae-won held up a gleaming compact disc. Although CDs were still primarily associated with music, the technology for storing data was already mature. One of the New Egg’s options allowed the floppy drive to be replaced with a CD-ROM.

“For a faster installation, I will use the CD here on stage.”

After his explanation, Yoo Jae-won inserted the disc and launched the installer. Running the INSTALL file from the CD-ROM produced a brief text message, followed by an instruction to reboot.

Android 1.0 was a pure Unix-based operating system except for the INSTALL file itself. Just as DOS programs could not run natively under Android 1.0, the Android installer could not execute under DOS. The solution was to change the boot loader, reboot, and then run the installation program.

‍‍‌‌⁠​​⁠‌​​‍​​‍​‌​⁠‍‌‍⁠⁠‌⁠‌‍‌‍‌‌‌‍⁠​‌​‌​‌‍‌‌‌⁠‍​​‌‍⁠‌‌⁠⁠

The early creation of a robust bootloader proved invaluable here. Even if the computer lost power during installation, the system could return to the original DOS or Android Alpha. Multi-booting was precisely what had allowed Android 1.0 to be redesigned as a complete Unix system. Should a beloved game lack an Android 1.0 patch because its developer had gone out of business, users could simply boot into DOS or Alpha and run it without issue.

The reboot completed, revealing a radically different interface. Where the old DOS screen had been nothing but text, nearly every element was now graphical. The installation program had loaded.

Yoo Jae-won selected the full-installation option and clicked the button. The entire process took barely five minutes. The CD-ROM’s read speed was fast, and there was no need to swap disks. The only slight delay came from hardware detection and driver matching.

The audience’s reaction was delightful. Every time the progress percentage increased, laughter and gasps of wonder filled the hall. ID Technology had never relied on a simple bar graph for progress—not since Android Alpha. This time the Android robot delivered another charming performance.

The little robot buried itself in a pile of diskettes, rummaging busily. At every ten-percent milestone it performed a humorous animation. It discovered a shiny new robot arm among the disks, detached its old worn limb, and attached the upgraded one. As progress climbed, it continued swapping components. At one point it even removed its smoking, outdated engine and installed a glowing, futuristic power core in its place.

When installation reached one hundred percent, the tin-can robot from Android Alpha had transformed into a sleek, twenty-first-century android. The upgrade was depicted through a simple yet effective animation. The motion resources were not high-resolution—CD-ROM users might have received richer visuals—but with so ‍‍‌‌⁠​​⁠‌​​‍​​‍​‌​⁠‍‌‍⁠⁠‌⁠‌‍‌‍‌‌‌‍⁠​‌​‌​‌‍‌‌‌⁠‍​​‌‍⁠‌‌⁠⁠many diskette users still active, the sequence had been optimized to roughly two hundred kilobytes.

Upon completion, the reborn android displayed a message that reboot would begin in ten seconds.

“We are now entering the reboot phase,” Yoo Jae-won announced. “And I declare here and now that once you install Android 1.0, you will never need to reboot again—unless you replace hardware or suffer a sudden power failure. Even if an application crashes, the problem will remain isolated to that program. It will not affect the Android 1.0 system in the slightest.”

Yoo Jae-won radiated absolute confidence in the new OS’s stability. He had reduced unavoidable reboots to the absolute minimum. The guiding principle behind this design was simple: never trust the user. Core system files essential to operation could not be touched. Expert users might find it restrictive, but the system had been built so that even beginners could use it safely. Those with the skill to create their own programs would encounter no significant inconvenience.

The reboot finished almost instantly. The operating-system loading screen flashed by in the blink of an eye. The New Egg on stage was perfectly optimized, yet even on identical hardware Android 1.0 loaded noticeably faster than Alpha.

After loading, the desktop should have appeared immediately. This time, however, something special happened. A deep, resonant sound effect played as a horizontal blue gradient swept across the screen. White characters from countless languages began to cascade downward.

English and Korean appeared first, followed by European Roman letters and Arabic script. Even Japanese kana and Chinese characters joined the flow. At first the glyphs fell in chaotic disorder, but they gradually organized themselves into meaning.

“The characters you just saw falling are all fully supported in Android 1.0.”

A world map unfolded on screen, followed by a country-selection menu. The prompt asked users to choose their default language—in English, of course. Yoo Jae-won selected Korea. Instantly every message and system string switched to Korean.

He continued demonstrating, cycling through French, Arabic, Japanese, and other languages to show how the character sets changed on the fly.

The reaction was… lukewarm.

Each time the character set changed, the audience offered polite “oohs” of mild interest, but the energy never exploded. Even the background music seemed to grow quieter. The multilingual input and language support had been intended as a show-stopping feature, yet the response felt flat.

Yoo Jae-won quickly regained his composure. Most of the people in the hall were American. They had never struggled with computers that failed to support their native tongue. He was certain the reaction in the Middle East, Japan, and China—regions where native-language computing remained difficult—would be far more enthusiastic.

Besides, he still held several secret weapons in reserve. The real show was only beginning.