Posts: 13,714
Joined: Mar 2010
Reputation:
509
PatK
Team-Kodi Member
Posts: 13,714
Should work, perhaps the timeout needs adjustment.
taskkill /f /im XBMC.exe
ping 1.1.1.1 -n 1 -w 3000 > nul
"C:\Program Files (x86)\XBMC\XBMC.exe"
See what that does for you.
Posts: 13,714
Joined: Mar 2010
Reputation:
509
PatK
Team-Kodi Member
Posts: 13,714
It's the command script I have for a restart and it does work, there was an explanation in the forums for the ping, I suggest you search it up. I'm sure the OP saw the differences between the script and would change the drive letter to fit his circumstances, I'm not custom scripting.
The user is not running Linux (at least I presume, given this is a windows XBMC support forum), glad you can test for a operational executable, windows programmers rely heavily on timed loops, I'm sure there is a way to discriminate but I'm not a script kid.
Posts: 458
Joined: Aug 2010
Reputation:
14
If it's stopping XBMC, then the batch file is at least starting and partially running. Which would mean that the scheduler is choking on something in the batch file. Probably the quotes where you restart it.
You can always put a PAUSE at the end of your batch file (ensuring the windows doesn't start minimized or such) and see what error it throws back at you.
HP Stream Mini w/Libreelec -> HDMI -> Toshiba 37"
Intel NUC8i3BEH w/Libreelec -> HDMI -> LG OLED55C3PUA -> S/PDIF -> Sony HT-CT80
Dell Optiplex 7050 Micro w/Libreelec -> HDMI -> Yamaha RX-V467 -> HDMI -> Toshiba 47L7200U
Posts: 19,982
Joined: May 2009
Reputation:
451
nickr
Retired Team-Kodi Member
Posts: 19,982
You can always put a PAUSE at the end of your batch file (ensuring the windows doesn't start minimized or such) and see what error it throws back at you.
If I have helped you or increased your knowledge, click the 'thumbs up' button to give thanks :) (People with less than 20 posts won't see the "thumbs up" button.)