Happy Labor Day to all!The following is a copy of a post I made on the Dreamfleet GA aircraft forum. I thought it might get more exposure here, and possibly someone had been down this same road and knows a solution."Fatal Error 8891 for Dakota GNS430 --------------------------------------------------------------------------------I have upgraded my computer including an i7-975 CPU and Windows XP Pro 64 bit.I have reinstalled FSX and begun to reinstall aircraft.I installed the Dreamfleet Dakota along with full RXP/Garmin provisions with no problem and got no error messages. The final installation text stated that the program installed successfully and was finished.When I select the DF Dakota in FSX, I get the following error window including the red "X" in a circle:"Fatal ErrorReality XP Garmin GNS 430 Ver.5.2.0.0Can't start the Reality XP GarminError 8891"When I click "OK", FSX shuts down.I see that Lou has posted a sticky addressing some problems with this unit, but he states: "NB: the reason for the issue is Vista UAC." I do not have Vista, but the Windows XP Pro 64bit OS.I also see a number of replies regarding a similar problem with "Error 3524". I get "Error 8891".Previously, I have enjoyed this fine contribution with no problems at all. Is it not compatible with the 64bit system, or does anyone know what the problem is and/or a solution?Respectfully:RTHNote: The Garmin also did not completely install when I installed the Dreamfleet Baron in FS9 either. However, I can select the aircraft.Note: I have the RXP: GNS530 and GMA340 installed in a number of other aircraft and they function just fine. The problem is unique to the Dreamfleet birds. No, I have not tried anything on my own relative to installing these separately in the DF birds in question. Only a straightforward installation as per Dreamfleet's instructions. I did get errors during installation with the Baron, none with the Dakota. However, the Baron displays but the Garmin does not power up (FS9). The Dakota shuts down FSX." --------------------------------------------------------------------------------In a second reply to my own thread, I stated the following:"Progress (After a fashion):Still no luck on the Dakota in FSX.For the Baron in FS9, I have tried Alastair's recommendations from the "Problem with Garmin GNS 530 Installation" thread started by "Raul87" on July 19, 2009.As Alastair suggested, I downloaded the zipped versions of the Garmin Trainers, unzipped them and installed them in "C:\GNS430" and "C:\GNS530" folders. Alastair also states: "The Trainer is a 16-bit application and is not operable in a 64-bit environment", so I am not sure but what this is futile, and I can't tell that they do anything.At any rate, I still cannot get power to the Garmin.So, I disabled the garmin line items in the panel / panel.cfg and added the stand alone unit I purchased from RXP. Works like a charm, however, I do still get the error messages when I select the Baron in FS9 as follows:First error window:"InformationReality XP: Garmin GNS Unit1 DiagnosticEFIS Bus Fault. Number of available ports: 0"After I click "OK", I get the next error window:Second error window:"InformationReality XP Garmion GNS 530 Unit 1EFIS output has been disabled automatically. Insufficient Avionics Bus resources."After I click "OK, I get the next error window:"Fatal ErrorReality XP Garmin GNS 530 Ver. 5.2.0.0Can't start the Reality XP GarminError 8891"Note that this is exactly the same error number, "8891" that I get with the Dreamfleet Dakota which shuts down FSX, however, after clicking the last "OK", the Baron comes up just fine with my workable Garmin in FS9, or the original which I cannot get to power up. I realize that the problem is probably the 64 bit operating system, but there should be a workaround for this, as my RXP gauges do work just fine there.Is there anyway to just do away with the Garmin included with the Dakota so that the aircraft can be selected without it? If so, I will simply add my purchased unit (Yes, I know Lou said not to do this, but it is working in the FS9 DF Baron in spite of the error windows, and presently I cannot bring the Dakota to life).I sure would hate to loose either one of these planes. They are two of my favorites (Like just about everything else Dreamfleet has originated going back to the 737. The DF 727 alone makes me hang onto FS9).Suggestions would be appreciated."One Added Note: The Dreamfleet DreamManager is a blank window and does not work either in the Baron. "Anyone know how to get the Dreamfleet Dakota going under a WinXP 64 bit system?Respectfully:RTH

The Garmin uses a 16 bit program and 16 bit programs cannot be run on Vista 64. I'm quite convinced that the same goes for XP 64. The DreamFleets product info is very clear on this regarding Vista 64, but doesn't mention XP 64 at all.

The Garmin uses a 16 bit program and 16 bit programs cannot be run on Vista 64. I'm quite convinced that the same goes for XP 64. The DreamFleets product info is very clear on this regarding Vista 64, but doesn't mention XP 64 at all.

Actually the new WAAS RXP units use new 32 bit trainer.

Actually the new WAAS RXP units use new 32 bit trainer.

