Still, it would be nice to have two portable computers for when we travel. I have a horrible tendency to hog the laptop when we get back to the hotel.

The thing is, we don’t need a second laptop for normal use. So getting another MacBook, or even a full-size Windows laptop, is overkill. Would a netbook do the trick? What do I use a computer for when traveling?

• Reading/writing email.
• Managing & uploading photos.
• Blogging & managing blog comments.
• Twitter (and more recently Facebook).
• Web access.

Yeah, I could easily get by on a netbook, freeing up the MacBook for Katie to use.

But do I even need the netbook?

Almost everything on that list is something I can do with my Android phone, assuming WiFi or a decent 3G signal. Not as quickly, perhaps. I type a lot more slowly on the G1 than a full-sized keyboard, and even at 3G speeds web browsing can be slow, especially on sites that don’t optimize for mobile use. And websites that require Flash still won’t work.

The real deal-breaker is (still) photo management. I can upload photos I’ve taken with the phone, but only one at a time — and I can’t transfer photos from the regular camera. The small screen size also makes it harder to look through a set of several similar photos and pick out the best one.

So I could manage with just my phone if I had:

• A way to transfer photos from my camera to my phone. (The hard part. Android issue 738 is an enhancement request to be able to connect USB devices. It’s not clear whether the G1 hardware supports USB On-The-Go or not, but the drivers and Android OS don’t — at least not yet.)
• An app to mass-upload photos to Flickr. (They exist, I just need to research and try a few out.)

I guess for now the best way to handle it is for me to just upload photos on the laptop, without taking the time to label them, then hand it over and move to the smartphone. Though if the network connection is particularly slow, like it was at Comic-Con International this year, that would still be problematic.

Of course, we don’t have any travel plans at the moment until next spring. Who knows? By then a netbook (or a newer phone) may be more practical.

• 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.

Better something modular and easy to get at (well, except for the one stripped screw) than something intrinsic to the machine. Under the circumstances, I’m just having the shop replace it.

Though I guess I should’ve known better than to trust this guy:

moar humorous pics

(Check out the original lolcat post if you don’t recognize the phrasing.)

Assuming the box continues to pass diagnostics with the new memory, I should be able to pick it up at lunch on Monday.

Update: Success! The computer is back, and working again!

We only lost a few recent files. I had a chance to grab them on Saturday, but unfortunately I misread the signs and thought it was a software problem. Hey, you install a bunch of stuff including a system update, and the machine freezes, you figure it’s a software problem. Until it happens again, and this time it won’t come back up.

After doing all the diagnostics & resets I could possibly come up with, I set up an appointment at the local Apple Store’s “Genius Bar” during my lunch break today. They confirmed it was the drive, and since it’s long out of warranty, they pointed me to a local repair shop. (They were willing to do the job, but can only order parts directly from Apple, so it would’ve been insanely expensive just for the drive.)

Fortunately, as far as laptop hardware failures go, a hardware drive is relatively easy to fix. If the case were simpler, I’d be willing to do it myself, but as the Apple tech joked, “It takes 36 screws just to get the case open.” At least, I think he was joking.

So instead of having to replace the entire computer, or send it in and wait several weeks, we’re looking at ~$200 and 3–5 days. And while I was at it, I sprang for double the capacity.

I can live with that.

Update: It turned out to be the RAM upgrade, not the disk, which makes it considerably simpler to resolve. Finally got it back the following Monday.

“So,” I said. “I have to ask myself. Do I feel lucky?”
“Well,” Katie replied. “Do you? Punk?”
“What the heck.”

I’d done some research on application compatibility earlier this week, and the PowerBook looked ready. Katie’s desktop is going to need further study. The Mac Classic environment will no longer run under Leopard, and she’s still got a couple of Classic apps she pulls out occasionally. Also, Photoshop 7 is reported not to run under Leopard, and Adobe isn’t testing or updating anything older than CS3.

But the laptop? No critical data to back up (it’s all duplicated from the desktops), and everything we actually use on it has been tested on at least a pre-release.

So I fired up Netscape 4 for old times’ sake (and discovered that this theme is completely unreadable in it; then I switched the CSS around so that Netscape 4 won’t even try). Then I popped in the disc, selected some options, and let it install during Pushing Daisies.

No problems so far. Disk space is running low, but it’s a 3-year old laptop (so the drive is small) and I did an Archive and Install, so it has a backup of the old OS. Once it’s clear that everything works, I can free up ~6GB right there. It may also be time to wipe the Yellow Dog Linux partition. I haven’t used it in over a year.

Some highlights: I really like finally having virtual desktops (what Apple calls “Spaces”). The new search highlighting, previously seen in the Safari 3 beta, appears in other apps as well. Heck, Safari 3 is a big jump itself. (Hey, Apple, where are the Windows and Tiger releases?)

Last night I drained the old battery, plugged the new one in, and packaged up the recalled one in the box. At lunch today I went to the post office to send it off.

As I was walking up the steps, I remembered the “Does this package contain anything liquid, explosive, or otherwise hazardous?” question that postal clerks are required to ask. If you’re mailing a defective battery that could theoretically burst into flames, how exactly are you supposed to answer?

I figured it would be best not to joke about it.

As it was, I just said it was a laptop battery straight out, so the question didn’t come up.

Meanwhile, I’m reading the release notes, and found one item particularly interesting:

There are new experimental drivers that provide support for the widely-used Broadcom 43xx wireless chipsets (http://bcm43xx.berlios.de/).

This is the chipset used in Apple’s Airport Extreme wireless networking interface, which is what you’ll find in just about every wireless-capable Mac made over the last few years. Until recently, there were no Linux drivers because Broadcom would neither write their own nor release specifications for others to write them. The project at Berlios has apparently reverse-engineered the chip to produce an open-source driver, with its first usable version in December

One of the reasons I so rarely use Linux on the PowerBook is that it can’t use the wireless network. The last time I used it was a couple of months ago. I booted it into YDL just to make sure all the software was current, and discovered there hadn’t been any updates since July—even though I could think of plenty of security fixes that had been released since then. Now that Fedora Core has had two releases with full PowerPC support, I may just replace the Yellow Dog Linux partition with Fedora Core. A better security update policy, a wider range of applications, and possibly wireless network support. Sounds like it might be worth it.