PDA

View Full Version : 6.2.2. OK now! This is fun! NOT!



tonymuffin
2006-04-27, 17:21
Got the email today to upgrade to 6.2.2. Well, did so. The device is saying to press BRIGHTNESS to update the firmare. It goes through the process of connecting to my machine. It cognizes the IP address and the machine it needs to connect to. However, just before it connects it starts all over again saying Press BRIGHTNESS to update firmware. It has been doing this now in a loop 6 times. This is special!!!!

tonymuffin
2006-04-27, 17:29
Ok...this is now getting really good!!!

All 3 of my Slim Devices (2 wired and 1 wireless) are exhibiting the exact same behavior.

Now... this is really special! NOT...........

snarlydwarf
2006-04-27, 17:32
Then it sounds like your server is crashing for some reason: do you have a 3rd party plugin, perhaps, that isn't happy with some change? Look at the server logs and see what it says.

tonymuffin
2006-04-27, 17:34
Then it sounds like your server is crashing for some reason: do you have a 3rd party plugin, perhaps, that isn't happy with some change? Look at the server logs and see what it says.

Nope! No 3rd party plug ins...

PS....what logs?

kdf
2006-04-27, 17:38
Did you have 6.5 installed at some point? This sounds like an issue
there, where a couple plugins were interracting with the firmware
upgrade. Theoretically, this isn't possible with 6.2.2 but just in
case, if you have Trackstat or the Execute plugins installed, remove
them temporarily.
-k

dean
2006-04-27, 17:38
Ok, Tony, you press and hold the brightness button. do you see the
progress bar move across the screen? Does it then tell you that it's
going to take a minute?

Also, what kinds of players do you have (Squeezebox2, Squeezebox v3?
The sticker on the bottom will say.)

Also, what OS is slimserver running on?

tonymuffin
2006-04-27, 17:41
Did you have 6.5 installed at some point? This sounds like an issue
there, where a couple plugins were interracting with the firmware
upgrade. Theoretically, this isn't possible with 6.2.2 but just in
case, if you have Trackstat or the Execute plugins installed, remove
them temporarily.
-k

Per my previous thread............ no plug ins....

tonymuffin
2006-04-27, 17:44
Ok, Tony, you press and hold the brightness button. do you see the
progress bar move across the screen? Does it then tell you that it's
going to take a minute?

Also, what kinds of players do you have (Squeezebox2, Squeezebox v3?
The sticker on the bottom will say.)

Also, what OS is slimserver running on?

Correct... I press the Brightness button down just like any other time it has needed to update the firmware. Nope... not this time... there is no progress bar, it jumps immediatly to Welcome to Squeeze box and then obtaining an IP address. It obtains an IP address and then moves on the finding the IP address correctly of the Slim Server. It then says connecting to Slim Server and starts all over again.

By the way.... If I do nothing after pressing the Brightness button it will cycle through all on it's own... get to the same place and start all over.

Special huh? I am really curious how this stuff is tested??

All 3 are Squeezebox 2
OS: Windows XP Pro Service Pak 2 with all current critical updates and security patches.

tonymuffin
2006-04-27, 17:53
OK............

So obviously this isn't getting anywhere...

How do I get back to point A. Where can I find the previous version?

tonymuffin
2006-04-27, 17:57
Where Are The Log Files???????????

radish
2006-04-27, 17:58
They're all here

http://www.slimdevices.com/downloads/

tonymuffin
2006-04-27, 18:00
Did you have 6.5 installed at some point? This sounds like an issue
there, where a couple plugins were interracting with the firmware
upgrade. Theoretically, this isn't possible with 6.2.2 but just in
case, if you have Trackstat or the Execute plugins installed, remove
them temporarily.
-k
NO.... the previous version was 6.2.1

dean
2006-04-27, 18:09
On Apr 27, 2006, at 5:44 PM, tonymuffin wrote:
> Correct... I press the Brightness button down just like any other time
> it has needed to update the firmware. Nope... not this time... there
> is no progress bar, it jumps immediatly to Welcome to Squeeze box and
> then obtaining an IP address. It obtains an IP address and then moves
> on the finding the IP address correctly of the Slim Server. It then
> says connecting to Slim Server and starts all over again.
Hm, that sounds like the behavior of pressing the POWER button.
Very strange.

> By the way.... If I do nothing after pressing the Brightness button it
> will cycle through all on it's own... get to the same place and start
> all over.
>
> Special huh? I am really curious how this stuff is tested??
It's tested very carefully, both here at our offices and also in the
field by our community.

This is the first time we've heard of this particular issue. If we
had a report of this before, we certainly would have resolved it
before shipping 6.2.2.

If you want to downgrade, the older software versions are available
here:

http://www.slimdevices.com/downloads

But the player should be able to upgrade. Please feel free to get in
contact with support (AT) slimdevices (DOT) com for one-on-one support.

One thing that does surprise me, though, is that you have more than
one player that is showing this behavior. That makes me suspect

dean Wrote:
>> Ok, Tony, you press and hold the brightness button. do you see the
>> progress bar move across the screen? Does it then tell you that it's
>>
>> going to take a minute?
>>
>> Also, what kinds of players do you have (Squeezebox2, Squeezebox v3?
>>
>> The sticker on the bottom will say.)
Please answer this question.

>> Also, what OS is slimserver running on?
Please answer this question.

Finally, one more question: what firmware version is on the player
now? (or alternatively, what version of SlimServer were you running
before.)

-dean

tonymuffin
2006-04-27, 18:14
- Nope.... it is the Brightness button
- hmmmmmmmmmmm
- one would think..........
- Suspect of what? All was well prior to installing 6.2.2 this evening. I was playing and have been playing music right up to that time just fine.......
- already answered your other questions in green. Read my previous posts...
- I have no idea what firmware version is on the player right now. How would I tell??
- already answered the question as to what version I was running......
- I have attempted to contact your tech support in the past for issues and they do not typically respond....


Again....where are the log files??????????????/

dean
2006-04-27, 18:21
Ok, please get in contact with support (AT) slimdevices (DOT) com for one-on-one
support.

tonymuffin
2006-04-27, 18:27
OK.... how about this?????

Just installed 6.2.2 on another one of my computers...guess what???? Same F*&^%$#g thing

tonymuffin
2006-04-27, 18:33
Ok, please get in contact with support (AT) slimdevices (DOT) com for one-on-one
support.

hmmmmmmmmmmmmmmm.... ok... apparently you didn't read the last part of my previous post

Cronos
2006-04-27, 18:37
Perhaps you should try again.

tonymuffin
2006-04-27, 18:41
Perhaps you should try again.
ummmm...errrrrrrrrr...uhhhhh...hmmmmmmmmm... try again what?

kdf
2006-04-27, 18:44
The software is well tested and is working well for the large numbers
who have been testing for the last 5 months of daily builds. I think
it is very clear that this is not the standard outcome, and we are all
interested in trying to help find the root problem. I understand that
you have no plugins, and I had posted before you answered the other
posts, so please have a bit of patience.

You have people here trying to help, and you are barking back at
everyone. If you want help, please try to answer the questions and
remain calm.

Try looking in the windows event viewer (control panel, administrative
tools). If slimserver has been crashing, you will see something in
there (look for slim.exe). If you are not using windows, please let us
know and we can point you to the right location for log information.


or, ry opening up a command prompt window (start->programs->accessories)

then run:
c:\program files\slimserver\server\slim.exe

When you try to update, you'll see any problems show up in the command
prompt window.

hope that gets us a step further.

-kdf

tonymuffin
2006-04-27, 18:45
Once again.... where are these log files?????

By the way... Slim Server is up to it's old tricks again of pegging the CPU

CPU: Intel 3.2 Ghz
RAM: 1GB
HD: 250GB

tonymuffin
2006-04-27, 18:50
The software is well tested and is working well for the large numbers
who have been testing for the last 5 months of daily builds. I think
it is very clear that this is not the standard outcome, and we are all
interested in trying to help find the root problem. I understand that
you have no plugins, and I had posted before you answered the other
posts, so please have a bit of patience.

You have people here trying to help, and you are barking back at
everyone. If you want help, please try to answer the questions and
remain calm.

Try looking in the windows event viewer (control panel, administrative
tools). If slimserver has been crashing, you will see something in
there (look for slim.exe). If you are not using windows, please let us
know and we can point you to the right location for log information.


or, ry opening up a command prompt window (start->programs->accessories)

then run:
c:\program files\slimserver\server\slim.exe

When you try to update, you'll see any problems show up in the command
prompt window.

hope that gets us a step further.

-kdf
Problem: There is already another copy of the SlimServer running on this machine. (Unknown error)

I assumed you meant to shut down SlimeServer prior??

tonymuffin
2006-04-27, 18:53
Ok.... so I have now shut down SlimServer, confirmed it is not running... attempted to run at the DOS prompt as you suggest...

no response.... nothing happens

tonymuffin
2006-04-27, 18:55
What are the registry entries necessary to delete to remove this????

tonymuffin
2006-04-27, 19:21
So.... as I started this thread... this is SO SPECIAL!!!
Tomorrow we are having a party and now can no longer play any of our play lists....nothing...

You buyers/downloaders out there....beware!

tonymuffin
2006-04-27, 19:33
The Location Of The Log Files Please??????????????///

dwc
2006-04-27, 20:35
You specify a log file path when you turn on logging:

slim.exe --logfile /path/to/logfile.txt

see all options below...


C:\Program Files\SlimServer\server>slim.exe --help
Usage: slim.exe [--audiodir <dir>] [--playlistdir <dir>] [--diag] [--daemon] [--stdio] [--logfile <logfilepath>]
[--user <username>]
[--group <groupname>]
[--httpport <portnumber> [--httpaddr <listenip>]]
[--cliport <portnumber> [--cliaddr <listenip>]]
[--priority <priority>]
[--prefsfile <prefsfilepath> [--pidfile <pidfilepath>]]
[--d_various]

