What to do if you followed the "Other" dual-boot instructions?

I'm fortunate to have two MacBook Pros here at Pourhadi Labs. Yesterday I jumped on the opportunity to load XP
on one of them with Boot Camp. But when OnMac.net announced their Windows/Mac dual-boot solution a little while ago, our first instinct was to install right away and give it a whirl. Five hours,
six Cokes and a severe case of Post-Progress Bar Stress Disorder (PPBSD) later, we had a working Windows OS slowly sucking the life from one of our MacBooks. That was all well and good at the time...but then Apple introduced Boot Camp and a BIOS-enabling firmware patch and we were stuck with a copy of XP without all the bells and whistles of a functioning Windows installation (like, uh, graphics support).

Attempting to install the firmware update on a machine with the OnMac.net hacked-up bootloader doesn't work. Dunno why — we'd get the loud beep noise, indicating the MBP recognized an update was ready to install. But instead of loading it, OS X loaded instead. So hmph.

Turns out the only solution (that I found, at least), unfortunately, is totally formating your drive. Again. Then re-install OS X, load the firmware patch, and run Boot Camp. A good afternoon worth of tedious, PPBSD-inducing work.

Of course, I probably missed something that would've made the whole process easier. And I guess if you don't feel like going through the hassle of doing the installation The Right Way, you could get a Macintosh Drivers Disk
(produced by Boot Camp) from a friend with an (a) equivalent and (b) firmware-patched machine. If you do go that route,
let us know how it worked.

In fact, if you've installed the OnMac.net solution, let us know in the comments how you feel about the Boot Camp thing — and what you're going to do.