Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
2006/2007 Mac Pro (1,1/2,1) and OS X El Capitan
- Thread starter Mr. Zarniwoop
- Start date
-
- Tags
- mac pro 2006 mac pro 2007
- Sort by reaction score
My Mac Pro 1,1 is now FUBAR. I had a fully functioning Yosemite install and tried to upgrade to El Capitan. I have no idea what went wrong, but all of a sudden starting the computer results in the graphics card fan instantly spinning full bore. Within 15 seconds all the system fans start to ramp up. There's no startup chime. I'm wondering if I've done something to the EFI or firmware? I've now stripped out the computer to minimum RAM and only 1 HD. I also replaced the power supply. Any suggestions would be greatly appreciated.
Not sure this will help, but can you connect to another Mac in Target Disk mode and check the HD from there?
There's nothing wrong with the HD. Remember, the computer doesn't even look for a HD until POST is completed. All Macs can start, even with no HD present.
Sounds nasty - I guess you have done the usual things - blasted off any dust that may have built up etc. Seems odd the fans run at full power - perhaps they are getting a signal from a faulty sensor? Have you tried with different HD - in case there is something in the one installed that is triggering the issue. Unlikely, but worth a go perhaps. Logic board seems the next thing I guess. Good luck.
Yep, Mine sits around the same temp. keeps dropping 2 sticks, not sure if its because of the 3.0 upgrade. Will the 1,2 smc fix this?
Hi from Athens, Greece
So the problem with boot.efi 3.1 is the memory. That's why my MacPro with 5GB of Ram had craches after a minute and no one replied correctly when I post my problem even directy to the author. Thanks my friend, thats why I am using the previous boot.efi the one for yosemite with no problem.
Thank you again,
Nicholas
P.S. I ordered a memory expansion of 8 more GB and I will try the 3.1. I hope that it worth the upgrade.
Thanks - and indeed I have (more thoroughly) now. The problem remains though. Even with the latest 3.1 boot.efi (which takes me a step further) I am still unable to initiate the download through the MAS. I'm able to click the 'Download' button, which then goes grey as though something is happening, but the spinning wheel icon in the top left just spins indefinitely with no further activity to be observed. The Activity Monitor reports no network activity either.
I note that in the 'Updates' tab of the MAS it claims it's already downloaded. Clearing com.apple.appstore doesn't help.
On a separate note what field does 3.1 patch to enable the MAS not to fail at the first step? The model identifier remains as MacPro1,1
Last edited:
... also oddly, whether or not the 'Download' button has been pressed, the button says 'Get' for a fraction of second if the user presses either the Option or Command key first and then clicks the mouse on the large graphical 'X' above the Download button. It appears too briefly to be selectable. Very strange.
EDIT: Rephrase the above. Double-clicking on the X allows the 'Get' button to appear for just long enough for it to be clicked, but again nothing seems to happen.
EDIT: Rephrase the above. Double-clicking on the X allows the 'Get' button to appear for just long enough for it to be clicked, but again nothing seems to happen.
Last edited:
Chances are you ALREADY have El Capitan's installer somewhere on your hard drive. OS X knows this. The Mac App Store application will let you press "Download", but the download itself won't begin if the installer application is anywhere on your boot drive. Look for the installer, and delete it. The next time you try to download El Capitan, it will work.
Time is linear and rolls onwards! Sadly the security certificates on the Apple supplied “Install Mac OS X El Capitan” app do not get updates! (Some users have reported that if you re-download a fresh copy of "Install OS X El Capitan" app the security certificates are okay - see below)
Some users have found that re-installing El Capitan with Pikify is now failing. This is due to the security certificates having expired. You can still perform the installation, but there is an additional step. You need to set the Mac Pro’s clock to something like Jan 1st 2018.
To set the clock: follow the steps to boot into the installer. Before you proceed with the installer, open the Utilities menu and select Terminal.
Once the Terminal is running issue the date command to set the date
The date string is in the format: month day hour minute year. I’ve shown the first of January 01:01 ‘18 - mmddHHMMyy (optionally you can include the century too mmddHHMMccyy)
If you do this after the boot into the Installer partition (USB if you’re using one), then there should be no need to use the super user do command (sudo).
Run the date command on its own to verify the date is now as you expect. Then quit out of the Terminal. You should arrive back at the Installer, continue as normal
If you want to do this from MacOS before you boot into the Installer, then you will need to go into the Date & Time System Preference, turn off the automatic setting, then set the date/time in the Preference Panel.
Either way you might find it convenient to disconnect from the Internet to be doubly sure it won't then auto-update when you boot into the installer...
The Pikify App.
Version 1.0 had a bug which took me while to track down.
Version 1.1 would not run correctly on Snow Leopard 10.6. Turns out I was using a method for 10.7 or higher!
Version 1.2 fixes the 10.6 usage
Versions 1.3 through 1.7 weren't released
Version 1.8 contains many fixes and better progress visuals
Version 1.9 contains a small number of fixes, a new feature that detects an existing Data folder giving you the option to re-use it or build a new one, and I finally added a Help Book! If you choose to re-use the existing Data folder, the App will re-bless it to make it bootable again!
The current stable release is version 1.9 (build 148)
The App is not signed, therefore you may need to right-click on the app and select Open the first time you run it. This forces Gatekeeper to allow the app.
The same conditions apply:
Notes: The app is designed to run from Mac OS X 10.6 Snow Leopard or later;
Tested on:
USAGE:
The script-based Pikify tools
Version 14 marks a shift in technique. With V14 the installation process is much simpler, becomes a single pass, does not require an intermediate installer volume (USB memory stick), and does not require the use of the EFI boot selector (which should be a great help to those people with graphics cards that do not show boot screens).
NO USB!
Also note: I have tested V14 on Snow Leopard 10.6.8. It will work (even though the video says "Lion 10.7.x or higher" as the starting point.
See https://support.apple.com/en-us/HT206886 if you are having difficulty finding a copy of El Capitan.
12Gb or more of RAM is required
I made a video
To use v14, pass the path to your target disk. Let's say you want to install El Capitan onto the Macintosh HD disk....
============== Previous Versions ===========================
Are now retired....
V14 can build on a USB stick, then you can install from there...
==================== Version 12 ==================================
Version 12 saves the unmodified software in a format that makes it easier to restore. Also adds more checks. The biggest change is that the disk images are now mounted on specific mount points so that my script doesn't conflict with the default mount points.
==================== Version 13 ==================================
Not released
==================== Version 14 ==================================
Version 14 is a major change in strategy. With this version you no longer need an intermediate installation media (USB memory stick). Version 14 emulates the way Apple is currently performing the installation. With version 14 you target the disk you want to install El Capitan onto (not the USB memory stick). New users should use v14. If you encounter any issues, please post an entry on this thread.
One really big advantage to V14 is that it will reboot directly into the installer. This should be a great boon for those people with graphics cards that do NOT show boot screens. There's no more need to guess how to boot into the installer.
The only exception is using El Capitan to install another copy of El Capitan. If SIP is active, then the bless command is not allowed to change the boot device settings (setBoot). This is a security feature and should be applauded, but it means with SIP enabled, you must reboot and manually select the installer...
++++++++++++++++ MD5 ++++++++++++++++++++++++++++++++++++++++++
MD5 (pikify3.1.v14.zip) = e7b1699c8db8335c2331e1e8b247efa8
MD5 (PikifyAppV1-9.zip) = 981af2253c9610f2d13257a4368501c3
Some users have found that re-installing El Capitan with Pikify is now failing. This is due to the security certificates having expired. You can still perform the installation, but there is an additional step. You need to set the Mac Pro’s clock to something like Jan 1st 2018.
To set the clock: follow the steps to boot into the installer. Before you proceed with the installer, open the Utilities menu and select Terminal.
Once the Terminal is running issue the date command to set the date
Code:
date -u 0101010118The date string is in the format: month day hour minute year. I’ve shown the first of January 01:01 ‘18 - mmddHHMMyy (optionally you can include the century too mmddHHMMccyy)
If you do this after the boot into the Installer partition (USB if you’re using one), then there should be no need to use the super user do command (sudo).
Run the date command on its own to verify the date is now as you expect. Then quit out of the Terminal. You should arrive back at the Installer, continue as normal
If you want to do this from MacOS before you boot into the Installer, then you will need to go into the Date & Time System Preference, turn off the automatic setting, then set the date/time in the Preference Panel.
Either way you might find it convenient to disconnect from the Internet to be doubly sure it won't then auto-update when you boot into the installer...
The Pikify App.
Version 1.0 had a bug which took me while to track down.
Version 1.1 would not run correctly on Snow Leopard 10.6. Turns out I was using a method for 10.7 or higher!
Version 1.2 fixes the 10.6 usage
Versions 1.3 through 1.7 weren't released
Version 1.8 contains many fixes and better progress visuals
Version 1.9 contains a small number of fixes, a new feature that detects an existing Data folder giving you the option to re-use it or build a new one, and I finally added a Help Book! If you choose to re-use the existing Data folder, the App will re-bless it to make it bootable again!
The current stable release is version 1.9 (build 148)
The App is not signed, therefore you may need to right-click on the app and select Open the first time you run it. This forces Gatekeeper to allow the app.
The same conditions apply:
- You must have a unmodified copy of the Apple 'Install OS X El Capitan' app in your Applications folder.
- See https://support.apple.com/en-us/HT206886 if you are having difficulty finding a copy of El Capitan (STEP 4 AND STEP 5). The page has a download link that will deliver a disk image file (.dmg). Double-click the disk image to open it. Inside the disk image is an installer package. Don’t get excited, all the installer does is to put a copy of the “Install OS X El Capitan” app into your main Applications folder. Therefore run the installer. Assuming it completes okay, you will have Apple’s unmodified app in the right place and ready for the Pikify tools to operate on...
- depending on what system you do this on, the “Install OS X El Capitan” app might launch after it installs. Just quit out. Then run the Pikify tools.
- If you are running from a MacPro, you must have 12Gb of RAM or more.
Notes: The app is designed to run from Mac OS X 10.6 Snow Leopard or later;
Tested on:
- 10.6 Snow Leopard
- 10.7 Lion
- 10.11 El Capitan
- If you are going to use this app from El Capitan, be aware that SIP prevents the bless command from setting the boot partition. There are two workarounds:
- Reboot and hold the ALT key down, select the Pike Installer
- Reboot into the Recovery HD, turn off SIP, reboot back into El Capitan and run the App again...
- If you are going to use this app from El Capitan, be aware that SIP prevents the bless command from setting the boot partition. There are two workarounds:
USAGE:
It's an app, double-click it (or right-click and choose 'Open' if you get a unsigned/unknown developer warning). The rest should be self-explanatory...
The script-based Pikify tools
Version 14 marks a shift in technique. With V14 the installation process is much simpler, becomes a single pass, does not require an intermediate installer volume (USB memory stick), and does not require the use of the EFI boot selector (which should be a great help to those people with graphics cards that do not show boot screens).
NO USB!
Also note: I have tested V14 on Snow Leopard 10.6.8. It will work (even though the video says "Lion 10.7.x or higher" as the starting point.
See https://support.apple.com/en-us/HT206886 if you are having difficulty finding a copy of El Capitan.
12Gb or more of RAM is required
I made a video
To use v14, pass the path to your target disk. Let's say you want to install El Capitan onto the Macintosh HD disk....
Code:
sudo ./createpikeinstallmedia /Volumes/Macintosh\ HD
[your password]============== Previous Versions ===========================
Are now retired....
V14 can build on a USB stick, then you can install from there...
==================== Version 12 ==================================
Version 12 saves the unmodified software in a format that makes it easier to restore. Also adds more checks. The biggest change is that the disk images are now mounted on specific mount points so that my script doesn't conflict with the default mount points.
==================== Version 13 ==================================
Not released
==================== Version 14 ==================================
Version 14 is a major change in strategy. With this version you no longer need an intermediate installation media (USB memory stick). Version 14 emulates the way Apple is currently performing the installation. With version 14 you target the disk you want to install El Capitan onto (not the USB memory stick). New users should use v14. If you encounter any issues, please post an entry on this thread.
One really big advantage to V14 is that it will reboot directly into the installer. This should be a great boon for those people with graphics cards that do NOT show boot screens. There's no more need to guess how to boot into the installer.
The only exception is using El Capitan to install another copy of El Capitan. If SIP is active, then the bless command is not allowed to change the boot device settings (setBoot). This is a security feature and should be applauded, but it means with SIP enabled, you must reboot and manually select the installer...
++++++++++++++++ MD5 ++++++++++++++++++++++++++++++++++++++++++
MD5 (pikify3.1.v14.zip) = e7b1699c8db8335c2331e1e8b247efa8
MD5 (PikifyAppV1-9.zip) = 981af2253c9610f2d13257a4368501c3
Last edited:
Follow these instructions if you have just installed El Capitan, or are already using El Capitan and want to automatically put the modifications in place during updates.
============== Edit ==================
This has been tested from initial install 10.11 to 10.11.1, and from 10.11.1 to 10.11.2.
Each successive release of El Capitan is making it harder to use this method, which is only to be expected. SIP (aka "rootless") is continually being developed and extended by Apple.
As a rule of thumb, if in doubt turn SIP off first.
If you are nervous about a particular update to El Capitan, then you should disable SIP entirely before you commence with the update. Search this thread for "csrutil" to find out how...
Upgrades from -> to:
10.11.0 -> 10.11.1 safe
10.11.1 -> 10.11.2 overwrites boot.efi files
10.11.2 -> 10.11.3 safe
10.11.3 -> 10.11.4 overwrites boot.efi files
10.11.4 -> 10.11.5 overwrites boot.efi files
10.11.5 -> 10.11.6 safe
NOTE: If you install El Capitan and then use a "combo" updater usually downloaded from the Apple web site Support / Downloads section, then be aware ALL combo updates will replace the boot.efi files (perhaps with the exception of 10.11.0 -> 10.11.1)
===================================
SECURITY UPDATES:
All security updates up to and including Security Update 2017-005 will install without issues.
CAUTION: Security Update 2018-001 has a modified kernel that crashes the boot sequence. There is a workaround which is to roll-back the kernel file to the last known good version from the 2017-005 Security update. You will need a second working partition of MacOS (or a working Recovery HD partition) so that you can roll-back the kernel). See post #3896...
Please note: Boot64 is only designed to protect the boot.efi file. The issue with a boot loop after applying Security-Update-2018-001 or later is due to a changed kernel file. Boot64 does not protect the kernel file.
===================================
While Pike is recuperating (take your time Pike
), I have figured out how to set up our working El-Capitan installs so that they will survive the Apple update mechanisms. You will need to install your choice of "pike yos fix" the updated version now called CapitanPikeFix is at post #1253 (courtesy of @666sheep) , or my very own Boot64 stuff, they both pretty much do the same thing. My Boot64 stuff installs a Launch Daemon that watches the boot.efi files, if they get changed (by the Apple update) it simply puts the Pike copies back!
@666sheep's CapitanPikeFix requires that you permanently disable SIP.
My Boot64 modifies SIP, keeping most of the security advantages of SIP enabled.
CAUTION: Apple will probably alter SIP in the future to prevent Boot64 from working, but in the meanwhile....
"Ah, but SIP stops them working!" I hear you cry. True!
But, we can exclude the boot.efi files from SIP - here's how:
I will assume your working El-Capitan is on the hard disk named Macintosh HD - change it to suit
I don't claim to have discovered this fix. I'm simply good at using search engines, and then realising how this fits together. The credit goes to the Hackintosh community again. See http://www.idelta.info/archives/sip-rootless-internal-in-el-capitan/
I've tested this with a clean install of El Capitan 10.11 and successfully installed the 10.11.1 update from the App Store, and from a clean install using the 10.11.1 downloadable update.
I will modify my pikify3.1 script bundle with the mods for SIP exclusions already in (but without the install of Boot64 itself - you still need to install this - or CapitanPikeFix). Look out for pikify3.1.v3.zip pikify3.1.v#.zip at post #1390 ...
===================== Version 2 ============================
V2 includes mods to watch the SIP/Sandbox paths file in addition to the boot.efi files
===================== Version 3 ============================
Fixes an issue identified with the 10.11.2 update.
If you are using Boot64 AND you have already updated to 10.11.2 then you should probably check your system, see post #1484
++++++++++++ MD5 ++++++++++++++++++++++++++++++++++++++++
MD5 (Boot64.v3.mpkg.zip) = 9ed68334f6593ff7c64c32d29317f152
============== Edit ==================
This has been tested from initial install 10.11 to 10.11.1, and from 10.11.1 to 10.11.2.
Each successive release of El Capitan is making it harder to use this method, which is only to be expected. SIP (aka "rootless") is continually being developed and extended by Apple.
As a rule of thumb, if in doubt turn SIP off first.
If you are nervous about a particular update to El Capitan, then you should disable SIP entirely before you commence with the update. Search this thread for "csrutil" to find out how...
Upgrades from -> to:
10.11.0 -> 10.11.1 safe
10.11.1 -> 10.11.2 overwrites boot.efi files
10.11.2 -> 10.11.3 safe
10.11.3 -> 10.11.4 overwrites boot.efi files
10.11.4 -> 10.11.5 overwrites boot.efi files
10.11.5 -> 10.11.6 safe
NOTE: If you install El Capitan and then use a "combo" updater usually downloaded from the Apple web site Support / Downloads section, then be aware ALL combo updates will replace the boot.efi files (perhaps with the exception of 10.11.0 -> 10.11.1)
===================================
SECURITY UPDATES:
All security updates up to and including Security Update 2017-005 will install without issues.
CAUTION: Security Update 2018-001 has a modified kernel that crashes the boot sequence. There is a workaround which is to roll-back the kernel file to the last known good version from the 2017-005 Security update. You will need a second working partition of MacOS (or a working Recovery HD partition) so that you can roll-back the kernel). See post #3896...
Please note: Boot64 is only designed to protect the boot.efi file. The issue with a boot loop after applying Security-Update-2018-001 or later is due to a changed kernel file. Boot64 does not protect the kernel file.
===================================
While Pike is recuperating (take your time Pike
), I have figured out how to set up our working El-Capitan installs so that they will survive the Apple update mechanisms. You will need to install your choice of "pike yos fix" the updated version now called CapitanPikeFix is at post #1253 (courtesy of @666sheep) , or my very own Boot64 stuff, they both pretty much do the same thing. My Boot64 stuff installs a Launch Daemon that watches the boot.efi files, if they get changed (by the Apple update) it simply puts the Pike copies back!@666sheep's CapitanPikeFix requires that you permanently disable SIP.
My Boot64 modifies SIP, keeping most of the security advantages of SIP enabled.
CAUTION: Apple will probably alter SIP in the future to prevent Boot64 from working, but in the meanwhile....
"Ah, but SIP stops them working!" I hear you cry. True!
But, we can exclude the boot.efi files from SIP - here's how:
I will assume your working El-Capitan is on the hard disk named Macintosh HD - change it to suit
- You don't need to do steps 1, 2, 3, and 4 if you have just used pikify3.1 (v3 or higher) to install El Capitan From the post above because it's already done for you)
- You DO need to complete steps 6 - 8...
- Boot off another partition, I use the Recovery HD partition.
- Open a Terminal
- If you are NOT using the Recovery HD, you will probably need to elevate your privileges. Become the super user
if you ARE using the Recovery HD there is no need for the sudo command.Code:sudo -s [your password] - Now type or copy/paste
Code:chflags nouchg /Volumes/Macintosh\ HD/System/Library/CoreServices/boot.efi echo "/System/Library/CoreServices/boot.efi" >> /Volumes/Macintosh\ HD/System/Library/Sandbox/Compatibility.bundle/Contents/Resources/paths echo "/usr/standalone/i386/boot.efi" >> /Volumes/Macintosh\ HD/System/Library/Sandbox/Compatibility.bundle/Contents/Resources/paths echo "/System/Library/Sandbox/Compatibility.bundle/Contents/Resources/paths" >> /Volumes/Macintosh\ HD/System/Library/Sandbox/Compatibility.bundle/Contents/Resources/paths - Reboot from your other partition back into your normal El Capitan disk (Macintosh HD)
- Install CapitanPikeFix, or my Boot64 (attached)
- If you are going to install my Boot64, download the zip file below, unzip it, and double-click it, follow the installer prompts (you might need to allow it with Gatekeeper - if you get a "can't install" message, try opening System Preferences > Security & Privacy > General, look for the "Open anyway" button). If that doesn't work, choose 'Anywhere' from the options and try again... (Don't forget to put this option back to your preference after Boot64 is installed!)
- Sit back and enjoy El-Capitan
I don't claim to have discovered this fix. I'm simply good at using search engines, and then realising how this fits together. The credit goes to the Hackintosh community again. See http://www.idelta.info/archives/sip-rootless-internal-in-el-capitan/
I've tested this with a clean install of El Capitan 10.11 and successfully installed the 10.11.1 update from the App Store, and from a clean install using the 10.11.1 downloadable update.
I will modify my pikify3.1 script bundle with the mods for SIP exclusions already in (but without the install of Boot64 itself - you still need to install this - or CapitanPikeFix). Look out for pikify3.1.v3.zip pikify3.1.v#.zip at post #1390 ...
===================== Version 2 ============================
V2 includes mods to watch the SIP/Sandbox paths file in addition to the boot.efi files
===================== Version 3 ============================
Fixes an issue identified with the 10.11.2 update.
If you are using Boot64 AND you have already updated to 10.11.2 then you should probably check your system, see post #1484
++++++++++++ MD5 ++++++++++++++++++++++++++++++++++++++++
MD5 (Boot64.v3.mpkg.zip) = 9ed68334f6593ff7c64c32d29317f152
Last edited:
Missed your response; sorry about that.
Difficult to say what could be the problem.
Others here have narrowed panics to being caused by add-in cards and failing ram modules....
If the older boot.efi works for you, I'd suggest using/staying-with that one . . . or stay with Yosemite until El Capitan, boot.efi and other things mature some more: I have El Cap installed thrice, but I still use Yosemite on a daily basis.
There are some issues with regards to the Mac Pro 1/2,1 requiring a minimum of 12GB of ram to complete the installer:
https://forums.macrumors.com/threads/boot-efi-developers-thread.1924434/page-36#post-22294363
...so, there might be issues past the installation phase, especially if the installer was performed on another machine, and transferred.
Too many variables for answers to be cut-and-dried.
Keep trying.
Regards, splifingate
Thanks for your reply, I will stay with the old efi on EL Cap. but I hope that Apple will fix facetime failure on Mac Pro 1.1.
Waiting...
I assume you've installed it?!
Open a Terminal
become the root user
Code:
sudo -s
[your password]
Code:
launchctl list | grep bootIf you see nothing, check with
Code:
ls /Library/LaunchDaemons/uk.co.rthpjm.*if you want to check the operation of my Boot64 daemon, open the Console App, click on the system.log in the left panel, in the Filter/Search box type boot
Then in a Terminal become the root user (see above) and type
Code:
touch /System/Library/CoreServices/boot.efiIf you want to change the colour of the background, use the Terminal, become the root user, then use -g for grey, or -b for black
Code:
/Library/Application\ Support/Boot64/ensureBoot.sh -g
/Library/Application\ Support/Boot64/ensureBoot.sh -b
Last edited:
Not installed. I have download your file pikyfi3.1 and double clik on the file pikyfi.pkg and follow the instruction... probably not the correct way to install this thing?
Thank you. Indeed that was the problem - though a copy of the installer was not on the boot drive but elsewhere.
Indeed, the download won't begin if Spotlight can find a copy of it on one of your indexed disks.
You are completely correct when you wrote "probably not the correct way to install this thing". The pikify.pkg is NOT intended to be run on an existing El Capitan volume.
The pikify3.1 set is used to create installable media, which you then use to install a fresh copy of El Capitan.
pikify.pkg is NOT designed to run on its own, it is designed to run from the Install Assistant. The Install Assistant passes in parameters. If you try to run it on its own those parameters are missing/unknown and therefore the package will not install.
If you are trying to modify an existing El Capitan installation, can I suggest that you re-read through the forum.
Ultimately all that is needed is to overwrite/replace the two boot.efi files.
- Have the system in a position so that you can overwrite the boot.efi files
- Boot from a different partition, change the boot.efi files manually
- Or
- Boot from the Recovery partition, disable SIP using csrutil, reboot to your normal partition, change the boot.efi files manually
- Or
- Modify your system to exclude the boot.efi files from SIP, change the boot.efi files manually
- Or
- Modify your system to exclude the boot.efi files from SIP, install one of the automated boot.efi replacement tools
- Boot from a different partition, change the boot.efi files manually
The last one in the list above gets most of us back to the Apple-like goal I mentioned above.
I think you really needed to follow the step-by-step instructions of post #1391. The "launch daemon" installer is the attachment at the bottom of that post (or CapitanPikeFix which does effectively the same thing can be found at post #1253.)
Last edited: