"FSUIPC Wait" - RC Hangs in flight

[northridge]

XP Sp3 FS9.1 FSUIPC Reg RC4.3 on WideFSHappening more and more often now, I input a keyboard command on the Server machine and after a long delay I get the RC message "Fsuipc_wait Cant get 0008 to change from 10533546 always 10533546".RC, minimized on the Client in flight, wont maximise and is effectively dead: I get no more contact. Sometimes I realise its hung because it wont respond to a command, and sometimes because it goes silent for so long I wake up and notice.On a cupla occasions RC has remained dead, but mostly it comes back - after random amounts of time. And its happening more and more.

[Ray Proudfoot]

Hmmm. Assuming you've made no other changes to your FS setup my first thought would be is your network playing up? FSUIPC, FS9 and RC4.3 are so established I feel the problem lies outside those applications.

[ronzie]

Try this with just FS9 and RC running to keep CPU and network loads at minimum. What else is on the RC client pc that is using WideFS?It sounds like your host or network is too busy to allow RC communication or FSUIPC might be overloaded.Be sure you are running with the latest FSUIPC links in the pinned forum topic.There are many threads regarding this. Search the forum for "fsuipc_wait" to come up with a list. In some solutions in FS9 turning off FS ATC (does not affect AI) helped. To do this in FSUIP3 in your modules folder back up FSUIPC.ini in another folder and renaming it to fsuipcxx.ini. Now in the General section add the following:RemoveATC=YesSee what happens.

[northridge]

Terribly lazy and no excuse - should have searched.I thought straight away that this was a "my hardware" problem rather than anything else: my Server has not been well for some time and is running a weaker-than-desirable Mobo and ocasionally does some very strange things.Also running on the Client is ASA and FSCommander: I have canned chatter on and Im not sure why but FS atc was on too.Ill try some of the suggestions in the linked threads.Thanks.

[ronzie]

ASA, RC, and FSC running on your client can cause quite a network load. FSC has a moving map and ASA does frequent weather writes. Is it ASA or ASE? RC also needs updates quite frequently with lots to read such as AI tables, your position updates, and weather reads from FS itself.That plus your server problems can cause quite a few delays.On your server, try that RemoveATC=yes statement in FSUIPC.ini as that is a bit more thorough than just disabling FS ATC in its menu.Regarding your server slowing down look for processes you don't need while in FS. Since your on a network unless you can kill your Internet connection you need to maintain your security services.If you want to do this here is a link to an application that displays process CPU loading and RAM use. It is a free app from sysinternals, now under Microsoft:http://technet.microsoft.com/en-us/sysinternals/bb842062 are all the utilities nice to have on hand.http://technet.microsoft.com/en-us/sysinternals/bb896653 is the utility I use. You can customize it polling frequency. You can set it up so physical RAM use %, CPU use %, are in its bottom status bar. Now with FS running, your CPU will be maxed out. I just use the top window pane. You can look for a RAM overload and set up the paging (RAM to disk for virtual memory). You can add columns for the ram use in bytes for each process, do an I/O byte count for each process, etc. I don't usually do the the separate graph display. Hovering the mouse over a service/application name will show you what is running. For instance there will we several svchost.exe names in the left column and hovering the mouse over that will bring up a hint of what that entry is running. The same is true for rundll32.exe.You can see what resources are being used by applications/services on both your host and client and take steps maybe swapping different apps among pcs for the best efficiency. Just set FS not to pause on task switch and then alt-tab to process explorer frequently to look at loading.I use the free AVG antivirus version and I load Process Explorer on startup. It shows me when AVG spawns its different processes some taking 100% CPU a few minutes after boot and I don't use the PC until after those intensive update/scan services are done. On my P4 3.2GHz Win XP SP3 that takes about ten minutes before CPU loading is normal. While Process Explorer is running it shows CPU minigraph in the task bar. After AVG is done and disk writes quiet down I shut down PE.A handy tool for trouble shooting RAM, CPU, and network requirements.If you kill or restart a process be sure you are careful. Have a sys restore ready just in case. I have not had a problem when occasionally hanging the pc by killing the wrong process and just the usual reboot recovery process worked fine.