dean Wrote: > Sorry that it's not working for you, and thanks for taking the time > to debug this.
Oh, you know, we love our squeezebox and the people that bring it to us. *hug* > On Mar 17, 2006, at 7:42 PM, trebejo wrote: > > Sooo undocumented. > Well, it's in the normal place for Preference Panes on OSX. Regular > folks shouldn't have to dig down here, so there was no reason to > document the file layout for accessing it via Terminal. > I think the very events that I'm describing justify documenting alternative boot schemes somewhere, so that people don't waste their time hunting down phantoms (like I did with my poor network). For example, I read somewhere (can't remember where) that if your squeezebox is showing up with an IP address that begins with "169", then you've got a network problem. That's good to know. Also, consider this: at the moment, I don't mind one bit using the terminal to boot slimserver; in fact, I think it may well become the way I do things from now on. However, I would LOVE to get a refund on the hour(s) I spent wondering what I needed to do to fix it, but mere humans don't have access to the rewind hands on the big clock so that's that. Open source empowers you to tell the enduser as much as he is able to handle. I suppose that by leaving /longpathname/Installation.txt in the distro, you did just that for a guy like me, I suppose, but even a guy like me could use a "Here is how everything works" paragraph in an obvious place. > Please try downloading and reinstalling SlimServer from the Slim > Devices website. It's possible there's some kind of corruption in > the original install. Also, try setting it to not start up > automatically, then set it again to do so. Well, that's what I already did. Tried 6.2.1 and 6.2.2 (the nightly). Same symptom on both. The install *seems* to be ok. When booted from the command line, it works fine. I can see all my albums and do all my usual stuff. I just can't start by clicking on "start server" in the preference pane, or by setting that to boot automatically at boot time. The only change that has taken place that I can think of has been that wednesday-night Tiger update. I am borderline certain that something got broken there, probably by Cupertino. Nonetheless, there is a robustness issue here. Everything is ready to go--network, squeezebox, slimserver--and it all comes to a halt because the "start" button is temporarily fritzed out (just to make it that much easier to question my sanity, the other preference pane buttons that I clicked on worked as they should). It's like cancelling a moon launch because the taxi driver taking the astronaut to the space center gets a flat tire... this merits a separate thread, I'm sure, but when the box stopped working I realized that its dependence on "virtual" factors in comparison with a braindead CD player is still a cause for concern; by putting in little debugging steps, you can make the experience a lot saner for the end user. Anyway, I *am* running all that I need to run when I run /longpathname/slimserver.pl, right? Cheers, Ariel -- trebejo ------------------------------------------------------------------------ trebejo's Profile: http://forums.slimdevices.com/member.php?userid=730 View this thread: http://forums.slimdevices.com/showthread.php?t=22188 _______________________________________________ Discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
