Questions:
(1) Will Apple's Disc Burner in Mac OS 9.2.x burn bootable CDRs?
(2) Has anyone out there ever actually used a CDR backup made either by Apple's Disc Burner or via Toast/Toast Lite to recover their data after a hard drive disaster?
__________________________________________________________________
Paddy,
You're the cat's meow!
I got it burning.
It's a long story - you know me - but the bottom line is that I am now the proud creator of four shiny new coasters, burned via a freshly hacked copy of Apple's Disc Burner 1.0.2. :-)
The CDRW is a Plextor PX-W4824A, driver ver. 1.4.7, revision 1.01. Internal, running on a B&W 450 on MacOS 9.2.2. Currently no MacOS X on this machine. The CDRW works fine on my Linux machine - data and bootable CDRs. Using good blanks - Taiyo Yuden 48X.
Checked out
www.xlr8yourmac.com as per your kind guidance. The available hacked file would not load - I think it was for MacOS X. So I did a little ResEdit hacking on my own machine - it has been a while - as per the instructions on xlr8yourmac, and whadya know - the CDRW burned under Apple's Disc Burner 1.0.2!
Victory!
The burned CDR - which had a MacOS on it burned from a separate volume from the startup disk - burned with minimal extensions while doing nothing else on the machine - looked fine on clicking around, but was not bootable either via the Startup Disk control panel or via holding down the "C" key on startup. Disk Warrior 2.1.1, looking at the CDR from my hard drive, could not create a graph or go any further due to "directory damage" on the CDR - "Error: (2401, -60)." Trying to startup Norton Disk Doctor 6.0.3 on my hard drive with the new CDR on the desktop froze the computer so hard that it required pulling the plug to shut it down. And the computer was still acting strange on reboot even after the CDR had been removed - i.e., it would not boot to the hard drive volume that was actually highlighted in the Startup Disk control panel, despite quite a bit of fiddlin' - finally did with booting with extensions off, then PRAM zapping.
Tried burning four different ways - with and without OSs on the CDR, recording off the same volume or a different volume - all had the same result. Even a CDR with just one little SimpleText 1.4 file on it. Same problems. Four coasters is enough for me -
My tables will be dry for years.
Only other thing that I can think of would be to upgrade the CDRW's firmware and try again - but it would apparently require a Windows PC to flash the firmware, and a Windows PC is what I do not have. Oh, well.
Maybe it's time to dual boot my Linux machine with Windows - only for updating firmware on various peripherals.
A pretty forlorn use for Windows. But two OSs is enough for me - I have no interest in learning a third.
Looks like the ResEdit hack was superficial on this particular CDRW - probably a lot of other things going on under the hood.
Computer has been Disk Warriored, PRAM zapped, etc., and now seems back to normal.
It was fun. :-)
Thanks, again,
Epaminondas
_____________________________________________________________
Krissel,
Thank you for the Toasty comparisons - exactly what I was looking for.
And your thoughts on Retrospect are a reassuring confirmation.
See ya,
Epaminondas