2011-02-13, 22:12
jroeben Wrote:The batch on its own works without a problem.I have spend more than 4 hours trying to fix this. That's a crazy problem...
However, when I call the batch from Advanced Launcher, I get an "Capplication:: create() failed - Check log file and that it is writeable" error.
I am NOT trying this over RDP and, as I said, the batch itself works without a problem if run manually. I have also tried to call a second batch instead of running XBMC directly from the first batch, same result. Running xbmc.exe without the "start" doesn't help, either.
The problem is that the started application (or .bat file) still linked to XBMC. So even when we close XBMC, the xbmc.log file still opened and linked to the active .bat file. When we restart XBMC, the application cannot open the xbmc.log file (because it is already opened) and generate the XBMC error "Check log file and that it is writeable".
Using taskKill /f /t /im XBMC.exe command line allows to force to close all the depend files and child process of XBMC... but unfortunately it also close the .bat file before it had time the start the applicaton.
There is also a way in python to "detach" a process (the .bat file) from the parent process (XBMC): make them independant. But... it is not working due to a bug of the python version included into XBMC.
So... the actual version of Advanced Launcher not allows to close XBMC from external scripts.
I will try... again... to found another way to start applications under windows and hope that the command line support will still fully functional. Sorry...