Ok let me look at some of my installs. I never used the rxp install software to install my 530. I always used fspanel studio to install all mt waas 530's in my FS9 aircraft. There's a swap gauge routine in Fspanel studio that allows you swap out the default gps with the rxp one. Then you can add in the rxp ini file to have a popup larger 530 when you press inside the 530 you swapped out. You might have a left over .dll from older version causing shut down. Look in your modules folder ther should be an rxpgnsdriver.dll dated 2012, with the update the older one should have been overwritten.

Thanks for your patience and tries Mack:

 

Ok, here was my last try.

 

1. In the Control Panel "Uninstall a program" provisions I removed the rxp GNS 530 WAAS.

2. Deleted all RXP files and folders that I could find, and as I am sure you know there are many. The only thing I did not do was remove the gauge entries in my many FSX aircraft.

3. Downloaded another fresh "GNS-530-WAAS-XP-GPS" from the RXP Store ("rxpGNS-530WAAS.exe" with the red aircraft symbol)

4. Reinstalled with the F1 Wrapper.

 

Sorry to say the exact same results.

 

My "rxpgnsdriver.dll" was and is dated 2012 both before and after removal with the new reinstallation.

 

One curious thing that happens that I failed to mention before is that with the RXP gauges installed in FS9, when a bird in question is selected, while it is displayed in the option window and it is revolving, the revolving stops for a few moments when chosen, then continues revolving without the aircraft being initiated. By clicking on it again, sometimes a third time, either the plane then kicks in, or in random fashion this may be the point where the shut down occurs.

 

A mystery huh!

RTH

 

Ok let me look at some of my installs. I never used the rxp install software to install my 530. I always used fspanel studio to install all mt waas 530's in my FS9 aircraft. There's a swap gauge routine in Fspanel studio that allows you swap out the default gps with the rxp one. Then you can add in the rxp ini file to have a popup larger 530 when you press inside the 530 you swapped out. You might have a left over .dll from older version causing shut down. Look in your modules folder ther should be an rxpgnsdriver.dll dated 2012, with the update the older one should have been overwritten.

Try this remove the rxp gauge in the AC you want to use. Open panal cfg and make sure all rxp entries are gone. Start fs9 and load AC, it should load ok. Close fs9, using FSpanel edit the same AC panel swapping the default GPS for the RXP GPS, Save and close. re start fs9 loading a default ac first, then once default AC laods, load the AC you installed the RXP gauge in and see if crash.

 

Also before you start FS9 right click on the FS9 exe and click on properties. Select the compadtabliy tab and check the "Disable visual themes" and "Run as Admin" boxes are checked. Click apply and ok. Then start FS9

 

Also when you reinstall the new waas gps do you let it reinstall the new trainers. That is very important that new trainers get installed. Don't use the older trainers.

Hello again Mack:

 

Last things first: I have downloaded and rinstalled the RXP GNS 530 WAAS multiple times including the Trainer. I even tried installing the trainer by itself from the alternate backup provisions included in the Program Data\Reality XP folder by the setup. No luck. FS9 still shuts down with the RXP GPS installed.

 

Regarding swapping out the unit with the default implementing Panel Studio, I have a couple of questions:

 

1. Is the gauge replacement "rxpGNS!GNS530"?

2. If so, how did you get it into the FS9 gauge folder? I do not find it available if I have removed it from all aircraft. I have always used the "Reality XP GNS WAAS Config 9.exe" execution file to make it available in aircraft as an alternate GPS. Once this is done, it is available in Panel Studio if so desired, but if it has never been installed in any aircraft by the RXP method, I do not fine it available.

 

What I did which I think simulates your method was as follows:

 

a. I installed in an aircraft with the "REality XP GNS WAAS config 9.exe" execution file.

b. I then was able to access the gauge in Panel Studio and swap out the "fs9gps!gps_500" gauge replacing it with the "rxpGNS!GNS530" gauge.

c. Removed the line items installed in the panel.cfg by RXP

 

Unfortunately all of this brought no success. FS9 still shuts down.

 

To try to confirm that I was equating what you recommended, I then tried the same method in FSX in an aircraft. Worked like a charm. It replaced the default GPS with the RXP unit and everything seemed to work fine. Of course the DropStack and GNS GMAGTX were not available.

 

I have just about run out of ideas. The RXP forum has also become silent. FSX works just fine with all RXP provisons, but my FS9 sure doesn't like them.

 

Thanks again for your efforts.

RTH

 

Try this remove the rxp gauge in the AC you want to use. Open panal cfg and make sure all rxp entries are gone. Start fs9 and load AC, it should load ok. Close fs9, using FSpanel edit the same AC panel swapping the default GPS for the RXP GPS, Save and close. re start fs9 loading a default ac first, then once default AC laods, load the AC you installed the RXP gauge in and see if crash.

 

Also before you start FS9 right click on the FS9 exe and click on properties. Select the compadtabliy tab and check the "Disable visual themes" and "Run as Admin" boxes are checked. Click apply and ok. Then start FS9

 

Also when you reinstall the new waas gps do you let it reinstall the new trainers. That is very important that new trainers get installed. Don't use the older trainers.

Well as usual, when you fiddle long enough one of two things happen. Either you find and fix your problem, or things get worse. Usually, I have been fortunate to have the former happen. However, this time I am afraid things are beginning to smell much worse.

 

