VOGONS


First post, by Qwseyvnd

User metadata
Rank Newbie
Rank
Newbie

I have been searched around the internet without finding decemt explanation to run it. Any workaround?

Greeting from Øyvind Hagen.

Reply 1 of 7, by Zup

User metadata
Rank Oldbie
Rank
Oldbie

Some thoughts...
- FS95 - The page on PCGW states that running it using compatibility settings would be enough.
- FS98 - It uses some kind of CD protection, but PCGW doesn't list it.
- FS2k / CFS2 - I've got those and made it work in Windows 10. They use Safedisc, so they won't work unless you get a no CD patch. Also, they need to be properly installed (from CD or CD images)... I don't know what DLLs do they need, but they won't work if copied around.

I have traveled across the universe and through the years to find Her.
Sometimes going all the way is just a start...

I'm selling some stuff!

Reply 2 of 7, by Qwseyvnd

User metadata
Rank Newbie
Rank
Newbie

Ok, thank you for information about FS98 and I will trying nocd for FS2000.

Reply 3 of 7, by Torturephile

User metadata
Rank Newbie
Rank
Newbie

They don't work properly. FSfW95 will crash when changing the views, specially backwards. FS98 will not run at all. They don't like 64-bit Windows at all. Best bet is to run them on Windows 7 32-bit, virtualization or not. Later 32-bit Windows give FS98 issues displaying the 2D panel in hardware rendering, though software rendering will be fine.

Reply 4 of 7, by Lifeisstrange74

User metadata
Rank Newbie
Rank
Newbie
Torturephile wrote on 2025-02-06, 05:32:

They don't work properly. FSfW95 will crash when changing the views, specially backwards. FS98 will not run at all. They don't like 64-bit Windows at all. Best bet is to run them on Windows 7 32-bit, virtualization or not. Later 32-bit Windows give FS98 issues displaying the 2D panel in hardware rendering, though software rendering will be fine.

DDrawCompat should be able to fix that, it fixes the 2D panels freezing the display in CFS1.

Reply 5 of 7, by Qwseyvnd

User metadata
Rank Newbie
Rank
Newbie

Hmm... Okay.

Reply 6 of 7, by Torturephile

User metadata
Rank Newbie
Rank
Newbie

Pardon me for two things, for necroposting, and for using Claude Code to check the issue that causes both games to crash on Win64. Turns out it was the division handler in the games that Win64 does not properly deal with, giving an overflow exception in FS95 and a divide by zero one in FS98. For FS95, the handler is DIVTRAP.DLL which the main EXE interacts with, and FS98's handler is in the main EXE itself. For those of you interested, I got Claude to write a patcher for FS95 and FS98's EXEs. It shouldn't tamper with anything else as all I wanted was for these games to run, with their original quirks and all. If you patch FS98, I suggest using DDrawCompat so the game will render 2D panels properly on hardware rendering mode, along other goodies.

Reply 7 of 7, by Torturephile

User metadata
Rank Newbie
Rank
Newbie

Pardon me a third time. Since I couldn't edit my previous reply, sadly I have to make another.

I figured out a different way to get Flight Simulator 95 and 98 to run on Windows 10/11, unfortunately still with Claude. Instead of patching both games' EXEs like before, I got Claude to create a new DLL file, FSDIVFIX.DLL, that can be placed in the Modules folder in both games. It shouldn't mess with anything, and it works with the games' respective official patches.