Bruce50010

Thanks for the quick reply. From the Event Viewer there are at least three different events...two appear to be related to 737 PIC as shown below. I will try uninstalling and re-installing as an administrator with virus protection disabled. Most common errors related to 737 PIC -- The only one that does not appear to be related to 737 PIC is this one --

I recently updated my computer to Windows 7 and installed FS9, Radar Contact, and Wilco 737 PIC. From the FS main menu, or in a flight, I get a "Microsoft Flight Simulator has stopped working" every time I try to select an aircraft in create a flight, or change an aircraft when in an existing flight. It does not matter what aircraft I am selecting -- an included FS9 aircraft or the Wilco add-on. I've had no crashes from any other menu options, only the aircraft selection. I've tried running as administrator, running in compatibility mode, running in full screen and windowed mode, and my video drivers are updated -- still crashes every time I try to select an aircraft -- really hoping someone has seen this before. Thanks in advance for any help.

Thanks much for your help. I copied the old RCV4.3 folder from my old computer to my new computer. It took awhile hunting for ocx and dll files, and copying and registering them, but it appears 4.3 is now running correctly on the new machine. Ended up being no need to do anything with the .dat files, at least that I've found so far. Thanks again.

Thanks for the feedback. If you can help with a new install file that would be great. Getting all the dll and ocx files installed and registered properly one at a time as errors occur is an exercise I would like to avoid, if possible. My email has not changed since my original 4.0 order or 4.3 upgrade.

I tried that last week; unfortunately no response so far. I do have 4.3 installed on another computer but I do not have an install ".exe" file. I can copy the program file from one computer to another but I'm assuming there are probably some required system files that would not be installed.

I'm curious how the problem was solved. I had installed Radar Contact v 4.0 from a CD and downloaded v4.3 at some point several years ago. I recently replaced my computer. I have installed v 4.0 from my original CD -- is there a way to upgrade this to 4.3?

One of my favorite scenic flights in FS9 -- approach & landing, runway 8, Juneau, Alaska after flight from Anchorage

I was flying Alaska #52 from Fairbanks to Anchorage with the feelthere 737 PIC and RadarContact. Flight was normal during startup, taxi, and climbout. RC held me at 29,000' for quite awhile which kept me from reaching cruising altitude of 35,000' before it issued me a descend command. In fact I was still climbing through 31,000 feet when it ordered me down to 29,000'. Re-programming the FMC and re-setting the altitude meant it took more than 15 seconds before I started descendiing, prompting the ever-present "Watch your altitude, your assigned altitue is 29,000' message". Later, while descending to 29,000', I was give the "Descend to 11,000', start down now I need you level in 30 miles or less". OK, 19,000' in 30 miles, guess I'm getting the "You missed your crossing restriction" lecture again. Oh well. As I was descending, the Anchorage ATIS gave me winds 240@5 and I was expecting to be assigned one of the east/west runways, but instead it said "landing and departing runway 14". Good deal for me since it's almost a straight-in approach. RC told me to expect vectors to Runway 14, I got handed off to approach, vectored east, then southwest to intercept the localizer. As I did, RC was vectoring other AI planes to runway 32. Odd, but I guess they know who is where. I got handed off to tower and when I came out of the clouds about 5 miles from the airport, I saw lights from other planes stacked up vertically on approach to runway 32. My runway, from the other direction. At about 2 or 3 miles out I was instructed to go around, told to fly heading 170 and climb to 6,000'.As I turned right and climbed, I got this shot out the LH window showing planes scattering in every direction. Some were taking off on 32, some were landing on 32 and landed, and some were landing on 32 and did go-arounds:Another view as a climb out. I count twelve planes either taking off from, landing on, or going around from runway 32, all within about a 5 mile radius:So, RC vectors me southwest, then northeast, then back southeast to intercept the localizer for runway 14 again. This time I don't hear any chatter of planes being vectored to runway 32, so I assume I'm good. I'm handed off to tower, come out of the clouds, and see no traffic. I'm cleared to land then just as I cross touch down, lights from the far end of the runway appear, get larger, and I watch a MD80 take off right in front of me. At the time I see the MD80's nose rising, RC tells me to go around. But my wheels are down, speedbrakes out, and the MD80 is above me, so screw that, I slow down and turn off the runway. At which point RC tells me I am losing my license for landing when being told to go around. :( I'm used to some of the peculiarities of RC like being told to start descents so I fly the last 100 miles of trips at 10,000', being told to descend 18,000' in 30 miles to avoid traffic (near Barrow, Alaska), and being warned about my assigned altitude when I don't start climbing or descending within 2 seconds. But several firsts on this one:* First time landing in a cross-wind (albeit small) when two runways aligned exactly with the wind are available.* First time I've seen RC vector airplanes to land on the same runway from opposite directions simultaneously.* First time I've seen RC make AI look like an Italian traffic jam.* Despite the frequent lectures I get from RC, this is the first time I've ever lost my license. :(

Thanks for the replies. I should have stated this, but I am using Windows Vista. Looking at other forums, it looks like this is an issue with the video card and/or drivers and not FSUIPC. I tried running FS in windowed mode and FSUIPC works fine; when running in full screen mode, accessing FSUIPC causes FS to lock up. At least as of yesterday. I don't know why I was able to access FSUIPC from FS full screen mode w/o any problems for a long time (i.e. years) and it just stopped working yesterday without anything else changing, but it happened. Maybe Vista installed some update in the background that somehow affected FS & FSUIPC. Regardless, I guess I just have to remember to change to windowed mode before I access FSUIPC until it's time for a new PC & new operating system.

After a long time using FSUIPC w/o problems it has stopped working and I can't see any apparent fix.The problem: Start FS9, click "Modules/FSUIPC" in order to do joystick calibration, and the screen turns black and locks up. No response to keyboard, mouse, or yoke/pedals. FS9 has to be killed manually w/task manager.Using FS9 with FSUIPC 3.9.9.1 (registered copy) & 737PIC. I reinstalled FSUIPC and checked for video card driver updates (NVIDIA GeForce 8500GT - most recent drivers already installed).Has anyone seen this before? I don't know what else to do short of complete reinstall of FS9. Thanks for any help.