Bruce F. Webster

A few months ago, I wrote a post contrasting my experience with setting up and using an Apple TV (v2) device vs. setting up and using a Roku 2 streaming device. The Apple TV device came out very favorably, and while I did get the Roku 2 to finally update its software and start functioning, I have continued to use the Apple TV (which I’ve had since last spring) far more heavily.

But now a problem has arisen with the Apple TV devices (I own two). Some weeks ago — I’m not sure exactly, since I have been traveling heavily since the start of November — my Apple TV(s) started dropping their wireless connection with my dual-band N router (DLink DIR-825, hardware version B1, firmware 2.06NA). Prior to that time, I could start streaming a playlist from one of our computers that have iTunes libraries, and the music would play for hours. Now it’s hard to get it to play for more than an hour the Apple TV drops, then reestablishes the wireless connection (halting the playlist in the meantime). Sometimes it will happen two or three times in the space of 5 minutes; other times, it will run for a few hours before resetting. But the problem itself and its variability makes the Apple TV fairly useless for streaming audio and video.

I did some of the usual — rebooted the entire wireless network, did a restore on the Apple TV, swapped the two Apple TV devices, made sure both had the latest software updates, and so on. Same problem. Searches on the ‘net showed that people have complained about similar or identical problems going back to 2010, but my problem didn’t start until about 6 weeks ago — my Apple TVs were pretty solid before then.

I ran a test earlier today which strongly suggests that the problem does lie with Apple TV. The living room Apple TV sits side-by-side with that Roku 2 device; both are hooked up to the same TV and are the same distance from the router (which, by the way, is only about 25-30′ away; most of that distance is open air, and there are no walls in-between). As it turns out, both the Apple TV and the Roku 2 support Netflix. So I fired up the Roku and picked a relatively short film to play (Blackadder’s A Christmas Carol). Said film played perfectly all the way through with no pauses, stutters, hiccups, or other issues. I then switched over to the Apple TV, brought up Netflix there, and selected the same film. It played fine for about the first 14 minutes — and then went into a pause mode (rotating circular arrow). Every few minutes, it would come out of that mode, play for another few seconds, then go back into pause mode again. This went on for a good half hour before I finally killed it.

I have yet another test running as I type this: I have both Apple TVs connected to the same router band (the same one the Roku is connected to), streaming audio from the same iTunes library (on this laptop) simultaneously. If one drops the wireless connection and the other doesn’t, then that increases the chances that it is in fact an Apple TV problem. So far, both are running fine (of course).

In the meantime, if others of you have encountered this problem and have known solutions, please let me know.  ..bruce..

This is actually a problem I’ve been dealing with — or, more accurately, ignoring and working around — for a few months, at least, so I thought I’d put a post up here to see if anyone has come up with an actual fix.

Back in July 2010, I bought an Acer Aspire easyStore Home Server running Windows Home Server 2003, primarily two solve two problems: (1) run nightly backups of all my Wintel PCs; (2) provide a common media file repository for myself and my wife (who runs Macs). After a few bumps, it worked just fine and has been working fine since.

Except that a few months ago — which at this point may mean something like this past summer or even late spring, given how time flies — I noticed that I could no longer run the WHS Console app from any of my PCs (all running Win7 Pro). Any attempt to do so resulted in an error box with the message:

This computer cannot connect to your home server. Check your network connection and make sure your home server is powered on. If your home server has recently restarted, try again in a few minutes.

Here’s what’s strange: the server itself still shows up in the Network panel, I can still access all the shares, and I can still log onto the server via the Remote Desktop Connection application (and, by the way, run the Console app there, on the server itself). I can ping the server in a console window via its name and its (fixed) IP address. And the automated backups keep happening (though more on this below).

At roughly the same time — and it may have been exactly the same time — I began to get certificate warnings when I used RDC to log into the server. This is a well-known problem with a kludgy work-around (configure RDC to ignore certificate warnings). That problem appears to be associated with Service Pack 1 of Windows 7, and I suspect the Console problem showed up at the same time as well.

However, to date, I have not found a workaround to the Console problem. What’s more, I’m starting to have backup problems. In particular, one desktop system stopped backing up. In an effort to fix that, I uninstalled the WHS Connector Software and attempted to re-install it. No go — I get this error during installation, after entering the server’s admin password:

