I've been using PIC 767 for over six months now in FS2002 with the 1.2 patch. It has worked very well with no problems whatsoever. It has been great fun learning the FMC, exporting and loading flight plans created in Nav 3.1, and flying all over the placeYesterday, I was loading a flight plan into the FMC, and all of a sudden, a bunch of garbage alphanumeric characters went across the FMC RTE screen, and the application hung. I restarted FS2002, and selected the Wilco 767 in Aircraft. Upon clicking OK to load the plane, my system seemed to lock up, and looking at the processes, FS2002 was using 97-99% CPU. The only way to get out was to end the process.I loaded the DreamFleet 737 and FMC, works great. All other aircraft can be loaded and flown without any problems either. It appears FS2002 is operating normally, but wheb=ver I load a PIC 767, the CPU goes nuts.To try and isolate the problem to the 767, I renamed the Panel folder in the Wilco 767 aircraft directory, then copied the default 747 Panel over into the directory. When I load the PIC 767 aircraft, it comes up perfectly with a 747 panel. Remove the 747 panel directory and rename the original 767 Panel directory, the problem comes back. So there seems to be something going on with the panel itself, not the aircraft, upon loading.I reinstalled PIC 767 and added the 1.2 patch again, still no luck. Any ideas?Thanks!Pentium41.8 GHz512MB memoryNvidia TNT64

hiur fmc navdata might be corrupted.I suggest u uninstall PIC, then delete ur FMCWP directory (located in FS2002 directory), then reinstall PIChope that works :)

Thanks! I have a feeling that the uninstall process for PIC767 is not getting rid of everything, so there indeed may be some files left over. Besides the Wilco 767 aircraft folder and the FMCWP folder, any other places that files might be located?

"I have a feeling that the uninstall process for PIC767 is not getting rid of everything". This is correct. This also goes for most other installed programs including Fs2002. I always remove manualy what's left over to avoid these problems.Best Wishes,Randy J. [email protected]" A little learning is a dangerous thing"

Steve,Don't worry about CPU usage being at 97-99%, it's like that just loading FS :-) I have checked CPU usage numerous times and it is always the same whether on a Duron 650, 900 or XP1800!

Hi Vulcan,Unfortunately, the CPU just sat there with the aircraft selection page visible, along with the hourglass. This happened after simply selecting the 767 and clicking OK. The only way to kill it was to end the process, which brought the PC back to life.What I did find was that the PIC 767 uninstall process did not remove all the gauges in the Gauges folder. Once I physically removed them and reinstalled PIC 767, I was back in business. It appears that some of the gauges were corrupted, and during the load of the aircraft, caused FS2002 to go CPU hungry.Thanks for everyone's guidance and recommendations! I'm back in business carrying passengers and bringing in revenue. :-)