2006/2007 Mac Pro (1,1/2,1) and OS X El Capitan

[synaptech]

Bad CPU type in executable

What cpu are you using?

 

[aoshi2012]

Intel(R) Xeon(R) CPU 5160 @ 3.00 GHZ

 

[plentyoftimeto69]

Do these beasts have an internal USB header?
[doublepost=1469518287][/doublepost]

I have tried with a different sub drive as well as a partitioned secondary hard drive and it keeps giving me the error. This is the last bit before the error occurs

Adding resources...
.........................................................................................................................................
Elapsed Time: 5m 53.735s
File size: 6079159444 bytes, Checksum: CRC32 $EDC52DA5
Sectors processed: 13037600, 12557796 compressed
Speed: 17.3Mbytes/sec
Savings: 8.9%
created: /Applications/Install OS X El Capitan.app/Contents/SharedSupport/InstallESD.dmg
\nRunning Apple's createinstallmedia tool...
./createpikeinstallmedia: line 553: /Applications/Install OS X El Capitan.app/Contents/Resources/createinstallmedia: Bad CPU type in executable

\n\n=================================================================================================================================
==
==\tERROR
==
=================================================================================================================================
==
==\tA problem occurred when creating the install media with Apple's createinstallmedia tool
==\tThe most common issue is that the installer volume could not be unmounted because some other process is using it
==\tClose all other windows (especially terminal windows) and try again
==

Do you have the drive open in Finder by chance? Even having a Finder window open can cause a drive to fail unmounting. Make sure nothing is accessing the disk.

 

[rthpjm]

I have tried with a different sub drive as well as a partitioned secondary hard drive and it keeps giving me the error. This is the last bit before the error occurs

Adding resources...
.........................................................................................................................................
Elapsed Time: 5m 53.735s
File size: 6079159444 bytes, Checksum: CRC32 $EDC52DA5
Sectors processed: 13037600, 12557796 compressed
Speed: 17.3Mbytes/sec
Savings: 8.9%
created: /Applications/Install OS X El Capitan.app/Contents/SharedSupport/InstallESD.dmg
\nRunning Apple's createinstallmedia tool...
./createpikeinstallmedia: line 553: /Applications/Install OS X El Capitan.app/Contents/Resources/createinstallmedia: Bad CPU type in executable

\n\n=================================================================================================================================
==
==\tERROR
==
=================================================================================================================================
==
==\tA problem occurred when creating the install media with Apple's createinstallmedia tool
==\tThe most common issue is that the installer volume could not be unmounted because some other process is using it
==\tClose all other windows (especially terminal windows) and try again
==

Hello aoshi2012,

Okay, that's serious. The script has done everything I expect it to do, and reached the last step which is to use the Apple-provided binary executable (program, or app depending upon your age!) called createinstallmedia.

Something in your environment is causing the error. Can you detail your hardware platform and post it here.
MacPro 1,1 or 2,1 (or some other Mac)?
Have the CPUs been upgraded?

"Bad CPU type in executable" is odd. It generally means an old PowerPC type executable with no hybrid Intel binary part (also known as fat binary) or vice/versa.

Are you running on a PowerMac G5?

If your Mac is running, go to the Apple menu (top left), choose About this Mac, and maybe click 'more info' or 'system profiler'.

Where did you get your copy of Install OS X El Capitan.app from?

 

[azimuthal]

I just Googled your error message. I think you can safely ignore it. At the end of the createpikeinstallmedia script, I added a check to identify the machine and the amount of RAM in the machine, I use the command line version of system profiler. My intent was to warn the user if the machine is a MacPro and it has less than the recommended 12Gb of RAM.

For some users, this use of the system profiler seems to have issues. Since it's just a convenience check, it can be ignored.

If you want to help me out, please let me know what version of Mac OS X you were running on when you ran createpikeinstallmedia and what model of Mac....

Okay I was finally able to get everything working. I'm not sure what was causing the issue but this is what I did, summarizing with my initial steps first.

1) created an image of my Piker-alpha updated Yosemite OS SSD.
2) Used that same version of the OS to create the El Capitan Installer using the Pikify3_1_v11 setup script.
3) When I did this, I would always get that strange message. I finally resorted to using my 2012 macbook pro and created the install script using the latest version of the El Cap OS, that seemed to do the trick. When I used that macbook to run the Pikify script and create the El Capitan Installer, i never got the strange message about the platform plugin dictionary etc.

So now I have a fully functioning Mac Pro 1,1 (flashed to 1,2) with 32GB of Ram and 2 x Quad core xeon 3.0Ghz CPUs.

