Here’s how it’s done…

1. Have your cat awaken you at 4:30am, pawing your face to let you know he’s hungry.
2. Head downstairs in a stupor, leaving the annoyingly-bright lights off.
3. Open cat food and start scooping it into the cat’s bowl, letting the cat know just how you feel about the 4:30am wake-up pawing.
4. See the light from, and hear the click of, the downstairs bathroom light coming on.
5. Have heart attack.

OK, so clearly I didn’t actually have a full-on heart attack. Instead, my pulse merely doubled and I had an amazing adrenaline surge.

As soon as I started breathing again (quietly), I reasoned that any intruder with even a quarter of a brain wouldn’t actually bother to turn on the bathroom light, nor would they have ignored my easily-audible talking to the cat.

So what was the cause of the spurious pulse-quickening light? It turns out that our six-year-old daughter apparently heard me, and had gotten up to use the bathroom. Why she chose to come downstairs–very quietly, I might add–I have no idea, as there’s a bathroom just down the hall from her room.

Needless to say, after bundling our daughter off to bed again, I found it basically impossible to go back to sleep, given the adrenaline coursing through my veins.

I’m a big fan of golf, both real and virtual. The best iPhone golf game I’ve yet found is Tiger Woods PGA Tour, from EA. At $10, it’s not cheap, but it is fun. It does, however, suffer from one fairly annoying problem: it’s way too easy in its default mode. As an example, here are the final results from a four-round tournament at St. Andrews:

Per round, my average score (my player’s first name is Wheat) was 15.25 under par, which is simply unbelievable. Look at second place–14 under par for four rounds, or worse than I do for one round! At about 3.5 strokes under par per round, however, the second place score is much more realistic.

So what’s the problem? The problem is that TW for the iPhone includes both a caddy and a putt preview feature. Combined, those two features making putting the ball ridiculously easy. Here’s how to use those two features together to crush the PGA events in Tiger Woods.
More »« Less

Greetings, my faithful handful of readers…

For an upcoming Macworld project, I need a large volume of email. To that end, I’ve set up a new account in which to build my collection. The address is:

ineedalearjet@gmail.com

Please feel free to share this address with anyone, post it on your blog, Tweet your friends about it, etc. I’m looking for a big collection; I assume most of it will be spam, but if you feel like just dropping a line and saying “hello!,” that’s fine, too! Note that I won’t be replying to any messages sent to this account.

Thanks in advance for help spreading the word!

With this morning’s semi-annual changing of the clock for Daylight Savings Time (DST), I’m once again left to ponder…why, in this era of GPS-equipped automobiles, do I have to manually set the clock in my car? We had, until very recently (we sold one), three cars with factory GPS units. Of those three, only one uses the GPS signal to set the car’s clock. In the other two vehicles, we have to manually adjust the clock, even though an extremely accurate time and date signal is one of the features of the GPS satellites.

So my car knows the date, and it knows the correct time…so why can’t it figure out that DST has started or ended?

Things have definitely improved over the last 30 years, though–today, we had only a handful of clocks to change. In addition to one of the cars, there were a couple of televisions (another device that seems to me should be capable of changing its own clock), our microwave, and a few assorted clock radios and wall clocks. But most of the clocks we own synchronize automatically with a time signal, so they were correct when I woke up this morning. The computers, of course, handle the change seamlessly. (The fact that I stopped wearing a wrist watch a few years ago also helps; I have ten or so sitting in a drawer somewhere, but I no longer bother to set them.)

I’m not sure I’ll live long enough to see a DST start/stop day where I don’t need to manually set a clock…but I’m hoping I do!

For quite a while, I’ve wanted an electric radio controlled (R/C) helicopter–one of the small ones you can fly around inside the house. Over the last couple years, I’ve tried cheap versions (complete waste of money; they fly like crud), and the expensive versions seemed too, well, expensive for what would be nothing more than a silly time waster.

Then, just before Christmas, E-Flite released the new Blade mCX, a smaller, lighter, and easier-to-fly version of their Blade CX2. The CX2 was one of the expensive models I’d passed on earlier. The mCX, however, comes in $50 cheaper than the CX2, and came close enough to my self-imposed $100 limit that I bought myself one for Christmas :). (Click the image at left [and any image in this writeup] for a larger view.)

After only a few minutes with the mCX, I was hooked. This machine is unlike any other R/C helicopter I’ve ever tried to fly. Within a couple minutes of my first power-up, I had it hovering in place, and could maneuver it relatively well. Even for me, a complete novice to R/C flying, this machine is incredibly easy to fly. R/C purists probably dislike it, though–relying on dual counter-rotating rotor blades and a gyro, the mCX isn’t a “real” R/C helicopter in any sense. But for my desires, it’s (nearly) perfect.

The mCX weighs one ounce (with battery), and has a rotor span of just 7.5 inches. Everything about this machine is tiny, including the motors (the round items in the image at left) and the battery (visible at the bottom of the image; it’s got a red dot on it). The front of the machine is the brains, though–a circuit board there holds the gyro, motor control units, fully proportional servos, and radio receiver. Amazing that it all weighs but an ounce.

Combine that with very sensitive flight controls, and you can fly the mCX almost anywhere–I’ve flown it above the garage’s workbench, for instance. The throttle is amazingly precise, making it easy to fly at whatever altitude you desire. As a brief example, here’s a video of me flying around in the den, trying to keep the mCX within view of the fixed video camera:

Read on for more about this amazing little machine…
More »« Less

If you know me at all, you know how I feel about glossy screens, especially on laptops. As nice as the new MacBook and MacBook Pros are (and they are very nice, based on some early hands-on time with the new MacBook at the local store), the glossy screens are a deal breaker for me. I tried to use a MacBook for six months or so, but in the end, the glossy screen was too much for me, so I went up to the MacBook Pro and its nice matte display.

With the lack of a matte option on the new MacBook Pro line, I won’t be buying another Mac laptop (of the 15″ variety) until Apple comes out with some form of non-glossy screen–whether that’s a true matte screen, or just an effective anti-glare coating, I don’t really care. But until there’s a solution, I’m going to use what I have for as long as I possibly can.

My current machine is a two-year-old 15″ 2.33GHz MacBook Pro with 2GB of RAM–and it’s a very nice machine. However, it’s already two years old, and I want to get at least five more years out of my matte screened laptop…so I figured I’d go look on eBay for used last-gen 2.6GHz MacBook Pros–the fastest 15″ machine with a matte screen available, basically.

On my way to eBay, though, I got sidetracked by the Special Deals section of the Apple Store–otherwise known as the Refurb Store.
More »« Less

I found the following examples of horrendously poor translation on the same box–a kid’s play set called Fairyland Journey that we bought a while back at the local mall (click each image for a larger version):

I know good translation is difficult and expensive, but some of these are so bad they’re hilarious. My favorite is probably “FLASHING ENTER!”, used in a context where it makes absolutely no sense (not that I can think of many contexts where it does make sense!).

When iTunes 8 came out, one very annoying change was the removal of the “Show iTunes Store arrow links” preference — in previous versions of iTunes, you’d toggle this setting to remove the link arrows that appear when you select an item in your Library.

I never use these things, and they bother my eye, so as soon as I got my hands on iTunes 8, I started looking for a solution (here’s how I do that). With some help from Kirk McElhearn, we soon found the solution in a hidden preference value — a variable named show-store-arrow-links.

After a quick test, we confirmed that it worked, and I wrote it up as hint on Mac OS X Hints. At the same time, I ran a Google search for ’show-store-arrow-links’, and came up with no matches.

Note that this does not mean Kirk and I were the first people to post about this workaround — more than likely, it had already been posted elsewhere, but Google hadn’t yet indexed those sites (we were doing this shortly after iTunes 8 was released).

Still, I thought this was a perfect chance to see how things propagate across the internet, as I could repeat my search for show-store-arrow-links over time, and see how quickly the hit count increased. Given the uniqueness of the term, any matches would definitely be people either linking to the hint on some other site, or actually posting their own version of the hint.

Within two hours of the original hint’s posting, the hit count was up to five. After seven hours, 137. At 24 hours, 384. At that point, I grew bored with tracking the increases, and tabled the study. Today, though, after 12 days, I ran the search again, and there are now over 1,000 sites that contain the hint (or a link to it) on how to block the iTunes Store arrow links in iTunes 8.

I think that’s a good measure of how many people dislike these arrows, and who really wish Apple would have left that preference in place. (Sorry iTunes for Windows users; preferences are stored differently in Windows, and I’m not sure anyone’s figured out how to make similar modifications on that platform.)

OK, so it’s strange math :). The top-left image (taken before we bought the place; I didn’t actually take any “before” pictures) is the wall of brick that surrounded the fireplace in our home. Add to that a Dasco Pro Mason Chisel with Hand Guard and a Stanley Three-Pound Drilling Hammer, and the end result is a pile of brick in the driveway … oh yea, you need to add a fair bit of sweat, and a wheelbarrow will greatly ease the task of hauling out the brick.

This was the first time I’d ever tried to demolish a brick wall. Overall, it was actually a bit easier than I expected, other than the sheer number of bricks involved. I can highly recommend the chisel I used; it made short work of the mortar between the bricks, and the hand guard definitely works well–I didn’t hit my hand once, despite swinging the three-pound hammer probably well over 1,000 times to break out all the bricks. If you’re going to break down a brick wall, I definitely recommend a chisel with the hand guard.

(I took out the wall so that we could use the space on the right of the fireplace for a built-in bookshelf and storage cabinet, and to install a gas fireplace in place of the current wood-burning insert. Those projects, however, will be handed off to a professional–I can destroy, but I’m not so good at the build-it-up part!)

For the last few weeks, I’ve been getting hundreds of registrations here, and given (a) there’s no reason to register except to post a comment, and (b) there aren’t very many comments posted, I figured something was up. Until yesterday, though, I didn’t know what was going on. Now, thanks to the WordPress 2.6.2 release, I do:

With open registration enabled, it is possible in WordPress versions 2.6.1 and earlier to craft a username such that it will allow resetting another user’s password to a randomly generated password. The randomly generated password is not disclosed to the attacker, so this problem by itself is annoying but not a security exploit. However, this attack coupled with a weakness in the random number seeding in mt_rand() could be used to predict the randomly generated password.

In other words, by registering often enough with specially-crafted usernames, you may eventually be able to force the admin user’s password to be reset to something random, and you may know that random password. Scary stuff. So today, I upgraded to 2.6.2, and cleaned out the vast majority of recently-created accounts.

If you’d signed up for a legit account and I zapped it, please just register again — and sorry for the inconvenience.