home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Support
Installation, configuration support
Restart MediaPortal on resume
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="craigparris1" data-source="post: 613499" data-attributes="member: 75254"><p>Hi guys,</p><p></p><p>OK, I still haven't had a chance to test this on my own MP setup, but I did just take a moment at work to knock up a quick .Net app which essentially replicates what MediaPortal is doing - that is, my app does this:</p><p></p><p>1. starts up with a form containing a single button</p><p>2. click on the button - it runs a vbscript the same as MP's restart.vbs</p><p>3. the vbscript attempts to kill the running app, then restart it again</p><p></p><p>If I start the .Net app, then run the script in a separate command prompt window, it kills the app and then restarts it. If I use the button within the app to run the script, then it kills the app but does not restart it (log entries are the same as those users who are having MP restart problems - the kill command is logged, then no more entries).</p><p></p><p>If I remove the /T parameter from the "taskkill" command, then use the button to run the script, it kills the app and restarts it successfully (with log entries as expected).</p><p></p><p>I believe, therefore, this proves my earlier suggestion that the /T parameter is killing MediaPortal AND the restart script, so it never actually gets to the line in the script to start MediaPortal again.</p><p></p><p>My next suggestion would be to remove the /T parameter on "taskkill" in the restart.vbs script file, and monitor how that goes. Obviously, removing the /T will also mean that other child processes started by MediaPortal (aside from the restart script) will also not be terminated (and may then have duplicate instances started when MP starts again), but I don't know if this will actually be an issue or not. Plug-ins and the like should be instantiated as objects from DLLs, so they should be automatically killed when MP closes - it will be a possible problem where users have 3rd-party players or things that MP might not automatically close.</p><p></p><p>Anyhow, I do know that my own system has "tskill" on it, so I haven't personally experience the "taskkill" problem ..... but I'm also not aware of any stray executables where I have multiple copies running because MP keeps starting new ones. And my MP box is pretty much suspended and restarted just about every day (and invariably I'm on the console from time to time, and have never come across multiple instances of orphan processes).</p><p></p><p>Cheers,</p><p>Craig</p><p></p><p>In fact, if I can work out how to log this is a bug, I will do so.</p><p></p><p>Cheers,</p><p>Craig</p></blockquote><p></p>
[QUOTE="craigparris1, post: 613499, member: 75254"] Hi guys, OK, I still haven't had a chance to test this on my own MP setup, but I did just take a moment at work to knock up a quick .Net app which essentially replicates what MediaPortal is doing - that is, my app does this: 1. starts up with a form containing a single button 2. click on the button - it runs a vbscript the same as MP's restart.vbs 3. the vbscript attempts to kill the running app, then restart it again If I start the .Net app, then run the script in a separate command prompt window, it kills the app and then restarts it. If I use the button within the app to run the script, then it kills the app but does not restart it (log entries are the same as those users who are having MP restart problems - the kill command is logged, then no more entries). If I remove the /T parameter from the "taskkill" command, then use the button to run the script, it kills the app and restarts it successfully (with log entries as expected). I believe, therefore, this proves my earlier suggestion that the /T parameter is killing MediaPortal AND the restart script, so it never actually gets to the line in the script to start MediaPortal again. My next suggestion would be to remove the /T parameter on "taskkill" in the restart.vbs script file, and monitor how that goes. Obviously, removing the /T will also mean that other child processes started by MediaPortal (aside from the restart script) will also not be terminated (and may then have duplicate instances started when MP starts again), but I don't know if this will actually be an issue or not. Plug-ins and the like should be instantiated as objects from DLLs, so they should be automatically killed when MP closes - it will be a possible problem where users have 3rd-party players or things that MP might not automatically close. Anyhow, I do know that my own system has "tskill" on it, so I haven't personally experience the "taskkill" problem ..... but I'm also not aware of any stray executables where I have multiple copies running because MP keeps starting new ones. And my MP box is pretty much suspended and restarted just about every day (and invariably I'm on the console from time to time, and have never come across multiple instances of orphan processes). Cheers, Craig In fact, if I can work out how to log this is a bug, I will do so. Cheers, Craig [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
Installation, configuration support
Restart MediaPortal on resume
Contact us
RSS
Top
Bottom