I am not aware of anything I have changed without returning it to the configuration I had when FS9 worked fine as long as the RXP gauges were not installed in any of my fs9 panel.cfgs. But now, I am having difficulty with other items. I thought it was just the fS9 default GPS, but it seems to apply to any secondary windows on certain aircraft, including some defaults.

 

With a troubled aircraft, I see the following results:

 

1. Startup FS9 with the default Baron (or any number of other select default aircraft that seem to have no problem - (i.e. Default 172, 737, 747, extra)

2. Select the FS9 default 777 (or any number of other default or third party aircraft which have the problem - i.e.(Default 777, DC3, Ford Tri-Motor, Piper J3 Cub. plus the G5 or Dassault 50 third party bird. I have tried few third party aircraft as there are plenty defaults in question.)

3. Click on a shortcut such as the default GPS, Radio Stack or another similar choice to open. At this point everything is fine and all panel switches work.

5. Click on the shortcut again to close the chosen secondary window. For example, the GPS window does not close and everything is locked up. No panel switches work.

 

I fear that I am near the point where reinstallation of FS9 may be advisable, but I sure hate to do that. In addition to this I fear that the culprit may be somewhere outside of FS9 as I tried the following. I renamed Flight Simulator 9 and edited my default installation to run. I also did the same thing with the "Roaming\FS9 folder. Everything should have been back to the default installation with the exception of registry entries, and I still had the problem. I fear that with a reinstallation of FS9, the culprit may remain somewhere.

 

I will try not to bother anybody with this again until I find the problem. Probably will sleep on it for a day or two and come back to it. Like a Ford commerical, I have found that sometimes after a recess that a light comes on. Fortunately, FSX flies on not knowing there is any problem anywhere.

 

Thanks for your help.

RTH

Success (After a fashion)!

 

First a brief review of how I got here from there.

 

1. Initially in FS9 with the RXP GNS 530 WAAS GPS installed in any bird, I got a random shutdown of FS9 anywhere from setup to after a flight had begun.

2. With the RXP GPS removed from all aircraft, FS9 performed just fine.

3. Renamed "Flight Simulater 9" to be "Flight Simulator 9 with problems" in order to disable it.

4. Installed a complete new installation of FS9 and added the 91upt update with no modifications or addons.

5. Installed the RXP GPS into the default Baron.

6. Same results, FS9 had random shutdowns

7. Removed the RXP GPS.

8. Found that I had new problems. With some planes like the 777, DC3, Tri-Motor, J3 cub and 9 others, if a shortcut opened anything like the radio stack or default GPS, all panel switches froze and would not function. Cycling views was also strange and incomplete. For example in spot view, the panel still was present. There were other strange happenings.

 

Now the solution I found what was causing this:problem with my new installation. When FSX is started up, in the lower right corner of my screen I get a notification window informing me that "The color scheme has been changed to Windows 7 basic. A running program isn't compatible with certain visual elements of windows.". I cannot swear to it, but i think I use to get the same message when I started up FS9. If so, I have no idea what happend to change that which probably caused these problems. Therefore, I went into the "control panel>Appearance and Personalization>Change the theme" options and tried "Basic and High Contrast Themes". All problems went away. Views cycled correctly. Secondary windows opened, closed, unlocked, and moved as desired and everything still worked fine.

 

I also reinstalled the RXP GPS into the Baron and 737. They performed flawlessly without the previous FS9 shutdown or any other problems.

 

I thought maybe the "Disable Visual thems" check in the FS9.exe Property options would by a similar cure, but that does not cure the problem if "My Themes" or "Aero Themes" are chosen as a desktop theme. I have no idea what changed in order to suddenly make this an issue with FS9 as it just showed up.

 

So I thought I would rename my new FS9 default installation to disable it and edit my full installation with addons back to a working configuration and be ready to fly away.

 

Not so! Now I have a new problem. My original existing installation will not start up. I get the splash screen displaying the image of the DC3, and then a few moments later after a brief black screen it crashes back to my desktop, I have tried the Flight One Registry tool, but that was not a solution. My assumption is that when I installed the parallel default installation of FS9, that something was changed in the registry that now does not allow me to start up my original installation. I may post a new thread titled: "FS9 will not start up". I have tried all the suggestions so far that I could find by a Google search and on this forum.

 

If anyone knows the cure, it sure would be appreciated.

 

Respectfully:

RTH

 

Edit: Spoke a little too soon. I made a copy of my full installation of FS9 including all addons and FS9 now starts up fine. Unfortunately, I am back to my original problem of RXP gauges shutting down FS9, even with the basic theme desktop.. They work great in FSX, and in my alternate default FS9 installation. FS9 seems to work great without them in the full installation. Therefore, the solution may have to be a delaty until some future time when a full deletion and clean installation is possible.

 

Thanks all:

RTH

Well, I am completely snowed and confused.

 

Last night after my last reply I shut everything down and went to bed. (I have shut down and restarted the computer already many times during this scenario which cured nothing.)

 

This morining after cranking up my computers, I created my personal desktop background and screensaver again and started up FS9. I installed the RXP 530 WAAS GPS in my G5.

 

I don't know how long it will last, but presently everything is working flawlessly in FS9 including the RXP gauges.

 

For the last few days I think my FS9 has been playing tricks and teasing me.

 

Respectfully:

RTH

Several users have now confirmed that FS9/RXP GNS crashes are fixed by going back to RXPGNS V1.4.

 

If you're still having problems, visit the RXP support forum - there is a pinned topic on this..