The only solution that would work for me was to just go out and purchase a whole new MacBook Pro, and ‘restore’ my old identity onto it. Two years ago, I had an internal hard disk drive fail the day before going on a job abroad – thankfully it didn’t happen on the job, as I needed to offload SxS cards whilst on site. You simply MUST use Time Machine – it’s so easy and works so well… ![]() It has also given me absolute faith in Time Machine as a backup system. It’s also left behind a very useful little disk drive that will be a constant travelling companion. I’ve upgraded the internal hard disk of my main MacBook Pro this week, and whilst it’s not the most stunning upgrade in the world, it has left a rosy glow on things. (Note to self – Matt: don’t touch that button! Don’t do it!)Īlex4D has a bunch of links to get you started, training from Ripple and Larry Jordan (hopefully IzzyVideo will have some new stuff soon too), FCP.co discussion forums already alight with debate… and a week or two of holiday season to enjoy it all in. So, I’m spending the first day having to NOT download the update, but format drives, archive disks, install software whilst reading and watching the sudden deluge of 10.1 info. If you’re jumping from 10.X to 10.Y (especially to 10.Z) it’s worth the time it takes to do a proper clean install.Īnd of course once it’s done, you still may need to be able to go back to the ‘old’ system – so you’ll need to clone – not back up or archive but CLONE – your old system before you start, if only for the comfort factor of running back to it when the new system refuses to do something. Serious, serious problems that impacted work (and backups, and archives). I did this ages ago, and the problems didn’t show until 12 months on and we’d gone through some minor version changes and bug fixes. And then there’s the creeping rot of a brand new operating system ‘installed in place’ over the old one. Then of course there’s the impatient teenager in all of us who, after backing up, installs the new OS on top of the old OS, downloads the new app, finds what’s broken in the rest of the system and fixes it, finds out that a few tools don’t work, plug-ins need shuffling, projects don’t render as they used to, fonts have gone missing… All this takes longer, funnily enough. But until you’re sure that the new OS won’t kill your current must-use apps, you can simply shut down, unplug, and return to your current safe system. Plus, it will take time to do the official switch – you’ll have to rebuild your apps, delete old versions that don’t work, sort out new workflows, new versions, reinstall, find license agreements, it all takes time (and it’s not billable for freelancers). Really, that is the safest way – but its frustrating as the performance of a system booted on an external drive isn’t quite what you’re used to, and it’s a bit clunky. You want to play in a protected ‘sand-box’ (I preferred ‘sandpit’ but hey…) so you don’t accidentally convert your current projects to the new system and find yourself committed to the switch. New versions of software often change the file format and rarely is it back-compatible. Install the new software on the fresh OS, and play with COPIES of older projects that you copied across. The safest option for me is (having backed up your main machine of course) to unwrap a brand new hard drive, format it and install the latest OS on it, then boot from THAT. Things can go wrong, things like backups and archives invariably take more time than you thought, and what if it’s all horrible and you need to back track? Smaller jumps, a minor ‘point-oh-one’ upgrades can be welcome relief, but this is a ‘point-one’ and it needs an OS upgrade to boot (pun not intended). Rule 1 of upgrades: never upgrade during a job.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |