Q: yosemite on my 1,1 mac pro

hotwheels 22 wrote:

 

so, wait. what is the deal here? i mean, i have a ton of cheat sheets on re-installation but actually i am not re-installing in this case.

 

so - wait - you are saying that /some/ apps require me to de-authorize on the old hardware prior to using on the new hardware? i guess i have CS 5.1 which means i do in fact have to de-authorize on the old hardware?

I haven't installed a CS app for a while, but from what I recall, there is a setup process when you install the app, in which you submit a code in order to get back an authorization code from Adobe that you must then enter to get the software to run. So since you are moving your drives to a new machine and presumably will not be trying to use the same apps on the old machine, you should de-authorize them before you remove them and install them in the new machine. The first time you launch CS 5 apps on the new Mac Pro, you'll be prompted to go through the authorization process again.

what is the issue here? somehow the app registered itself by phoning home with some data about my Hardware?

When you installed CS5, you would have had to go through a process of registering and authorizing the software for use on your computer. There is evidently enough information transmitted about the computer that Adobe knows when you've shifted your apps to a different machine. You can install a CS app on as many machines as you want, but you can only have two active authorizations at a time. BTW Adobe software phones home a LOT. It's one of the reasons I installed Little Snitch.

how do i know ahead of time which apps need me to do this??

 

ALSO, can anyone tell me how to search on how i get from Lion to Yosemite if/when i upgrade to a new machine...?

I don't know how you would determine this, unless you can remember which ones put you through this kind of procedure when you installed them. Some audio software requires this sort of thing.

You can go directly from Lion to Yosemite, but I would recommend not upgrading your Lion disk. You should install Yosemite on its own drive or partition and give it a thorough test drive. Some folks are having problems using CS5 apps with Yosemite. I haven't tried any Adobe apps with Yosemite yet. You should probably check out the Adobe support forums to get good info about that. Linotype’s FontExplorer X Pro seems to work OK with it, but I really haven't had time to try much of anything with my Yosemite guinea pig drive beyond that.

If Yosemite seems stable and you want to use it, you could clone your Lion drive to another HD or partition, and then upgrade the clone to Yosemite to see how everything works with it, Just leave yourself a functioning Lion disk to go back to if necessary.

You cannot just take Windows to a new computer as is and it eeds new license

hotwheels 22 wrote:

 

actually, now that i think about it - i /could/ keep the old computer running if/when i need it, install Yosemite on the new machine and put all my data in the new machine - and /slowly/ work on getting XP and Windows 7 onto the new machine if and when i feel like it or need it, yes?

 

this way i could focus on getting the new Mac OS up and running on a new machine.

 

- jonathan

Exactly. There is no reason why you have to move everything at once or to burn your bridges by upgrading your Lion system disk to Yosemite rather than keeping a clone of your Lion drive while setting up Yosemite on its own drive to test everything. You are in an especially good position to do this, because you have a working current system, and will be acquiring another working system, each with room for four internal drives. You have more flexibility than you would with any system that has only one internal HD. You can keep your Windows setup where it is for as long as necessary. I'd suggest getting a KVM while you have both systems going. I have the 4-port version of this one and it has worked very well: http://www.bhphotovideo.com/c/product/658263-REG/Iogear_GCS1102_2_Port_DVI_KVMP_ Switch.html. Switching between the connected Macs is as easy as anyone could want.

DO have a look at the Adobe support areas to see what problems people have run into running CS5 in Yosemite.

You might also contact Microsoft to find out more about getting your Windows setup moved.

It's a pity that Google didn't get you over to MacRumors before you bought 2012.

With that said, 2012 is a much more capable machine.

But myself and many others have benefited from some guys who compiled a new boot.efi file for 1,1 and 2,1.

You replace 2 instances of this file on your main OS install of Yosemite and BANG...IT JUST WORKS.

It does require that you have a newer GPU then shipped with them.

Specifically, the 7300GT, Q4500, AMD X1300, and X1900XT are all left behind by drivers since 10.8.

So, newer GPU and your 2006 can still play with the big boys. You can even switch out the WiFi card and get full ability to run Handoff, etc.

Go to Macrumors forums in the MacPro section, a guy named Hennesie has been running the thread. Nearly 100 pages long, lots of people got it running. Other info at Netkas forum.

Note, it is exactly 1 bazillion times easier if you can use a supported Mac to do the install, then replace the files, then put in 2006.

There is a way to create a Yosemite Installer that works on 2006 by itself but people tend to have more issues with that.

As far as moving your drives, the sleds in 2006 are shorter than 2009-12 so you have to remove the screws and swap them.

EDIT: For the Apple Purists who will doubtlessly come to decry my blasphemy, I have something for you to try. Dig deep in your install, any one since 10.7.5. In the "Core Services" folder is an app called "Expansion Slot Utility". You can try to run it but if you aren't using a 1,1 or 2,1 Mac Pro it won't let you start it up.Now note that this app has not only remained in every iteration of OSX, it has been updated as the OS was. So, an app that ONLY works on 1,1 and 2,1 has not only remained present in EVERY CURRENT COPY OF OSX ON THE PLANET (ie, Jim in Malaysia has it on his MBA) it has been updated. SOMEBODY has to be updating it and testing it.