Again, I have to give my sincerest thanks to all of you who continue to keep these beasts working. I purchased my original Mac Pro nearly 10 years ago to the date. Its amazing how well these machines were built. I really wish Apple would keep up with the Pro market but it looks like Apple is going more and more the consumer only market.

 

[aoshi2012]

Hello aoshi2012,

Okay, that's serious. The script has done everything I expect it to do, and reached the last step which is to use the Apple-provided binary executable (program, or app depending upon your age!) called createinstallmedia.

Something in your environment is causing the error. Can you detail your hardware platform and post it here.
MacPro 1,1 or 2,1 (or some other Mac)?
Have the CPUs been upgraded?

"Bad CPU type in executable" is odd. It generally means an old PowerPC type executable with no hybrid Intel binary part (also known as fat binary) or vice/versa.

Are you running on a PowerMac G5?

If your Mac is running, go to the Apple menu (top left), choose About this Mac, and maybe click 'more info' or 'system profiler'.

Where did you get your copy of Install OS X El Capitan.app from?

My mac is a Mac Pro 1.1, I do not not believe the CPU has been upgraded. Towards where I got my copy of El Captain it is was from here
http://www.hackintosh.computer/?p=199

 

[Ant3000]

That's your problem - Hackintosh - You have a Mac so need the genuine version from the Mac App Store. The version you have has probably been messed with to make it work on a PC. You may need a supported Mac to download the Apple version as it will report your Mac isn't supported. Once you have it, follow the instructions as before.

 

[aoshi2012]

That's your problem - Hackintosh - You have a Mac so need the genuine version from the Mac App Store. The version you have has probably been messed with to make it work on a PC. You may need a supported Mac to download the Apple version as it will report your Mac isn't supported. Once you have it, follow the instructions as before.

I see, would anyone know a good source to download El Captain from?

 

[Ant3000]

The Mac App Store is the ideal place - it's free, but you need a supported Mac to download it to.

 

[owbp]

I see, would anyone know a good source to download El Captain from?

