Here's an interesting problem related to bug 1181(firmware) and maybe others(server). I didn't add a comment to bug 1181 for exactly this reason.
The facts: I recently bought a new SB2 wireless. I use the SB2 w a range extender - the signal strength varies between 86-88%. The firewall is well configured - the symptoms below are the same w or wo the sw firewall. When I upgraded the server the rules were manually updated by me to point to the new executable - which is point moot since I can shut it down for the duration of the test. What's OK: The SB2 and slimserver 6.1.1 work together flawlessly. This server apparently has a different version of the firmware than the one required for squeezenetwork. SB2 shows it as being ver 15. Worked OK for a day, and yesterday(Oct 26, 2005) it asked for an upgrade while connected to squeezenetwork. What's NOT: Slimserver 6.2/6.2.1(nightly) are unusable as they are - at least for me (Win XP SP1). 6.2.1 didn't install the service (didn't check why). 6.2.0 installs fine, the service starts nicely but SB2 & the server can't find each other. Why did I upgrade *8-) An upgrade is performed every time I switch between slimserver & squeezenetwork. Squeezenetwork's firmware version is shown by SB2 as ver 26. However, once that upgrade is made, the brightness is fixed (to dimmest setting) and cannot be adjusted while connected to squeezenetwork. Also, more apparent while changing the volume, the screen flickers and looks unstable. The player can connect and play the radiostations MOST of the time. Sometimes after an attempt to connect to squeezenetwork it will: - shutdown before reporting a succesful connection. Power button (remote) needed to restart & restarts as connected w dim display OR - it says it can't connect The above is true w 6.1.1 & 6.2.0 server versions with & without the firewall. What would be nice: I would like to be able to cancel the attempt to connect at least rather than be forced to upgrade. (bug 1181) squeezenetwork should accept different firmware versions; the reason being that a defect in the current server version will make this resurface. In the near future I plan to use the slimserver on a FreeBSD box and the latest version may or may not work on that platform - maybe I'll have to stick to the ports version. The ability to run the server on smth other than Windows was a deciding factor in buying this particular hardware so this is important for me. TIA, Fry -- fry _______________________________________________ squeezenetwork mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/squeezenetwork