--help => Show this usage information.
--audiodir => The path to a directory of your MP3 files.
--playlistdir => The path to a directory of your playlist files.
--cachedir => Directory for SlimServer to save cached music and web data
--diag => Use diagnostics, shows more verbose errors. Also slows down library processing considerably
--logfile => Specify a file for error logging.
--daemon => Run the server in the background. This may only work on Unix-like systems.
--stdio => Use standard in and out as a command line interface to the server
--user => Specify the user that server should run as. Only usable if server is started as root. This may only work on Unix-like systems.
--group => Specify the group that server should run as. Only usable if server is started as root. This may only work on Unix-like systems.
--httpport => Activate the web interface on the specified port. Set to 0 in order disable the web server.
--httpaddr => Activate the web interface on the specified IP address.
--cliport => Activate the command line interface TCP/IP interface on the specified port. Set to 0 in order disable the command line interface server.
--cliaddr => Activate the command line interface TCP/IP interface on the specified IP address.
--prefsfile => Specify the path of the the preferences file
--pidfile => Specify where a process ID file should be stored
--quiet => Minimize the amount of text output
--playeraddr => Specify the _server's_ IP address to use to connect to Slim players
--priority => set process priority from -20 (high) to 20 (low) no effect on non-Unix platforms
--streamaddr => Specify the _server's_ IP address to use to connect to streaming audio sources
--scanonly => Only run the library scanner, then exit.
--noscan => Don't scan the music library.
--nosetup => Disable setup via http.
--noserver => Disable web access server settings, but leave player settings accessible. Settings changes arenot preserved.
--perfmon => Enable internal server performance monitoring

The following are debugging flags which will print various information to the console via stderr:

--d_artwork => Display information on artwork display
--d_cli => Display debugging information for the command line interface interface
--d_client => Display per-client debugging.
--d_command => Display internal command execution
--d_control => Low level player control information
--d_directstream => Debugging info on direct streaming
--d_display => Show what (should be) on the player's display
--d_factorytest => Information used during factory testing
--d_favorites => Information about favorite tracks
--d_files => Files, paths, opening and closing
--d_filehandle => Information about the custom FileHandle object
--d_firmware => Information during Squeezebox firmware updates
--d_formats => Information about importing data from various file formats
--d_graphics => Information bitmap graphic display
--d_http => HTTP activity
--d_http_async => AsyncHTTP activity
--d_http_verbose => Even more HTTP activity
--d_info => MP3/ID3 track information
--d_import => Information on external data import
--d_ir => Infrared activity
--d_irtm => Infrared activity diagnostics
--d_itunes => iTunes synchronization information
--d_itunes_verbose => verbose iTunes Synchronization information
--d_mdns => Multicast DNS aka Zeroconf aka Rendezvous information
--d_memory => Turns on memory debugging interface - developers only.
--d_moodlogic => MoodLogic synchronization information
--d_musicmagic => MusicMagic synchronization information
--d_mp3 => MP3 frame detection
--d_os => Operating system detection information
--d_paths => File path processing information
--d_perf => Performance information
--d_parse => Playlist parsing information
--d_playlist => High level playlist and control information
--d_plugins => Show information about plugins
--d_protocol => Client protocol information
--d_prefs => Preferences file information
--d_remotestream => Information about remote HTTP streams and playlists
--d_scan => Information about scanning directories and filelists
--d_select => Information about the select process
--d_server => Basic server functionality
--d_scheduler => Internal scheduler information
--d_slimproto => Slimproto debugging information
--d_slimproto_v => Slimproto verbose debugging information
--d_source => Information about source audio files and conversion
--d_source_v => Verbose information about source audio files
--d_sql => Verbose SQL debugging
--d_stdio => Standard I/O command debugging
--d_stream => Information about player streaming protocol
--d_stream_v => Verbose information about player streaming protocol
--d_sync => Information about multi player synchronization
--d_sync_v => Verbose information about multi player synchronization
--d_time => Internal timer information
--d_ui => Player user interface information
--d_usage => Display buffer usage codes on the player's display

Commands may be sent to the server through standard in and will be echoed via standard out. See complete documentation for details on the command syntax.

slim.exe -install [auto] to install the service, (optional: auto start)
slim.exe -remove to remove the service

dean
2006-04-27, 20:35
On Apr 27, 2006, at 6:33 PM, tonymuffin wrote:

>
> dean Wrote:
>> Ok, please get in contact with support (AT) slimdevices (DOT) com for
>> one-on-one
>> support.
>
> hmmmmmmmmmmmmmmm.... ok... apparently you didn't read the last part of
> my previous post
I'm not sure why that is, it could be spam filters.

I've asked our tech support manager, Kevin, to get in touch with you
directly.

kdf
2006-04-27, 21:07
On 27-Apr-06, at 7:33 PM, tonymuffin wrote:

>
> The Location Of The Log Files Please??????????????///
>
http://slimserverIP:9000/log.txt

or

c:\program files\slimserver\server\slim.exe --logfile
c:\myfreakinglog.txt


oh, and yes, make sure you stop the service before running the
cocmmand-line.

-kdf

tonymuffin
2006-04-27, 21:56
On 27-Apr-06, at 7:33 PM, tonymuffin wrote:

>
> The Location Of The Log Files Please??????????????///
>
http://slimserverIP:9000/log.txt

or

c:\program files\slimserver\server\slim.exe --logfile
c:\myfreakinglog.txt


oh, and yes, make sure you stop the service before running the
cocmmand-line.

-kdf
Ok...this is special... http://slimserverIP:9000/log.txt returns, page cannot be displayed.

c:\program files\slimserver\server\slim.exe --logfile
c:\myfreakinglog.txt.... does absolutely nothing....

tonymuffin
2006-04-27, 21:57
You specify a log file path when you turn on logging:

slim.exe --logfile /path/to/logfile.txt

see all options below...


C:\Program Files\SlimServer\server>slim.exe --help
Usage: slim.exe [--audiodir <dir>] [--playlistdir <dir>] [--diag] [--daemon] [--stdio] [--logfile <logfilepath>]
[--user <username>]
[--group <groupname>]
[--httpport <portnumber> [--httpaddr <listenip>]]
[--cliport <portnumber> [--cliaddr <listenip>]]
[--priority <priority>]
[--prefsfile <prefsfilepath> [--pidfile <pidfilepath>]]
[--d_various]

--help => Show this usage information.
--audiodir => The path to a directory of your MP3 files.
--playlistdir => The path to a directory of your playlist files.
--cachedir => Directory for SlimServer to save cached music and web data
--diag => Use diagnostics, shows more verbose errors. Also slows down library processing considerably
--logfile => Specify a file for error logging.
--daemon => Run the server in the background. This may only work on Unix-like systems.
--stdio => Use standard in and out as a command line interface to the server
--user => Specify the user that server should run as. Only usable if server is started as root. This may only work on Unix-like systems.
--group => Specify the group that server should run as. Only usable if server is started as root. This may only work on Unix-like systems.
--httpport => Activate the web interface on the specified port. Set to 0 in order disable the web server.
--httpaddr => Activate the web interface on the specified IP address.
--cliport => Activate the command line interface TCP/IP interface on the specified port. Set to 0 in order disable the command line interface server.
--cliaddr => Activate the command line interface TCP/IP interface on the specified IP address.
--prefsfile => Specify the path of the the preferences file
--pidfile => Specify where a process ID file should be stored
--quiet => Minimize the amount of text output
--playeraddr => Specify the _server's_ IP address to use to connect to Slim players
--priority => set process priority from -20 (high) to 20 (low) no effect on non-Unix platforms
--streamaddr => Specify the _server's_ IP address to use to connect to streaming audio sources
--scanonly => Only run the library scanner, then exit.
--noscan => Don't scan the music library.
--nosetup => Disable setup via http.
--noserver => Disable web access server settings, but leave player settings accessible. Settings changes arenot preserved.
--perfmon => Enable internal server performance monitoring

The following are debugging flags which will print various information to the console via stderr:

--d_artwork => Display information on artwork display
--d_cli => Display debugging information for the command line interface interface
--d_client => Display per-client debugging.
--d_command => Display internal command execution
--d_control => Low level player control information
--d_directstream => Debugging info on direct streaming
--d_display => Show what (should be) on the player's display
--d_factorytest => Information used during factory testing
--d_favorites => Information about favorite tracks
--d_files => Files, paths, opening and closing
--d_filehandle => Information about the custom FileHandle object
--d_firmware => Information during Squeezebox firmware updates
--d_formats => Information about importing data from various file formats
--d_graphics => Information bitmap graphic display
--d_http => HTTP activity
--d_http_async => AsyncHTTP activity
--d_http_verbose => Even more HTTP activity
--d_info => MP3/ID3 track information
--d_import => Information on external data import
--d_ir => Infrared activity
--d_irtm => Infrared activity diagnostics
--d_itunes => iTunes synchronization information
--d_itunes_verbose => verbose iTunes Synchronization information
--d_mdns => Multicast DNS aka Zeroconf aka Rendezvous information
--d_memory => Turns on memory debugging interface - developers only.
--d_moodlogic => MoodLogic synchronization information
--d_musicmagic => MusicMagic synchronization information
--d_mp3 => MP3 frame detection
--d_os => Operating system detection information
--d_paths => File path processing information
--d_perf => Performance information
--d_parse => Playlist parsing information
--d_playlist => High level playlist and control information
--d_plugins => Show information about plugins
--d_protocol => Client protocol information
--d_prefs => Preferences file information
--d_remotestream => Information about remote HTTP streams and playlists
--d_scan => Information about scanning directories and filelists
--d_select => Information about the select process
--d_server => Basic server functionality
--d_scheduler => Internal scheduler information
--d_slimproto => Slimproto debugging information
--d_slimproto_v => Slimproto verbose debugging information
--d_source => Information about source audio files and conversion
--d_source_v => Verbose information about source audio files
--d_sql => Verbose SQL debugging
--d_stdio => Standard I/O command debugging
--d_stream => Information about player streaming protocol
--d_stream_v => Verbose information about player streaming protocol
--d_sync => Information about multi player synchronization
--d_sync_v => Verbose information about multi player synchronization
--d_time => Internal timer information
--d_ui => Player user interface information
--d_usage => Display buffer usage codes on the player's display

