In a previous article, I bemoaned the fact that my Mac Pro 1,1 (First Edition) was left behind as part of the Mountain Lion launch. Even though I had upgraded the video to an ATI Radion 5770 HD and boosted the RAM to 18 GB, Apple decided that my workhorse machine was just to ugly to get an invitation to the Upgrade Party.
Not wanting my Mac Pro to feel left out, I decided to take action.
First, I did upgrade my 2008 Aluminum MacBook to Mountain Lion. Thankfully, that machine had secured a spot for an upgrade, just barely. Once that installed, I moved back to my Mac Pro.
Using Parallels Desktop for Mac, Version 7, I created a Mac OS X Lion virtual machine from the recovery partition on the Mac Pro. Once I had that up and running, I tweaked the Virtual Machine settings in preparation for Mountain Lion.
- Boosted the virtual RAM to 4 GB
- Increased the video RAM from 32 to 512 MB.
Never the less, I pressed the “Download” button to the right of the Mountain Lion icon and patiently waited for the installation app to download. The network traffic was such that I had to attempt this multiple times. At first, I thought the Mountain Lion would get the better of me. Was it detecting that I was using a VM running on obviously inappropriate hardware? Was that why the download was failing?
On the third attempt, the Mountain Lion installation app beamed at me from the VM Launch Pad. I clicked the icon and the OS installation process started up. After about 35 minutes, and a couple of restarts, I had a full fledged Mountain Lion OS running as a VM on my Mac Pro 1,1.
It’s still not what I really want, i.e., Mountain Lion accepting my Mac Pro and running natively on it’s hardware, but , at least I can let the Lion roam within the confines of it’s virtual world. Hopefully, a reprieve will surface that will give me what I want, but, in the meantime …