Google
 


Subscribe to The Tech Night Owl Newsletter

*Required



 

Archive for July, 2008


The Personal Computer Chaos Theory

Thursday, July 31st, 2008

During this week’s episode of The Tech Night Owl LIVE, my friend Adam Engst, a noted Mac author and editor, was talking with me about the fact that Internet connections on the Mac generally work perfect out of the box, as it were.

Except when they don’t.

You have undoubtedly come across such situations. Say you are trying to connect wirelessly to the Internet using your Mac’s AirPort card. Most times, it works just fine. Sometimes, it just won’t make the connection. Try and try again, and it still fails.

Now Adam spoke of one such instance during the interview on the show, where he had to connect his Mac via FireWire, using TCP, to another Mac to share a connection and get online. His conclusion about such matters: ”There’s a certain amount of chaos in the universe that we’re never gonna be able to break free of.”

Now I am not talking here about paranormal phenomena or the other weird stuff we cover in detail on our other radio show, The Paracast. Instead, I’m talking about the trials and tribulations we all encounter on a regular basis with all sorts of electronic gear.

I know I’ve run into situations of this sort occasionally when performing various tasks on my Macs. At least 98% of the time, everything works perfectly. Then, to site one example, an application quits, but that particular symptom doesn’t appear again for at least several weeks. Now I know that random crashes and other anomalous behavior, if it’s repeated fairly often, may be traced to defective RAM or some other hardware ailment. But these occurrences are far too rare for that.

Surely it happens to you, and, if you think about it, you can probably set down an ongoing diary about other weird events on your Mac. It’s easy to forget about them, unless you take note at the time, as weeks of bliss may cause the unsavory moments to fade from your conscious memory

But it’s not just personal computers that are afflicted by such ailments. I dare say lots of electronics can do things that are totally strange.

For example, I use a Logitech Harmony 890 universal remote. It’s really a well-designed product, with backlit display and color LEDs for the main functions. With a little time and effort, you can program it it to work with pretty much any standard home entertainment device, from your cable or satellite company’s set top box, to your TV, DVD and even your trusty old VCR.

Without going into much detail, the Harmony sometimes has to be set so it activates a function, perhaps to turn on your TV, and then enters a pause before it activates your cable box. If that doesn’t happen, it will try to switch them both on at the same time, and that can cause problems. Well, this is one of those situations where everything works most of the time. But every few days, one or more devices fails to turn on, or the TV’s input setting goes to VCR, when you really want it to switch to the DVD player.

Well, Logitech has a Help feature on its remote that assists you in finding a resolution by asking simple questions, such as whether the TV is on, whether it switched your home theater audio system to the correct input and on and on until it resolves your problem.

Sometimes, you just have to dig out the old remotes and do it all manually.

Now I suppose you could blame Logitech for not being able to anticipate all the possibilities of perhaps holding the remote at the wrong angle, or a glitch in the software on the entertainment gadget in question that makes it respond incorrectly to a random command. Eventually, the system breaks down and you have to just turn it all off and start again.

But these functions are relatively simple and straightforward in the scheme of things.

With personal computers, whether a Mac or a PC, you are dealing with sophisticated operating systems containing millions of lines of code. One function depends and 20 others, which, in turn, depend on another set of code activating still another command at the very same time. It’s amazing that it ever works.

Long ago, a tech support supervisor from a hardware company gave he his pet theory, that programmers are actually just a tiny bit insane to go into that profession. Now I’m not singling out anyone in particular here; I’m just telling you what he said. Anyway, after a number of years on the job, the programmer might occasionally slip out of control and express the encroaching insanity with errant code entries. So if the proper conditions are met, things will go wrong.

In another situation, I actually had a lead programmer from a company come to my home office and try to debug a problem they had difficulty reproducing. Well, after I demonstrated how easily it was to repeat the problem, which caused my Mac to crash, he opened the source code, which he had copied to his notebook, and fiddled around with something. After a few minutes of this, he pronounced the problem cured.

Indeed, he gave me the revised version of the utility, and the crashes were history. That version became the final shipping build for the product, a tiny app that would simply flash an icon on your Mac’s menu bar when the hard drive was reading or writing data. Nothing to it, right? Well, evidently the original developer, who sold the code to the software company in question, left a single line of code that, under most circumstances, did nothing. When a certain combination of functions were present, however, it would go into a endless loop, and your Mac would crash.

Now I won’t mention the name of that programmer. I’m sure he has long since lived that one down, but I bet he’ll know what I’m talking about if he reads this article.

But between the eccentricities of the developers, just plain human error, and maybe the great unknown, hardware and software will occasionally misbehave. Worse, sometimes we’ll never know why.

Related Articles:


Apple Walks the Tightrope

