Posts: 68
Joined: Dec 2009
Reputation:
8
alexpigment and smithr99-
If it was an issue with the <rompath> having spaces, wouldn't it cause issues when launching the emu directly from the <application> line in launchers.xml? htpc guy said he can launch it perfectly when he calls it our directly (from <application>), but it's when he puts the emu path in the <args> area and the launcher.sh file in <application> that he has problems. This is my experience also. Again, I'm new and my logic doesn't always translate.
rausch101-
Am I missing something in the angelscry posts that has to do with this stuff? Forgive me if I'm overlooking something.
Thanks again for the help.
Posts: 89
Joined: Jul 2007
Reputation:
0
2010-11-02, 02:10
(This post was last modified: 2010-11-02, 02:48 by waverz.)
I finally got it working....
Posts: 68
Joined: Dec 2009
Reputation:
8
Malte,
I'll give it a try when I get home... Thanks.
I was under the impression that XBMC Live Dharma Beta 3 ran on a minimal install of Linux and when XBMC was killed, Linux was still running to handle the windows. Is this not correct?
Posts: 1,650
Joined: Jan 2010
Reputation:
138
malte
Skilled Python Coder
Posts: 1,650
Did you try to run the command without XBMC in the background from command line?
You could also try to check the command that is passed to the launcher.sh. Modify your launcher.sh like this:
/usr/bin/killall -STOP xbmc.bin
echo "$@"
"$@"
/usr/bin/killall -CONT xbmc.bin
If you fall back to the console after trying to run the emu, you should see the command in the console.
Posts: 68
Joined: Dec 2009
Reputation:
8
Adding the windows manager fixed my problem. When I launch the emu (whichever one I'm using... mupen64plus, mednafen, zsnes), it no longer just blinks back to XBMC. The sound on mupen64plus seems to be better as well. Thanks for all the help everyone!
Also, just out of curiosity, is there a command I can use to check if XBMC has been killed when I'm running one of the emus?