So, it initially looked as if swapping the DIMMS around and reseating everything fixed my PowerBook. Paranoia is an old friend, however, so I decided to do some more testing before trusting it.
First up, TechTool Deluxe, a piece of software that Apple gives you when you buy AppleCare support. I ran the full suite of tests half a dozen times, with no errors.
Next up, World of Warcraft. I booted normally, logged in and had one of my characters stand in the middle of the busiest city, opened up the Activity Monitor, and… success! Or, more precisely, failure. It locked up good and hard, filling the screen with garbage.
Packed it up, made a support appointment at the Apple Store, walked over at the appointed time, waited 40 minutes for someone to get to me, and then spent the next 40 minutes proving that the problem really existed.
Standard diagnostic tools passed with flying colors. The tech’s random mix of apps worked just fine. We ended up testing each DIMM separately, loading up memory and CPU with World of Warcraft, QuickTime Player (random music video set to loop), and VLC (random VOB file set to loop). With the DIMM that I initially had figured was the good one, this produced several crashes within five minutes. The other DIMM worked fine, and in fact it’s been running for about half an hour now back in my office.
They’ll have a replacement DIMM for me in a few days, and meanwhile I’m going to keep stressing the machine to make really sure there’s nothing else wrong. Then I’ll migrate back from my G3 iBook.
Update: I spent a few days abusing the replacement RAM, and now everything’s back to normal. It was interesting using the G3 iBook for a while; it was perfectly adequate for use at work (Terminal, Safari, Mail, iTunes, MS Word, SSH Agent, Cisco VPNClient, Firefox, and Thunderbird), and only really showed its age when confronted with video clips (no, Choco Party is not work-related, or particularly work-safe, but it was certainly popular, especially after I googled out the name of the featured model, Miri Hanai).
I don’t plan on buying one of the current MacBook Pro models, even after they sort out all the early hardware problems (I’ve had enough early-adopter fun with Apple for a while, thanks). It will probably be a year before it’s worth the effort of migrating my primary machine to the new platform, but an x86 Mini is a possibility. We’re buying some for the office, so I’ll be able to check it out soon.
Here’s my simple RAM-thrasher. Kicking off half a dozen of these is more predictable than standing around in Ironforge in World of Warcraft:
#!/usr/bin/perl open(In,"/dev/random"); foreach (1..250000) { read(In,$x,1024); push(@x,$x); } @y = sort @x;
So, it took two trips to the shop to get my brand-new Quad G5 running reliably, demonstrating once again that it’s never safe to buy The Latest Thing from Apple (or, to be fair, most vendors). It works great now, and when I took it in the second time, it received automatic priority as a “looper”, so it was done in two days. That’s the good news.
Now for the bad news: this morning, my PowerBook died with repeated kernel panics (most likely bad RAM, from the symptoms). I had backups, of course, but I didn’t need them. All I had to do was carry it over to another Mac, connect them with a FireWire cable, and reboot the second Mac from the PowerBook’s hard drive. In 30 seconds I was back in business, with everything exactly the way I like it.
I immediately made a fresh backup to a portable FireWire drive, and just for good measure, stored a disk image of that backup on the other Mac’s drive. Since I still need a laptop, I’m now booting my ancient 700MHz G3 iBook from the FireWire drive, and that’s what I’ll be carrying to work until the PowerBook is fixed. It’s a lot slower, and a bit clumsier to carry around, but I don’t have to spend any time fixing preferences, reinstalling applications, etc, etc.
Best of all, everything was done with vendor-supported tools that ship with Mac OS X, without ever opening up a case. You can rescue data from a broken Windows or Linux laptop, but the process is a touch more involved (coughcough), and the odds aren’t good that you can just boot another computer from that disk.
Update: okay, there are a few things that don’t “just work” when you pull this trick. The OS stores some of its preferences on a per-host basis, keying off the MAC address on the primary ethernet port. These are stored in ~/Library/ByHost/, and include that address in their name. Most of them are pretty obvious, like network port configurations, display preferences, and iDisk synchronization, but I was surprised that it included the input menu contents for multi-language input. The menu was there, but I had to click the checkboxes to re-enable Japanese input. So far, that’s the only host-specific preference I’ve had to set.
So, add 5 seconds to the transition time. :-)
There is one annoying side-effect to this. If you’ve turned on local mirroring of your iDisk, that mirrored copy is also host-specific. It makes sense, but it means that I have a hidden disk image chewing up 1GB.
If you’re going to make your VPN Client software completely incompatible with the Mac OS X built-in VPN support, could you at least make it capable of connecting to non-Cisco servers? It’s just not fun to be forced to delete my other VPN config and reboot every time I need to connect to one of your servers. It’s not like this stuff is some kind of standard or something…
Love, J
I’m sorry, but this is bullshit so raw that even a Democratic presidential hopeful wouldn’t touch it:
The parents filed a suit against Blizzard Entertainment on Wednesday, saying their son jumped to his death while reenacting a scene from the game, the report said.
What scene would that be? The one where you deliberately send your character off the edge of a cliff, knowing that he’ll die when he hits the ground? Or did he leave a note saying that he was going to teleport to the top of the Twin Colossals and try out that cool new Parachute Cloak he picked up at the Auction House in Gadgetzan? Or did these loving parents just not pay enough attention to their kid to notice that he was suicidally depressed?
If this cash-grab fails, no doubt they’ll turn up a witness who claims that the kid was shouting “Accio Firebolt!” on the way down, and sue J.K. Rowling next.
Daring Fireball demonstrates at length why it’s a bad idea to pretend that a programming language’s syntax is “English-like”. Personally, I’ve avoided AppleScript due to a bad experience with Apple’s similar HyperTalk language, which scarred my brain the day I tried to do something extremely simple,and found myself typing:
get line one of card field short name of the target
This was the simple, concise way to do it…
A Japanese-language online radio show I like, 6Sense, is published in an annoying way. They keep more than a month’s worth of archives online in MP3 format, but each episode is split into 60+ audio files, accessed through a Flash interface.
Examining the Flash app told me very little. Examining my Privoxy logs gave me the regular-but-unpredictable naming convention for the audio files, and a little more digging turned up the URL that the Flash app calls to get the list for a specific day. After that, I simply used wget to download the complete show… as 60+ MP3 files.
Knowing that someone had to have written a Perl script to concatenate MP3 files, I googled and found mp3cat, part of Johan Vroman’s mp3cut package. Making the results into a podcast required the use of another Perl script, podcastamatic, and a web server to host the results. I just turned on web sharing on my Mac, moved the files into ~/Sites, and typed the appropriate URL into iTunes.
With the latest version, iTunes supports podcasts directly, but the integration is kind of peculiar, and carries over to the iPods. Both correctly track what you’ve listened to, and where you left off in the middle of an episode, but otherwise they’re not treated like regular audio tracks.
In iTunes, if you finish listening to one episode of a podcast, instead of moving on to the next episode, it skips to the current episode of the next podcast. On iPods, there’s no concept of “next” at all; when a podcast ends, it just stops playing. If you’ve set it to repeat, it repeats the episode you just heard. Unfortunately, not all podcasts are an hour long; some are quite short, such as ナナライフ, which averages about 90 seconds.
Ironically, the least sophisticated iPod handles podcasts the best right now. The iPod Shuffle just treats them as sound files, and syncs up the play count when you connect it to your computer. When you delete an episode from iTunes, it’s deleted from your Shuffle. Not perfect, but better for long drives (and I’m driving 150 miles a day right now, as I settle in to my new job…).
When I was getting ready to switch jobs back in June, I decided it would be a good time to consolidate all my backups and archives, sort out my files, and in general clean up my data. The vehicle I chose for this exercise was a pair of LaCie 500GB Firewire 800 drives.
The idea was to copy everything to one of them, then clone it all to the second one, which would be kept offsite and synchronized on a weekly basis over the Internet. My many other Firewire drives could then be used for short-term backups, scratch space, etc. One thing led to another, though, and I didn’t unpack the second drive until Tuesday night, and it was DOA.
LaCie’s online tech-support form didn’t produce a response, so I called them this morning. Ten minutes later, a replacement was in the mail, due to arrive tomorrow. They charged the new one to my credit card, and they’ll refund the money once I ship the dead one back (using their prepaid label). Because the price has dropped since June, the refund will be about $30 larger than the charge.
While I’d have preferred to have a working drive the first time, I like the way they handle problems.
I hate Adobe Illustrator. I’ve always hated it. If the folks responsible for CorelDRAW! hadn’t turned it into crap by constantly shipping new major releases that didn’t fix crippling bugs that were in the previous version, I’d still be using it. On Windows, no less.
Oh, sure, they never really got on the typography bandwagon, severely limiting your ability to use features like ligatures, swash caps, true small caps, optical kerning, etc., but there were a lot of things I could do in Draw 4 that are still a complete pain in the ass in Illustrator 12. Some days, I still find myself writing PostScript by hand and importing the results, just to save time and energy.
And it keeps getting slower. Photoshop is still pretty snappy on my 1.25GHz G4 PowerBook with 2GB of RAM, but Illustrator gets sluggish well before I start trying to get fancy, and it doesn’t have Photoshop’s scriptability, so I can’t easily automate a complex task and walk away while it runs. There’s no real competition out there today, though, so I’m stuck with it.
Sigh. Done ranting for the day, off to cook and kill murlocs. (note that these are separate activities…)