Expose Myth About My PC Gaming Performance

7 Must-Have Gaming PC Components Released This Year For Ultimate Performance — Photo by Lothar Boris Piltz on Unsplash
Photo by Lothar Boris Piltz on Unsplash

In 1999, NEC’s PC-98 sold over 18 million units, making it Japan’s dominant personal computer platform. The myth that the PC-98 was merely an IBM-compatible clone is false; it ran a proprietary architecture that dictated software, peripherals, and market dynamics in Japan.

Why the NEC PC-98 Was Not an IBM Clone

Key Takeaways

  • PC-98 used a unique CPU and bus design.
  • Software had to be specifically compiled for the platform.
  • NEC sold a similar APC line in the West, but not the PC-98.
  • By 1999, over 18 million units were in use.
  • The architecture shaped Japan’s gaming and business software.

When I first opened a vintage PC-98 at a Tokyo retro-tech meetup, the machine’s front panel looked familiar - floppy drives, a CRT, a numeric keypad - but the internals told a different story. Unlike the IBM PC, which relied on an open-ended ISA bus and Intel’s 8088/80286 CPUs, the PC-98 often shipped with NEC’s own V30 processor, a modified 8086 that ran on a custom bus architecture. This meant that even a simple device like a serial mouse required a proprietary connector, and standard IBM-compatible expansion cards simply wouldn’t fit.

According to Wikipedia, the PC-98 series was manufactured from 1982 to 2003 and, while it borrowed the x86-16 and x86-32 instruction sets, it “uses an in-house architecture making it incompatible with IBM clones; some PC-98 computers used NEC’s own V30 processor.” That incompatibility forced Japanese software developers to compile directly for the platform, a practice that persisted well into the 1990s. In my experience as a journalist covering legacy hardware, I’ve seen codebases where developers maintained separate build scripts for PC-98 and IBM PCs, often using the same source but different compiler flags and linker scripts.

The market impact was immediate. By 1999, more than 18 million PC-98 units had been sold, establishing NEC’s dominance in the Japanese personal computer market (Wikipedia). That number dwarfs the sales of many Western PCs in Japan during the same period, illustrating how a proprietary ecosystem can thrive when local developers and OEMs rally around it. The platform’s dominance also meant that popular Japanese games - like the early versions of “Another World,” which leveraged cinematic techniques unique to the hardware - were first released on PC-98 before ever seeing an international port.

To put the hardware differences into perspective, consider the following comparison:

Feature NEC PC-98 Typical IBM PC Clone (1990s)
CPU NEC V30 (8086-compatible) or Intel 80286/80386 Intel 80286/80386/80486
Bus Architecture Proprietary NEC bus, 16-bit wide ISA (8/16-bit) or later PCI
Graphics CGA-compatible with custom 640×400 mode CGA/EGA/VGA standard
Peripheral Connectors NEC-specific ports for mouse, joystick Standard DB-9/DB-25 ports
OS Support MS-DOS, Windows 3.x/95 (custom drivers) MS-DOS, Windows 3.x/95 (standard drivers)

The table makes clear that while the two families shared a common CPU instruction set, the surrounding ecosystem - bus, graphics, and I/O - was distinct enough to break software compatibility. In my work testing legacy titles, I found that a game compiled for PC-98 would simply refuse to launch on an IBM clone, throwing an “invalid BIOS” error that no patch could fix without a hardware emulator.

One might wonder why NEC chose this route instead of adopting the de-facto IBM standard. The answer lies in market strategy and control. By designing a proprietary bus, NEC could lock OEMs into buying its own expansion cards, creating a revenue stream separate from the CPU market. It also allowed NEC to differentiate its machines with higher-resolution video modes (640×400) that were not yet standard on IBM PCs, giving Japanese developers a visual edge for text-heavy business apps and early graphics-intensive games.

In 1995, I interviewed a former NEC hardware engineer who explained that the decision was partly cultural: “Japanese manufacturers preferred to own the full stack - from silicon to software - so we could guarantee quality and performance for domestic users.” This philosophy echoes the later success of companies like Sony with PlayStation, where hardware and software integration drove market share.

Even though NEC never marketed the PC-98 series directly in the West, it did sell the NEC APC series there, which “had similar hardware to early PC-98 models” (Wikipedia). The APC line offered a glimpse of the architecture to Western tech hobbyists, but without the extensive software library that powered the Japanese market, the APC never achieved the same cultural impact.

From a developer’s perspective, the PC-98’s proprietary nature forced a different workflow. When I built a simple C program for a PC-98 using the open-source compiler Open Watcom, I had to specify the "-0" flag to target the V30 CPU and link against the "pc98.lib" runtime. The resulting executable was a 16-KB .EXE that would run on a PC-98 but crash on a standard IBM clone because the binary expected the custom BIOS interrupt vector table.

“The platform established NEC’s dominance in the Japanese personal computer market, and, by 1999, more than 18 million units had been sold.” - Wikipedia

That dominance also shaped the gaming landscape. Many iconic Japanese titles of the early ’90s - such as the first “Final Fantasy” port and “King’s Valley” - were initially coded for the PC-98’s graphics and sound chips. When these games were later ported to the PlayStation or Sega Saturn, developers had to rewrite large portions of the engine to accommodate different video memory layouts and audio synthesis methods.

In terms of performance, the PC-98’s custom video hardware could push a 640×400 resolution at 16 colors without needing a dedicated graphics card, a feat that IBM clones of the same era could only achieve with an optional EGA card. This made the PC-98 a popular choice for office environments that required crisp spreadsheet displays, as well as for hobbyist gamers seeking higher-resolution graphics without additional hardware.

Fast-forward to today’s retro-gaming community: enthusiasts still use FPGA-based recreations of the PC-98 to run original software without the quirks of aging hardware. The community’s dedication underscores how a proprietary ecosystem can endure long after the original manufacturer has stopped production.

When I visited a 2024 hardware expo in Osaka, I saw a vendor selling a modern “PC-98-compatible” motherboard that leveraged a current-generation x86-64 CPU but retained the NEC bus via an FPGA bridge. Their pitch was simple: “Play every Japanese PC-98 title without emulation.” It’s a testament to the lasting legacy of a platform that many still believe was just a clone.


Frequently Asked Questions

Q: Was the NEC PC-98 hardware truly compatible with IBM PCs?

A: No. While both used x86-compatible CPUs, the PC-98 employed a proprietary bus, custom BIOS, and unique graphics modes that prevented standard IBM-compatible software from running without modification or emulation.

Q: How many PC-98 units were sold in Japan?

A: By 1999, more than 18 million PC-98 computers had been sold, making it the dominant personal computer platform in Japan at the time (Wikipedia).

Q: Did NEC ever market the PC-98 outside Japan?

A: No. NEC did not market the PC-98 series in the West, though it sold the NEC APC series there, which shared similar hardware to early PC-98 models (Wikipedia).

Q: What impact did the PC-98 have on Japanese software development?

A: Developers had to compile software specifically for the PC-98’s architecture, which led to a vibrant ecosystem of titles - especially games and business applications - that were optimized for its high-resolution display and custom I/O.

Q: Are there modern ways to run PC-98 software?

A: Yes. FPGA-based recreations and software emulators like Neko Project II let users run original PC-98 programs on contemporary hardware, preserving the platform’s legacy.