Skip to content
agentusehub

Reverse-engineer a 1997 PC game and make it run on modern hardware

Claude Code got an old DirectX game running on modern hardware, decompiled much of it, built a headless parallel runner, and now writes full level guides with screenshots.

Time saved
Not reported
Setup time
Not reported
Running cost
Not reported
Cost range
Not reported

Use case overview

Claude Code got an old DirectX game running on modern hardware, decompiled much of it, built a headless parallel runner, and now writes full level guides with screenshots.

Reported experience

  1. What they did

    Claude Code got the 1997 game running on modern hardware in about 30 minutes, setting up a basic reverse-engineering environment along the way. Over further iterations it decompiled most of the game. At the user's request it extended a shimmed DirectX DLL to run headlessly on a Windows Private Desktop, allowing parallel instances. It mapped memory addresses and scripts, and the user nudged it and checked its work.

  2. How it went

    Claude now writes full level guides with decent screenshots of key moments, zero-shot. The user's goal of making the game look as it did in their memory is still in progress.

  3. Worth knowing

    Ask the agent to build helper tools that expose how the game is built, so you can verify its work and steer it. Headless runs also avoid computer-use sessions taking over your PC.

Example prompts

Try with Claude Code
I have an old Windows game from [year] installed in [folder path] that won't run on my modern computer. Figure out why it fails, get it running (compatibility layers or wrappers are fine), and tell me exactly what you changed. When it launches and reaches the main menu, stop and show me how to start it myself. Don't delete or overwrite any original game files; work on a copy.
Coding · Advanced
  1. Write migration plan
  2. Agent edits in batches
  3. Tests per batch

Ship a 40-file refactor with a coding agent

Plan, execute and review a cross-cutting refactor in small batches, with Claude Code making the edits and GitHub Copilot reviewing each PR.

Claude Code · GitHub Copilot
Coding · Advanced
  1. Run coverage
  2. Pick 3 riskiest files
  3. Write + run tests

Generate missing unit tests for untested modules

Claude Code reads your coverage report, picks the riskiest untested modules and writes unit tests that pass, one small PR at a time.

Claude Code · GitHub Copilot · Slack