Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I tried but it didnt copy any of the installer files over.

What should these be set too, I was confused.

--------------------------------------------------------------------
Target System for Recovery Creation is: 8gb
--------------------------------------------------------------------
Target System to re-Patch is: 8gb
 
osxinstallIEDD something like that, you need to enable hidden files, or it might be the osxbase.dmg


Im at work so dont quote me on those names.
 
I think I got SFOTT working I might have mapped to the installer app wrong looks like its coping all the files the only thing I did different was manually go through each step vs auto run.
 
First of all, I would thanks to all persons, who are in charge of the whole project!
After I reactivated my MacPro 1.1 with the tools and help here, I am totally happy and satisfied! :)
And I tried also a bunch of other things, to reactivate my MacPro 1.1!

But I have a question, I have not found right now here:

After the reactivating does someone also uses the Server-Software from Apple on it?
Are there some strange behaviors, or anything else I have to think about it?
Because this was normally the main reason I wanted to use my MacPro 1.1!

Thanks in advance

:)
 
After the reactivating does someone also uses the Server-Software from Apple on it?
Are there some strange behaviors, or anything else I have to think about it?
Because this was normally the main reason I wanted to use my MacPro 1.1!

Thanks in advance

:)

I'm running Mac OS X Server on my updated 1,1. It is no different to running it on any other supported Mac.

-Rob
 
MacPro 2.1 (1.1 > 2.1)

Update 13C48 -> 13C53

On my side boot.efi files have been replaced by 13C53.

Replaced the new boot.efi files with Tamio's file and everything is O.K.
 
MacPro 2.1 (1.1 > 2.1)

Update 13C48 -> 13C53

On my side boot.efi files have been replaced by 13C53.

Replaced the new boot.efi files with Tamio's file and everything is O.K.

Great info, updating now. Will keep that finger on the Option key to boot into Lion on reboot...
 
Great info, updating now. Will keep that finger on the Option key to boot into Lion on reboot...

no idea why, but it took me like 10 tries to get that damn boot loader to come up. An annoying game that has to be played.
 
Incase somebody else has a problematic 5770 (as I mentioned before) I flashed the card with another rom by the same make (XFX) and all is working.

Popped in an SSD and I have a brand new machine :) ... until woes with 9.2 I guess but that's for another day!
 
MacPro 2.1 (1.1 > 2.1)

Update 13C48 -> 13C53

On my side boot.efi files have been replaced by 13C53.

Replaced the new boot.efi files with Tamio's file and everything is O.K.

Not aimed at you specifically Peloche but… :)

If you are a Mac dev program member the direct links to the standalone downloads for the delta and combo updates are posted in the dev forums, accessible by clicking on the forums pic down the right hand side of the Mac Mavericks dev page.

So? I hear you ask.

Well you just mount the disk image you just downloaded, double click the installer package, and it uses the standard Mac installer leaving you with full access to your machine.

So when the install completes and asks you to click here to restart, DO NOT DO IT.

Instead, change user to log in as 'root', swap the boot.efi that the installer has just been put in place with Tiamo's boot.efi.

Log out of root back to your normal user where the installer is still waiting for you to restart.

NOW you can restart.

And your system should come back prettily in 13C53, or whatever release is now current.

-Rob

ps Just make sure you've enable the root user before starting out eh?
 
Not aimed at you specifically Peloche but… :)

If you are a Mac dev program member the direct links to the standalone downloads for the delta and combo updates are posted in the dev forums, accessible by clicking on the forums pic down the right hand side of the Mac Mavericks dev page.

So? I hear you ask.

-Rob

Thanks Rob for your help, but i never asked for it.

You need to know why, I don't have any more update download available on my dev account since i've choosen long time ago to accept Update seed, so when there is a dev beta update it starts to ask for authorization and then download the update without giving you the chance to do anything until completion.

But it isn't a very big issue for me i've always a SuperDuper of my system disk.

So when update is completed and boot.efi files have been changed Mac Pro restarts on SuperDuper allowing to change boot.efi files.

Anyway thanks Rob for your help.
 
So when the install completes and asks you to click here to restart, DO NOT DO IT.

Instead, change user to log in as 'root', swap the boot.efi that the installer has just been put in place with Tiamo's boot.efi.

Log out of root back to your normal user where the installer is still waiting for you to restart.

NOW you can restart.

And your system should come back prettily in 13C53, or whatever release is now current.

-Rob

ps Just make sure you've enable the root user before starting out eh?
I thought that 'Restart' was the only available option?
 
I thought that 'Restart' was the only available option?

You can have it download, but not restart. When it asks you if you want to download and restart, choose the other option. I forget it it's cancel or whatever. Then it just downloads and has the option for you to restart at your leisure.
 
You can have it download, but not restart. When it asks you if you want to download and restart, choose the other option. I forget it it's cancel or whatever. Then it just downloads and has the option for you to restart at your leisure.

Gotcha. Ta.
 
screen sharing

I've succeeded on installing on a MacPro 2,1 with an X1900 and am very pleased with local results. But when I try remotely (either Timbuktu or ARD) the cursor lags and any action takes extreme time to complete. I want to use this as a remote headless server and need the GUI besides the command line. Is this a matter of the graphics card, or something with Marericks/efi?
 
I've succeeded on installing on a MacPro 2,1 with an X1900 and am very pleased with local results. But when I try remotely (either Timbuktu or ARD) the cursor lags and any action takes extreme time to complete. I want to use this as a remote headless server and need the GUI besides the command line. Is this a matter of the graphics card, or something with Marericks/efi?

It's usually almost entirely dependent on network speed and/or connection type - a detail you neglected to mention :)

My 2,1 is on my local 1gig network, to which I'm connecting via 5ghz Airport on my MBA - There's no lag worth mentioning.
 
I've succeeded on installing on a MacPro 2,1 with an X1900 and am very pleased with local results. But when I try remotely (either Timbuktu or ARD) the cursor lags and any action takes extreme time to complete. I want to use this as a remote headless server and need the GUI besides the command line. Is this a matter of the graphics card, or something with Marericks/efi?

just pull the X1900 if you're going to use it headless anyways. the Mac Pro should boot without the graphics card.
 
I am pretty sure the boot.efi files from the update are swapped during the shutdown of the machine, leaving no window for switching back to Tiamo's files.

If you do the update via the App Store mechanism, you are quite correct - However if you follow my guidelines and download the updater from the direct links at the Mac dev forums at Apple and use the standard Mac OS X installer, the installation completes entirely before you need to restart - giving you the window to update the boot.efi before restarting.
 
If you do the update via the App Store mechanism, you are quite correct - However if you follow my guidelines and download the updater from the direct links at the Mac dev forums at Apple and use the standard Mac OS X installer, the installation completes entirely before you need to restart - giving you the window to update the boot.efi before restarting.

Are people actually doing this without having a bootable clone to make adjustments from or fall back on?
 
Last edited by a moderator:
Are people actually doing this without having a bootable clone to make adjustments from or fall back on?
I'm keeping the modified Mavericks usb installer around for this purpose.
I should be able to copy back the boot.efi using the Terminal if needed.

Though I can use target disk mode from my other Mac if needed.
That and if my Mac Pro stops working for a bit it isn't a major issue for me.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.