Wednesday, July 30th, 2008

A now-deceased comedy performer once used the catch phrase, “If it isn’t one thing, it’s another” as part of a classic TV routine. And clearly that applies to Apple Inc. these days.

Indeed, it’s not easy being a star, although many of you have no doubt aspired to that status. For one thing, bottom feeders, jealous people and lots of others will have it in for you. You become a ripe subject of incessant gossip. One misstep, and you’re yesterday’s news.

With Apple’s recent trials and tribulations, it seems very much like theater. First, they ran out of stock of the first-generation iPhone weeks before the new model was scheduled to be released. Now I don’t know if they planned it this way, just to make sure that they didn’t have any leftovers in the stock rooms that had to be sold at closeout prices, or it was just one of those things.

But considering how carefully they keep tabs on inventory, that simply doesn’t pass the logic test. They would have known months in advance if they were about to run out of stock, and could have adjusted production accordingly. I suppose it’s possible they encountered manufacturing difficulties with their new model, or they wanted to start as early as possible to satisfy the initial clamor for the iPhone 3G. Then again, that didn’t work so well now did it?

Or perhaps, as I first suggested, that’s precisely how Apple’s marketing people planned it all along. Make you salivate for the second generation iPhone, and there would be long lines waiting outside Apple’s stores and those of independent resellers to get theirs. Sending lots of disappointed people home because stores ran out of stock also made for good headlines.

What doesn’t sound so good, however, is when things break. I continue to complain about the MobileMe fiasco because it put Apple in the worst possible light. For so long, those Mac versus PC commercials have portrayed Apple products as being easy to use and relatively foolproof, while Windows is a constant source of irritation.

With MobileMe, Apple’s customers simply wanted reliable email service and the ability to sync their stuff in a timely fashion. They don’t want to have contacts and messages disappear from their iPhones, or suffer extended outages where the prospects for full recovery may be questionable.

Now there are a few published reports that claim Apple has finally restored those missing messages to all affected customers, but the MobileMe status blogs speak of restoring “historical” messages and not the recent ones that were identified as lost. Now perhaps the Apple blogger misspoke — or perhaps not. Regardless, the folks who did suffer from lost messages will no doubt chime in soon with their own war stories, if there are any.

When it comes to the App Store, Apple proudly boasts of 25 million downloads in the first week. They don’t, however, talk about the delays in getting application updates posted. A number shipped with crashing bugs or other defects, and it would be nice to have the updates available as quickly as possible. However, Apple has to review each and every product they distribute. While I can understand their concerns and their desire to keep unsavory content off the App Store, legitimate software publishers ought to be treated better.

Another problem is Apple’s NDA, which evidently didn’t expire when the new iPhone software was released and the App Store opened for business. That means, for example, that developers are not only barred from talking with other publishers, but in holding proper external beta testing programs. Even though iPhone apps tend to be simple affairs, with basic features and few options, certainly hardworking developers ought to have full control of their own intellectual property.

On the other hand, Matt Mullenweg and his crew at WordPress have made their iPhone app open source, and, so far at least, Apple hasn’t complained. But give them time.

Now while you might think some of these issues were unfortunate side-effects of the rush to get lots of products and services out real quickly, Apple’s stuff has been infected with a number of early-release bugs in recent years. When the first Intel-based notebooks came out, for example, there were battery failures and complaints they ran too hot. The bad batteries were readily replaced, and the cooling fans began to run more efficiently as the result of firmware updates, but calling them laptops was still a stretch. That is, unless you just want to keep your legs warm in the winter.

My 2008 edition MacBook Pro runs a whole lot cooler than the original version, but a lot of that is probably due to the use of Intel’s new Penryn chips, which are are also more power efficient. Running the fans twice as fast didn’t hurt either.

Apple’s Time Machine worked pretty well out of the starting gate, with Leopard’s release, but the Time Capsule router and network backup device had some serious early teething pains. Now mine works just fine, but I didn’t acquire one until after a couple of downloadable updates were released.

I haven’t had a lick of trouble with my Mac Pro, but I was always concerned about danger of leaks from the liquid cooling system on its predecessor, a Power Mac G5 Quad. No, I didn’t have any such issues, nor did the computer’s new owner, but there have been some troubling reports. You can well understand why Apple was delighted to ditch the ultra-hot running G5 and move on to Intel’s processors. Yes, the Pentium 4 was notorious for running hot, but that was yesterday.

Meantime, Apple’s reputation for smooth-running, reliable products and services has been tarnished. Yes, they can live it down, and they are certainly doing better than some of the competition. But too many failures will not help their bottom line, particularly if a lot of potential Windows switchers decide that things aren’t really so much better on the other side of the tracks.

Related Articles: