Upgrading MBP to Core 2 Duo MBP

[mstecker]

Hi,

I've just ordered a Core 2 Duo MBP to replace my "old" Core Duo MBP. The spread between my new cost and what I got for my old machine on eBay was so small, I couldn't pass it up.

So anyway, I'm thinking about how to get my data onto my new laptop. I made a Carbon Copy Cloner image of my old laptop's hard drive onto an external firewire disc (made sure it was an Intel bootable partition).

The question is: When I get my new machine, can I just boot off of the external drive and clone my disc image back to my "new" computer?

Even if this works, will the binaries for the Core2Duo be compiled with any different optimizations or flags that would make this an inefficient route? Would there be any problems with different drivers that a cloned image might not have (for the new Airport card, for instance).

I have a whole system of files, applications, and preferences on my machine that I'm quite fond of and I'd really prefer not to start from scratch - reinstalling all applications and importing all of my content.

So are there any downsides of the Carbon Copy Cloner approach for migration in this instance?

Thanks for any help.

Matthew

 

[PygmySurfer]

Hi,

I've just ordered a Core 2 Duo MBP to replace my "old" Core Duo MBP. The spread between my new cost and what I got for my old machine on eBay was so small, I couldn't pass it up.

So anyway, I'm thinking about how to get my data onto my new laptop. I made a Carbon Copy Cloner image of my old laptop's hard drive onto an external firewire disc (made sure it was an Intel bootable partition).

The question is: When I get my new machine, can I just boot off of the external drive and clone my disc image back to my "new" computer?

Even if this works, will the binaries for the Core2Duo be compiled with any different optimizations or flags that would make this an inefficient route? Would there be any problems with different drivers that a cloned image might not have (for the new Airport card, for instance).

I have a whole system of files, applications, and preferences on my machine that I'm quite fond of and I'd really prefer not to start from scratch - reinstalling all applications and importing all of my content.

So are there any downsides of the Carbon Copy Cloner approach for migration in this instance?

Thanks for any help.

Matthew

I don't see why that wouldn't work, unless perhaps the MBP C2D requires a later version of OS X than you had installed on your old MBP. I seriously doubt the OS X binaries are compiled any differently, so that shouldn't be a problem.

Try it and see, if it doesn't work, you can reinstall OS X from your install discs, then manually migrate data from the FW drive over.

 

[interlaced]

If you use Migration Assistant, you cannot simply transfer applications over, right? So does Carbon Copy Cloner let you do that?

I always thought that applications couldn't transfer without reinstalling them.

 

[mstecker]

If you use Migration Assistant, you cannot simply transfer applications over, right? So does Carbon Copy Cloner let you do that?

I always thought that applications couldn't transfer without reinstalling them.

Generally, that's true - Some applications need files in /Library or ~/Library or the ApplicationSupport folders, etc. but with Carbon Copy Cloner, you're essentially making a copy of the whole drive - with all of those supporting directories as well. If all goes according to plan, I'll end up with the identical environment I left on my old machine without reinstalling anything.