My macbook has a 320gb drive which I thought I’d partition - Snow Leopard on the main part, but I’d install ALL my old Tiger installation in another partition.
I created the partition successfully in disk utility, and then used Carbon Copy Cloner to make an entire bootable copy of the desktop Mac running Tiger. I did this by starting the desktop Mac in target mode and then copying the entire drive. It took several hours, even by Firewire, but then it was done and I had another drive showing on my macbook desktop and in the ‘devices’ list of the Finder.
But it doesn’t show up if you go to system prefs and try to choose it from startup disk? CCC said the volume would be bootable…but I can’t see how?
Have I done this wrong way around? Should I have started the Macbook in target mode and the Powermac in normal mode? I find the instructions somewhat confusing…they always tend to say “startthe mac in target mode…” but never tell you which mac to start in target mode
Possibly your MacBook doesn’t like the Desktop install of Tiger.
Instead install a fresh copy of Tiger on the MacBook partition then
use Migration Assistant to transfer everything else over from the
Desktop Mac.
My macbook has a 320gb drive which I thought I’d partition - Snow Leopard on the main part, but I’d install ALL my old Tiger installation in another partition.
I created the partition successfully in disk utility, and then used Carbon Copy Cloner to make an entire bootable copy of the desktop Mac running Tiger. I did this by starting the desktop Mac in target mode and then copying the entire drive. It took several hours, even by Firewire, but then it was done and I had another drive showing on my macbook desktop and in the ‘devices’ list of the Finder.
But it doesn’t show up if you go to system prefs and try to choose it from startup disk? CCC said the volume would be bootable…but I can’t see how?
Have I done this wrong way around? Should I have started the Macbook in target mode and the Powermac in normal mode? I find the instructions somewhat confusing…they always tend to say “startthe mac in target mode…” but never tell you which mac to start in target mode
Well I’m sure it was a retail version of tiger originally…just that I never got the disks. Doesn’t it make it non-retail, does it?
A new Macbook?..no, it must be three years old I imagine, it’s a 2ghz model with the divided trackpad. The Mac install disks that came with it (the grey ones, two disks) appear to be Tiger…when you load a disk and it shows the contents, there’s a pdf called ‘Welcome to Tiger’.
The age of the MacBook won’t be the problem then so I think it’s that
you’re transferring a Desktop install of Tiger onto the MacBook.
Unless you can install Tiger on the MacBook from disks I don’t think
it’s going to work.
Well I’m sure it was a retail version of tiger originally…just that I never got the disks. Doesn’t it make it non-retail, does it?
A new Macbook?..no, it must be three years old I imagine, it’s a 2ghz model with the divided trackpad. The Mac install disks that came with it (the grey ones, two disks) appear to be Tiger…when you load a disk and it shows the contents, there’s a pdf called ‘Welcome to Tiger’.
Well I can try and use the original grey disks to install Tiger on the partition, I suppose?
Just seems odd to me. The ‘clone’ is everything…Tiger install and data, lock stock and barrel. If it works on disk space A (say my Powermac), why won’t it work on disk space B (macbook) or diskspace C (external USB drive). They’re all sata drives formatted mac os extended?
When you install OS X the system installs only the components required
for that particular machine so a Desktop install won’t necessarily
have everything needed to support the different hardware of a laptop.
Similarly the disks supplied with one type of Mac aren’t designed to
work with a different type of Mac. Only the retail versions of OS X
have everything necessary to support every possible hardware
combination.
Well I can try and use the original grey disks to install Tiger on the partition, I suppose?
Just seems odd to me. The ‘clone’ is everything…Tiger install and data, lock stock and barrel. If it works on disk space A (say my Powermac), why won’t it work on disk space B (macbook) or diskspace C (external USB drive). They’re all sata drives formatted mac os extended?
Talk about making things more complicated than they need be. What should, in any sensible reality, be a five minute job is turning into a two day marathon…
Come on Apple, get a grip!
Oh and by the way, if I do successfully install Tiger on the partition, I’ll then have to update it to 10.4.11 of course…!
Talk about making things more complicated than they need be. What should, in any sensible reality, be a five minute job is turning into a two day marathon…
Come on Apple, get a grip!
Hold hard there Hugh! It’s fairly well known that the disks that come with Macs are machine-specific. I’ve had many experiences in the past where a system on a disk would not install onto a particular machine; as Roger has said, only the retail version will install on any machine. That is to say, the system that you buy as a standalone product, not the disks you get with the machine. I’d also say that it’s fairly unusual to have a Mac without the installation disks that go with it? I don’t really think you can lay this one on Apple …
Oh and by the way, if I do successfully install Tiger on the partition, I’ll then have to update it to 10.4.11 of course…!
Yes, yes, yes, Paul…but really, come on, it’s taking two days to do what should take 5 minutes, regardless of what disks I’ve got. It’s simply ludicrous. You know it’s nonsense, stop defending Apple!
Example…I’ve set the Tiger install disks that came with the Macbook going (previous owner had upgraded to Leopard and then Snow Leopard, and has supplied all disks). It’s taken half an hour just to ‘check the installation DVD’…!!! For frick’s sake, Apple, you supplied it! A DVD check should take 5 seconds not 30 minutes!
Heavens above, what are we coming to. Reminds me of all those wonderful software phrases…“and you’re done”…“it’s a snap”…hehehe
You know me, ranting as usual. But really, I do think this sort of mularkey utterly ridiculous. And yes, Apple are to blame.
Yes, yes, yes, Paul…but really, come on, it’s taking two days to do what should take 5 minutes, regardless of what disks I’ve got. It’s simply ludicrous. You know it’s nonsense, stop defending Apple!
Sorry Hugh, I know you’re feeling frustrated, so I won’t do any more to add to it.
Sorry to rant off, Paul, it’s not at you…it’s just I find the whole process ridiculously lengthy for what should be, at megabits per second speeds, a matter of minutes, not hours.
The Tiger install has just completed…took over an hour. Why?.. I just think it’s ludicrous!
Now I have to update the installation…then transfer all my data over (again, you’d think Firewire 400 would take a few minutes, not several hours…)
Go and enjoy your bank holiday! Hope the sun’s shining down your way, a bit grey and cold oop north!
The Tiger install has just completed…took over an hour. Why?.. I just think it’s ludicrous!
Now I have to update the installation…then transfer all my data over (again, you’d think Firewire 400 would take a few minutes, not several hours…)
Hugh, without wanting to get you going again, I think a lot of this is of your own making—FireWire 400 is slow as the devil, hardly any faster than USB, and I’m not surprised it took so long. I’m not sure where you get these expectations from? Now FireWire 800 is a different matter …
You’re probably right, Paul…my expectations are too high most likely. I don’t spend all of my time hanging out for the latest technology but I always thought Firewire was the speed merchant. But maybe that was back then…
It probably would have been a lot quicker over USB2, but the Mac installer said to connect a Firewire cable…!
One thing to realize when making this comparison: USB is processor-
bound, FireWire is not. Each bit that you move over USB moves through
the processor, because USB is a “dumb” port. FireWire is autonomous.
Two FireWire devices can chat with one another without ever involving
the processor.
As a result, moving large amounts of data over FireWire will always be
faster than any equivalently-rated USB port, often by a very large
factor, particularly when that data also needs to be inspected by the
processor for some other purpose (like updating a local cache,
generating a preview, etc). The processor has to pull double duty to
manage the port’s IO as well as to inspect the data, and it can only
do one thing at at time.