Mac App Store is the best route. I don't know what OS version you have at the moment, but if you don't have supported Mac you have two very straightforward options:
1. Mac Route - Download and install pre-patched Yosemite from this forum (you'll have to search Yosemite topic, same as this one) since the boot.efi for 10.10-10.11 permanently changes your Board-ID to 3,1 - model that is supported and that can download 10.11 from MAS.
2. Hack/Mac Route - You could create Clover USB with SMBios for MP3,1 or iMac10,1.
Sign out of every Apple/iCloud account, boot from Clover USB, sign in again, download El Capitan, song out again and reboot normally.

I'm sure there are other ways but these two first came to my mind.

Edit: Boot.efi for 10.10/10.11 can also boot into Maverick (if you have Install OS X Maverick.app somewhere) but it gave me random kernel panic. Enough time do download 10.11 from app store, just don't freak out if your Mac reboots out of the nowhere.

 

[plentyoftimeto69]

Guys, I made a disk image of my system before I did any configuration. It's just a .dmg file and it can be restored using Lion recovery's disk utility to the main system disk of your Mac Pro. I'd gladly share it, but I don't know if that'd be violating any OS X licensing. Thoughts? The image is just shy of 15GB so it'd fit on a 16GB+ USB stick easily.

 

[Ant3000]

Just to muddy the waters further, I installed Mavericks using SFOTT to build the installer, but I think I had to download from the MAS on my laptop so may not help much. I assume you do not have access to a supported Mac? If this is the case, The pre-patched version of Yosemite, linked to on P1 of the Yosemite thread, would be my choice - no need to update it either if you are using it to enable the download of El Capitan. You will effectively be doing what many have done here but in a much shorter time span!

 

[plentyoftimeto69]

Also, I benched this Mac Pro 2,1 and my MacBook Air 6,2 last night using the Geekbench trial. I was surprised at the results! No wonder this Mac Pro can crunch video so quickly.

http://browser.primatelabs.com/user/106091

 

[aoshi2012]

Thanks everyone for the advice, I'll try going the Yosemite path tonight and see how that works out. Will post the results afterwards.

 

[aoshi2012]

So it appears that the link to download Yosemite will not work for my current browser, so I'm back to step one again. Not sure if this is allowed but given the issues I'm facing would it be possible to have someone mail me a USB drive with the setup ready? I'll pay for the postage and labor.

 

[Ant3000]

There may be something you can download here... #4048

Or have you installed Firefox or Chrome? These may run on your current OS and allow the download - I am assuming you are running Safari. What is your current OS and how much RAM do you have installed?

 

[Eagalution]

Have you tried logging out of your Apple account and logging back in? Not sure why it would throw this message as it is a free update and I have never seen this before. Are you running Boot64 (or similar) as this will protect the boot.efi files from being overwritten although whether this may happen appears to be dependent on which version you are going from. What version are you currently running? The other update available on your screenshot is for iPhoto which doesn't run in El Capitan so I am confused as to why it is being offered as an update. I assume you are trying to download the El Capitan Update from El Capitan?

Have a look here - there seems to be a similar issued that is caused by iPhoto being installed which caused the same error you are seeing...
https://discussions.apple.com/thread/7303899?start=0&tstart=0

Be careful if you have lots of pics in iPhoto still.

Thank you so much for your respond!!
The version of El Capitan that I am running is 10.11.5 and I was using pikify3.1.v8 for the upgrade. I am NOT using Boot64: Should I add Boot64 to my El Capitan? (Could you tell me how?)
I was following your link to the discussion in apple, and indeed it looks as if the problem is with iPhoto. (even if I don't use it anymore since all my Photos are on Photos now. (and it works fine

 

[Ant3000]

Boot64 allows an update without overwriting the boot.efi files - more info here #1391
Some have reported updating from 10.11.5 to 10.11.6 works without using it so you may be OK without it. I have it installed and have updated several times without issue. If you read back a few pages you will be able to see more reports of updates to 11.6 and if any problems encountered. Good luck.

 

[Eagalution]

Boot64 allows an update without overwriting the boot.efi files - more info here #1391
Some have reported updating from 10.11.5 to 10.11.6 works without using it so you may be OK without it. I have it installed and have updated several times without issue. If you read back a few pages you will be able to see more reports of updates to 11.6 and if any problems encountered. Good luck.

THANK YOU!!!
[doublepost=1469621381][/doublepost]

Strictly speaking, the pikify install method prepares the machine for Boot64, it is not pre-installed you still have to install it.

The steps to modify SIP to exclude the boot.efi files from SIP's protection are in place if you use the pikify method to install.

If you don't use the pikify method to install then you need to perform steps 1-4 of post 1391 (as well as all the other steps) when installing Boot64.

Just wanted to use your Boot64.v3 to protect the boot.efi file before updating from 10.11.5 after upgrading from Lion, using your pikify version 8, with the help of your video. (works perfect! Thank you!!!)
So now I got an error "Boot65.v3 cant be opened because it is from an unidentified developer"

 

[rthpjm]

THANK YOU!!!
[doublepost=1469621381][/doublepost]

Just wanted to use your Boot64.v3 to protect the boot.efi file before updating from 10.11.5 after upgrading from Lion, using your pikify version 8, with the help of your video. (works perfect! Thank you!!!)
So now I got an error "Boot65.v3 cant be opened because it is from an unidentified developer" View attachment 642057

that's Apple's Gatekeeper protecting you.

There are various ways of working with Gatekeeper:

• You can open the System Preferences, click Security & Privacy, click the General tab, click the lock icon, enter your password, change the value of "Allow apps downloaded from:" to Anywhere. Now run the installer. Remember to go back and put the "Allow apps downloaded from:" back to a sensible value.
• OR
• Try to launch the installer (and get the warning), then go to System Preferences > Security & Privacy > General, there is usually a button saying "open anyway". Click that.
• OR
• Right click on the installer and choose Open. You'll be prompted to allow the installer to run anyway

 

[plentyoftimeto69]

Just hold control while launching that installer and it should give you the option to launch it anyway.

 

[plentyoftimeto69]

Okay guys, I read the info on page 1, and it looks like Macvidcards is out of the cards that they have in stock. What part #'s work for Apple handoff? BCM94360CDAX is the one Macvidcards sells, but will a BCM94360CSAX work? It looks like I have to stick either in a cheap mini PCI-X adapter. Am I on the right track? Really wanna get handoff working on this system.

 

[Apple Master]

I upgraded my 1,1 to Yosemite as a recommendation on here because somebody said it was more stable, but now to only find out that a ton of mac apps don't work with Yosemite. Now I have to upgrade to El Capitan.

I can't remember if I need to find a patched version or just the clean version from the app store. This will only work on a usb boot drive correct?

 

[Ant3000]

Post 1391 and post 1 of this thread have the information you require. Check you Mac is up to spec with RAM (12gb if you install using the USB method) and GPU if you want boot screens.

 

[cdmawolf]

Okay guys, I read the info on page 1, and it looks like Macvidcards is out of the cards that they have in stock. What part #'s work for Apple handoff? BCM94360CDAX is the one Macvidcards sells, but will a BCM94360CSAX work? It looks like I have to stick either in a cheap mini PCI-X adapter. Am I on the right track? Really wanna get handoff working on this system.

Be careful, I think the CS as opposed to the CD has different antenna connectors.
Or at least be sure to check.