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

I finally started looking, and that’s not the case. It seems that the Airport Extreme chipset manufacturer, Broadcom, refuses to release Linux drivers or to release specs to allow anyone else to write Linux drivers.

I don’t expect it to do any good, but I signed my first online petition.

Ah, well, I can do almost everything under Mac OS, and for those occasions that I actually need Linux, I can always go solo or plug in a cable, though it does limit where I can hook it up.

Well, here’s a big fragging “Why Not:” I couldn’t remember the exact specs required. There was, however, a chart listing various laptop models, and the employees could look up requirements by model in the computer. The problem there was that I knew it as “the new 12″ PowerBook G4,” not as “Model A1010,” so they ended up (as near as I can tell) pulling up the specs for last year’s PowerBook (the 1 GHz instead of the 1.33 GHz). Naturally, the two models use different kinds of RAM.

When we got home last night, I cracked open the manual to compare the specs. Tonight, I waded through the Fry’s return line, and this time I brought the manual along — as I’d intended to do in the first place.

Everything went smoothly except for one glitch. The memory slot is covered by a panel with four size #0 Phillips head screws. I do have a size #0 screwdriver, and three of the screws came out easily. One of them refused to move, and the head ended up getting stripped somewhat. Eventually I was able to get it.

So, now the laptop has gone from having the smallest amount of memory at 256 MB (barring the ancient Mac clone in the closet) to having the most memory of all our computers at 1.25 GB.

So I should have thought of the hub immediately when the network started acting up today.

I had been on and off the computer and the net all morning with no noticeable problems, and Katie had been on for just a few minutes when it stopped loading websites.

The players involved:

• My computer, the homebrew Linux system
• Katie’s computer, the Mac G4
• The shared laptop (a PowerBook, not hooked up initially)
• The DSL modem
• The consumer-grade mini-router
• The ethernet hub
• Lots of cables

Initial troubleshooting:

1. Modem lights: all good.
2. Load a site from homebrew: check.
3. Ping G4: check.
4. Reset router: check.
5. Connect to router config: uh…. come on…

It was about that point that I looked at the hub and saw the insane amount of traffic apparently going between one of the computers and the router, along with a high number of collisions. Powering the hub off and back on didn’t seem to make a difference. Once I determined it was my computer, I disconnected it from the hub, and Katie was able to reach the web.

OK, so I’d found out what was preventing the G4 from connecting. Now I had to figure out what was going on. The traffic didn’t show up on any network monitors, and nothing seemed to be running to generate it. I started shutting services down one by one. No change. I logged off. No change. I deactivated the network and dropped to single-user mode. No change.

So I turned the machine off. Traffic stopped. (Good.) But the network card was chattering even when it was supposed to be inactive, which suggests either it was in some funny mode or it was broken. I hoped it was just some funny mode, because I really didn’t want to have to replace it. Aside from the whole disassembly process, it’s a combination USB2/Firewire/Ethernet card, so I’d need to either find another with the same combination or get a separate USB2/Firewire card… and I couldn’t remember whether there were enough free slots.

Power on. The insane network chatter started up during the BIOS check! There was no operating system running, and it was saturating the connection! Fine, I disconnected the computer and started trying to figure out whether it was something I could fix, or whether I’d have to replace the card.

At this point I pulled out the laptop and hooked it up so that I’d be able to do some troubleshooting online. But the weird thing was, the same bizarre traffic pattern was going on between the router and the laptop. Again, no sign of any network hogs actually on the system. I started to get suspicious.

I hooked my system back up to the network, watched the hub go insane, and then disconnected the router. Now, the ridiculous traffic was going between my computer and the laptop!

So here’s the situation:

• One device (the G4) seems okay.
• Of three other devices (including the connection to the Internet), any two cause the network to be flooded.
• What’s left that hasn’t been changed? The hub

Fortunately, I never got rid of the old 10-baseT hub when we went to 10/100. I dug it out of the closet, hooked up all the computers to it instead of the faster one, and you know what? Everything worked.

So now we need to head over to Fry’s or someplace and pick up a new hub. I’m hoping to find a wireless access point that has enough physical ports, because then we only need to get one device. (We want to go wireless for the laptop, but the other machines — with the possible exception of the G4 — still need cables.)

Woo hoo!

Presumably they had some in stock when they updated their store, in which case this is probably a good thing: it means not only are the new PowerBooks selling faster than expected, but they’re selling well through a Linux shop!

That said, if I have to wait too long I may just cancel this order and drive down to the Apple store. Of course, then I’d have to deal with repartitioning and trying to set up dual booting myself, and not only is it more complicated than dual-booting a PC*, there’s a lot less information available.

Ah, well.

* In particular, I don’t know of any utilities like Partition Magic or Parted that will allow you to resize an active Mac OS filesystem, so I would have to wipe the disk and reinstall Mac OS along with installing Linux.

And so tonight I finally ordered a dual-boot PowerBook from TerraSoft. We’re splitting the cost as a combined wedding and belated/early birthday present to each other.

Sometime this weekend, we’ll have a new computer in the house!