View Full Version : V24 Firmware- What changed?

Robert Wallace
2004-06-14, 17:24

I'm really not wanting to know all changes on a daily basis, and I certainly
get enough email just being subscribed to the discuss list -- not that
there's anything wrong with that.

But firmware changes are relatively rare and since you've mentioned we're
down to the last few blocker bugs before release, I was curious to know
which, if any, of those bugs this firmware release was intended to fix and
if the group I believe I'm part of, (a non-developer user who's not adverse
to beta testing) was supposed to verify the the bugs, if any, were truly
fixed. But I sense that you already have plenty of people doing that


-----Original Message-----
From: discuss-bounces (AT) lists (DOT) slimdevices.com
[mailto:discuss-bounces (AT) lists (DOT) slimdevices.com] On Behalf Of kdf
Sent: Sunday, June 13, 2004 10:27 PM
To: Slim Devices Discussion
Subject: [slim] V24 Firmware- What changed?

to quote the slim-checkins mailing list (which you should join if you need
know the reason for changes on a daily basis):

Update of /home/cvs/cvsroot/slim/server/Firmware
In directory lists.slimdevices.com:/tmp/cvs-serv14120

Modified Files:
Added Files:
Log Message:

Firmware V.24

- Fix crash when attempting to locate the server again if it disappears
- Change "re-discovery" mechanism so it continues trying to contact the
"last known" IP on port 3483 while also attempting discovery in case
the server has moved.
- Change timeout on control connection to 20s instead of 10s to prevent
needless re-connections if the server blocks for a little while
- Adjust TCP window update timer to prevent excessive dup acks as the
buffer opens up
- fix minor issue with IR responsiveness

Quoting Robert Wallace <rawallace (AT) comcast (DOT) net>:

> Hello,
> I installed the latest (6/13) nightly and was surprised to find Firmware
> came with it. I was hoping that the Pause blocker bug had been fixed, but
> discovered it to be still present.
> What I did notice was that the buffer indicator on my Squeezebox, which
> to peg full when I started playing my uncompressed tunes, was now
> fluctuating around the full mark, emptying down to about 75% then filling
> back up. Nothing changed on my network, and it was otherwise idle. Hmm.
> So what should we be checking for in V24?
> Robert