I'm sure some of this--if not all, has been addressed in previous posts, but I went 3 pages back and didn't see any reference to them like I was looking for.My box is a Dell PowerEdge 400SC upgraded to P4/3ghz; 2 gb dual-channel DDR (2 1gb sticks push-pull); ATI Radeon 9550 (256mb). RC3xx ran great on this box. RC4 is very slow, comparitively. Yes; I uninstalled RC3. After installing RC4, I defragged the HD, installed the latest FSUIPC 3.51 and AdvDisp; defragged again. Set the "switch" to "realtime" as it was in RC3xx. I not only disabled Norton AV, but removed its boot reference in the registry, which, I've found, I must now do every time I run FS2004 with the newest version of Norton. Thanks, Symantec, for trying to invade my computer!Overall; it seems to take a long time to respond to keyboard commands. And the pilot/controller speech seems extremely deliberate and disjointed at times, as if the new pilot/controller voice tracks weren't tightly edited. I push 7, for example, to ack...and it takes several seconds for the pilot to respond. Same thing when I check "pilot reply." Anyone else with this problem?On the other hand; I like the new interface and addition of new procedure features. But it seems very plodding, compared to the last version.Don't worry; it's not coming off my computer. I'll check a few other things and see if that improves the speech.sean hall

Sean,With a PC of that power you shouldn't have any problems running RC4 and FS9. When you say you set the switch to 'realtime' can you please clarify that? You shouldn't set the priority of any program higher assuming you're running XP. Standard priority is just fine.On a single PC RC responses should be more or less instantaneous. That's certainly the case on my 2year-old P4 3.0, 1GHz RAM, ATI 9800 Pro running XP SP2.Cheers,

hi ray:i'm running 2k sp4. "switch" in shortcut looks like this:"C:Program Filesrcv4rcv4.exe" /realtimei'll remove the "realtime" and see what happens, but it was kinda slower before that. sean

i definitely wouldn't do realtimeare there any other programs you might be running to capture keystrokes, that might be slowing things down? spyware? logging software?there are a couple of places where slow keystroke detection may occur, but they are in very specific locations, and only a couple.jd

To avoid you having to edit the registry try to locate these:EndItAll - you set profiles of what to kill. You need to reboot after FS use to get it all working. You can get version 2 by subscription to PC Magazine utilities but version 1 (I use) is floating arount the net.FSAutoStart - freeware here on AVSIM by Ken Salter. You set up things to kill and start with FS and when your done it resets everything without a reboot.PC Mag's StartupCop. For more "profiled permanent" startup preventions on bootup. It moves registry starts to a temporary registrry folder and back.I use Enditall without issues but be careful of what you allow to kill. For NAV kill the file called CAPP.EXE and if you get a runtime error just say OK and go on.