Landscape Mode

One of the touted features of the 3.0 iPhone upgrade was the addition of landscape mode throughout most Apple applications. Initially this sounded like quite a boon. Until I realized: I never use landscape mode, I don't like landscape mode, landscape mode is always activating when I don't want it to and there's no way to turn it off.

Quit Doing That!

My biggest complaint about landscape mode — and what seems to me the biggest UI gaffe — is that it forces itself on the user. If you happen to be reading something in Safari using portrait mode and, for instance, lying on your side, the iPhone will constantly attempt to reorient the screen to landscape mode, even if it's completely inappropriate. It interrupts what you're doing and requires all manner of acrobatics to keep the thing in your orientation of choice. In the end you give in and just sit up. And that sucks.

The one time I almost always like landscape mode is when I'm looking at photos in the Photos app. Ideally we'd have a way to opt-in to landscape mode on a per-app basis. But at this point I use it so little I'd settle for a way to just turn it off.

I understand a lot of people love landscape mode, but the way it is now is far more annoying than useful for me.

Archives

Let's face it, my data is everywhere. I have drives all over the place for various and sundry purposes. Some are full. Some aren't. I also have a folder for things I plan on trashing eventually, when I need to reclaim some space, but want to keep around just in case, called TrashMe. And I have a folder with items I plan on backing up some day called BurnMe. This name comes from the fact that traditionally I archived up my data to optical media: either DVDs, or, in the distant past, CDs, so I also have several containers full of optical media.

This isn't working for me anymore.

Optical media is no fun to use for backups. It's slow, requires keeping a stock of media on hand, and it's often undersized for today's hefty data needs. For instance, backing up my current BurnMe folder will require about fourteen DVD-R discs. Burning and verifying those DVDs will take as many if not more hours. And then it will all need to be cataloged somehow, which is also a lengthy process. Finally, retrieval is almost as slow and tedious: find the disc you need in the catalog, get it from storage, load the disc up and copy the data back to the computer, which can also take quite some time. And if, heaven help you, there's one tiny scratch on that disc you could lose all that data.

So I'm switching to a better way: hard drives.

1-machd

One of the best bangs for your buck per-gigabyte of storage is, of course, the hard drive. In addition to being cost-effective, they're fast, they hold a lot of data, they're read-write and extremely versatile. You can use them internally, depending on the drive and computer in question, of course. Or you can use them externally in any number of ways, the most obvious being in a firewire or USB case. Using such a case allows for the attachment of the drive to just about any computer you can get your hands on. Drives don't require much physical space, and because they're so fast, they're quick and easy to catalog and restore from. In fact, using hard drives as an archive solution entails little difference from accessing local storage. The hardest part is getting the drive off the shelf and getting it attached to your machine. But there are hardware solutions to simplify that process as well. Hard drives, which have largely remained the same since I began working in this business ten years ago, are more future-proof than optical media, which is constantly the subject of format wars and which is often subject to a raft of compatibility issues. Put another way: getting data off a hard drive in the next ten years is more likely to be supported by my current hardware than getting it from a DVD.

So, my plan, going forward, is to use hard drives to archive all non-essential data. I will continue to archive certain critical files to DVD in addition to the hard drive archive. But most of my stuff will be on hard drives. Things like bittorrent backups and movie files, old audio, video and web projects, images and what have you will stay on hard drives earmarked for the archive. Once one of those drives is full and I'm no longer using the data, I'll burn anything critical — finished projects and their assets, for instance — to optical media, catalog the drive with CD Finder or similar software, and then put the drive in a Hudzee and up on the shelf. Done and done!

This greatly speeds and simplifies my archive procedure. And, because of the increased space and time efficiency, I can archive a lot of data I would have thrown out in the past. I still have yet to work out the details of this system, but I think it will be a vast improvement over the old burn-and-catalog weekends of my not-so-distant past.

If anyone has thoughts on how best to archive data I'd love to hear them in the comments.

Battery Removal

I've often heard tales involving the removal of a Mac's battery — the little, round, watch-style one that makes sure the machine remembers what time it is, among other things — from the motherboard for a half an hour as a solution to various power issues, but it's never been effective for me. Until recently, that is.

The other day I was vacuuming. The computer was shut off. When I'd finished with my cleaning I noticed that my powered-down Mac Pro was making a faint clicking noise which was coming from near the power switch. The machine would not turn on.

I recalled something similar happening before — New York City has notoriously flaky electrical power — and I remembered that the solution involved resetting the SMC switch, the little module that's in charge of certain aspect of power management for the system. So I unplugged the beast from everything, laid her on her side, opened her up and pressed the SMC switch. Waited a minute. Plugged her back in. Same faint clicking, no power.

What followed is your basic lesson in hardware troubleshooting 101, in a nutshell: Remove and reseat all removable internal components and test. This includes the RAM, the graphics card, whatever fans I could pull and an extra internal hard drive. Nothing helped. After each remove-and-reseat, the same clicking sound, the same inability to boot.

Finally, the last ditch attempt. Before heading all the way down to the Apple Store to request service, I figured I'd pull the little internal watch battery — the PRAM battery as it's called — and wait a half an hour. I mean, what could it hurt, right?

Bingo! It actually worked. After putting the battery back in the Mac, and plugging her in, the clicking was gone and I could power up again. Amazing!

I was pretty disappointed to find literally no such similar problems out there in Internetland. In fact, searching "Mac Pro battery" seems to only yield results pertaining to MacBooks. So consider this my contribution to the great troubleshooting reference in the sky. Hopefully, those having similar problems — if they're even out there — will land here and know what to do.

If none of these steps works for you, you might try replacing the battery altogether. The battery for my Mac Pro (Early 2008) can be found at OWC. Apple keeps a list of systems and their batteries if you have a different machine.

If that doesn't do it I'd highly suggest heading to an Apple Store (or certified repair shop), if possible, or calling up Apple for service if not. My guess is you likely need a new power supply or motherboard.

Update Verification?

So that's what this is all about!

Update Verification

I grabbed this screen shot a while ago when I updated to iPhone OS 3.1. I do that sometimes. See something that strikes me as odd and get a screen shot of it, just in case.

Today I just happened to stumble upon some info that explains the odd, "...verify the update with Apple," that concludes this message:

"Rather than just throw in new local protections, Apple decided that every restore of the device would be verified as being valid and safe by Apple itself.

To do this, during the restore process, users see 'Verifying restore with Apple...', during which time a challenge/response protocol is used between the iPhone and Apple: a 'partial digest' of the firmware files being used is sent to a server, which can then decide to sign off on the result... or not.

Not only does this allow Apple to keep custom firmwares from getting loaded onto the device, but it also allows them to recall existing firmwares by keeping people from restoring to them in the future. To do this they simply would refuse to ever sign, for example, iPhoneOS 3.0 again."

Fascinating! Check out the full article.

Arrivals

Just a note to say that my MacBook Pro arrived yesterday (Sep 9). I've not had a chance to play much with it beyond transferring my data, but I'll be sure to report on it as soon as I can.

Also, today (Sep 10) my Snow Leopard Box Set — which I pre-ordered from Amazon on Aug 20 — finally arrived.

The MacBook Pro was a built-to-order system shipped from the plant in China and came in one week.

The pre-ordered software, counting from its release date, took twice as long to arrive.

You do the math. Me, I'm gonna go play with my new machine.

See ya!