Squueze Network Bug Status

[Mark]

How can I determine where a reported bug is on the "to do" list? I have an SB3 and have had problems connecting to and playing stations using ShoutCast:All Streams since I got it several weeks ago.

Bug #2565 was opened 11/1/2005 and assigned a severity of "Major". It affects all platforms. I have contacted Slim Devices in all ways I know possible (phone, email, and online) and other than hearing "we are aware of the problem" on the phone, I don't see any progress.

Please help me understand how your bug tracking/resolution process works.

Thanks,

Mark

[dean]

The bug list _is_ the to-do list, sorry for the slowness on fixing
bugs with the SqueezeNetwork. We've recently hired some new
engineering talent to help out, expect things to get better quickly.

I can't comment on the specific bug, but I do believe that it's high
priority. Look for updates to the specific bug for progress.

-dean

On Jan 21, 2006, at 7:44 AM, Mark wrote:
> How can I determine where a reported bug is on the "to do" list? I
> have
> an SB3 and have had problems connecting to and playing stations using
> ShoutCast:All Streams since I got it several weeks ago.
>
> Bug #2565 was opened 11/1/2005 and assigned a severity of "Major". It
> affects all platforms. I have contacted Slim Devices in all ways I
> know
> possible (phone, email, and online) and other than hearing "we are
> aware
> of the problem" on the phone, I don't see any progress.
>
> Please help me understand how your bug tracking/resolution process
> works.
>
> Thanks,
>
> Mark
>
>
> --
> Mark
> ----------------------------------------------------------------------
> --
> Mark's Profile: http://forums.slimdevices.com/member.php?userid=3506
> View this thread: http://forums.slimdevices.com/showthread.php?t=20282
>
>

[Mark]

OK. I sure hope you can fix it soon. SqueezeNetwork is unusable browsing in this fashion. It seems to have gotten worse over the weekend. A couple times the unit has completely locked up, requiring me to unplug to reset it. In fact, the only way I got it work was by forcing a firmware reload and even then it only worked for that session. Once I logged on and off of SN, it was not functional.

BTW, I mistakenly referred to the Bug as 2565. It is 2465.

Mark