After I thought I got everything right, I hit a BIG problem with RC.On a KSDF-KMDW flight RC stopped working. I was instructed to 10,000 at 250 kts. about 30 miles out. I started wondering why many minutes went by with no ATC at all, not even chatter. I was about 5 miles away from KMDW. RC basically stopped working! I kept on going thinking that it was maybe a weird approach. Nothing happened by the time I was 40 miles past the airport. Even my ADVDISPLAY window was froozen, I couldn't even change settings there. I minimized FS9 and tried to pull up RC, it didn't respond. It's clear that RC froze up for some reason. I paused FS9 and finally got RC closed. I turned on RC again and it worked, but it put my plane back to KSDF at the altitude I was at when I closed it 40 miles NW of KMDW.Why would RC just stop working? BTW, I don't have problems with any other software that I have purchased for FS9. It seems like this program needs alot of attention. This is the most expensive package that I've ever purchased for FS and it's great, but it's not working.

It sounds like Flight Simulator lost focus. If that should happen again move you cursor to anywhere on the screen except right on top of Adv Display and click your left mouse button. RC should start responding.

you have advdisp docked to the panel?right? no way it can gain focus, right?when you say frozen, did the menus work? could you press 9 to advance to the next page of menus? how many wavs do you have in winwodd2, winwood3, ...12? they should all have the same numberdo you have autoreply on? did you descend to 10000@250? did you acknowledge the clearance, or did autoreply handle it? did you have the comms and plane, or did the copilot?what is the version number of fsuipc, advdisp, and rcv31.exe? (exact numbers not "latest version")

1) advdisp is docked2) menus did not work, 9 did nothing3) The winwood thing, I have hundereds of folders in that file. Is that what you're asking?4) Autoreply is not on5) I descended to 10000/250 about 5 miles before the crossing resriction6) Yes I acknowledged the clearance, it's the last thing I heard7) I don't use the co-pilot for anythingI'm showing FSUIPC 3411 and advsisp 2130. Hope I didn't make you mad...

JD,Your post sounded like docking the advdisp is not the right thing to do, the manual says to do it. Just making sure I didn't miss something.Thanks again.

Reference number 3. What JD wants to know is how many files you have in each of the Winwood folders numbering 2 - 12Please open Windows Explorer and navigate to your Radar Contact Winwood folder. Highlight each folder name and click your right mouse button. A menu will drop down - choose properties. Part of the output will be total files in that folder.

Ok thanks. Folders 2-12 in the Winwood file all show 1134 files each.

Mine show 1135 but that includes the Readme - does yours?Andy b

In propeties, it shows 1134 files and zero folders.BTW, last night I gave it another try. After receiving t/o clearance it frooze again. I closed everything down, rebooted and started again. It worked perfectly without an issue. I don't know, I did everything the same way the second time around.

I guess you missed my message from above. It sounds like Flight Sim is losing focus. to correct this move your cursor to anywhere on the panel except on top of Adv display and click the left mouse button. RC should start responding.

what operating system?sounds like something else is going on. if you are getting freezes at different times on different flights, sounds like the os, a video driver, sound driver, something non flight related.i know you're probably thinking, this doesn't happen without rc, but running fs and rc together puts more stress on cpu, memory, hard disk, etc. something is giving up.has it ever worked correctly?you have a freeze everytime you fly with rc?no freeze without rc?jd

I may have found the answer. I happened to run Registry Healer a couple of days ago. I happened to use RC the first time around that same time. I restored back to system state before I ran Registry Healer and I had no RC contact problems at all. Matter of fact it was a lot of fun. I'm hoping that was it. It must be as I have 3 sessions down with no problems at all.JD, sorry about my "this program needs a lot of attention" post. I was was just mad and RC seemed like the obvious suspect.This registry healer needs to go away though.

i get this a lot. rc has been running for 12 months, and all of a sudden, rc stops working. like the rc bits were flipped by mysterious gamma ray radiation.troubleshooting 101, something has stopped working, what has changed since the last time it was working? that's where i always startand as far as your comment, no problem. with thousands of installations and happy customers, i was pretty certain it wasn't rc crashing your machine.jd