Okay. So I've had Disk Warrior 3 for several months now. A few months ago I booted from it successfully and ran it with no problems. Since that time I moved, during which time the CD got a little banged up. I decided to make a bootable CD using bootcd (I had copied DW to my harddrive). I know this CD works, because I took it to work and booted a machine in X using it. BUT this CD will not work at home. What happens is this:
(1) CD in drive (original internal or ext usb drive), startup [startup disk changed to CD or startup with "c" key held down],
(2) machine thinks for a bit, accesses CD in drive, screen flickers,
(3) machine restarts again ("c" key still held down), this time, the old os 9 happy mac shows up (which makes me think it's looking for OS 9!?), accessing CD ... but
(4) gives up and restarts again.
Happy mac and restarts continue ad infinitum/nauseum until I cease holding "c" key, and machine boots up from internal HD in X.
The machine: ZIF G4-upgraded beige G3 running Jaguar 10.2.6.
I have OS 9.2.1 on both partitions of the internal HD as well as X, but I rarely use them any more (and never use "Classic").
I'm planning on upgrading to 10.2.8 and I hope that solves the problem, but I'm wondering if anyone has heard of this kind of behavior. Isn't there a way to get/set the boot parameters or something in the command line?
Thanks in advance for any response.
-CG
(1) CD in drive (original internal or ext usb drive), startup [startup disk changed to CD or startup with "c" key held down],
(2) machine thinks for a bit, accesses CD in drive, screen flickers,
(3) machine restarts again ("c" key still held down), this time, the old os 9 happy mac shows up (which makes me think it's looking for OS 9!?), accessing CD ... but
(4) gives up and restarts again.
Happy mac and restarts continue ad infinitum/nauseum until I cease holding "c" key, and machine boots up from internal HD in X.
The machine: ZIF G4-upgraded beige G3 running Jaguar 10.2.6.
I have OS 9.2.1 on both partitions of the internal HD as well as X, but I rarely use them any more (and never use "Classic").
I'm planning on upgrading to 10.2.8 and I hope that solves the problem, but I'm wondering if anyone has heard of this kind of behavior. Isn't there a way to get/set the boot parameters or something in the command line?
Thanks in advance for any response.
-CG