2009-12-11, 08:18
rmhome Wrote:Ah..... right..... Got it. (Attempt to not look like a new XBMC poster-------failed)
Thanks for the link.... Im up and good to go.... much appreciated.
No problem, as we say.. crow.. tastes like chicken
rmhome Wrote:Ah..... right..... Got it. (Attempt to not look like a new XBMC poster-------failed)
Thanks for the link.... Im up and good to go.... much appreciated.
pechspilz Wrote:I'm stuck. There's no Launcher in my ATV menu.
2009-12-12 11:56:21.977 Finder[291] [DEBUG] +[XBMCAppliance initialize]
2009-12-12 11:56:22.009 Finder[291] [INFO] Launcher running in pure mode
2009-12-12 11:56:22.009 Finder[291] [DEBUG] +[XBMCAppliance className]
2009-12-12 11:56:22.319 Finder[291] [DEBUG] +[XBMCAppliance className] called for whitelist check, so I'm lying, m'kay?
Dec 12 11:56:22 AppleTV FrontRow[291]: Failed to allow loading of appliance /System/Library/CoreServices/Finder.app/Contents/PlugIns/XBMCLauncher.frappliance
I was using the v3.2.1 Launcher on a fresh 3.0.1 ATV.
turbinez Wrote:I am using Launcher 3.1 now, but i do not see 3.2 in the downloads list at all. Any benefits to upgrade to 3.2 over 3.1? I am using ATV OS 2.x and xbmc 9.11b2 at the moment.
Should I stick to 3.1 or upgrade to 3.2?
Here we go:
1) "patchstick" the 3.0 ATV
2) ssh into it and download Launcher-3.2.beta3-debug.run
3) install Launcher chmod +x Launcher.. ; ./Launcher-3.2...
4) install XBMC with Launcher or just re-symlink your old install (ln -s /Users/frontrow/Applications/XBMC.app /Applications/XBMC.app)
5) test
wget http://dl.getdropbox.com/u/858897/XBMC/Launcher-3.2.1-debug.run
chmod +x Launcher-3.2.1-debug.run
./Launcher-3.2.1-debug.run
zsoard Wrote:I have followed the instructions multiple times. I was able to ssh into the apple tv and to download beta3. However, I am having trouble with the permission and running the program. Here is the code from terminal.
-bash-2.05b$ wget http://atv-xbmc-launcher.googlecode.com/...-debug.run
--20:19:54-- http://atv-xbmc-launcher.googlecode.com/...-debug.run
=> `Launcher-3.2.1-debug.run.1'
Resolving atv-xbmc-launcher.googlecode.com... 66.102.7.82
Connecting to atv-xbmc-launcher.googlecode.com|66.102.7.82|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1,197,330 (1.1M) [application/x-shellscript]
100%[====================================>] 1,197,330 1.22M/s
20:19:55 (1.22 MB/s) - `Launcher-3.2.1-debug.run.1' saved [1197330/1197330]
-bash-2.05b$ chmod +x Launcher-3.2.1-debug.run1
chmod: Launcher-3.2.1-debug.run1: No such file or directory
-bash-2.05b$ chmod +x Launcher-3.2.1-debug.run
-bash-2.05b$ / Launcher-3.2.1-debug.run
-bash: /: is a directory
-bash-2.05b$ ./ Launcher-3.2.1-debug.run
-bash: ./: is a directory
-bash-2.05b$
I am assuming the 1 after "run.1" is because it was the 2nd time I downloaded the file. Any help would be greatly appreciated!
davilla Wrote:It's "./Launcher-3.2.1-debug.run", Not "/ Launcher-3.2.1-debug.run", see the period and slash are right next to the name.
lorenvazquez Wrote:Hi, I've read the whole Thread and saw most of the people are here because they got an unwanted atv update to either 3 or 3.0.1.
I am actually using an ATV 2.3 with Launcher 3.1 and XBMC 9.04.1 R20677. I was willing to test the new XBMC 9.11 directly downloaded from the launcher downloads.
Should I update to ATV 3.x, Launcher 3.2.1 for this or should I stay as I am and just update XBMC and Boxee? Is there any benefit to update the ATV from 2.x to 3.x?
Thanks and good job with XBMC