When something ‘just works’ 99.9% of the time, that .1% of downtime is particularly frustrating. This is what I recently experienced with my Time Capsule networking fiasco, and was paralleled by another problem stemming from an Apple firmware update.
The new MacBook Pros were shipped with their SATA II data speeds crippled; they were limited to 1.5Gps rather than the SATA II 3.0Gbps standardized speed. While this had no real effect for HDD users, it did affect SSD users – SSD is capable of taking advantage of the SATA II spec, and so SSD users rightly complained.
Apple heard these complaints, and released a firmware update for the MacBook Pro line; they warned that the update might not work with non-stock drives (!) but that it would restore SATA II speeds. I decided to update the firmware, just because having an up-to-date system is a good idea. This is right-minded thinking, right?
Almost all my home computer equipment is composed of Apple products, save for the Windows media center that I’m using to power the TV/display old TV shows/movies/listen to the radio. I’ve been using Windows Vista to power the ‘center until (very!) recently, and for the past two or three weeks have had my Time Capsule and attached AirPort Disk vanish from the network every couple of hours. Given that a lot of my movies and TV shows are on the AirPort Disk, this has been a real problem. Despite the drops, the router-element of the Time Capsule continued to work – I could browse the ‘net, and even run my automated backups using Time Machine, though I couldn’t actually access the data on the Time Capsule!
At first I assumed that the problem was a Windows Vista-related issue. I’d had other issues getting everything set up, and third-parties had mucked around with the media center while I was gallivanting around Ontario a few weeks ago. The only time that the router (and AirPort Disk) become unresponsive was when I used Vista to connect to the AirPort Disk. No issues arose when just browsing the AirPort Disk using a Mac (note: all Macs in the house are running 10.5.7). Read more…
I’ve recently become responsible for the upkeep of an Aspire One netbook. My thoughts, thus far: wait for a while, get another model than I did, and dump Linpus as quick as possible. First, I’ll provide the actual specs for the network in the house, and then outline my thoughts a bit more.
Acer Aspireone (AOA110-1531 (Refubrished))
Sapphire Blue
Intel Atom Processor N270 (512KB L2 cache, 1.60GHz, 533MHz FSB)
When something ‘just works’ 99.9% of the time, that .1% of downtime is particularly frustrating. This is what I recently experienced with my Time Capsule networking fiasco, and was paralleled by another problem stemming from an Apple firmware update.
