QUOTE(juju2 @ May 23 2008, 10:55 AM)
In this mode, the log is in standard XBMCSM window in "Operations" tab into text zone. It's something like that
---- EXCEPTION TRACEBACK ----
---- END TRACEBACK ----
If you want the log in a file (xbmcsm.log in intallation directory), add "l" option :
"disk:\path to xbmcsm\xbmcsm.exe" dl
But I see what's the problem now : on prevois versions, Internet connection was tested with a dummy HTTP request on google.com (provided by a Python standard function) : it's a very heavy method, so I replaced it by a simple ping request which fails for some reason and "Download" checkbox is grayed when ping doesn't work.
BUT this doesn't affect SVN synchro (a little bug, normally it's skipped) that works : so you can see SVN updates but you can't download them....
For your problem, you can download this
(replace your library.zip file into your xbmcsm 0.6 installation directory) : this a updated version which doesn't gray download checkbox any more, so you should
be able to download SVN skin (I'm not sure about HTTP ones) and tell me if you obtain a traceback, because I don't see why the ping fails
Well, the new library.zip let me download the SVN skins, but not the HTTP skins, as suspected. Also, I tried it out on the laptop running XP, and it works fine there (original library.zip), so we can rule out the router blocking the ping. It must be related to Vista, or the firewall (unlikely, as it was disabled, but I suppose it's possible it doesn't quite disable itself all the way... I've seen that before).
There must be someone else out there that has tried this with Vista... anyone?
Or, anyone using it with Norton Internet Security (successful or not, we need to rule one of them out).
QUOTE(juju2 @ May 23 2008, 04:45 PM)
I thought about something else : the ping timeout is a bit short (1 second) try to execute
And see if response time is > 1000ms
Ping ranged from 40ms to 44ms, and that was with Second Life running on another computer, and Azureus running on this one. Doesn't look like that's the problem.
Oh, I got NOTHING in the log other than the standard messages, btw. Could you verify that the command-line is "xbmcsm.exe d"?