kdf, i respect you quite a bit, but that really was over the top. i think you need a vacation from slim or something. i like the slim stuff, and i understand that those like you who contribute code to it have a personal feeling of ownership over it, but like i said long ago this is a consumer product sold for profit first and foremost, not some high school hobby open source playground. the high priests of the forum really need to separate their feelings from criticism leveled at a sold for profit product.
and i def take issue with you attacking arnold, b/c not only is it out of place in the thread and the forum, but there's no reason to think the prof doesn't share your political views. i don't and its irritating to be insulted by just reading your rant. and professor, i do think you're also a bit, shall we say, petulent. your response [seemingly] to my post was to say: "...have suggested that resetting the device is the "obvious" answer. I don't think these users have actually encountered the problem. Physically power cycling the Transporter "apparently" cures the problem, only to have it recur when one tries to play another file..." well fine, but i didn't see that mentioned in your first post, was it? people are just trying to help. and there are many such issues that a DL could cause havoc with, not just this one. why should this one issue get a warning and not others? how many should be posted? how many is practical? did you ever call slim and did you downgrade? -- MrSinatra www.LION-Radio.org Using: Squeezebox2 (primary) / SBR (secondary) / SBC - w/SC 7.2b - Win XP Pro SP3 - 3.2ghz / 2gig ram - D-Link DIR-655 ------------------------------------------------------------------------ MrSinatra's Profile: http://forums.slimdevices.com/member.php?userid=2336 View this thread: http://forums.slimdevices.com/showthread.php?t=52514 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
