FS2004 and Windows 10

[aeroart]

For all the grief I'm reading about on other flight sim websites about FS2004 and Windows 10, no one has mentioned dual-booting Windows 10 and an older version of Windows?

Have any of you tried that? If so, how did it work?

Art

[Al]

While I went thru a few problems when I first converted to Windows 10 everything was fixable after a little trial and error on my on machine. On a second windows 10 upgrade on another machine I had no problems at all so I think a lot depends on the condition of your Win7 or 8 machine when you upgrade it. If your starting out with a new windows 10 machine and a fresh install of FS2004 you shouldn't have any real issue if you follow the same protocol as you would installing in a win 7/8 machine.

Al

[dave mcqueen]

My 3 year old Sony 64 bit laptop came new with Windows 7. I upgraded to Windows 8 and then to 8.1. I've always left my main desktop computer with Windows 7. Just for fun the laptop was upgraded to Windows 10 this week --> quite easily too; Installed FS2004 from the 12 year old CDs for the first time on it - within the Program files X86 / Microsoft Games etc folder along with the FS9.1 upgrade and the No - CD fix.

I don't have any add-on scenery or aircraft with it, but everything worked perfectly, including the default Boeing jets which some say have caused CTDs. Still don't have enough courage to upgrade my main desktop with all the hard work done by others on it but I'll probably try it. Everything is backed up to an image file if it became necessary to roll back to Windows 7.

[aeroart]

That was encouraging. Thanks, Al and Dave.

[londonlad]

Computer came with windows 8. Upgradd to 8.1. Upgraded to W10 and everything except FS9 was OK. Could not load FS9 which is full of add-ons and calclassic scenery. Tried as much as my limited computer knowhow would allow. FS9 would try to start and then stop. Think it might have been the 4th CD requirement.

Hope someone solves this problem and shares because I really liked what I saw with W10.
br

[Tom/CalClassic]

I think you need to use the no-cd patch to avoid the CD 4 requirement.

[londonlad]

Thanks, Tom. Can you advise me on how to obtain the patch?
br

[Tom/CalClassic]

Send me a Private Message.

[leutnantwerner]

Hi, can be found at "flyawaysimulation.com".

Cheers
Bernie

[markg55]

Yes Aeroart, I just did a dual boot with a second hard drive last night. I am digging Windows 10 as a whole but not so much for my FSX and FS9.
Works beautifully so far. Of course a "Upgrade to Windows 10" is now on the Windows 7 drive. I will keep the Windows 7 drive strictly for Flight Simming. No added Bovine Fecal Matter whatsoever.

[aeroart]

markg55 -- Please check your Messages.

Art

[Randy_Cain]

Thank you, Dave and Aeroart.

That's very encouraging. I've been doing some homework and the more I hear about the details of the myths and legends, the less frightening the process becomes. I haven't heard of anyone that couldn't successfully roll back, if need be. Thank you all.

Yours,

[csmj]

Hello,

Sorry to come so late to this thread, I'm new here in this forum and am just reading through some older threads.  I had a recent experience with Win10 and wanted to post this in case it will be helpful to someone else. 

I've been running FS9 (with the No CD fix) on a separate USB harddrive on my main desktop which has Win7-32.  FS9 was originally installed on the USB drive, and all updates to it have been done there. The drive (a 400g Western Digital 2.5" Passport Drive) has only FS9 on it and remains unplugged until I want to fly.  I have another desktop with Win10-64 and decided to plug the USB drive into it and see if it would work.

The only problem was a black screen, which ALT+Enter fixed.  I also had to do these three things to get all my saved flights and settings working the same:

1) Copied from Win7 PC to Win10 PC this folder and all its files...
\Users\<username>\AppData\Roaming\Microsoft\FS9

2) Copied from Win7 PC to Win10 PC this folder and all its files...
\Users\<username>\Documents\Flight Simulator Files

3) Edited the SITUATION line in the fs9.cfg file that is in the FS9 folder. Changed the username
from the Win7 name to the Win10 name. In my case below, the Win7 name is cj7 and the Win10
name is cj4, so for me I just had to change that single number, but this will surely be
different for everyone. The last part of the line, in this case "Heading for Zion-7", is the
name of the last flight used.

SITUATION=C:\Users\cj7\Documents\Flight Simulator Files\Heading for Zion-7
SITUATION=C:\Users\cj4\Documents\Flight Simulator Files\Heading for Zion-7

Note that even though FS9 was not installed on the Win10 PC and there is nothing about FS9 in the Registry, it runs fine.

I think having the sim on a dedicated separate drive is a good thing because the drive only runs when I'm using it, so it's less likely to fail from being worn out.  And if the files mentioned above are regularly backed up, if the PC ever fails or is simply replaced, it's very easy to get FS9 running on the new machine without having to run a complete install and then all the updates, etc, which could be many hours of work.  I have several of these USB drives which I use for backups, and one of them has a backup of the FS9 drive.  So I think I'm pretty well covered.

I hope this is helpful,
Clayton

[coscri]

To run FS 2004 , alias FS9 under windows 10 you need to put run in emulation windows XP for FS2004
Resolution screen and in fs2004 seems neded to be set at 1024 x 768
All seems to work and even alt return

[zswobbie1]

No, no need to run in emulation mode at all. If you have upgraded to Windows 10, make sure your graphic drivers are updated & you can use any resolution. If you are having any kind of problem, run in windows mode, turn down UAC & try running as ADMIN.