2011-02-13, 23:31
malte Wrote:Not sure if this fits in your situation but an RCB user had the exact same error message and solved it by adding "explorer" before the XBMC launch command. I guess this shifts the control of the process and with this the lock on the log.file to another process. See his post here: http://forum.xbmc.org/showpost.php?p=715...tcount=992Thank you for the advice Malte. It effectively allows the correctly close XBMC without killing the running .bat file, but the .bat command windows is not anymore hidden. But it give me some ideas. Thank you.