# Flight Simulator 95/98 finally running on 64-bit Windows, patched by Claude Code — retained record

> Retained reddit record from reddit:ClaudeAI.

Canonical: https://highsignal.app/data/records/f66991ed9a4127f9

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:ClaudeAI)  published 2026-10-25 07:46 ingested 2026-10-26 02:36

[original source ↗](https://www.reddit.com/r/ClaudeAI/comments/1xew9ma/flight_simulator_9598_finally_running_on_64bit/)

## retained text



```
Howdy there. I'm a lifelong fan of *Flight Simulator* who doesn't let go of old stuff. Since I've seen people using Claude Code to come up with some crazy mods that mash two entirely unrelated games together without somehow breaking, I figured I'd give Claude Code two old games, *FS95* and *FS98*, which don't run on 64-bit Windows, to figure out why they won't. Something much simpler, right?

I knew for about ten years that both games crash out of divide by zero exceptions that occur with their handling of their 2D and 3D windows, so I suspected that the issue had to do with two of both games' DLLs, namely WINDOW.DLL and G3D.DLL. I tried running both games with DxWnd with the "handle exceptions" box ticked, but the games were unplayable with extremely glitchy rendering. A Reddit user named u/rozniak [wrote some interesting stuff](https://www.reddit.com/r/MicrosoftFlightSim/comments/tjje3q/comment/i4q1ddx/) about it years ago. Anyway, I got Claude to patch the aforementioned DLLs for *FS95* and it worked, but once I was debugging *FS98*, it discovered that it was the game's EXE file that was the culprit, not the DLLs. It used its finding to trace down the same issue in *FS95*'s EXE so its original DLLs could be left alone.

Here's what Claude stated:

"FLTSIM98.EXE contains the game's routine Microsoft wrote to handle these faulting divisions. When a division fails, it reads the instruction from memory, puts a capped result in the right registers, and skips past the instruction. The game runs everything under it with `__try`/`__except`, which is exactly the mechanism 64-bit Windows can’t reach inside a window callback.

Windows has a second kind of exception handler, the vectored handler, which runs before that callback boundary matters. The game’s routine has exactly the signature such a handler needs. So the patch adds 86 bytes at the program’s entry point that register the routine with `AddVectoredExceptionHandler` and then start the game normally. One patch covers every division with exactly the results the game was written for." To add to this, *FS95* has its routine located on its DIVTRAP.DLL, not on its EXE like *FS98* does. With that said, now both games run on 64-bit Windows with no issue based on my testing.

Here's the [MediaFire download](https://www.mediafire.com/file/jk0v86lv407hs3s/FS95_and_FS98_Win64_patcher.zip/file) of the EXE patcher, because I don't feel like supplying the EXEs myself. Alternatively, here's the [GitHub link](https://github.com/Torturephile/FS95-and-FS98-Win64-patcher/tree/main) since someone requested it. You still need to install the games, either from your CDs or from the high seas. Read the readme file included for instructions, please. Also, please comment about any issues.

Edit: the patch was redone so that it only handles the division faults, so if the game crashes for non-division faults, Windows will handle it. The assembly code is now included as well. Sorry mods for updating the text again.
```



document fetched 2026-10-26 00:22 · canonical https://reddit.com/r/ClaudeAI/comments/1xew9ma/flight_simulator_9598_finally_running_on_64bit