Commands may be sent to the server through standard in and will be echoed via standard out. See complete documentation for details on the command syntax.

slim.exe -install [auto] to install the service, (optional: auto start)
slim.exe -remove to remove the service

turn on logging??? how about speaking English??

tonymuffin
2006-04-27, 21:58
How does one fucking get back to point A?

Michaelwagner
2006-04-27, 22:03
http://slimserverIP:9000/log.txt returns, page cannot be displayed.

Did you put your slimserver IP address in there? Or did you literally type the letters slimserverIP?


c:\program files\slimserver\server\slim.exe --logfile
c:\myfreakinglog.txt.... does absolutely nothing....

If that's all you do, yes, it won't do anything unusual.

You also have to turn logging on, by going to the server web page and setting a logging option.

I think you need to speak to slim devices technical support one on one. This sort of problem is not one that the forum solves well or quickly.

kdf
2006-04-27, 22:16
On 27-Apr-06, at 9:56 PM, tonymuffin wrote:
>>
> Ok...this is special... http://slimserverIP:9000/log.txt returns, page
> cannot be displayed.
>
yes, that is for watching it when the server is running, and you do
need to use your proper IP address in place of slimserverIP (all of
this you could get from a search of the forum, btw)

> c:\program files\slimserver\server\slim.exe --logfile
> c:\myfreakinglog.txt.... does absolutely nothing....
>
it won't until you use the server, since it is writing everything to a
logfile instead of to the command line. This isn't new stuff.

I've also suggested the event viewer, assuming you are using windows.
Please report on what you find in relation to slim.exe or slimserver.

you've been asked twice what OS you are using, but you have only barked
at everyone instead of answering. Please fill in this blank.

If you are not on windows, and in fact are using linux, try looking for
/tmp/slimserver.log (default log for rpm installation)

-kdf

kdf
2006-04-27, 22:42
How does one get back to point A?

uninstall, then reinstall:

you can uninstall from control panel, add/remove programs. I'd recommend doing a search for 'slimserver.pref' and saving a copy so that you can keep your preferences. I believe it gets placed in c:\program files\slimserver\server by default.

then you can reinstall 6.2.1, downloadable from here: http://www.slimdevices.com/downloads

or you can reinstall 6.2.2 if you wish to take a deap breath and try to step through things calmly.

Dr Lovegrove
2006-04-28, 03:13
On 28/04/06, kdf <slim-mail (AT) deane-freeman (DOT) com> wrote:
>
> However, just before it connects
> it starts all over again saying Press BRIGHTNESS to update firmware.
> It has been doing this now in a loop 6 times. This is special!!!!

FWIW, I've had this happen to me quite a bit with 6.5 nightlies.. Half
way through updating and the server crashes.. Often it's a simple
case of removing the power lead from both my SB and my wireless
access point.. This usually fixes things..

If it doesnt, I completely nuke my Slimserver folder and re-install..
I suspect this is related to the settings file getting junk in or something ?
Not sure.. It's easier to toast the whole folder..

If that doesnt work I manually drop my DB tables..

- Dr Lovegrove

Siduhe
2006-04-28, 03:21
uninstall, then reinstall:

you can uninstall from control panel, add/remove programs. I'd recommend doing a search for 'slimserver.pref' and saving a copy so that you can keep your preferences. I believe it gets placed in c:\program files\slimserver\server by default.

then you can reinstall 6.2.1, downloadable from here: http://www.slimdevices.com/downloads

or you can reinstall 6.2.2 if you wish to take a deap breath and try to step through things calmly.

This is excellent advice. Uninstall, then delete any Slimserver folder left under "Program Folders", then reboot your machine. Then reinstall either 6.2.1 or 6.2.2.

I also wonder if you have made any other changes to the machine that is running slimserver since you first installed 6.2.1 - installed a new antivirus product or something similar which could account for the problems you're having with 6.2.2 ? If you have an antivirus / firewall set up, make sure you disable it before installing slimserver.

Michaelwagner
2006-04-28, 06:51
you've been asked twice what OS you are using, but you have only barked at everyone instead of answering. Please fill in this blank.

While I agree he's been barking, back in the 8th post of this thread he wrote:


All 3 are Squeezebox 2
OS: Windows XP Pro Service Pak 2 with all current critical updates and security patches.
Elsewhere he wrote one is wireless 2 are wired.

Fifer
2006-04-28, 07:09
While I agree he's been barking, back in the 8th post of this thread he wrote:


Elsewhere he wrote one is wireless 2 are wired.
Poor signal to noise ratio, vital info gets lost.

tonymuffin
2006-04-28, 07:16
On 27-Apr-06, at 9:56 PM, tonymuffin wrote:
>>
> Ok...this is special... http://slimserverIP:9000/log.txt returns, page
> cannot be displayed.
>
yes, that is for watching it when the server is running, and you do
need to use your proper IP address in place of slimserverIP (all of
this you could get from a search of the forum, btw)

> c:\program files\slimserver\server\slim.exe --logfile
> c:\myfreakinglog.txt.... does absolutely nothing....
>
it won't until you use the server, since it is writing everything to a
logfile instead of to the command line. This isn't new stuff.

I've also suggested the event viewer, assuming you are using windows.
Please report on what you find in relation to slim.exe or slimserver.

you've been asked twice what OS you are using, but you have only barked
at everyone instead of answering. Please fill in this blank.

If you are not on windows, and in fact are using linux, try looking for
/tmp/slimserver.log (default log for rpm installation)

-kdf
I have already stated what the OS is previously.
Windows XP Pro, Service Pak 2 all current critical updates and security patches

tonymuffin
2006-04-28, 07:17
uninstall, then reinstall:

you can uninstall from control panel, add/remove programs. I'd recommend doing a search for 'slimserver.pref' and saving a copy so that you can keep your preferences. I believe it gets placed in c:\program files\slimserver\server by default.

then you can reinstall 6.2.1, downloadable from here: http://www.slimdevices.com/downloads

or you can reinstall 6.2.2 if you wish to take a deap breath and try to step through things calmly.
I have uninstalled 6.2.2 and reinstalled 6.2.1. Same thing.

tonymuffin
2006-04-28, 07:18
This is excellent advice. Uninstall, then delete any Slimserver folder left under "Program Folders", then reboot your machine. Then reinstall either 6.2.1 or 6.2.2.

I also wonder if you have made any other changes to the machine that is running slimserver since you first installed 6.2.1 - installed a new antivirus product or something similar which could account for the problems you're having with 6.2.2 ? If you have an antivirus / firewall set up, make sure you disable it before installing slimserver.
No changes have made.

tonymuffin
2006-04-28, 07:19
On 28/04/06, kdf <slim-mail (AT) deane-freeman (DOT) com> wrote:
>
> However, just before it connects
> it starts all over again saying Press BRIGHTNESS to update firmware.
> It has been doing this now in a loop 6 times. This is special!!!!

FWIW, I've had this happen to me quite a bit with 6.5 nightlies.. Half
way through updating and the server crashes.. Often it's a simple
case of removing the power lead from both my SB and my wireless
access point.. This usually fixes things..

If it doesnt, I completely nuke my Slimserver folder and re-install..
I suspect this is related to the settings file getting junk in or something ?
Not sure.. It's easier to toast the whole folder..

If that doesnt work I manually drop my DB tables..

- Dr Lovegrove
As I have already posted.... the previous version was 6.2.1. I have already done your other suggestions

tonymuffin
2006-04-28, 07:20
Poor signal to noise ratio, vital info gets lost.
All was working perfectly yesterday and prior. Things stopped working with the upgrade to 6.2.2

jonheal
2006-04-28, 07:32
How does one fucking get back to point A?
Your avatar matches your charming personality quite well.

tonymuffin
2006-04-28, 07:36
Your avatar matches your charming personality quite well.
How about getting this thing working again and then we can throw spats at each other.....

zooropa320
2006-04-28, 07:39
So.... as I started this thread... this is SO SPECIAL!!!
Tomorrow we are having a party and now can no longer play any of our play lists....nothing...

You buyers/downloaders out there....beware!

I installed 6.2.2 over 6.2.1 with no problems then my player upgraded smoothly as well. Maybe this new version has an obnoxious detection feature and yours is responding accordingly?

slimpy
2006-04-28, 07:40
Try the following:
1) Turn off all your Squeezeboxen by unplugging the power cord.
2) Unplug the power from your router.
3) Uninstall Slimserver from your computer
4) Manually delete the Slimserver folder
5) Reboot your computer
6) Install Slimserver 6.2.2, start Slimserver and make sure it's running
7) Switch on your router, wait at least 1 minute
8) Apply power to ONE Squeezebox
9) If the update succeeds turn on the remaining SB one at a time
10) Post back here

It seems that people who read the mailing list in an e-mail client don't receive all posts. That's why they keep asking questions that have been answered before.

-s.

slimpy
2006-04-28, 07:45
How about getting this thing working again and then we can throw spats at each other.....
Don't forget that it's you who wants to get this working. The number of people who are with you on this steadily declines...

-s.

jonheal
2006-04-28, 07:45
How about getting this thing working again and then we can throw spats at each other.....
I had the firmware get hosed on me once.

I got back to "square one" by:

1. Check the "Forget this player checkbox" in SlimServer.

2. Unplug the Squeezebox.

