Computer not shutting down via WideFS

[A320 East]

Hi Peter,

Hoping you can help. One of my sim computers will not shut down via Wide Client. I have 11 in the network and use RunReady, CloseReady and AllowShutdown commands to start up and shut down my sim network. I use registered versions of FSUIPC 3.75 and WideFS 6.75. All machines are running XP Pro and all are identical Compaq EVO P4 1.7Ghz units set up the same to optimize performance, save for the server which is an HP/Compaq P4 3Ghz machine. I run FS9.1, the full PM suite including both MCDU's and instructor station, and FS Communicator, all machines are using TCP protocol and I have no other connectivity problems.

The machine running FSCommunicator and Wide Client is the offending party. When I use the PM MCDU to "Shut down all PC's" all do so except this one. FSCommunicator closes but the PC doesn't shut down, rather just sits idle. There are no error messages and pressing the power button on the front panel shuts it down immediately....

Any thoughts?

Regards,

Christopher Coote

Halifax, NS Canada

[Pete Dowson]

The machine running FSCommunicator and Wide Client is the offending party. When I use the PM MCDU to "Shut down all PC's" all do so except this one. FSCommunicator closes but the PC doesn't shut down, rather just sits idle. There are no error messages and pressing the power button on the front panel shuts it down immediately....

Are you using UDP protocol, or TCP? I get this on one or sometimes two (out of 8) PCs on my cockpit occasionally, but more often using UDP where, I think, the blocks get lost in the confusion of traffic with others closing. It seems quite rare with TCP here, though it can happen. And it isn't always the same PC.

All WideClient can do is issue the instruction to Windows, requesting the shut down. Have you checked in the Windows task manager on that PC (CTRL_ALT_DEL) to see if there is something running still, stopping the shutdown? See if it shuts down without FSCommunicator running (i.e close that first, then do the full shut down).

Regards

Pete

[A320 East]

Thanks Peter,

As mentioned my net is using TCP (specified in the WideClient.ini file) and each machine has it's own specific IP of course.

I have never had this happen on any other machines and I've even wiped this one and reinstalled a fresh copy of XP, WideFS and FS Communicator but to no avail.

I'll try your suggestions tonight and report back.

Is there any other way I can tell Windows to shut down when FS Comm closes? I'm pretty new at PC's - been a MAC guy all my life and only bought the PC's for the sim project starting last Nov. so I'm still really green with them.

[Pete Dowson]

I have never had this happen on any other machines and I've even wiped this one and reinstalled a fresh copy of XP, WideFS and FS Communicator but to no avail.

WideClient will certainly be issuing the command to Windows -- assuming your parameters in the INI are the same as in the other PCs. Something is preventing Windows from closing.

I've had problems like that, completely separately from and nothing to do with anything FS-wise. It was more frequent on Windows 98 and before, but it does still happen with WinXP too. I think it is some service, driver or other background activity which won't close for some reason. How you find out which and how to stop it is difficult. Trial and error usually.

From what you said I thought WideClient had actually teminated, but check that first -- via the task manager (you can't tell just by whether there's a Window there or not. Apps can close their windows yet still be running). If it is still running and FSComnunicator is the only app, it may be that this is somehow tying up WideClient. There are parameters you can use to stop that (slowing FSCommunicator down by idling in between calls), but this really hasn't been necessary on any App I know of for a long time.

Is there any other way I can tell Windows to shut down when FS Comm closes? I'm pretty new at PC's - been a MAC guy all my life and only bought the PC's for the sim project starting last Nov. so I'm still really green with them.

I don't know if there are any other programs which will do this for you. There are several programs to start things up automatically, but I don't know about closing the system itself down.

I have a Master power switch on the wall, where the whole cockpit -- PCs, control boards, panels ,etc - can all be switched off. I just ruthlessly switch the lot off there even if one or two are stuck on. If they are idling in any case it does no harm.

Regards

Pete

[A320 East]

All great advise Peter - many thanks and I'll update you when I get home and investigate further.

I too have a main switch on my rack distribution / filter unit that shuts AC down for the entire mess. It's also my startup master and works so very well because of WideFS! From reading some posts on other forums I'm surprised that not everybody uses this method to start and shut down their sims - some peoples setups must be a nightmare...! :shock:

I did turn off the AC mistakenly to my server before it had shut down one time and it wouldn't start after that - had to wipe the drive and do a complete reinstall so I'm very gunshy about just flipping off the mains before all has shut down on it's own.

[A320 East]

Good Day Peter,

Here is what I found after some experimentation....

Using the task manager I checked that there was nothing else running that wasn't running on any other machine - all was in order - same processes going on as on all other machines. Strangely though, with the task manager open and the "MCDU shut down" command given the machine shuts down as it should along with all the others.... (maybe I should have the task manager going all the time!!)

With the shut down command issued via the MCDU:

-FS communicator and WideFS both shut down but the machine doesn't.

-If FS communicator is not running the machine shuts down normally.

If a restart or shutdown command is initiated via the start menu on that machine with both WideFS and FS Comm running both programs close but the machine stays running. Issuing a second shutdown or restart command then shuts it down.

So it would appear that perhaps the problem is related to FS Comm itself. I'll email Robert and present the problem to him to see if he's been made aware of it or ever run accross it.

Thanks Peter for your prompt help and also for the great software!

Kindest Regards,

Christopher

[A320 East]

Hey Peter,

With the update to WideFS 6.757 the computer running FS Communicator now shuts down normally with all the rest.

Many thanks for keeping this in the back of your head and providing a solution to the issue.

Hope you're having a great relaxing time!

Christopher