Why you don't install and tell us about it?!?Really, no one has installed the fifth beta yet?
Why you don't install and tell us about it?!?Really, no one has installed the fifth beta yet?
Why you don't install and tell us about it?!?
DP5 = PB4, so it's not an excuse…Happily, but I don’t have a developer account
Oh really, didn’t realize, will get on it right away.DP5 = PB4, so it's not an excuse…
Really, no one has installed the fifth beta yet?
What surprise are you looking for?
View attachment 851042
I don’t know, 4.1 or 5.1 being totally blocked?
OK, so I ran version 1.0.4 of dosdude's patcher, downloaded 15.0.21 and it went through all the hoops and told me I had a successfully produced Catalina installer, on my USB stick. However what I had was not bootable, but a single folder called Contents per the attached jpg. So now I am totally confused as using The pAtcher version 1.0.2 and 15.0.18 it all worked like a charm...
What could I be doing wrong?
Did you actually try booting from it? Most probably there is hidden content. Also, make sure the USB is GPT formatted.OK, so I ran version 1.0.4 of dosdude's patcher, downloaded 15.0.21 and it went through all the hoops and told me I had a successfully produced Catalina installer, on my USB stick. However what I had was not bootable, but a single folder called Contents per the attached jpg. So now I am totally confused as using The pAtcher version 1.0.2 and 15.0.18 it all worked like a charm...
What could I be doing wrong?
Yes I tried, but it didn't appear in the list of startup disks in Startup disk preferences, nor does it appear when option is held down during startup.Did you actually try booting from it? Most probably there is hidden content. Also, make sure the USB is GPT formatted.
Nope, there are no microcode updates for Westmere processors from Intel. Perhaps one of the reasons support for the MacPro5,1 line was dropped from Catalina, as Apple can no longer guarantee the security of the systems through OS patches alone. I'm in the same boat and have disabled multithreading in order to protect against the vulnerabilities.I have a cMP 4,1 flashed to 5,1 and upgraded to dual X5690 cpus which I believe are Westmere. Does anyone know if this architecture gets decent protection from the MDS and other vulnerabilities? Looking to upgrade to Catalina on release, presumably with the dosdude patch if its pretty safe & reliable to do so. Running an RX 570 8gb gpu.
Hi all, have been keeping a keen eye on this thread, thanks all for contributing and helping everyone out.
I have a cMP 4,1 flashed to 5,1 and upgraded to dual X5690 cpus which I believe are Westmere. Does anyone know if this architecture gets decent protection from the MDS and other vulnerabilities? Looking to upgrade to Catalina on release, presumably with the dosdude patch if its pretty safe & reliable to do so. Running an RX 570 8gb gpu.
Thanks,
Richard.
It's like thinking someone is going to break into your house, plugin a firewire device into your Mac Pro and dump it’s unencrypted ram contents. Can it happen? Yes. Is it likely to happen ? NO
I think we are going waaaaaay off topic here. I noticed for example newer applications like the newest Virtualbox does not start if any process tries to injects unsigned drivers in the memory, even though that process is from a legitimate software (powerbroker). My point is the software vendors already take proactive measures to prevent some of the newly discovered Intel flaws. Anyway let's stay on topic.I haven't totally been following this issue, but can you explain why it isn't likely to happen? Can this exploit be used to get passwords or account information? Could it be used to dump the memory used by, for example, my LastPass password manager to gain all my account passwords?
I'm not asking this in a snarky way, I really don't know the answers and am hoping the issue isn't as dire as people have made it out to be. I have an MP5,1 that I was in the process of setting up, and when the security issue made the news I sort of stopped using that computer -- largely because I didn't understand things well enough to know how much risk existed.
OK, so I ran version 1.0.4 of dosdude's patcher, downloaded 15.0.21 and it went through all the hoops and told me I had a successfully produced Catalina installer, on my USB stick. However what I had was not bootable, but a single folder called Contents per the attached jpg. So now I am totally confused as using The pAtcher version 1.0.2 and 15.0.18 it all worked like a charm...
What could I be doing wrong?
Curious, can you just install Catalina on a supported machine, take that drive and boot the 5,1? I cannot/will not ever use a 3rd party patch (unless their is source code) because potentially they could plant any kind of crazy stuff on your install and cannot risk that for work machines. Or do you need the patch beyond the installer in that the OS won't boot without it? (Sorry if this is obvious or already answered).
There are two types of updates, macOS point releases and Security updates have the same blocks as full installs while Apple app updates like Safari or iTunes (it's a example, iTunes is dead with Catalina), usually don't have the same checks as macOS updates.If I install Catalina in a supported Mac and then move the drive to an unsupported Mac Pro 5,1 with a metal capable card. How will updates work? Would I be able to update from that point forward using the Mac Pro or would I be forced to erase and re-install every single update using a supported Mac?
Any information is appreciated. Thanks
There are two types of updates, macOS point releases and Security updates have the same blocks as full installs while Apple app updates like Safari or iTunes (it's a example, iTunes is dead with Catalina), usually don't have the same checks as macOS updates.
You can use a VMM emulation patch like the one made by @Czo, use VMWare Fusion raw disk, or install your Catalina disk back in a supported Mac and do the updates if you don't want to use any patches or don't have Fusion.
Btw, added this to the first post since will be a frequent question in the future.