This operation cannot be completed at this time.

Please try again later. If the problem persists, please contact Product Support.

This appears to be a well-known, if intermittent, problem, but one for which a variety of suggested-but-not-necessarily-effective solutions have been offered. I started to tackle the problem again this morning, trying some of the solutions, and found some other oddities:

• Even though I can see my server (which we’ll call foo-bar for now) in the Network panel, can access it, can ping it (by name or by IP), and can remotely log into it, I cannot bring it up in a browser, e.g., http://foo-bar or even http://<fixed IP address>. That last one is particularly surprising.
• Yesterday, I brought down and then brought back up my entire home-wide network (modem, router, access point, lots of computers and other network-accessing devices). I noticed that the Acer server box took forever (probably 15+ minutes) to reboot itself and reappear on the network.
• I’ve been getting flaky behavior from WHS itself over the past few months when I remotely log in (which I don’t do that often). For example, when I logged in today, I got three standard Windows “unexpected error – send info to Microsoft?” boxes, all associated with the backup utility.
• I did bring up the Computer Management panel on the server, thinking that the inability to browse to the server may depending on something running here. I did find that IIS Admin Services was not running and would not start, even though its two dependencies (RPC and Security Accounts) were, in fact, running.

I suspect that what I may actually need to do is reinstall WHS 2003, but that means that I will have to (for safety’s sake) back up the (non-automated) shares. Not a bad thing to do anyway, but not how I envisioned spending my Thanksgiving weekend.

What struck me while researching on-line is how many people had posts that said, in effect, “I did this and it fixed everything”, followed by posts saying, “I tried that and it still doesn’t work”. Similarly, not everyone running the same systems gets the same problems. It goes to the heart of the underlying complexity, uncertainty, and — to a certain extent — unknowability of the systems upon which we depend.

That said, I welcome suggestions.   ..bruce..

Last spring, I bought an Apple TV device to go along with a new large-screen TV in our living room. Setup was simple, and I kept discovering new things that I could do with it. It gets used a lot more than either the Blu Ray player or the DirecTV satellite box also attached to the same TV.

Today, I bought a new (smaller) TV for our bedroom, replacing one that we have had for 8 or 9 years. On impulse, while picking out the TV at Costco, I also picked up a Roku 2 kit (Roku 2, HDMI cable, 2 month subscription to HuluPlus). I figured it would be interesting to see the comparison. Once home, I set up the new TV, hooked up the Roku 2 to it, and started the Roku 2 setup process. I got it talking to my in-home LAN (dual-band 802.11N router), and it signaled successful connection all the way out to the internet. It then told me that an update was available and gave me no other option than to download that update. Not a problem, I thought — always want the latest software.

Sigh. The Roku was never able to download the upgrade, and — this is critical — gave me no option to proceed to use the device without the upgrade. I made half a dozen attempts (all with the same failure, Code 011, unable to connect to Roku server), went to roku.com/support and had a nice chat with Jane, who suggested I reconfigure my router with explicit DNS addresses and then reboot my network. Did so — same problem.  She opined that the Roku server might be having troubles, or that it might be some other unspecified error.

Just to make sure there wasn’t some specific problem with the actual physical location of the Roku 2, I went out to the living room, unplugged my Apple TV, brought it into the bedroom, and plugged it in sitting right where the Roku 2 had been. Worked like a charm. I then went to Amazon and ordered a second Apple TV unit (scheduled to be delivered Saturday morning for just $3.99 in shipping, even though I ordered it Thursday evening — Amazon Prime is just brilliant).

I will probably hang onto the Roku 2 unit and in fact will likely connect it to the living room TV (along with the new Apple TV unit). Assuming that I can get it to update itself and let me use it, I’d like to see what it offers that’s different and/or better than Apple TV. But having had a fair amount of contact with Steve Jobs back during his NeXT days, I know that one of his product mantras was, “It just works.”

The Apple TV, like so many Apple consumer products, just works. And that’s why Apple wins.

[UPDATED 12/19/2011] Of course, having written that firm statement, I am now having problems with my Apple TV units. In the meantime, I did finally get the Roku 2 to register the day after I wrote this post, and it is working fine even though my Apple TV is not. Sigh…

