For some reason now, I can't get FS to start. The splash screen comes up, but after a few seconds, it goes off, and FS never starts. The only thing I changed is I updated my video card drivers to the Forceware 65.62. Anybody have any ideas??Tim

Hi Tim,Are you running ActiveRadar by any chance? The reason I ask, is because I had the same problem. Renaming the ActiveRadar DLL to *.LLD cured the problem, which was due to some corrupt weather data.In other words: You can try to disable (just rename them to something else than DLL) 3rd party DLL's in the MODULES folder.Other than that, you might want to delete fs9.cfg and let FS rebuild it. You can also try to move 'Previous Flight' files to somewhere safe.HTH & BRGDSSven Sorensen, EKCH

I do use Active Radar and I tried your tip, but it still simply closes down after the splash screen is up for a few seconds. It's getting really frustrating. I've also tried deleting the fs9.cfg but it still isn't working. Any other ideas?Thanks,Tim

If you have XP, try doing a system restore to the point where you installed the new drivers. When you installed the drivers, did you disable your virus scanner? Maybe the drivers were corrupted during the install? Try also the latest drivers 61.77,the 56.72's work very well too, I'm still using them, although I have a pretty new card. After you've finished, try deleting the FS9 cfg again, and let it build a new one recognising the new drivers. Hope this helpsBestGrahame (EDHL)

I rollbacked to the last drivers that worked, and deleted the FS9.cfg but still no luck. I don't use system restore, so I can't do that. The only thing I can think of is that I was messing around witht he virtual page file and I tried setting it to no page file, because someone told me that might help performance. I tried putting it back to where it was, but still no luck...

The looks like you have a reinstallation coming. Why would you switch off the ONE thing that could have got you out of this mess?The 65.xx drivers are highly beta, modded drivers that are only for Quadro cards as released - they don't even contain an NV4_disp.inf. FS will not boot with these drivers according to several posts over at www.guru3d.com, but in each case they were able to roll back to the previous driver set with absolutely no problem. As happened with me too.In future, use System Restore if you want to play with beta drivers or your system.Hope you get everything reinstalled OK, but you might try using driver cleaner 3 after uninstalling the drivers you have now, then installing the 61.77's again. You might also safe boot Windows, then try using `last known good configuration` in the hope that it might work.And for Gods' sake leave the page file alone.Allcott

Deleted origianl advice as I just saw you've already tried that.I'd go with Driver cleaner as mentioned above.Don't forget to remove the old drivers in safe mode.Also if you have XP but not SP2 try installing that. A lot of the newer drivers need SP2 for certain games to run.I had a problem with FS2004 crashing after about ten minutes when I installed the 61.77 drivers, and since I added SP2 I haven't crashed once.It's 270mb, but its worth a try if your planning to get SP2 anyway.

OK, I've been having ForceWare driver problems as well. I would suggest testing different resolutions in your NVIDIA menu. If, when testing resolutions, you get a black screen, then that resolution doesn't work for your setup and I think it will shut you down if you try it that way. Another thing to check is the screen refresh rate. Mine defaults to 200! That's way too high. When I adjusted it to a minimum of 60, all resolutions worked just fine.Don't know if this will help, but I had the same probelem and this seemed to fix it right after the driver install. Just give it a shot before the agony of a re-install. PS Don't forget to turn off all virus scan programs and completely delete the previous NVIDIA driver before installing another driver. Good luck! :>

Hi I had a similar problem with the spash screen comming up and then freezing.I finally figured that the FS9.exe file was corrupt and I replaced it with the original from the FS9 disk one. This fixed the problem.Hope this helps.Arnold