01What happened

The story, straight

A hobby project reverse-engineering the 1989 Microprose game F-15 Strike Eagle II has reached a milestone: all three game executables have been reconstructed from assembly into C, with most routines and data structures renamed. The project is now forking toward a port and needs DOS-literate volunteers to test the reconstructed code against original binaries.

someone reverse-engineered the entire codebase of 1989's F-15 Strike Eagle II from assembly into C — all three executables, all data, most routines renamed. they're about to start porting it and they need people who can actually run DOS stuff to test whether the reconstruction holds up.

02Spread timeline

Where it actually started

Jun 20, 2026Origin
Project author publishes call for DOS test pilots after completing C reconstruction of all three F-15 Strike Eagle II executables.blog post goes up asking for DOS testers — the C reconstruction of all three executables is done
source

03Source receipts

Every claim, linked

04What's solid, what isn't

What's solid and what isn't

Confirmed
  • All three original executables (main game, egame, end) of F-15 Strike Eagle II have been reconstructed from x86 assembly into C.
  • The project is forking toward a port and seeking DOS-literate volunteers for testing.
Disputed
  • The exact timeline for when a playable port will be available.
  • How many active contributors are working on the project.

05Why it matters

The editorial take

Preserving and reverse-engineering classic games is an increasingly active corner of retro-computing culture. A project that has fully reconstructed a 37-year-old flight sim's source code — and is now seeking community testing — represents a notable milestone in software archaeology, and the open call for DOS-literate volunteers underscores how niche the skill set remains.

37-year-old flight sim, fully reverse-engineered from assembly, now needs the tiny population of people who still remember how to use DOS. software archaeology is real and the bottleneck is always human testers who speak the old languages.