Fleet Ops Process Ended Twice Before It Shut Down
Program aborts? Network configuration? Graphic errors? Bugs? Post your question here.
posted on November 9th, 2012, 12:07 am
I started a game where I had to leave suddenly and didn't have time to close out the application properly. It started with me thinking that I would be back in a couple of minutes, but then I realized I wouldn't be able to come back.
So I went into Task Manager and shut down Tunngle, Fleet Operations and TeamSpeak, but when I came back, I found Fleet Operations was still running and the game was comming to an end. First off, why didn't shutting down tunngle disconnect me, and secondly, why is it that I had to end the Fleet Ops process TWICE before it finally shut down!?
So I went into Task Manager and shut down Tunngle, Fleet Operations and TeamSpeak, but when I came back, I found Fleet Operations was still running and the game was comming to an end. First off, why didn't shutting down tunngle disconnect me, and secondly, why is it that I had to end the Fleet Ops process TWICE before it finally shut down!?
posted on November 12th, 2012, 5:12 am
To the first question:
While I don't know how FO interacts with Tunngle, it's likely that Tunngle just finds things, it doesn't do any actual communication. It just finds the appropriate IPs and hands them off to FO which does the rest. But I could be completely wrong.
To the second question: How did you end it? Did you use the Applications tab (the first one) or the Processes tab (the second one)?
If you used the former then that's like clicking the close button; it sends a message to the app saying "it's time to shutdown". If the program doesn't respond then after some time Windows marks the program as unresponsive and the next time you try to close it Windows will just kill it.
In the latter case, that just kills the process dead. The program receives no notification that it's being terminated.
While I don't know how FO interacts with Tunngle, it's likely that Tunngle just finds things, it doesn't do any actual communication. It just finds the appropriate IPs and hands them off to FO which does the rest. But I could be completely wrong.
To the second question: How did you end it? Did you use the Applications tab (the first one) or the Processes tab (the second one)?
If you used the former then that's like clicking the close button; it sends a message to the app saying "it's time to shutdown". If the program doesn't respond then after some time Windows marks the program as unresponsive and the next time you try to close it Windows will just kill it.
In the latter case, that just kills the process dead. The program receives no notification that it's being terminated.
posted on November 12th, 2012, 8:41 am
afaik killing the tunngle gui process won't disconnect you from games.
look for the tunngle service called tnglctrl.exe (it's set to manual, so it only runs when needed), I think that's what deals with the tunngle adapter and provides actual connections to the other players (once the main gui process has selected a room).
look for the tunngle service called tnglctrl.exe (it's set to manual, so it only runs when needed), I think that's what deals with the tunngle adapter and provides actual connections to the other players (once the main gui process has selected a room).
posted on November 12th, 2012, 3:13 pm
I shut down using the process tab. And I know how to use Task Manager. But there is no reason I should have to end the Fleet Ops process TWICE before it actually shuts down.
Who is online
Users browsing this forum: No registered users and 12 guests