The second personal computer I ever owned[1] was an Apple II, with no floppy drive. I bought it, along with a small color TV, from my close friend Robert Trammel while we were both living in Houston sometime around 1980.We had already spent hours together programming on it, then carefully (though not always successfully) saving our programs out to cassette tape. After three months, I sold the computer and TV back to Robert — not because I didn’t like it, but because I was spending far too much time on it.

A few years later — in 1982 — my close friend Wayne Holder hired me into his nascent software company, Oasis Systems, in part to help with his existing and planned word processing utilities (The Word Plus, Punctuation + Style), but mostly to develop computer games. And we did, developing Sundog: Frozen Legacy on the Apple II, a game for which I still get e-mails (and which Wayne is even now working on resurrecting for modern platforms). In January 1984, a few months before Sundog shipped, we were invited by Guy Kawasaki to come up to Apple to see a preview of the Mac and to talk about what software we could port to the Mac. Through my connections with computer stores in San Diego, I was able to get a personal loan of a Mac for a few days at home prior to the official announcement in Cupertino later that month, which Wayne and I attended as well. That was my first time seeing Steve Jobs in person, and it remains a memorable highlight of my professional life.

When the Mac shipped a few days later, I went down to the one computer store in San Diego that I knew would be getting machines from Apple. I took $3000 in cash with me and managed to convince the store owner — a friend — to let me have one of the three Macs he had to sell. Through a connection with Phil Lemmons — editor-in-chief at BYTE — I ended up writing the official BYTE review of the 128K Macintosh (August 1984 issue). By the end of 1984, I was writing full-time for BYTE, including on-going coverage of the Macintosh, particularly once my BYTE column started in mid-1985. After a few years of writing for BYTE, I switched to writing for Macworld magazine. Steve was now long-gone from Apple, and Apple was having some of its own problems going forward.

But in late 1987, I was contacted by Addison-Wesley. They were interested in having me write a book about Steve Jobs’ new project at NeXT. Folks at NeXT had apparently suggested me to Addison-Wesley, probably due to my writing at BYTE and Macworld. I leapt at the opportunity, particularly since in coincided with our family moving from Utah to just outside Santa Cruz (where I would be doing technical writing for Borland on a consulting basis). Once there, I found myself invited to visit NeXT HQ on Deer Creek Road, sit in on meetings, and attend the 0.3 NeXTstep Dev Camp. And, yes, that meant getting actual face time with Steve Jobs as well — not a lot, but this was a man whose creations had been impacting my personal and professional life for over a decade at this point.

The writing of the book dragged out as I waited to get my hands on an actual NeXT cube, which finally happened (if I recall correctly) at the end of 1988 or early 1989. I wrote the first several drafts of the book on that NeXT cube itself. The book came out in the fall of 1989; it remains the single most successful book I’ve ever written, due to the intense interest in NeXT itself, more than any particular writing skills or technical insight on my part.

The following year, I found myself working with a world-class typographer (Mike Parker) and graphic designer (Vic Spindler) to create a design-oriented desktop publishing system. I was doing all the software prototyping on my NeXT cube, and we made the decision to make the NeXT our first target platform. For five years — 1990 to 1995 — I served as chief architect and CTO at Pages Software Inc, where we developed Pages by Pages and then WebPages, while spending nearly two years just trying to raise venture funding. We closed on funding at the start of 1992 and shipped our first version of Pages in early 1994. We quickly sold all that we were going to in the all-too-small NeXTstep market. My frustrations at seeing larger firm try to leverage off of NeXT’s incredible innovations led to an op-ed piece in the November 1994 issue of BYTE, “Whither NextStep?” The day that issue came out was the last time that Steve Jobs and I spoke — he called me from the back of a car somewhere to ask me what the hell I was doing writing that. I said, telling the truth. Pages would close its door the next year, unable to secure additional funding to move its technology to Windows.

When Steve engineered his brilliant reverse takeover of Apple — getting Apple to buy NeXT for $400 million, then slowly moving himself into the CEO seat — I was not optimistic. I still had unconditional praise for the NextStep technology, but I was dubious about Steve’s ability to sell technology to markets and to compete with Microsoft.

