• Test the memory so that, if it’s good, we can resell it instead of recycling it.
• Wipe the hard disk so that we can recycle the computer.

Tools:

• Tech Tool Pro 4 disc
• Tech Tool Pro 5 disc
• Mac OS X 10.5 Leopard install disc
• Mac OS X 10.3 install disc (came with laptop)

You’d think this would be easy…

Sunday

I spent a couple of minutes looking for the Tech Tool Pro 5 disc, but couldn’t find it, so I figured I’d try version 4 since I knew where it was. I’d forgotten that TTP4 doesn’t like this display. The colors were so messed up I couldn’t read it.

So I figured I’d use the Leopard install disc to wipe the hard drive first, and look for the TTP5 disc in the meantime. I spent at least an hour and a half looking through my CD rack and a messy pile of paper and had no luck. Meanwhile, the laptop froze while zeroing the disk. The screen had turned off, so I have no idea how much it actually wiped.

Then I found the TTP5 disc between two CD boxes.

At this point I figured I’d let the machine cool off overnight and deal with it the next day.

Monday

I got home from work, then set the laptop up on a cooling rack with a floor fan next to it. Booted to Tech Tool Pro 5 — no problem. The memory test options are time-based: do you want to test for 15 minutes, 1 hour, 2 hours, etc. I figured I’d start with 15 minutes and see what it did. It passed. Just in case, I ran it for another hour. Again, it passed. *whew!*

Not wanting to risk damaging the RAM, I powered the laptop off, unplugged it, removed the battery, opened up the access panel and removed the RAM extension. I closed everything up, plugged it back in, and tried to boot to Leopard.

10 minutes later, with the DVD drive still chugging away and the beach ball still spinning, I thought maybe I should take another approach.

I dug out the original install discs, which I’d found while looking for TTP5 the day before, and tried booting to that. 2 minutes, tops. That’s when I checked the Leopard box and saw that it required 512 MB of RAM. The G4 PowerBook only had 256 MB built-in. You’d think the boot loader on the disc could maybe tell you “This requires more memory than you have” instead of sitting there trying to load everything without any swap space.

Anyway, from the 10.3 installer I fired up Disk Utility, told it to zero the drive, and waited. 10 minutes later, it still said “Preparing to zero drive.” The day before, it had only stayed in that state for a few seconds before starting to show progress.

Great. Maybe it needed the memory. Power down, open it up, plug the RAM back in, close it up. This time it after booting to the installer, I couldn’t even get the menus to respond.

I figured it had managed to overheat (or whatever is going on) despite the fan and cooling rack. So I closed it down and put everything away to try again the next day.

Next Sunday

I picked things up again a few days later. First I pulled battery out in case it was overheating. So, with the extra RAM, I booted to the Leopard install discs and tried to zero the drive. After about 10 minutes, a message popped up that the computer needed to restart. So I tried again. Same thing.

Since I half-suspect the drive itself is part of the problem (though it could be a fan), at this point I decided it was probably as close to wiped as it was going to get. So I pulled out the RAM again and set it aside to sell, and figured I’d just send the machine back.

Then I remembered I should drain the battery.

What could I do with a machine that had no OS to drain the battery?

Of course! I could run Disk Utility! So I left the computer unplugged, booted to the 10.3 discs (since I’d already removed the extra RAM), and started to zero the drive again, figuring it would either freeze or run out of power.

About half an hour later I looked over…and as near as I could tell, it was done. There was no message, but there was also no progress gauge and no error…and Disk Utility showed an empty Mac OS filesystem on the drive.

Great! It finally worked! But I still needed to drain the battery, so I figured I’d start a second round. This time it froze, and the computer made grinding/clicking noises until it ran out of power. But the mission had been accomplished.

Aftermath

I sold the RAM on eBay last week. Now I just need to send the computer back to be recycled. End of an era in some ways, but we haven’t actually used it in almost a year.

I thought a major point of PulseAudio was to let applications share the sound card cleanly. *grumble* Sound worked fine before Fedora switched. I can’t even blame it on a bleeding-edge distribution, since from what I hear, Ubuntu has similar problems.