3. Uninstall SlimServer. (If you're paranoid, you can search through the Registry for "Slim" and delete keys, but I think that's overkill.) Delete the Slim folder, too.

4. Reinstall an old version of Slimserver.

5. Plug the Squeezebox back in while holding down the "+" button.

6. Let it load the firmware.

7. Reset IP infomation on the Squeezebox.

tonymuffin
2006-04-28, 07:48
Try the following:
1) Turn off all your Squeezeboxen by unplugging the power cord.
2) Unplug the power from your router.
3) Uninstall Slimserver from your computer
4) Manually delete the Slimserver folder
5) Reboot your computer
6) Install Slimserver 6.2.2, start Slimserver and make sure it's running
7) Switch on your router, wait at least 1 minute
8) Apply power to ONE Squeezebox
9) If the update succeeds turn on the remaining SB one at a time
10) Post back here

It seems that people who read the mailing list in an e-mail client don't receive all posts. That's why they keep asking questions that have been answered before.

-s.

1) Turn off all your Squeezeboxen by unplugging the power cord. [tonymuffin] I have already done this
2) Unplug the power from your router. [tonymuffin] What does unplugging my router have to do with any of this? There is no issue with the router and all 8 of my other computers.
3) Uninstall Slimserver from your computer [tonymuffin] I have already done this
4) Manually delete the Slimserver folder [tonymuffin] I have already done this
5) Reboot your computer [tonymuffin] I have already done this
6) Install Slimserver 6.2.2, start Slimserver and make sure it's running [tonymuffin] I have already done this 3 times
7) Switch on your router, wait at least 1 minute [tonymuffin] Again... what does my rounter have to do with any of this? The LAN is working just fine.
8) Apply power to ONE Squeezebox [tonymuffin] I have already done this
9) If the update succeeds turn on the remaining SB one at a time
10) Post back here [tonymuffin] update never succeeds.

I have also uninstalled 6.2.2, removed all folders, removed all entries in the registry, re-installed 6.2.1. Again, the Squeezeboxes see the network, obtain and IP address, see the SlimServer, attempts to connect and then recycles. So, now I am not even able to get back to 6.2.1 which has been working up to installing 6.2.2 last evening.

tonymuffin
2006-04-28, 07:50
Don't forget that it's you who wants to get this working. The number of people who are with you on this steadily declines...

-s.
Doesn't matter to me. I want to make sure others get a clear picture of the product.

jonheal
2006-04-28, 07:52
Doesn't matter to me. I want to make sure others get a clear picture of the product.
Have you tried going back to the previous version with a WIRED connection?

Dr Lovegrove
2006-04-28, 07:56
On 28/04/06, tonymuffin
<tonymuffin.26zblc1146235802 (AT) no-mx (DOT) forums.slimdevices.com> wrote:
>
> 2) Unplug the power from your router. [tonymuffin] What does unplugging
> my router have to do with any of this? There is no issue with the
> router and all 8 of my other computers.

But you've tried doing it ? My (USR) router/access point occasionally
gets put in state in which everything works normally apart from the
slim stuff.. When it's in it's little state, 'press the brightness' is exactly
what you see, and it fails as it's failing with yours.. Worth a go..

--
- Dr Lovegrove
http://www.rusticrhino.com/drlovegrove

tonymuffin
2006-04-28, 07:56
Have you tried going back to the previous version with a WIRED connection?
What part of my posts is not clear here??? I do have a wired connection... As I have stated a number of times here in this post I have 2 wired Squeezeboxes and 1 wireless...

slimpy
2006-04-28, 07:59
Yes, I know you have done most of the things. But in this specific order?
Unplug your router to make sure it is properly initialized. At this point each and every component or software could be the culprit.

-s.

slimpy
2006-04-28, 08:05
Doesn't matter to me. I want to make sure others get a clear picture of the product.
Well this says it all. You sure give a clear picture of your personality.
May I suggest this guy be ignored?
I feel sorry for the support staff at slimdevices though.

Out.

-s.

tonymuffin
2006-04-28, 08:16
On 28/04/06, tonymuffin
<tonymuffin.26zblc1146235802 (AT) no-mx (DOT) forums.slimdevices.com> wrote:
>
> 2) Unplug the power from your router. [tonymuffin] What does unplugging
> my router have to do with any of this? There is no issue with the
> router and all 8 of my other computers.

But you've tried doing it ? My (USR) router/access point occasionally
gets put in state in which everything works normally apart from the
slim stuff.. When it's in it's little state, 'press the brightness' is exactly
what you see, and it fails as it's failing with yours.. Worth a go..

--
- Dr Lovegrove
http://www.rusticrhino.com/drlovegrove

Even though it is not clear. I am guessing you are referring to a wireless router? What does that have to do with my wired connections? As I have stated here, I have 2 wired Squeezeboxes and 1 wireless. My wireless router is an access point to my "wired" LAN. So, as I have asked a couple times here, what would unplugging the wireless access point have to do with my wired devices that don't even go through it??

tonymuffin
2006-04-28, 08:19
Well this says it all. You sure give a clear picture of your personality.
May I suggest this guy be ignored?
I feel sorry for the support staff at slimdevices though.

Out.

-s.
Blow it out yours........

freelunch
2006-04-28, 08:19
On 4/28/06, tonymuffin
<tonymuffin.26zblc1146235802 (AT) no-mx (DOT) forums.slimdevices.com> wrote:
> 2) Unplug the power from your router. [tonymuffin] What does unplugging
> my router have to do with any of this? There is no issue with the
> router and all 8 of my other computers.

You asked for help, right? Nothing has worked up to this point, right?

Yet for some reason you still refuse to perform *TRIVIAL* diagnostic
steps that are recommended... because you somehow "know" that cannot
be the problem.


slimpy Wrote:
>> Don't forget that it's you who wants to get this working. The number of
>> people who are with you on this steadily declines...
>>
>> -s.
>Doesn't matter to me. I want to make sure others get a clear >picture
>of the product.

That clears things up. You don't actually care whether it works. Silly
us - we thought you wanted help to get it working.

Amusing thread.


FL

tonymuffin
2006-04-28, 08:23
On 4/28/06, tonymuffin
<tonymuffin.26zblc1146235802 (AT) no-mx (DOT) forums.slimdevices.com> wrote:
> 2) Unplug the power from your router. [tonymuffin] What does unplugging
> my router have to do with any of this? There is no issue with the
> router and all 8 of my other computers.

You asked for help, right? Nothing has worked up to this point, right?

Yet for some reason you still refuse to perform *TRIVIAL* diagnostic
steps that are recommended... because you somehow "know" that cannot
be the problem.


slimpy Wrote:
>> Don't forget that it's you who wants to get this working. The number of
>> people who are with you on this steadily declines...
>>
>> -s.
>Doesn't matter to me. I want to make sure others get a clear >picture
>of the product.

That clears things up. You don't actually care whether it works. Silly
us - we thought you wanted help to get it working.

Amusing thread.


FL

Obviously you and a number of others are not reading this. No one has answered yet what unplugging a wireless router/access point has to do with the wired Squeezeboxes that do not even touch the wireless access point?

Jacob Potter
2006-04-28, 08:28
On 4/28/06, tonymuffin
<tonymuffin.26zczb1146237601 (AT) no-mx (DOT) forums.slimdevices.com> wrote:
> Blow it out yours........

Do you honestly expect useful assistance at this point? Considering
how abusive you've been, neither us forum members nor Slim Devices
have any obligation to help you.

azinck3
2006-04-28, 08:30
Perhaps you don't need to reboot your wireless access point (WAP), but it would be a good idea to reboot your router. Many WAPs are really three devices: an access point, switch, and router, all built into the same device. Many (most?) people use the routers that are built into their WAPs, but even if you aren't using your WAP as a router, there's surely a router somewhere on your network -- that's what's assigning IP addresses and is allowing you access to the internet. So, as has been repeatedly suggested, you'd be well advised to reboot your router (if your WAP's not routing then perhaps you have a separate router? or maybe you're using your cable or dsl modem as a router?) as well as any switches on your network.

As has been mentioned, these are complicated devices that can behave in surprising ways. Just because a certain type of traffic is making its way between certain devices doesn't mean that everything is kosher.

Don't be so averse to just giving it a try--it isn't a particular difficult or risky endeavor to reboot your network devices.

I'll also reiterate that you'll probably want to reset your SB2s again before you send the update (do this by holding down the power button for 5-10 seconds).

Mitch Harding
2006-04-28, 08:31
Worked fine for me on Windows XP.

You aren't going to find a company with better customer service than Slim
Devices. If you are calm and lose the attitude, I'm sure your problem can
be resolved.

On 4/27/06, tonymuffin <
tonymuffin.26yd3n1146191101 (AT) no-mx (DOT) forums.slimdevices.com> wrote:
>
>
> So.... as I started this thread... this is SO SPECIAL!!!
> Tomorrow we are having a party and now can no longer play any of our
> play lists....nothing...
>
> You buyers/downloaders out there....beware!
>
>
> --
> tonymuffin
> ------------------------------------------------------------------------
> tonymuffin's Profile: http://forums.slimdevices.com/member.php?userid=1420
> View this thread: http://forums.slimdevices.com/showthread.php?t=23389
>
>

Mitch Harding
2006-04-28, 08:34
Wow, I find myself wanting to help you more and more now.

On 4/28/06, tonymuffin <
tonymuffin.26zczb1146237601 (AT) no-mx (DOT) forums.slimdevices.com> wrote:
>
>
> slimpy Wrote:
> > Well this says it all. You sure give a clear picture of your
> > personality.
> > May I suggest this guy be ignored?
> > I feel sorry for the support staff at slimdevices though.
> >
> > Out.
> >
> > -s.
> Blow it out yours........
>
>
> --
> tonymuffin
> ------------------------------------------------------------------------
> tonymuffin's Profile: http://forums.slimdevices.com/member.php?userid=1420
> View this thread: http://forums.slimdevices.com/showthread.php?t=23389
>
>

