[Double Ugly]

According to this thread (scroll to the bottom), the problem with connecting a SB to an Apple Time Capsule-based network was resolved with the introduction of firmware v88.  My question is, how do I go about upgrading the firmware?

I used to do it all the time when I used a PC, but now that I'm using a Mac, I don't know where to begin.

I had hoped Logitech/Slim Devices would update SqueezeCenter 7.0 with the new firmware, but I've found no evidence to that end.

I've received *tremendous* support and assistance from the facilitator of The Apple Core, but aside from possibly getting a PC on the network, he doesn't know how to fix the problem either.

Any ideas?  Anyone? 

TIA. 

[Freo-1]

Well, one usually can go to the manufacturer's web site, and there usually is a download section for this sort of thing.

I have a IAudio 7, and there were annoying bugs with the interface. I went to the Cowon website, and lo and behold, there was a firmware upgrade to fix this problem. They also provided instructions on installation.

You may have already tried, but it's worth a shot if you have not. 

[Double Ugly]

Hi Freo,

Well, the thread I linked is from the manufacturer's site, and though I'm relatively familiar with the download section, I can't tell which is the updated firmware for my Mac.

As the thread indicates, the problem was fixed only 2 days ago, so hopefully someone in an administrative capacity @ Slim Devices will expound as Time Capsules become more common.

FWIW, the latest "official" software is SqueezeCenter 7.0.  I already have it loaded on my machine, but the SB firmware found within is v86.

[Freo-1]

Hiya, DU!

Well, hopefully, they will post some data on this post haste. Meanwhile, a gentle prod to customer service might be in order.

[Double Ugly]

Well, hopefully, they will post some data on this post haste. Meanwhile, a gentle prod to customer service might be in order.

Might be.  Someone posed a potentially related question only 2 hours after the fix was announced, and yet no reply in the 2 days since. 

That said, I'm *not* familiar with this particular section of their site.  Maybe their policy is to ignore threads once a problem is supposedly resolved, or maybe they don't offer weekend web-based support.  I'll look again (4^th time today ) for an answer in the "regular" Slim Devices forum. 

I have to believe someone else in the world is struggling with this, too, but then I'm often reminded of the pitfalls associated with underestimating the depth of my ignorance. 

Thanks again, Freo. 

[JEaton]

Each release version of SlimServer/SqueezeCenter ships with a certain version of the firmware for each of the different products (SB1, SB2/3, Transporter, Duet/Receiver).  If a newer version of the firmware fixes a problem that you're having, then the only way to get the new firmware is to install a newer version of the server.  That would have to be a nightly release, downloadable here:

http://www.slimdevices.com/downloads/nightly/latest/trunk/

These nightlies are technically 'beta' versions of the software, but the only things being checked into this 7.0.1 branch are bug fixes, so they're arguably more stable and more bug free than the most recent release.

[Double Ugly]

Each release version of SlimServer/SqueezeCenter ships with a certain version of the firmware for each of the different products (SB1, SB2/3, Transporter, Duet/Receiver).  If a newer version of the firmware fixes a problem that you're having, then the only way to get the new firmware is to install a newer version of the server.  That would have to be a nightly release, downloadable here:

http://www.slimdevices.com/downloads/nightly/latest/trunk/

These nightlies are technically 'beta' versions of the software, but the only things being checked into this 7.0.1 branch are bug fixes, so they're arguably more stable and more bug free than the most recent release.

I thought about that, J, but according to this thread, even yesterday's nightly didn't have it, and I've found nothing to indicate tonight's will.

Rather than run the risk of upgrading to a beta in the search for a firmware that isn't there, I'd rather have some confirmation.  I'd love to read the nightly change log, but apparently I can't do so without a password.

Which begs the question - Why offer a link to information when you intend to lock out the very people who need it? 

[Double Ugly]

I downloaded the nightly beta 7.0.1 build yesterday because they've finally incorporated firmware v.88 into the build.  Yes, it's a beta, but I couldn't care less.  Firmware v88 is finally loaded on the SB2. 

I'm glad someone finally noticed the beta change log was locked down, and made it available again to end users.  As per my comments above, I'd have never downloaded the beta had I been unable to confirm the inclusion of firmware v88.

Anyway, I'm happy to report the TC/SB wireless connection problem is resolved.  Even after moving the SB is moved to its normal location (same floor, other end of the house), I'm getting a solid 71% signal strength.

Nevertheless, I still think it's borderline dumb to build a router capable of superior range and speed, and yet significantly decrease the effective range of the former by avoiding the use of antennae.  I haven't kept track, but I don't believe I've seen another pre-N router without 'em, and all have received high marks for extended range.  Conversely, the AEBS and TC have been slammed for their wireless performance.  The performance I'm getting is apparently better than what others have experienced, but the Apple engineers' chosen approach seems odd at best.  What am I missing in my analysis, Crimson?

In summary, the issues I've encountered with the Time Capsule make me feel as though I've been taken to a degree, but I feel a lot better about it now.  Assuming the Transporter/TC connection works as expected and the signal strength is sufficient to avoid drop outs (different floor, opposite end of house), I'll feel even better about it.

Dan Wright received my Transporter yesterday, so hopefully I'll have both systems up and running in the next few (2?) weeks.

[Crimson]

Nevertheless, I still think it's borderline dumb to build a router capable of superior range and speed, and yet significantly decrease the effective range of the former by avoiding the use of antennae.  I haven't kept track, but I don't believe I've seen another pre-N router without 'em, and all have received high marks for extended range.  Conversely, the AEBS and TC have been slammed for their wireless performance.  The performance I'm getting is apparently better than what others have experienced, but the Apple engineers' chosen approach seems odd at best.  What am I missing in my analysis, Crimson?

Uh, I've never used one with an antenna? 

Even the earliest base stations offered from Apple did not have antennae.

[Double Ugly]

Even the earliest base stations offered from Apple did not have antennae.

Exactly; that's my point.  They continue to get mediocre-at-best wireless performance reviews, and yet competitors with antennae (Belkin Pre-N, for example) are praised for their speed and range.  At some point, you'd think Apple would do something to increase the range of their routers, be it via antennae or something else.

Regardless, the more important aspect of the post is that I'm back to streaming music again, and the performance I'm getting from the TC is more than adequate.  I've no complaint with the status quo, and if the Transporter works as well as the SB, I'll be walking in tall cotton. 

BTW, do you know of a USB wireless adapter that works with the TC?  My wife's Netgear doesn't work at all with it, so we're looking for options.

[Crimson]

Odd, very odd. My daughters machine has a prehistoric Linksys USB -b adapter that works just fine. Is it an -n adapter and are you running in -n-only mode (5 GHz) or mixed mode (2.4 GHz)? You may want to try running the TC in 2.4 Ghz mode if the adapter supports it.

[Double Ugly]

I'm running 802.11n (802.11b/g compatible).  It seemed the most logical choice since I know my wife's work computer isn't -n compatible, and I assumed her relatively old (2 years?) wireless adapter isn't either.

She went online and found plenty of complaints about the Netgear being incompatible with Apple's routers.  I realize she could be mistaken, but she's a MS-based network administrator, and I'm inclined to give her the benefit of the doubt.