At least now I know (sort of) why it stopped again after applying the Complete guide to fix PulseAudio and video/audio VLC Media Player issues.

Sure enough, someone had plugged the sink with a paper towel, then walked away.

That’s inconsiderate enough in any public restroom. But when the sink is automatic, there’s another problem: Once the water reaches high enough, it trips the sensor, and it can get into a feedback loop. As near as I can tell, it filled up the sink until it hit the overflow drain, and eventually the sensor stopped registering movement and shut off.

I rolled up my sleeve, reached in there, and pulled the soggy paper towel out. It started draining, and I started washing my hands in another sink. As I watched, the movement of the water triggered the faucet, and it started running, though fortunately the drain was faster. By the time I was finished, it was clear. Problem solved, though it had already wasted a whole sinkful of water (or more — I have no idea who long it was running before it shut off).

So please, if you must plug a restroom sink with a paper towel, especially if it’s automatic, take two seconds to remove the paper towel before you leave.

But it’s still annoying to read the early reports that Android 2.0 “Eclair” won’t fit on the G1.

We have done this dance before, when rumors surfaced that the G1 wouldn’t be able to handle Android 1.6 “Donut.” Fortunately, engineers managed to squeeze it into the space available, and T-Mobile sent out Donut as an OTA (over the air) update to MyTouch and G1 devices alike. But I’ve had time to think about the issue, and my thoughts basically come down to this:

• New software eventually reaches a point when it can no longer support old hardware. You can’t run Snow Leopard on a G4 or Windows 7 on a Pentium II.
• When the hardware is usually tied to a fixed-term service contract (in this case, 2 years), the provider really ought to fully support it for the length of that contract. The G1 launched 1 year ago with (in most cases) a 2-year contract.
• Even if this is the last major update, my phone is still better now than it was when I bought it.

It will be very nice if history repeats itself, and Google and/or T-Mobile finds a way to cram Eclair onto the G1. Even if it means dropping the convenience of OTA updates and instead requiring you to download it to a PC and update over a USB cable. More likely, though, they’ll freeze the G1 on Android 1.6 except for bugfix and security updates, and it’ll be up to unofficial distributions like cyanogen to bring a newer OS to the older phone.

Because I don’t really want to mess with rooting my phone and installing a third-party distribution, if this is the end of the line for the G1, well…Android 2 has some really nice features that I’d really like to be able to use, but nothing that screams “must have!” The only real worry I have at this point is that app developers might start requiring newer versions of Android.

The other option: buy a newer phone. I’ll probably want to do that anyway in a year or so, but I’m not there yet. It still feels like I just got this one.

Last night, while watching “The Order 23 Job” on our MacBook, we got to the final commercial break — and TNT popped up an error saying that the content required Windows to play. The episode played fine. Previous commercials played fine. But this one? The DRM wasn’t compatible with the player on the Mac.

Yeah. The DRM for the commercial wasn’t compatible.

It wouldn’t have been so bad if TNT approached it the way Hulu does when a commercial fails to play, which is to blank the screen for the duration of the ad (typically 30 seconds) and admonish you for not watching the commercials. Unfortunately, the episode didn’t pick up again.

As near as I can tell, the player was set up to continue the episode when the ad finished, and didn’t account for the possibility that the ad might not play. To make matters worse, the scene selection thumbnails don’t work right in Safari, so we couldn’t jump straight to the final act.

Because neither of us wanted to spend a lot of time troubleshooting, we just went into another room and brought up the Windows box to finish the episode. I suspect the scene selection would have worked in Firefox on the Mac, but haven’t tested it yet. I did go back later to see where I could report the problem to TNT, but the wording in their FAQ suggests to me that they’ll just ignore any reports of Mac problems.

I don’t mind watching reasonable ads to get a free service, but if the ad breaks, it shouldn’t take the actual service down with it. You don’t kick people out of a movie theater because the previews didn’t play, and you don’t send them home part way through an event because one of the sponsors’ banners fell down.

• Listening to new Vertical Horizon. Hope their tour makes it out to SoCal – the last concert we saw was really good. #MusicMonday #
• Got honked at because I actually stopped before turning right at a red light & paused half a second to see if the pedestrian at the corner would step in front of me. #