dean
2006-04-28, 08:36
tonymuffin: Abusive language will not be tolerated on this forum.

Please tone down the conversation and edit your inflammatory posts or
we'll start banning folks.

Dr Lovegrove
2006-04-28, 08:45
On 28/04/06, tonymuffin
<tonymuffin.26zd7n1146237901 (AT) no-mx (DOT) forums.slimdevices.com> wrote:
>
> Obviously you and a number of others are not reading this. No one has
> answered yet what unplugging a wireless router/access point has to do
> with the wired Squeezeboxes that do not even touch the wireless access
> point?

Any bit of network gear on a network can potentially send/block random
data and wreak havoc with devices connected anywhere on a network.

It's probably also worth turning off all squeezeboxes except 1 wired one
and getting that working first. Make sure there aren't any conflicting IP
addresses on the network and you've only got 1 copy of slimserver running
too..

Also, when turning stuff off, leave it turned off for a good 5 seconds
before turning it back on.. Also delete any Phil Collins mp3s you've got on
your server - that can cause untold damage.. ;-)

--
- Dr Lovegrove
http://www.rusticrhino.com/drlovegrove

Michaelwagner
2006-04-28, 08:51
Tony:

I'm not sure why this isn't getting through, so let me explain it slowly.

There is a piece of state information, a bit or a byte or a megabyte, of bad information somewhere in your *entire* system.

In this case, the entire system is end-to-end. From the Squeezebox hardware, the Squeezebox firmware, the Squeezebox XiLinx matrix, through the router, through any firewall your router may be running, through your server computer.

We don't know why your SB dies when doing an upgrade. Clearly something somewhere isn't talking to something else somewhere else.

A standard diagnostic procedure in this case is to turn off everything that may be keeping state information in memory.

A router keeps state information about every port. If the router is really a switch, it keeps a *lot* more state information.

Some piece of state information somewhere is screwed up. We can guess until the cows come home and not be able to come up with the *correct* guess about why that matters, let aside one that pleases you in your current state.

I understand you want to get your party going tonight, and depending on where you are in the world, tonight might be very soon. So please power off everything, all at the same time, then power it all back on, in the order server, router, 1 squeezebox. See if that fixes it.

If not, uninstall Slimserver completely, erase the direcotry where the player preferences are (you'll lose the fact that one is called bedroom, one is called den, etc. Small price to pay at this point). Disconnect all your Squeezeboxen. Power everything off, power it all back on (except the squeezeboxes). In that order.

Then download old Slimserver 6.2.1 from the downloads page here
http://www.slimdevices.com/downloads/SlimServer_v6.2.1/

Pick the one marked windows executable.

Install it.

Power up one squeezebox.

If it still has this problem, then run the reset procedure. Hold down the power on button on your remote for like 20 seconds. This will remove *most* state information from the Squeezebox.

If that doesn't do it, you will have to reset the Xilinx. It's a programmable array, and it's also got state information in it. There is a procedure for doing this, but I can't off the top of my head remember. Someone else please help me out here. It's something like power down your SB, hold down the 1 key on the rmote while powering it back up.

If this doesn't work, phone Slim. I can't speak for them, but I expect at this point, to get you going, they'd be willing to call you back on their dime and talk you through it.

The contact information is here:
http://www.slimdevices.com/au_company.html

Here's the phone number: +1 (510) 743-1152 It's in the US, on the west coast.

I'm sure it must be very frustrating to have had a plan for a party and have it ruined this way.

It may be small consolation, but I've been running 6.2.2 for months, updating it every week or 2. I have 2 SB3s and 3 SB1s, one of them wireless. I've upgraded the firmware at least a dozen times. I never had this happen. So it's not like it hasn't been tested at all. But some combination of factors is making your system different.

I'm sure by now we'd all like to get it diagnosed and fixed, no one less so than you.

If we knew a one button cure, we'd all have prescribed it long ago. We don't. We can't understand why your experience is so different.

I hope you get this going by party time.

Michaelwagner
2006-04-28, 08:59
Also delete any Phil Collins mp3s you've got on your server - that can cause untold damage.. ;-)

I can see it in the air
tonight
oh, lord

I remember ...

tonymuffin
2006-04-28, 09:03
Perhaps you don't need to reboot your wireless access point (WAP), but it would be a good idea to reboot your router. Many WAPs are really three devices: an access point, switch, and router, all built into the same device. Many (most?) people use the routers that are built into their WAPs, but even if you aren't using your WAP as a router, there's surely a router somewhere on your network -- that's what's assigning IP addresses and is allowing you access to the internet. So, as has been repeatedly suggested, you'd be well advised to reboot your router (if your WAP's not routing then perhaps you have a separate router? or maybe you're using your cable or dsl modem as a router?) as well as any switches on your network.

As has been mentioned, these are complicated devices that can behave in surprising ways. Just because a certain type of traffic is making its way between certain devices doesn't mean that everything is kosher.

Don't be so averse to just giving it a try--it isn't a particular difficult or risky endeavor to reboot your network devices.

I'll also reiterate that you'll probably want to reset your SB2s again before you send the update (do this by holding down the power button for 5-10 seconds).

As mentioned already, the WAP is just that... an access point. It is not being used as a router. Thus I could not see why unplugging that would make any difference except possibly with the wireless Squeezebox but certainly not with the wired ones that don't touch it. I certainly know how easy it is to unplug a router and also know how to re-initialize the Squeezebox. Not an issue. I am more than willing to reboot a device... I was asking for clarification as to how rebooting the WAP would make any difference here. I can certainly reboot my wired router

joncourage
2006-04-28, 09:04
tonymuffin probably works for Sonos.

why is anyone still trying to help this guy?!

SlimPeople: imo this whole thread should be nuked - it's an embarrassment to Slim and to it's user community, not because one user is having a problem he can't sort out (which frankly I'm less and less inclined even to believe), but because this guy is far from representative of your average customer and is behaving dismally.

bahnsah
2006-04-28, 09:05
Best.

Thread.

Ever.

tonymuffin
2006-04-28, 09:07
tonymuffin: Abusive language will not be tolerated on this forum.

Please tone down the conversation and edit your inflammatory posts or
we'll start banning folks.
feel free to edit as desired

azinck3
2006-04-28, 09:10
Best.

Thread.

Ever.

haha,

I don't know...the QNap thread puts up some pretty stiff competition. But I think this thread wins, because at least in the QNap thread the (totally uncalled-for) vitriole was directed at someone who could be arguably considered "responsible" for the problem.

Mitch Harding
2006-04-28, 09:12
Power down the router and then power it back up. Forget the WAP for now,
although if I were you, I'd power it down just to be safe. I've seen plenty
of computer issues cleared up by doing things that logically (as far as I
could tell) should have no affect on the issue at hand.

In the time you've spent arguing about it, you could just try it and see if
it fixes your issue.

On 4/28/06, tonymuffin <
tonymuffin.26zf2b1146240301 (AT) no-mx (DOT) forums.slimdevices.com> wrote:
>
>
> azinck3 Wrote:
> > Perhaps you don't need to reboot your wireless access point (WAP), but
> > it would be a good idea to reboot your router. Many WAPs are really
> > three devices: an access point, switch, and router, all built into the
> > same device. Many (most?) people use the routers that are built into
> > their WAPs, but even if you aren't using your WAP as a router, there's
> > surely a router somewhere on your network -- that's what's assigning IP
> > addresses and is allowing you access to the internet. So, as has been
> > repeatedly suggested, you'd be well advised to reboot your router (if
> > your WAP's not routing then perhaps you have a separate router? or
> > maybe you're using your cable or dsl modem as a router?) as well as any
> > switches on your network.
> >
> > As has been mentioned, these are complicated devices that can behave in
> > surprising ways. Just because a certain type of traffic is making its
> > way between certain devices doesn't mean that everything is kosher.
> >
> > Don't be so averse to just giving it a try--it isn't a particular
> > difficult or risky endeavor to reboot your network devices.
> >
> > I'll also reiterate that you'll probably want to reset your SB2s again
> > before you send the update (do this by holding down the power button
> > for 5-10 seconds).
>
> As mentioned already, the WAP is just that... an access point. It is
> not being used as a router. Thus I could not see why unplugging that
> would make any difference except possibly with the wireless Squeezebox
> but certainly not with the wired ones that don't touch it. I certainly
> know how easy it is to unplug a router and also know how to
> re-initialize the Squeezebox. Not an issue. I am more than willing to
> reboot a device... I was asking for clarification as to how rebooting
> the WAP would make any difference here. I can certainly reboot my
> wired router
>
>
> --
> tonymuffin
> ------------------------------------------------------------------------
> tonymuffin's Profile: http://forums.slimdevices.com/member.php?userid=1420
> View this thread: http://forums.slimdevices.com/showthread.php?t=23389
>
>

Michaelwagner
2006-04-28, 09:24
As mentioned already, the WAP is just that... an access point. It is not being used as a router. Thus I could not see why unplugging that would make any difference except possibly with the wireless Squeezebox but certainly not with the wired ones that don't touch it.

Because even a WAP contains state information.

A WAP is a switch. It knows what MACs are on each side of it. It can chose to route traffic to one side of it or the other. Or not. If it's got wrong state information, it can break your network. Even for items that seemingly don't have anything to do with it.

Tony, we don't have time for an entire talk on how every piece of ethernet equipment works. Just power every thing connected to your computer system down, even if you don't think there's a good reason.

State information lives in the damnest places, including the clock chip in your computer, which remains powered up even when you power the computer down. Let's hope we don't have to go there.

dean
2006-04-28, 09:33
As a matter of policy, we don't edit or delete posts unless they are
obviously spam. We rely on the community for self-policing.

Unfortunately, if somebody can't participate in the community and get
along, we may give a "time out" and ban temporarily, then permanently
if it continues.

