
Signature
James Leo Ryan ..... Austin, Texas ..... taliesinsoft@mac.com
> I have a MacBook Pro which is normally connected to two external firewire 800
> drives, one with two partitions and one with four partitions. Five of these
[quoted text clipped - 14 lines]
>
> I'm open to suggestions and such, and here are the "thanks" in advance!
Beyond me at this point (still awaiting my MacBook which should
arrive by Tues).
But have you checked the Apple discussion forums? Lots of good
info and help from users there.
Phil
> I have a MacBook Pro which is normally connected to two external firewire 800
> drives, one with two partitions and one with four partitions. Five of these
[quoted text clipped - 10 lines]
> have no trouble creating such a virgin boot partition and they could offer no
> suggestions as to why my attempts to do such have been thwarted.
This is a little convoluted but it will work. First, create a clone of
your current system on a SuperDuper! partition. Do a clean re-install
of OS X on your computer. Use SuperDuper! to clone it to your "virgin"
drive. Restore the original system from your backup.

Signature
Robert B. Peirce, Venetia, PA 724-941-6883
bob AT peirce-family.com [Mac]
rbp AT cooksonpeirce.com [Office]
Matthew Kirkcaldie - 17 Jul 2006 12:41 GMT
> > I would like to create a "virgin" installation of OS X on that currently
> > empty partition. The mystery is that any attempt to install OS X on that
[quoted text clipped - 10 lines]
> of OS X on your computer. Use SuperDuper! to clone it to your "virgin"
> drive. Restore the original system from your backup.
Actually that might not work. The partition table needs to be in a
particular format for Intel Macs to see it as a bootable drive. PowerPC
Macs (G3, G4, G5) need an Apple partition map, Intel Macs need the GUID
partition scheme. Unless the disk is partitioned correctly for its
processor type, the Mac cannot boot from it, no matter what system
software is on it. It's also impossible to change the partition scheme
unless you completely erase the entire drive.
If the drive IS partitioned using the GUID scheme, I've got no
suggestions, sorry. If not, the OP should tell the "geniuses" at the
Apple store they might want to consider reading a few manuals and
updates.
Cheers,
Matthew.
Robert Peirce - 17 Jul 2006 18:10 GMT
In article
<m.kirkcaldie-B2DCC9.21411117072006@un-2park-reader-01.sydney.pipenetwor
ks.com>,
> > This is a little convoluted but it will work. First, create a clone of
> > your current system on a SuperDuper! partition. Do a clean re-install
[quoted text clipped - 8 lines]
> software is on it. It's also impossible to change the partition scheme
> unless you completely erase the entire drive.
The writer said he had made bootable backups with SuperDuper! so this
would work in this case. It might not in other cases, but I wasn't
addressing that. Frankly, I wasn't even aware of it. The key for me
was the claim that he could use SuperDuper! to make bootable backups.
OTOH, I will have to keep this in mind if/when I get a dual-core
machine. It will explain why my backups fail!

Signature
Robert B. Peirce, Venetia, PA 724-941-6883
bob AT peirce-family.com [Mac]
rbp AT cooksonpeirce.com [Office]
TaliesinSoft - 17 Jul 2006 16:22 GMT
> This is a little convoluted but it will work. First, create a clone of your
> current system on a SuperDuper! partition. Do a clean re-install of OS X on
> your computer. Use SuperDuper! to clone it to your "virgin" drive. Restore
> the original system from your backup.
And yes, it did work! Many thanks.

Signature
James Leo Ryan ..... Austin, Texas ..... taliesinsoft@mac.com
Fred Moore - 17 Jul 2006 19:37 GMT
> > This is a little convoluted but it will work. First, create a clone of
> > your
[quoted text clipped - 6 lines]
>
> And yes, it did work! Many thanks.
Glad you got it to work. As to the real cause, there have been a few
discussions at various places around the web on similar Firewire
problems. The solution for some was to obtain a firmware update from the
drive enclosure's manufacturer, so you might want to check into this.
The latest firmware _might_ prevent other problems as well.
--Fred