Archived

This topic is now archived and is closed to further replies.

Scott Miller

Problems with FS2004 after migrating WinXP install on to Win7 sys

Recommended Posts

Following the advice in the Win 7 forum thread "Migrating FS9 WinXP 32-bit to Win7 64-bit" I got FS2004 up and running over the weekend on the new system.  However,I've encountered a few problems.  One appeared to resolve itself when I copied my WinXP FS2004 install backup from an external drive.  Two are minor and can be ignored.  Two involving A/C can be delt with by going with same the planes by other manufacturers (but I'd rather not if there is a way to fix the problems with them).  Two other problems came with the WinXP install when I copied it to the Win7 system.  Finally two I consider major enough I'll dump the Win7 system and go back to the WinXP system if they can't be resolved somehow...Here they are (I'm saving the major ones till the very end):

 

1)  When I first installed FS9 on the new system I did reinstall all addons such as Ultimate Traffic and AcktiveSky wxRE and some scenery addons like my MegaScenery or FS Global 2005 (haven't got around to upgrading to a new system yet) and only the aircraft addons I have on CD-ROM so they would be properly enterd in the add/delete software list.  The only freeware aircraft I re-installed was the Porject Fokker F28.  When I tried to load one and switched to the panel view FS9 crashed.  This problem went away on its own after I renamed the FS9 folder "WIN7FS9" and copied my XP F2004 install from the  external drive.   Icopied the FS9.cfg from the XP system, too, and ran the 4gb_patch last.

 

2) On both the Just Flight 757 Professional and 777 Professional all the flight/engine display panels, FMC and the electronic check Flight window (not the FS checkflight window) are either completely blank or devoid of any numbers or letters even though the engines are running (unless I'm forgetting to do something here.  Its possible, I haven't flown anything for a couple of years!).  The engines PFD display have the power scale outline but thats all.  I also have the QualityWings 757 which doesn't not suffer from this problem (which didn't go away when I copied the XP install from the external drive) as well as the Wilco 777.  I hate to give up the JF planes however mainly because I have dozens of liveries for them I hate to lose (and it'd be money down the drain)!

 

3)  At least on one occasion the cursor arrow turned black (later it turned back to white).  This is one of the issues that can be ignored.

 

4) The other issue that can be ignored is a flikering I get on the Kuhn Garmin 530 installed on a JCA 717 with ValueJet livery that happens ONLY on this particular plane and livery ONLY at KSAN (US Airports 1 scenery).  No problem with the 530 with any other plane including the JCA 717 at this airport or at any other airport (so far).  Flickering is minmal when the 530 is turned on so I can live with it.  Worst comes to worst I can just not use the 530 with the ValueJet JCA 717 (the 717 isn't equipped with the 530 anyway)!

 

Old Problems that came with the WinXP install:

 

5)  When looking for an airport in the Airport list I have both a "United States" and "USA" listed in the country list.  6 or 8 states no longer show up in the United States list. To find an airport in one of these states I have to select "ANY".

 

6)  When FS2004 starts up a shrunken splashscreen appears (roughly only 2/3 normal size) in the upper left hand corner of the screen (standard screen monitor).  The normal sized splashscreen appears when a saved flight is loading.

 

Major Problems

 

7)  When ever I press a keyboard command such as the S or A or select somethng, say a saved flight, aircraft, or view option the last selected menu screen (or the splashscreen the 1st time something is selected after FS9 is started and a flight loaded.  A black rectangle is visible where the scenery loading, terrain loading box appears when a saved or created flight is loading. A second press of the S, A, or whatever key makes this go away.  A third press and the normal view (of the menu bar in the case of the A key) or menu bar appears.  While this doesn't appear to cause any problems with FS9 I still consider it major since it isn't NORMAL FS9 behavior!

 

8) Last and THE most major problem has to do with the TinMouse II 737-200.  Since I posted a detailed description on the TinMouse forum, I'll only describe it briefly here.  The plane loads okay in sport plane view, but when I try to switch to the panel view I get a black screen (or the prior screen/splashscreen view) and FS9 locks up.  I have to hit the esc key, select end flight and exit FS to get out of the problem.  If I just retart FS2004 and try to load a different saved flight, or just a different plane, it won't load.  I have to restart my system completely clear the problem.

 

I'd rather go back using FS9, even with its single digit FPS rate than give up my TinMouse II or have to deal with item 7!  I'm REALLY hoping others have encountered these problems (particularly the last two) and can offer some help on resolving them!  The frame rates I'm getting on the new system are MASSIVE even with the most detailed addon scenery with pretty much everything set to maximum but won't mean much if these last two problems can't be fixed...

 

 

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Scott,

 

