After installing a new joystick - SAITEK Cyborg 3D Force plus XP Updated drivers; disaster struck! First my Nvidea GE4 Ti4200 was corrupted - Updated Drivers cured that, but since then I have been unable to Boot up FS2004; it refuses to go beyond the opening window e.g. DC3 and Flight Simulator 2004 - the window just freezes, the first time this happened an error window popped up asking for a MFC70.dll file - got that from Disc 1 - since then just refuses to boot! I've tried re-installing twice, no dice; defragged, nothing works.I cannot think of anything else to try; I'm jest hoping someone out there can help? Btw, I've tried looking on the MS FS2004 Website and Knowledge Base - I seemed to be chasing my tail there :)KenSomerset, England

If you have XP, try to restore your system to a point prior to installation of the joystick. Sounds like a classic scenario--the updated driver install went south, and overwrote some critical MSFS components. Anytime one of the MFC dll's is involved, there's also the chance that MSFS is picking up a customized copy used by your controller update. Those dll's, in their standard form, are required to allow most programs compiled under Microsoft's devel tools to work properly. Some vendors modified them...and issues arise if programs like MSFS are calling functions which aren't present in the vendors copy.One quick trick to try--restore everything that is supposed to be in FS9's root folder from the CD. You have an edge since you know how to find and restore the files required.... There's some DLL's that go with the one mentioned, and they all have to be in synch... -John

Hi John, thanks for your quick reply - I'll go for the FS9 Root .dll restore. I omitted to mention that I did try the System Restore - I thought that would repair the Nvidia Drivers; no deal though.Ken

John, I replaced all the .dll files into the FS9 Root directory, no luck though. Another thing I remembered is that shortly after the MFC70.dll Error message came up; another one popped up mentioning 'Language.dll'? - I think I'll replace that one as well.Only other point to mention is that I checked the WindowsSystem32 Folder and found that there are some MFC**.dlls there e.g. MFC42.dll; is it worth adding the .dll's from Disc 1 in that Folder? or is that a no! no! ?I've run out of ideas completely now ((:Ken

Don't try to replace the dll's in the WindowsSystem32 folder...that's a rather big no no, as it can pretty much wreck many of your installed applications.Replace all of the files--not just the dll's, that reside in the root folder of FS9.Also it isn't a bad idea to compare your modules folder against the module dll's on the CD. There's always a chance a third party module could be dropped in there.If you reinstalled by the best method--i.e., you removed all files and folders related to FS9, likely your controller has loaded some driver conflicting with FS9. But sometimes simmers reinstall by loading FS9 on top of an existing installation. That may not fix the problem.Sorry to say, it's very hard to troubleshoot via web.... If you want to try a back to basics approach, try what I suggested first regarding replacing all the root entries for FS9, perhaps followed by a reinstall of DirectX 9..... Also, do a search for the dll mentioned in the error everywhere on your hard drive. See if there are dupes of that one...

A reinstall, standard method, does not remove the FS9.cfg which is stored outside of the FS folder structure. As you have reinstalled, but have yet to start FS, you should NOT have a FS9.cfg in your system - it is created on Sim startup under the My Documents structure on your C: drive, but some way down the sub-folders. So simply search the system for FS9.cfg (including `search hidden files and folders`, it's hidden by default), and delete it. Then reboot FS. Then there should be no need to go messing about with .dll files or any such nonsense, which has a 90% chance of only making things worse IMHO. The fact that it gets to the boot screen tells me there's nothing wrong with the dll files.Allcott

JohnCi and Allcott, gentlemen thank you both for your input re my disaster. The great news is I am now back in action!! :) ; FS9 loaded perfectly after another 'clean' install - the clincher was due to the download of DirectX 9.0b - I watched directx install; it was flinging .dll files etc. everywhere :) so I new I was 'on a winner' as they say hereabouts.I appreciate more than I say, your comments plus the fact I felt I was not fighting this problem alone; that helps a lot; I really was stuck!In the past I have cursed FS9 for not being so nice to 'fly' in; but I can say, with feeling, it is a million times worse without it!!Only problem I have now is to decide whether this Saitek Cyborb 3D Force stays; or goes back to the Store am tomorrow, I have now found that others have also experienced trouble with this Joystick.Thanks once again for your inspiration.KenSomerset, England

Did reinstalling FS9 over your current installation A) remove your settings :( cause you to have to reinstall all your aircraft?

Reinstalling only replaces amended default files - all other installed files remain in place. So if you have amended sound files for the default aircraft they will be overwritten, but if you have aftermarket aircraft with their own folders, they will not.Settings are controlled by the FS9.cfg. Along with everythng else in those folders outside of the main FS2004 file strcuture, they will be left alone so your settings will stay where they were.It's one good reason for deleting the .cfg file when installing new drivers, for example, although you can get by by just removing the graphic card information from the .cfg file, leaving all your bespoke key assignments and terrain and texture mods in place.Allcott

Hi GiZBUG,One of the key items Allcott mentioned in reply to my cries for help was to ensure I removed 'all' copies of the FS9.cfg file - in fact I found no less than 3 fs9.cfg files on my system? how come? I don't know but I made sure they were all deleted before re-install; so some settings had to be Edited after re-install; all add-on aircraft were untouched, possibly the default aircraft were overwritten, I'm not sure, I rarely use them. But following Allcott advice, including installing Directx 9b cured my problems with the Saitek Cyborg Force joystick; the Yoke has long gone :) I find the Saitek to be perfect for me.Hope this helps.Ken