It's clear to me that you are frustrated and that there are a large
number of people ready to help you, including our own support team
that can be reached at support (AT) slimdevices (DOT) com or +1 (510) 743-1152.

kdf
2006-04-28, 09:42
Quoting joncourage <joncourage.26zf2b1146240301 (AT) no-mx (DOT) forums.slimdevices.com>:

>
> tonymuffin probably works for Sonos.

I doubt that. Tony has had his turn praising slimserver:
http://forums.slimdevices.com/showthread.php?t=15994&page=3

We just happen to be stuck in a nasty 'quirk' loop, and I expect it
will eventually return to playing music.

>
> why is anyone still trying to help this guy?!

Because the people in this forum are dedicated helpers.

>
> SlimPeople: imo this whole thread should be nuked - it's an
> embarrassment to Slim and to it's user community, not because one use
> is having a problem he can't sort out (which frankly I'm less and less
> inclined even to believe), but because this guy is far from
> representative of your average customer.

This forum is rife with 'not your average user', good and bad. The
thread is tedious, but I wouldn't say it was embarassing at all (well,
not for Slim at least). Every effort is being made, and there is only
one participant being truly abusive here.

I'll now add one more suggestion:

try the factory reset of the squeezeboxen. Given the firmware update
funniness and now even reverting to 6.2.1 still being a problem, clean
slate is a good place to start. I'll back the suggestion to reset
routers, switches, aps etc just to be sure. Letting the electrons
rest for a moment is never a bad idea.

As for how to do a factory reset:

1) unplug the squeezebox
2) wait 5-10 seconds
3) plug it back in
4) press and hold ADD button while it start up, and wait for it to reset.

Now, I'll go away and let this run its course. I'm confident that KP
and the support staff will be on this and deal with it appropriately.

-kdf

tonymuffin
2006-04-28, 10:00
Quoting joncourage <joncourage.26zf2b1146240301 (AT) no-mx (DOT) forums.slimdevices.com>:

>
> tonymuffin probably works for Sonos.

I doubt that. Tony has had his turn praising slimserver:
http://forums.slimdevices.com/showthread.php?t=15994&page=3

We just happen to be stuck in a nasty 'quirk' loop, and I expect it
will eventually return to playing music.

>
> why is anyone still trying to help this guy?!

Because the people in this forum are dedicated helpers.

>
> SlimPeople: imo this whole thread should be nuked - it's an
> embarrassment to Slim and to it's user community, not because one use
> is having a problem he can't sort out (which frankly I'm less and less
> inclined even to believe), but because this guy is far from
> representative of your average customer.

This forum is rife with 'not your average user', good and bad. The
thread is tedious, but I wouldn't say it was embarassing at all (well,
not for Slim at least). Every effort is being made, and there is only
one participant being truly abusive here.

I'll now add one more suggestion:

try the factory reset of the squeezeboxen. Given the firmware update
funniness and now even reverting to 6.2.1 still being a problem, clean
slate is a good place to start. I'll back the suggestion to reset
routers, switches, aps etc just to be sure. Letting the electrons
rest for a moment is never a bad idea.

As for how to do a factory reset:

1) unplug the squeezebox
2) wait 5-10 seconds
3) plug it back in
4) press and hold ADD button while it start up, and wait for it to reset.

Now, I'll go away and let this run its course. I'm confident that KP
and the support staff will be on this and deal with it appropriately.

-kdf

The only thing not been done here yet is power cycling both the WAP (the jury is still out on this one) and the router. I have done the following as previously mentioned:
1. Rebooted the Slim Server computer
2. Powered off both the 2 wired Squeezeboxes and the 1 wireless one
3. Turned off all Squeezeboxes except for 1 wired
4. Uninstalled and reinstalled 6.2.2
5. Uninstalled 6.2.2 again, deleted the SlimServer folder form Program Files, removed all registry settings to SlimServer
6. Unplugged the one powered on Squeezebox and held down the + key while powering on. It comes back up immeditaly to the Network setup and sees all the correct IPs and aquires one as well.
7. Uninstalled 6.2.2 again, deleted the SlimServer folder form Program Files, removed all registry settings to SlimServer and re-installed 6.2.1
8. Power cycled the 1 wired Squeezebox again
9. Unplugged the 1 wired Squeezebox and held the + key down while plugging back in again

No luck

So, when I get home from work today I will try powering off everything...

joncourage
2006-04-28, 10:23
Quoting joncourage <joncourage.26zf2b1146240301 (AT) no-mx (DOT) forums.slimdevices.com>:

>
> tonymuffin probably works for Sonos.

I doubt that. Tony has had his turn praising slimserver:
http://forums.slimdevices.com/showthread.php?t=15994&page=3

We just happen to be stuck in a nasty 'quirk' loop, and I expect it
will eventually return to playing music.

>
> why is anyone still trying to help this guy?!

Because the people in this forum are dedicated helpers.

>
> SlimPeople: imo this whole thread should be nuked - it's an
> embarrassment to Slim and to it's user community, not because one use
> is having a problem he can't sort out (which frankly I'm less and less
> inclined even to believe), but because this guy is far from
> representative of your average customer.

This forum is rife with 'not your average user', good and bad. The
thread is tedious, but I wouldn't say it was embarassing at all (well,
not for Slim at least). Every effort is being made, and there is only
one participant being truly abusive here.

kdf - the sonos comment was facetious.

as far as being helpful, I don't think it's a stretch to say that after the well-over-the-top antagonistic posts it's not at all unreasonable to say it's time that any right to expect help is forfeit. you're entitled to your opinion as are all the "helpers". however there are reasonable people having problems from whom attention is diverted to someone who is unworthy of continued assistance imo if not an outright troll. keep helping if you like, no skin off my back; I just say it's no longer help, it's masochism.

not to mention, the CTO of SlimD offered to have his Support manager call this guy DIRECTLY. I didn't see a reply accepting that offer, I only saw continued resistance to following the suggestion so generously offered and more obnoxious, antagonistic statements by tonymuffin. grow up, time to move on; it's enough to make one nauseous.

maybe you think it shows the outside world "how helpful" the online Slim community is; I just think it shows immaturity (not personal, but in the generally accepted protocols for participating in an online forum, and perhaps in perspective on where to spend time). imo your altruism is woefully misplaced. spend time helping someone who deserves it and demonstrates some appreciation.

last, my comment regarding the thread was not directed to you, but to Slim.

tonymuffin
2006-04-28, 10:30
kdf - the sonos comment was facetious.

as far as being helpful, I don't think it's a stretch to say that after the well-over-the-top antagonistic posts it's not at all unreasonable to say it's time that any right to expect help is forfeit. you're entitled to your opinion as are all the "helpers". however there are reasonable people having problems from whom attention is diverted to someone who is unworthy of continued assistance imo if not an outright troll. keep helping if you like, no skin off my back; I just say it's no longer help, it's masochism.

not to mention, the CTO of SlimD offered to have his Support manager call this guy DIRECTLY. I didn't see a reply accepting that offer, I only saw continued resistance to following the suggestion so generously offered and more obnoxious, antagonistic statements by tonymuffin. grow up, time to move on; it's enough to make one nauseous.

maybe you think it shows the outside world "how helpful" the online Slim community is; I just think it shows immaturity (not personal, but in the generally accepted protocols for participating in an online forum, and perhaps in perspective on where to spend time). imo your altruism is woefully misplaced. spend time helping someone who deserves it and demonstrates some appreciation.

last, my comment regarding the thread was not directed to you, but to Slim.
un...uh...er...hmmmm..... Slim Support was contacted last evening. What are you rambling on about?

Kyle
2006-04-28, 10:58
tony, can't wait for the party, man. I'm sure it will be a blast 'cause you're such an upbeat guy. Maybe you should stick to 8-track.

oreillymj
2006-04-28, 11:09
Tony,

I'm assuming you're still at the point where the SB's are looking for a firmware upgrade. If not, ignore the rest of this post.

I vaguely remember someone having a similar problem to yours, and it was down to old batteries in the SB2 remote.

Just to rule them out as a root cause, can you put 2 fresh batteries into your remote before holding down the brightness button for 5 seconds.

Have you ever done a firmware upgrade on any of your SB's before?

Much earlier in this thread, you were asked to look in Windows event viewer. Have you done this? Are there an Slim releated messages in the Application section of the event log.
to run Event Viewer, you can go to the Windows Start menu, click on run, and type eventvwr.msc into the box which appears, then click ok.

My experience is that if you remain calm and provide as much info as possible, the people on these forums will do their best to help fix your issue.

Mick

Zten
2006-04-28, 14:01
This type of thing can be EXTREMELY frustrating. You have this super cool thing that is more addictive than heroin and now its busted, right before your party. Yes, tony is pissing off all the UNPAID folks who are trying to help him, and that is not a wise thing to do. I’m glad to see the Dean gave Tony a phone number to call. I think Tony should call it and work through the issues with a LIVE support person.

I love my SB, and like all of you, I am fairly tech savy. When I got the email from Sean a couple days ago about the SW upgrade, I was pumped, because I have been wanting a solution to synch up Softsqueeze with my SB. (I use FLAC almost excusively, so I am all too familiar with the timing problems) Anyway, I figured I would look in on the old message board before doing the upgrade, and boy am I glad I did. I surely will not upgrade to 6.2.2 until the root cause of tonymuffin’s problems are documented.

Slim Devices needs to be very concerned about these things. It seems to me the Squeezebox business case is centered on word-of-mouth communication. I know I bought one based on the recommendation of a co-worker. I also have influenced 3 other people to buy one. There is no significant advertising for it and there are no (or at least very few) major retail outlets for it. All the business is based on word-of-mouth.