Actually the Dakota isn't equipped with the WAAS.Edited: http://www.dreamfleet2000.com/Previews/236/purchase_236.html

Actually the Dakota isn't equipped with the WAAS.Edited: http://www.dreamfleet2000.com/Previews/236/purchase_236.html

Yes, I know, I have it. But I also have the stand-alone RXP WAAS unit. But the stock Deamfleet FSX Dakota also uses the 32 bit trainer, as no RXP unit worked in FSX until it's release. Very shorty after the Dakota release, the new WAAS RXP unit became available.

AFAIK, the Garmin 430 that is installed in the DF Dakota is the Reality XP 430 unit that uses the Garmin 16 bit trainer to actually provide the functionality. In Win XP 32 (and I assume Vista 32), the trainer has to run within ntvdm.exe 16 bit virtual environment. I don't believe ntvdm.exe will work on any 64 bit OS. I think the fix is to purchase the current Reality XP WAAS-enabled 430W which uses a 32 bit Garmin trainer as its base (the database is also newer as well) and modify the panel to accept it in place of the 16 bit 430 unit.scott s..

AFAIK, the Garmin 430 that is installed in the DF Dakota is the Reality XP 430 unit that uses the Garmin 16 bit trainer to actually provide the functionality. In Win XP 32 (and I assume Vista 32), the trainer has to run within ntvdm.exe 16 bit virtual environment. I don't believe ntvdm.exe will work on any 64 bit OS. I think the fix is to purchase the current Reality XP WAAS-enabled 430W which uses a 32 bit Garmin trainer as its base (the database is also newer as well) and modify the panel to accept it in place of the 16 bit 430 unit.scott s..

Again, I do not believe that is not correct. The trainer used in the stock Dakota was 32 bit. Again, when the FSX Dakota was released, it was the first time an RXP GNS unite could be used in FSX, as it used the new trainer. And again, the new RXP WAAS unit was released just a day ir two after the Dakota release. But, until I purchased the stand-alone, I could, for the first time, run an RXP GNS unit in FSX provided with the Dakota package.

You'll need to buy the RXP GNS430 unit if you want the Dakota to work in a 64bit OSThat's what I did. It's actually really easy. All you need to do is swap out the old lines in the panel.cfg for the new RXP gauge definitions

You'll need to buy the RXP GNS430 unit if you want the Dakota to work in a 64bit OSThat's what I did. It's actually really easy. All you need to do is swap out the old lines in the panel.cfg for the new RXP gauge definitions

Ryan, a question (as I've stuck with XP 32 bit, did you have to modify anything in 64 bit? Or did the WAAS unit work 'out of the box'?As I have said earlier, I have stayed clear of running a 65 bit app, just because I do not want to loose my RXP GNS units, and I know it was an issue for some early on. I might consider an OS upgrade if there is no longer an issue.

Basically all I did to get it working was:A) Buy the unit:( configure it using the RXP programC) manually edit the CFG file and replace the Dakota RXP units for the WAAS RXP units. Everything works pretty well

Basically all I did to get it working was:A) Buy the unit:( configure it using the RXP programC) manually edit the CFG file and replace the Dakota RXP units for the WAAS RXP units. Everything works pretty well

i wasn't talking about the Dakota in particular, as I've already changed out all my GNS units to the WAAS versions months ago, including the Dakota. But, it is good to hear you have had no problems with your 64 bit OS, as it seems others have had problems.

yep, fortunately I have not encountered the "red airplane" icon or any other strange happenings.

yep, fortunately I have not encountered the "red airplane" icon or any other strange happenings.

Jean-Luc finally took care of that, it was a video driver issue as it interfaced with the GNS exe file. As many of us deduced months prior to the fix.

Thanks for the reply Scott:Tried that. Worked on the Dreamfleet Baron in FS9, but not on the Dakota in FSX. However, I believe I was trying the Garmin 530, maybe that makes a difference. I also tried to just disable all line items relative to the Garmin. I still could not select the Dakota. Every time I tried, it shut down FSX. Thanks to all of these replies I will try again. Happy to hear that some have got it to work.Respectfully:RTH

AFAIK, the Garmin 430 that is installed in the DF Dakota is the Reality XP 430 unit that uses the Garmin 16 bit trainer to actually provide the functionality. In Win XP 32 (and I assume Vista 32), the trainer has to run within ntvdm.exe 16 bit virtual environment. I don't believe ntvdm.exe will work on any 64 bit OS. I think the fix is to purchase the current Reality XP WAAS-enabled 430W which uses a 32 bit Garmin trainer as its base (the database is also newer as well) and modify the panel to accept it in place of the 16 bit 430 unit.scott s..

Careful, you need to find even the GTX327 lines of code as well....I think I modified everything unless it was a normal gauge or a normal RXP gauge.