Boy, was I wrong. I was not only wrong about his abilities at Apple, I was wrong in my BYTE article about NextStep being on a downward slope. NextStep, of course, was the foundation of Mac OS X, and Steve transformed Apple into the most-admired, most-imitated, and most-valuable company in the world. And I was tickled that, when Apple brought out its own word processor, it was named “Pages”. Steve had always liked that name when we were developing (and shipping) our own product years before; glad he was able to use it.

To quote John Perry Barlow over on FB, “The world is suddenly a less interesting place.” ..bruce w..

[1] The first was an HP-67 card-reading programmable calculator.

[Cross-posted from And Still I Persist]

A few months back, I bought an iPad portfolio case with a built-in bluetooth keyboard from ThinkGeek. (No manufacturer name appears on the case, but I’ve seen what appears to be an identical case offered on Amazon by Kensington.) That case is set up much like a traditional iPad portfolio case — slide the iPad in, secure it, fold a flap over to close the case — but has a bluetooth keyboard built into the inside of the fold-over cover.

While the concept was great, I found this case less useful than I had hoped. The keyboard was small and had a non-standard layout on the right side (no right Shift key; several other keys in different locations), which was frustrating for me, a touch-typist. Furthermore, it had a tendency to lose bluetooth connectivity with the iPad while I was using it; I’d be in the middle of typing, and suddenly the keyboard I was using would stop working and the on-screen iPad keyboard would appear. (Looking at the reviews of the Kensington unit over on Amazon, I found that I was not alone in having this problem.) I passed it to my wife, who encountered many of the same problems, and it generally got set aside.

However, a week ago, I spotted a new iPad case with keyboard on ThinkGeek: the ZAGGMate with keyboard, from ZAGG, Inc. I ordered it; it showed up; and so far, I’m very, very happy with it.

Unlike the earlier black-folio case, the ZAGGmate is an aluminum shell with a keyboard inside. For carrying purposes, you place your iPad face down into the shell, and you end up with what looks like a solid aluminum unit (the ZAGGmate aluminum matches the back of the iPad). To use your iPad, you simply pull it out of the case (which is notched along one side to allow you to pry the iPad out). You can then either use your iPad as you normally would, or you can prop it in a trough inside the case and use the keyboard.

This approach has several immediate advantages over  the earlier iPad keyboard case. First, the folio case only allows one orientation for the iPad: horizontal, with the home button to the right. The ZAGGmate not only allows you either horizontal orientation, it also allows you either vertical orientation as well. I personally find writing on the iPad more pleasant and productive in horizontal mode; I can see more of the text at once.

Second, the iPad rests in a trough that’s more than a full inch in from the back side of the case. That means that an iPad + ZAGGmate has an overall smaller footprint (depth + height) than most netbooks, which can be critical if you’re trying to get work done seated in coach on an airplane.

Third, since the iPad is just sitting in the trough (with a plastic prop behind it), you can easily pick it up and use it sans keyboard (such as for games), then set it down when you want to use the ZAGGmate keyboard again.

Fourth, the ZAGGmate with the iPad stored is only about half the thickness of the folio case with the iPad inside.

Unlike the keyboard in the folio case I bought earlier, the ZAGGmate keyboard has a near-standard layout, including a Right shift key and all the other keys in expected places. The only real problem I’ve had with this keyboard — aside from the size, which is the same problem I’ve had with my Acer netbook and the folio iPad case — is that the space bar is flush with the bottom edge of the case. This means I have to use a different motion with my right thumb do actually get the space bar to go down.  As a result, I still sometimes either miss spaces or hit two.

That’s a small complaint, though. On the other hand, several of the function keys across the top are mapped to iPad functions: home, search, slideshow, black screen, play/track, volume/mute. There is even a key to bring up the iPad on-screen keyboard, should you want to pick up the iPad and still do typing. Note that the ZAGGmate keyboard is still active as well, so you don’t have to reconnect.

I haven’t had a single bluetooth dropoff to date with the ZAGGmate. In fact, the only bluetooth problem I’ve had was figuring where the ‘bluetooth button’ was. Yes, it is that little LED right above the bluetooth symbol — it’s actually a tactile switch underneath the surface, and you need to be brave enough to press hard enough until you hear it click.

Note that this review is for the iPad 1 version of the ZAGGmate (and, for that matter, of the black folio case). Both ZAGG and Kensington have iPad 2 versions that are coming out.

Recommended.  ..bruce..