Tonymuffin clearly loves his SBes too. He’s got 3 for cryin’ out loud. If tonymuffin had NOT upgraded to 6.2.2, he would be like the rest of us; showing it off to all his friends at his party tonight. But since he DID upgrade to 6.2.2, his whole system came down and now he’s going to be telling all his friends how he’s spent 800 bucks on these pieces of junk. That’s not the type of word-of-mouth Slim Devices needs. IMHO.

Mitch Harding
2006-04-28, 14:14
I agree with most of what you say. To be fair, though, I do question the
wisdom of doing an upgrade right before a major event where you know that
you're going to be using your Squeezebox.

That having been said, you do expect officially released code to have been
tested. As far as I can tell, the code had been tested. Given that he is
the only one speaking up about this, I'm assuming he's likely one of a very
few people (perhaps only?) to hit the problem. I know that my upgrade went
completely smoothly.

I feel like this community has been very helpful to Tony, moreso than I
expected given the way in which he chose to vent his frustration. I've had
technical issues with my SB on occasion. However, the response I have
gotten from these lists and from SD has always left me with even more good
things to say about the company. Technical problems are always going to be
a factor when you are dealing with products which have regular updates, like
SlimServer. No matter how much testing you do, problems will slip through.
My profession is software test, so I'm painfully aware of this. I do think
it's reasonable to hold a company accountable if their product is plagued by
bugs. But I don't think it's reasonable to hold them accountable for
occasional bugs that somehow escaped their testing. My loyalty to SD is
base largely on the responses I've received personally when I've had
technical problems, and the responses I've seen others receive. Try getting
anything approaching this level of quality and service from other companies..

Not, I imagine, that any of this is any comfort to Tony. When something
doesn't work, it's frustrating. But you can choose how to vent your
frustration in better ways, I think, than lashing out at people trying to
help.

On 4/28/06, Zten <Zten.26zsyb1146258301 (AT) no-mx (DOT) forums.slimdevices.com> wrote:
>
>
> This type of thing can be EXTREMELY frustrating. You have this super
> cool thing that is more addictive than heroin and now its busted, right
> before your party. Yes, tony is pissing off all the UNPAID folks who are
> trying to help him, and that is not a wise thing to do. I’m glad
> to see the Dean gave Tony a phone number to call. I think Tony should
> call it and work through the issues with a LIVE support person.
>
> I love my SB, and like all of you, I am fairly tech savy. When I got
> the email from Sean a couple days ago about the SW upgrade, I was
> pumped, because I have been wanting a solution to synch up Softsqueeze
> with my SB. (I use FLAC almost excusively, so I am all too familiar
> with the timing problems) Anyway, I figured I would look in on the old
> message board before doing the upgrade, and boy am I glad I did. I
> surely will not upgrade to 6.2.2 until the root cause of
> tonymuffin’s problems are documented.
>
> Slim Devices needs to be very concerned about these things. It seems to
> me the Squeezebox business case is centered on word-of-mouth
> communication. I know I bought one based on the recommendation of a
> co-worker. I also have influenced 3 other people to buy one. There is
> no significant advertising for it and there are no (or at least very
> few) major retail outlets for it. All the business is based on
> word-of-mouth.
>
> Tonymuffin clearly loves his SBes too. He’s got 3 for
> cryin’ out loud. If tonymuffin had NOT upgraded to 6.2.2, he
> would be like the rest of us; showing it off to all his friends at his
> party tonight. But since he DID upgrade to 6.2.2, his whole system came
> down and now he’s going to be telling all his friends how
> he’s spent 800 bucks on these pieces of junk. That’s not
> the type of word-of-mouth Slim Devices needs. IMHO.
>
>
> --
> Zten
> ------------------------------------------------------------------------
> Zten's Profile: http://forums.slimdevices.com/member.php?userid=1810
> View this thread: http://forums.slimdevices.com/showthread.php?t=23389
>
>

jonheal
2006-04-28, 14:51
un...uh...er...hmmmm..... Slim Support was contacted last evening. What are you rambling on about?
Sean/Dean/et al:

PLEASE shut this monkey down! He's puttin' a bad vibe on the whole joint. He is clearly postal. There is nothing anyone here can do to help him (unless they're licensed to dispense psychotropic meds).

The notorious power supply thread reads like a Sunday School lesson when compared to the bile that has flowed in this thread.

jmpage2
2006-04-28, 15:42
Sean/Dean/et al:

PLEASE shut this monkey down! He's puttin' a bad vibe on the whole joint. He is clearly postal. There is nothing anyone here can do to help him (unless they're licensed to dispense psychotropic meds).

The notorious power supply thread reads like a Sunday School lesson when compared to the bile that has flowed in this thread.

The guy might be a little upset, but it's hardly like noone else has gotten rowdy in this playpen. Surely the guy has some right to be frustrated as;

1. He hasn't yet gotten real tech support on the issue even though he's tried.

2. His squeezeboxen are busted.

So I'd say calling him a Monkey and insisting he be silenced is rather unnecessary.

tamanaco
2006-04-28, 16:10
It is ->"possible"<- that all his Slimboxes were updated with a "corrupted" copy of the firmware file. This could have happened when he downloaded 6.2.2 or when he executed the 6.2.2 installation process. Meaning, that the installation process decompressed the firmware file to a bad sector of his drive. When he hit the brigtness button he updated all his SBs with a bad copy of the firmware. If this is the case... I'm not saying that it is... The only way to reverse this is to get the *Slimboxes* back to "factory" default.

Edit: Or the file (Build) he downloaded had a corrupted copy of the firmware.

jmpage2
2006-04-28, 16:13
OK, this is all twilight-zone esque.

After posting the above I upgraded (again) to 6.2.2 because the build I am on apparently was not the latest (release) version.

And now I'm having the SAME problem that the muffin man is having.

My Squeezebox 2 says the normal "press and hold brightness" bit and when I do the display simply blinks off and the box reboots itself and comes back to the same update firmware screen after accessing the LAN.

I never see the progress bar indicating that the SB is upgrading itself.

I was on Linux build 6.2.2-6245 and just re-upgraded to the final release after realizing I hadn't upgraded successfully. Slimserver is starting up just fine and now shows that it is 7135 but the SB won't upgrade.

Tailing the log file shows


[root@jaberwock slimserver]# ./slimserver.pl --logfile /var/log/slim.out --d_firmware&
[1] 3039
[root@jaberwock slimserver]# service slimserver status
slimserver.pl (pid
3039) is running...
[root@jaberwock slimserver]# tail -f /var/log/slim.out
2006-04-28 17:12:07.7405 squeezebox2 v. 33 requires upgrade to 48

And that's it.

No matter how many times I try to upgrade this is all I see from the logfile output.

kdf
2006-04-28, 16:18
Quoting jmpage2 <jmpage2.26zyyz1146266103 (AT) no-mx (DOT) forums.slimdevices.com>:

> No matter how many times I try to upgrade this is all I see from the
> logfile output.

--d_ir --d_slimproto --d_command --d_startup ?

snarlydwarf
2006-04-28, 16:19
Yes, though I was thinking (a dangerous thing) that the install process may have burped in one of those Special Windows Ways, blocking port 9000 but not blocking 3483. I think 9000 is where firmware comes from on the server. (For some reason I don't see that in the docs, and it's almost time to go home, so I'm not motivated :P)

Ie, the client can talk to the server on 3483, can be told there is a new firmware version, but can't get it.

Since a new executable was dropped in place, many firewall packages will notice that and deny network access to it.

Insufficient information on the problem, though. "It doesn't work" isn't much at all to go on.

dean
2006-04-28, 16:34
I heard from our support team that the original problem was resolved
by rebooting the router.

Glad to hear that it's up and running and that we can all move on.

Kyle
2006-04-28, 16:45
I heard from our support team that the original problem was resolved
by rebooting the router.

Rebooting the rounter ... really? If only someone had suggested that ... :-0

Michaelwagner
2006-04-28, 16:45
It is ->"possible"<- that all his Slimboxes were updated with a "corrupted" copy of the firmware file.
They are supposed to be checksummed.

Michaelwagner
2006-04-28, 16:46
If only someone had suggested that ... :-0

No kidding, eh? How did that one get by us?

jmpage2
2006-04-28, 16:50
I heard from our support team that the original problem was resolved
by rebooting the router.

Glad to hear that it's up and running and that we can all move on.

Interesting. I had to fix mine by taking it off of the wireless (WPS-PSK) network completely and hooking it up to a wired ethernet connection, getting it a new DHCP address and then it updated successfully.

Strange.

konut
2006-04-28, 17:07
I tell ya, this thread has been almost as entertaining as an episode of 'House'! The range of emotions was great! Bravo! The only thing missing is a last post from tonymuffin. I wonder what that might be like?

tonymuffin
2006-04-28, 17:17
I heard from our support team that the original problem was resolved
by rebooting the router.

Glad to hear that it's up and running and that we can all move on.

Perhaps that is what did it... and perhaps not...

Here is the course of action I did:
1. The computer was already off
2. All the Squeezeboxes were also already off
3. I powered down the LAN router, waited about 5 seconds and powered it back on
4. I left the Wireless Access Point still powered on as the only item in my house that uses the WAP is the wireless Squeezebox
5. I unplugged the powered cord from the already 3 powered off Squeezeboxes
6. I turned on the computer with SlimServer
7. I un-installed 6.2.1 and deleted the SlimerServer folder form Program Files (as I had twice prior), then rebooted the computer for good measure
8. I downloaded and installed 6.2.2 again
9. Once SlimServer came up I plugged in 1 wired Squeezebox closest to me
10. This time when holding the Brightness button down the bar that indicates the Firmware upgrade is happening appeared and progressed all the way through
11. Upon it's reboot after the frimware upgrade it found the SlimeServer just fine (as all other upgrades have done except last evening).
12. The network (IP) settings were exactly as they were prior for the device
13. I then plugged in and powered on the second wired Squeezebox and proceeded to successfully upgrade the firmware on that one as well. Same thing, all network settings on the device when completed were exactly as before
14. Finally I plugged in and powered on the 1 wireless Squeezebox and proceeded to update that one successfully as well.

Per my conversation with Kevin, the only thing done differently was 1. reboot the wired router and 2. unplugged all 3 Squeezeboxes and try one at a time.

The test would have been to try one more time without rebooting the wired router and unplugging the 3 devices and just uninstalling (for a 4th time), downloading and re-installing 6.2.2 however, we will never know.

I does not make any sense that all upgrades in the past went flawlessly and that I was playing on all 3 devices right up to stopping the play in order to upgrade to 6.2.2 from 6.2.1 last evening.

My guess is that it was the download was corrupted somehow. Especially after uninstalling 6.2.2 the second time and installating 6.2.1 only to find that Remove Programs under Control Panel still showed 6.2.2 listed (which could not be removed) and did not list 6.2.1 which had just been installed.

My guess is that the removing and re-installing a fresh download of 6.2.2 this evening is what did the trick... not the rebooting of the wired router especially when all 8 other computers and 2 network printers were all online, functioning and talking to each other just fine prior to the installation of 6.2.2 and after

zooropa320
2006-04-28, 17:22
I just knew he would be gushing with apologies and thanking everyone for their help and patience in spite of his poor attitude once he got it fixed!

mzpro5
2006-04-28, 17:24
I just knew he would be gushing with apologies and thanking everyone for their help and patience in spite of his poor attitude once he got it fixed!

Yeah, PERHAPS what did fix it was unplugging the router.

Kyle
2006-04-28, 17:57
"House" -- my new almost favorite show (after "The Office").

So, tony, what time is the party, what what was that address again?

dspeirs
2006-04-28, 18:39
Would it be approporiate to nominate this for thread of the year? I know the year is young but we have a strong contender. Like a car accident, it's so hard not to look.

Dan

Michaelwagner
2006-04-28, 19:16
Get's my vote. Can you turn a thread into a poll post-facto?

I think second place has to go to the QNAP thread. Or QSNAP. The box that runs Slimserver where the hardware was late so they blamed the software guy.

And third place to the never ending switching power supplies make a difference no they don't thread.

Rangdo
2006-04-29, 00:10
FWIW, jumping in at the end, I've just tried updating to 6.2.2 from 6.2.1 on my XP MCE server, got the same problem.

Reverted to 6.2.1 after uninstalling, same problem. Rebooted routers didn't help. Reset holding the + key didn't seem to help.

I'm now working again with 6.2.1, the only difference was that I normally manually enter the network details, final time I let them pick up via DHCP.

Plucking up the courage to try 6.2.2 and use the auto-DHCP part again.

Rangdo
2006-04-29, 02:33
And it worked :)

ehjones
2006-04-29, 08:23
http://forums.slimdevices.com/showthread.php?t=16743
:-p

kbeast
2006-04-29, 14:18
Yeah, PERHAPS what did fix it was unplugging the router.

honestly, I couldn't even read his resolve since I just read the entire thread of him moaning and not trying anything...by the time I got to his resolve, I could honestly care less.

The best part of troubleshooting to resolve a problem is try different steps...its always fun to help someone who wants to try nothing saying "I DID THAT." Hopefully you get lucky like we did and have it posted in all caps with extra puncutation marks...that also helps and makes for any easy read.

This guy must be a real treat in other real life events that need troubleshooting like, my car won't start, changing a flat, and my wife left me.

6.2.2 rocks.

curly
2006-04-29, 14:52
Who was it that said, "When you point a finger, three are pointing back at you."?

All this network stuff can be daunting and confusing for some (many) people and frustrating for even professionals.

Personally, I find the activity of stand-arounders kicking and shaming a man when's he's down to be extremely distasteful, counter productive and shows a lack of bawls.

Whoops! Are three fingers pointing back at me? No. I'm pointing all four fingers and a thumb straight out saving the other hand for backup.

Tony really just wants to play music. I'm glad he got it working with a great show of the unprecedented quality of support you get with Slim Devices systems.

radish
2006-04-29, 15:12
Tony really just wants to play music. I'm glad he got it working with a great show of the unprecedented quality of support you get with Slim Devices systems.

There are two kinds of support in this world, the kind you pay for and the kind you don't. The support he paid for (from SD) was excellent, looks like they got him right back up and running. They offered to call him, or email him, or whatever he wanted. I see nothing other than sheer professionalism from the offical SD folks on this thread. Above and beyond anything I get in a professional environment for products costing hundreds of times more.

The free support, on the other hand, well that you have to play a little differently. If you expect other people to help you out of the goodness of their hearts (and by posting on a forum that's EXACTLY what you're asking for) then you have to be prepared to be nice, polite and to TRY WHAT PEOPLE SUGGEST. If you want to be rude, arrogant and vent, and choose to do so in public, then you deserve what you get.

This forum is not a service, it's not a right, it's a COMMUNITY. Play by the rules and act nice, and you'll be rewarded in many ways with insight and excellent advice. If you want to play tough guy and throw your toys out of the crib, well that's what call centers are for. They're paid to put up with you.

Victor
2006-04-29, 15:53
Radish,

That's one of the best put posts on the topic I've ever seen. I suggest saving that somewhere, so the next time an unruly child wanders onto this playground, you can just point him at the post.

Victor

zooropa320
2006-04-29, 17:18
http://forums.slimdevices.com/showthread.php?t=16743
:-p

His recent behavior is nothing new I see. I feel bad for kdf who tried to help this ungrateful person twice.

Maybe we should blame tonymuffin's parents for not teaching him any manners? No, he's an adult (legally that is, not based on anything I've observed) so he deserves all the blame.

joncourage
2006-04-29, 20:15
There are two kinds of support in this world, the kind you pay for and the kind you don't. The support he paid for (from SD) was excellent, looks like they got him right back up and running. They offered to call him, or email him, or whatever he wanted. I see nothing other than sheer professionalism from the offical SD folks on this thread. Above and beyond anything I get in a professional environment for products costing hundreds of times more.

The free support, on the other hand, well that you have to play a little differently. If you expect other people to help you out of the goodness of their hearts (and by posting on a forum that's EXACTLY what you're asking for) then you have to be prepared to be nice, polite and to TRY WHAT PEOPLE SUGGEST. If you want to be rude, arrogant and vent, and choose to do so in public, then you deserve what you get.

This forum is not a service, it's not a right, it's a COMMUNITY. Play by the rules and act nice, and you'll be rewarded in many ways with insight and excellent advice. If you want to play tough guy and throw your toys out of the crib, well that's what call centers are for. They're paid to put up with you.

Actually, Radish, while I respect your well thought-out post, I beg to disagree.

It is not ok to berate or abuse or be rude to people you've paid to help you either. Professionals deserve every ounce of the same respect. My wife was in customer service and I was in IT for a long time and we now own and run a decent-sized business; the amount and degree of unbelievable abuse and rudeness people think they can get away with doling out is mind-boggling. My wife and I don't allow it - we professionally and firmly will shut down any interaction that becomes uncivil or unprofessional if reasonable attempts to redirect fail, and so we've instructed the many people who've worked for us over the years. Employers owe a respectful and professional work environment to their staff and should stand behind employees who have to correct for such a situation. If we let people ride rough-shod and rude over us or others in situations we have power over, by failing to actively discourage the problematic behavior we actually encourage it. The world would be a better place if people were held to treating each other respectfully and better held accountable for misbehavior.

I do agree that if you're seeking help gratis, as a courtesy, an ever higher standard applies. One which this mook fell woefully short of, repeatedly. There is no excuse for his behavior. We all get frustrated, and we're all expected to comport ourselves like adults, with civility. Once that social contract is unilaterally broken, no further obligation exists. I'll take it a step further and say that not only does no further obligation exist, but in a case like this where help is far from a serious quality of life issue, that any altruistic tendency to continue assisting bespeaks of misplaced consideration and is worthy of analysis. There are plenty of people in need of the time and energy spent on this misplaced assistance and compassion that better deserve it.

I find it doubly odd that people in this thread went as far as attacking others for calling tonymuffin on his behavior! How strange. I think it would take a psychologist to sort that syndrome out.... Unfortunately, I've found from experience that people like tonymuffin learn to take advantage of that benign quirk of human nature. Perhaps they even thrive off it.

Michaelwagner
2006-04-29, 21:02
Well said, Jon.

There's no need for abusive behavior on either side of the fence.

radish
2006-04-29, 21:34
It is not ok to berate or abuse or be rude to people you've paid to help you either.
Well I agree of course, people in all walks of life deserve respect and civility. Not only is it simple good manners, it also is usually the best way to get the result you desire. I guess my point was more one of degrees.

hal9000
2006-04-29, 22:14
wow reading this thread was amazing...

tonymuffin... what can i say... bad things happen sometimes when you update software and firmware. these problems can be very annoying but your rude, obnoxious behavior followed up with a complete lack of appreciation to the people who fixed your problem is unfathomable and frankly, sad.

i cruise a lot of boards and the slim boards are THE most helpful i have ever experienced. this community truly cares for this product and the people who enjoy it.

have fun at your party! i pity the people who actually have to interact with you directly.

-hal

btw I'm sure it was your router...all you had to do early on was reboot the thing as suggested instead of resisting the advice...i mean how hard is it to reboot a router?

Kevin O. Lepard
2006-04-29, 22:18
>joncourage Wrote:
>>
>> It is not ok to berate or abuse or be rude to people you've paid to
>> help you either.

Agreed

>Well I agree of course, people in all walks of life deserve respect and
>civility.

I would argue that while courtesy is for everyone, respect must be
earned. Certainly quite a number of people who responded with
attempts to help, to whom rude, snotty responses were made, are
people who have, IMO, earned respect in this forum.

Kevin
--
Kevin O. Lepard

Happiness is being 100% Microsoft free.