History: PF2000/PFE has been working fine for many flights. I did recently learn that I needed to disable my ESET Smart Security for the beginning of the flight to have voice recognition implementing Gamecommander2. Keyboard commands had no problems. As soon as everything is setup and voice recognition is achieved, ESET may be reenabled with no problems thereafter.
Intentions:
Virtually in FSX To make a flight from KMYR to KBTR where I will pick up family, then on to KMIA for the NCAA Championship, then back to KBTR after the game, and end back home at KMYR for the final of four flights. Aircraft will be the Eaglesoft Citation X. Weather: ASE. Flightplan originated with FlightSim Commander. ATC: PF2000/PFE.
1. Originatel and setup a flight from KMYR to KBTR.
2. Originated and setup a flight from KBTR to KMIA.
3. Originated and setup a flight from KMIA to KBTR
Note that all of these setups went flawlessly including the final stages of PF2000. I have already completed the first leg, KMYR to KBTR. No problems as has been the case for a number of preceediing flights to other destinations and PFE communicated fine.
Then I began to setup my final leg from KBTR to KMYR.
a. Setup in FSC had no problem, and the flight is stored and looks normal in the Flight Simulator X Files folder
b. Activated PFE and converted the fightplan. Everything looked normal and the resulting window tells me the "FS9 Flight Plan successfully converted to PF2000 Format."
C. Clicked on the "Click here to start ProFlight 2000" Icon for the final steps of the setup.
This is where I am now having a problem. I get a PF2000 Error window which states: "Run-time error 5: Invalid procedure or argument."
This same thing now happens if I try to reconvert and then bring up PF2000 with any of the previous successful flights that I still have in my directory as well. Any time I try to startup PF2000 regardless of anything else, I get this error now.
Thinking my setup for this last flight (KMYR to KBTR) might have been my mistake, I delted that Flight. Same thing. I tried temporarilly removing all of the Pilot and PF2000 flights in the applicable directories, and get the same thing.
I also found no error entries in the windows event viewer logs at the times I tried activating PF2000 which surprised me.
Any ideas before I reinstall PF2000/PFE? Could there be a corrupt file somewhere else causing the problem. I found no such files under AppData or similar locations.
Respectfully:
RTH