Back on the 12th my PC died on me (most likely a motherboard failure as when I turned it on I got no video signal nor any beep from the PC speaker) and needed to be replaced. I've now got most of my software installed on the new PC, but FS2004 still isn't working properly.
I installed FS2004 from my CDs to D:\Flight\FS9, followed by the 9.1 update and the NO-CD crack (as is required on Windows 10 due to its lack of secdrv.sys support: the same was true on the now-dead PC).
While I can start up FS2004 and load a flight, the 2D instrument panel is completely useless as the panel gauges and switches won't update (even on the default Cessna 172), except when a panel window is resized, closed then re-opened, or at the moment when FS2004 is switched between "Windowed" and "Full Screen" modes. Gauges on the virtual cockpit (in planes that have one of course) seem to be working normally.
Does anyone here have any idea what could have caused this problem, or even how I could investigate what's causing it? I'm desperate to get FS2004 working properly again so that I can re-start some development work. (I've also got a problem with badly aliased gauges in my FSX installation, but the FS2004 issue is more pressing for the time being...)
Thanks,
George
I installed FS2004 from my CDs to D:\Flight\FS9, followed by the 9.1 update and the NO-CD crack (as is required on Windows 10 due to its lack of secdrv.sys support: the same was true on the now-dead PC).
While I can start up FS2004 and load a flight, the 2D instrument panel is completely useless as the panel gauges and switches won't update (even on the default Cessna 172), except when a panel window is resized, closed then re-opened, or at the moment when FS2004 is switched between "Windowed" and "Full Screen" modes. Gauges on the virtual cockpit (in planes that have one of course) seem to be working normally.
Does anyone here have any idea what could have caused this problem, or even how I could investigate what's causing it? I'm desperate to get FS2004 working properly again so that I can re-start some development work. (I've also got a problem with badly aliased gauges in my FSX installation, but the FS2004 issue is more pressing for the time being...)
Thanks,
George