I migrated my hugely expanded FS2004 from my old WinXP machine to a new Win7 64bit machine about a year ago and initially had some strange and unpredictable problems like you also seem to be having.

 

I initially installed the native FS2004 onto my new machine from the four CDs by using all the default options with which WinXP never had problems. However, Win7 is far more strict than WinXP ever was, especially when it concernes addons (like programable cockpit instruments) which use all kinds of (possibly old) programming methods which Win7 could regard as being potentially malicious. Some of these addons can even cause unpredictable errors and CTDs, even blue screens of death.

 

To resolve most of your problems (like I did) I would want to suggest that you install your initial FS2004 by using the "custom" install option, the most important of which is that you install it into a different HD partition from the one (usually C) inwhich your Win7 resides.

 

By the way: I also have, e.g. the B737-200 with it's analogue panel in my FS2004 and can fly it without any problems.

 

Good luck

Hans

Share this post


Link to post
Share on other sites

Scott

Re the 757 and 777 go to the just flight web site and download the fonts from the support page of the 757. This should cure the problem with numbers and letter issue.

I had this problem with missing font types both in XP and W7.

 

I found W7 frustrating at first but wouldn't change back now. You must install fs9 correctly as Hanns has said. Plenty of on these forums.

I have 2 hard drives one for W7 and the other for FS9. Run all installs as admin and ua off.

F/ FS9

Steve

Share this post


Link to post
Share on other sites

Thanks for the response, Hans!  I was beginning get the impression I was being subbed for some reason!

 

Actually, I did install FS2004 into a different HD partition from the default.  In fact, I installed it onto a separate HD entierly reserved for Fltims (FS98, FS2002, FS2004, and eventually, FSX if I can get my FS2004 woes taken care of).

 

I had far fewer problems getting FS2002 to run on my new system than FS2004!  In fact, the ONLY problem I encountered  with FS2002 (so far!) was restricted to the Dreamfleet 737-400 2D panel (doesn't have a VC).  Intinally, FS2002 would crash if I loaded a DF 737 and then tried to switch to the instrument panel.  Then I downloaded and installed the latest driver (311.56) for my EVGA GeForce GTX 650 video card and the problem went away (other than a slight "jiggle" switching to one direction to to another which doesn't happen for that particular view again unless I exit the panel view then reenter it).

 

