Well replaced my old single channel sound card (RipTide) with a new SoundBlaster Live 5.1 card ($69US) and also had to buy a new modem card because the old one I had was a COMBO card and had both integrated in it. So, for about $150US I am back flying with FS2K, and RCV3, and have all the audio, from all channels!This is great and I even got my rear end chewed out landing in Chicago (KDSN -> KORD)for exceeding speeds below 10K. I would have done that but I could not understand the foreign ATC (maybe a Brit) and his instructions. Nothing against the Brits but, could not understand the transmission here. No big thing, I was so excited I had it working again that I listened to the repremand and went and had a couple cold ones and smiled as I had the problem solved!Now to continue my round the work trip in the family "trip 7". This is great stuff! Thanks JD, and the gang at RC, and AVSIM, for all the posts that led me to the final solution!New card = SoundBlaster Live 5.1 with the drivers that were on the CD. New modem card = USRobotics 56K/V.92.

Don, Glad to "hear" you're up and running with the new soundcard! Now, the fun begins! :-) Don't worry about the Brits, I have a workaround. ;-) Just remember not to exceed 250 kts below 10,000' at any time. You can, however, change the altitude at which this speed restriction comes into play on the options page of RC when you first start it up. Also, there are two other speed restrictions when coming into an airport with approach (maybe without too ). One is the downwind leg at 230 kts max. The other is base leg at 210 max. Bust these speeds on downwind or base and you'll hear about it. lolBest, Rob

Rob,Thx. Well aware of the 250 kt restriction below 10K. The flight last night was about over and must have been on base but ATC was hard to understand when they were asking for a "do not exceed". I knew it was 2 something but could not make out the last digit or two. I was running at 230 (in the UAL 777) at the time so I figured that if I was "chewed out" that it was because they were asking for 210. Oh well, no big thing, it was a RCV3 "test" flight anyway, playing with the options and not concentrating on a "perfect" flight.Regarding ATC voices I did see a few posts on the subject last week and ways to modify the WAV files so that all you get is English for the US. I am going to wait a while and see if it really gets annoying and then consider the change. Another note: I think in the past there was a "bug" with RC or FS for KORD and may have run into it again last night. Will try it again today but have you ever had a problem landing on 22R or 4L using ILS? I am talking about totally handled by "Otto" (Robin) all the way (both coms and plane). Vectored perfectly, picked up ILS, alt. about 2500 AGL, and never descended from there. Flew right over the runway at 2500 feet and kept going. Looks like we never picked up the GS.ATC vectored me around after taking a "missed approach" and I selected good old 9L. Set up for another ILS approach and twas a perfect landing. Have a good one!

i think those runways are localizer only. no glideslope

Don,4L/22R are LOC-only, there's no ILS (no GS). There are too many obstructions in the way for GS to work. You need to use the PAPI/VASI or a plate to land on it. It's a great visual-landing runway to practice with.

Awe, come on, it can't be "no GS"! We gotta blame the software developers at MS or RC for something? The heck with reality, it HAS to be a bug in your logic somewhere. All kidding aside, thanks for the "Oh my God, I didn't think of that" answer. You know I fought the same issue a year ago with Midway (KMDW) for almost a whole day of "go arounds". Never figured out why it would not work and just scrapped the research. Same issue, same answer! Again, it had to be obvious that it was a software problem not reality!Have a great Holiday and New Year!

Yeah, it sucks when reality gets in the way. ;-)