Some good news about the TinMouse panel issue.  I discovered last night that after loading a TinMouse plane and trying to switch to the panel, hitting the esc key twice (once gets me to the black screen/prior selected screen/FS2004 splashscreen thing I described) the panel starts working normally!  I can change views as well (where I'd initially get a pinging sound).

 

A gentleman on Flightsim.com suggested the problem might be related to my video card/driver, what he called "FSAA", something I'd never hear of before. The nVidia control panel for my GTX 650 card "manage 3d settings" window has a "FXAA" setting which I assume is the same thing.  While changing the FXAA setting from off to on didn't fix anything, it occurred to me that maybe one of the other 3D settings is causing the problem.  There are several more 3D settings options on the GTX 650 card than I remember the GeForce 7000 series video card on my XP system having.  I'm hoping changing one or more of the 3D settings unique to the GTX card will make all my FS2004 issues go away.  I don't suppose you have a nVidia card and can tell me what I need to have all my 3D settings set for, do you?  Otherwise, its going to take a considerable period of time of trial and error to track down the offending setting!


Thanks for the JF 757/777 tip, Steve!  I'll do that asap!  As I mentioned to Hans, most, fi not all, the other issues might be related to the 3D settings for my GTX 650 video card.  Any thoughts on that?

Share this post


Link to post
Share on other sites

Will do, Steve!  BTW, installing the fonts fixed the JF 757/777 problem!  Strange though, I'm sure I didn't have this problem when I intalled them on my XP system originally.  Maybe a previously installed program I'm no longer using had installed the missing fonts? Anyway, making progress!  I was on the verge of chucking my Win7 system into the deep end of my swimming pool (I still might)!

Share this post


Link to post
Share on other sites

I have this driver version for the GTX670

9.18.13.1106

This is about a year old now but works great so im leaving well alone.

Steve

Share this post


Link to post
Share on other sites

Mine is 9.18.13.3165  (331.65, not 311.56!) Normally, in spite of software manufacturers insisting that you always get the latest drivers for your video card, I don't change drivers unless absolutely necessary,  If I hadn't had the problem with fhe DF 737 panel in FS2002, I wouldn't have upgraded from the original driver...upgrading drivers can sometimes cause more problems than they solve!

Share this post


Link to post
Share on other sites

if you go to simforums/hardware, software, computer tech, and then NV inspector drivers ect it explains how to make the changes (which I found difficult to do until I found this) within the nvidia inspector.

 

Steve

Share this post


Link to post
Share on other sites

Thanks, Steve!  Just downloaded nVidia Inspector.  Strange the profile list includes FS2000 and FS2002 but not FS2004 or FSX which I need it for most.  Guess that would have been too easy!

Share this post


Link to post
Share on other sites

It's there under ms flight sim 2004 I think. Not at my computer at this time but on ipad so I can't check for you.

Steve

Share this post


Link to post
Share on other sites

Yup, you're right.  FS2004 and FSX are listed under "MS Flight Simulator".  Didn't catch that when I did a quick glance at the list...Thanks for alerting this to me!  I'm guessing it still won't be an easy fix, the way my luck generally runs!  Oh, well, as long as its successful it'll be worth it (though I doubt if I ever become a fan of Windows 7)!

 

BTW, to back up a bit, aren't one automatically setup as "Adminstrator" when installing Windows (unless you add additional users on the system)?  Its that way under Windows XP (and earlier versions), wasn't it?  Also, what is "au"?  Too late unfortunately, the horse has already left the barn...

Share this post


Link to post
Share on other sites

You mean re-install Directx9?  That can be done with Directx11 installed?  Forgive my ignornace, but how is that done?

Share this post


Link to post
Share on other sites

Scott, cant say ive ever re installed direct 9 runtimes on my system?

perhaps im also missing something, but as I said mine works perfect

steve

Share this post


Link to post
Share on other sites

Yeah, I've never had any problems migrating FS2004 to a new system (or new hard drive as I had to do a few years ago when my boot HD went south on me)!  What is happening this time around is simply bazaar!   I was going to paste some screen shots here so you could better see the Problems I'm haing but for some reason I can't (I've done it before so I don't know why I can this time).  I'll have to attach them instead:

 

 

 

 

 

The first and second screen shots (or similar screen shots such as #4) appear when I press the A key to access the menu bar. A second press of the A key and this goes away. A third press of the A key and the bogus screen appears for a split second and then the normal view with the menu bar appears.

 

 

 

 

This one is the screen I see after trying to switch to the TinMouse II panel view.  Pressing the esc key and the subpanels start appearing and disappearing as normal.  A second press of the esc key is required to get the panel and cockpit view keys working again.  This only happens when a TinMouse 737 is first loaded.

 

 

 

The last three here show the old problem showing both a "United States" entry and a "USA" entry which only shows one state when opened.  One shows Indiana selected but Illinois airports.  I need to get rid of the "USA" entry! 

 

 

 

 

 

 

Share this post


Link to post
Share on other sites

Just tried nVidia Inspector.  Unfortunately, it didn't resolve the Alt key/menu bar screen problem.  I tried both the default MS Flight Simulator 2004 profile and another I came across via Google.  Neither had any effect.  I'm back to square one at this point.

 

Just to double check I went back and renamed my FS2004 folder to "WINXPFS9" and renamed my windows 7 FS2004 install from "WIN7FS9' back to FS2004.  I then ran FS2004 to confirm that the Alt key problem is NOT unique to my WinXP FS2004 install.  It isn't the Win7 FS2004 has the same problem.

 

I could just live with this problem since it doesn't appear to affect FS2004, but it would be a constant reminder that FS is doing something that it isn't suppose to be doing.  Unless someone can come up with a way to resolve this problem I'll be going back to my XP system and retiring the Win7 system to the closet (or selling it)...

Share this post


Link to post
Share on other sites

Scott

Just to clarify did you do a fresh install of FS9, ie load each scenery and aircraft one by one. Takes along time but the way I did it, or did you do it some other way, ie plug in a HD and tranfer over the data. I think if youve done it that way there lies your problems. I could be wrong we need other views from some experts (which Im not)

Steve


Your entry USA and United States could be a AFCAD problem. Check the AFCADS using AFX or ADE to see which is a possible problem. Just a thought

Steve

Share this post


Link to post
Share on other sites

Steve

 

In migrating my XP FS2004 install to my Win7 system I basically followed the directions outline in the "Migrating FS9 from XP 32-bit to Windows 7 64-bit" thread from this forum.  As part of this, after doing a fresh install of FS2004 and all of non scenery and aircraft addons  like ActiveSky, EFB2004, ISG, Reality XP WX500, EZ-VFR and shockwavelights.  The only aircraft and scenery I reinstalled were payware that I had on CD/DVDROM that were listed on the add/remove software list on my XP system.  I then renamed the fresh install folder (FS2004) to "WIN7FS9" and copied my entire XP FS2004 (including all addon scenery and aircraft, gauges, effects, module, FS2004 scenery and texture folders) from an external drive backup into a new FS2004 folder.  I've done this twice in the past (once when upgrading from XP Home Ed. to XP Pro, and the second when I had to replace my boot HD).  Both times FS2004 run just fine without ANY problems.

 

Just the same, today, to confirm whether or not what you belief that doing this is the cause of the issues I encountered this time around, I renamed my FS2004 folder back to WINXPFS9 and did a fresh completely install of FS2004 (no addons of any kind installed).  I then ran FS2004, and as I suspected, found that it had the exact same Alt key/menu bar with splashscreen/black screen problem (as per the screen captures I posted yesterday).  This clearly proves that the way I migrated my XP FS2004 install to my new system is NOT the cause of this problem.  At this point, I'm convinced, even though nVidia Inspector didn't resolve the problem (at least not with the settings I tried), that my GTX 650 graphics card is almost certainly the culprit.  That or Windows 7 might be.  Are you using the 32 bit or 64 bit version of Windows 7?  I have the 64 bit version (I didn't know Win 7 was available in a 32 bit version.  I would have asked for it if I had!

 

Well, I'll try tinkering bit longer with FS2004.  But if I, or anyone else can't think of something else to try soon (like a week or two at the most), I'm going to have to live with the problem (which doesn't seem to affect FS2004's stability or functions) or simply through in the towel and go back to  my XP system and it's single digit frame rate on FS2004 (at least FS2004, along with FS98, 2002, FSX all run like they should on my XP system (haven't actually installed FSX on the new system yet.  If I can't get FS2004 working like it should, I'm not going to waste the time installing FSX)!  I might try switching to the 32 bit version of Windows 7 or check with the folks I got my Windows 7 system from (PC Workshop) to see if I can run XP Pro on my new system (which has an ASRock Z87 Extreme mb, an Intel i5-4670K cpu, and 8gb ram along with the GTX 650 card)  The documentation on the mb only lists Win 7 & 8.

 

As to the USA entry problem I'm going to have to make all my US addon scenery inactive then activate them one at a time to track down the one that created the USA entry.  At this point, unless its a major addon, I'll probably just delete it rather than go to the  trouble of trying to edit it.  That or just live with it too (as I have for some time).

 

Thanks for the effort you have put in to trying to help me!  I've really appreciate all the help everyone has tried to give me!

Share this post


Link to post
Share on other sites

Scott

I'm using w7 64 bit, and before you give up with it I'd uninstall the whole lot and start again.

I wouldn't transfer over anything from a external source which has come from XP but add all scenery and aircraft one at a time using the original install exe. I know this takes along time but it worked for me.

Look up the sadly late, David "opa" Marshall thread on how to install fs9 in W7 .

When I installed mine a year ago I saw the thread your using and (for me) found it to complicated and did not understand it not being very computer literate.

Good luck

Steve

Share this post


Link to post
Share on other sites

Hi Steve

 

Well, I'm not *quite* ready to throw in the towel.  Still, I'd be loathe to go back and install every single aircraft and scenery file I've got.  The number of each that I have numbers in the hundreds.  I think Windows 10 would be out before I finished re-installing all my scenery and aircraft (I'm exaggerating here or course, but I don't think by much)!

 

Yeah, the procedure outlined in the "Migrating FS9..." thread is somewhat involved but I didn't find it excessively so (or I wouldn't have tried it).  Perhaps because it was pretty close to what I had done when upgrading to XP and when I had to replace my boot drive.

 

I may not have to do it anyway.  I posted a description of my TinMouse II panel problem on the TinMouse forum and just got a response from a gentleman who recommended copying the FS2Audio.dll file into the SysWOW64 folder in Windows (a copy also goes in the System32 folder).  Per a link the gentleman provided,   http://forum.avsim.n...iodll-problems/,  Bob Scott says this has to be done on 64-bit systems.  Anyway, the TinMouse panel loads normally without my having to press the ESC key!  I still get the black screen with the scenery/terrain loading window for a split second though, but, hey, its progress!

 

Before entertaining any thoughts of throwing in the towel and dragging my XP system out of the closet I thought I'd see if EVGA has a support forum and ask for help there.  I might do the same for my ASRock motherboard.  ASUS makes the ASRock mb.  Perhaps they could help as well (or at least tell me if I can run Windows XP with it.  Resolving the TinMouse panel problem has given me hope that the Alt key problem can be fixed without having resort to following your suggestion or going back to the XP system!

Share this post


Link to post
Share on other sites