As far as I can tell without actually having this machine, you will have to replace the CPU (it's socketed, not soldered) with a Penryn type Core 2 Duo. Second requirement is a Nvidia or 2xxx/4xxx series AMD/ATI GPU. You can check both present setups by running the latest supported macOS (OS X) and see system infos...Hi guys. I never written before. I have managed to have in my hands the iMac 7,1. But it is the mid-2007 one. It is capable to run Big Sur with your stuff? I am missing this passage and I don’t want to make a mess…
I was unsure what the best approach is to upgrade from my currently 'patched' MacOS 11.1 install to MacOS 11.4 would be?
I updated to 11.4 using the same version of Patched Sur. After reading your post, I downloaded ClamXAV (trial version) 3.2 and did a full scan. No viruses or malware were found. I have a 13-inch mid-2012 MacBook Air with a 1.8 Ghz Intel core i5.I hope to hear from others who also may have experienced this? And I am also wondering how to proceed with updating Big Sur to 11.4 after this? Obviously I am not eager to download more copies of this Trojan to my iMac.
The answer is yes, IF you are willing to do research on opening and upgrading that iMac, spending some money on components necessary and swapping them out, make the iMac work after the modifications, learn OCLP, install Big Sur. That's it. 👍🏻 love the avatar.Hi guys. I never written before. I have managed to have in my hands the iMac 7,1. But it is the mid-2007 one. It is capable to run Big Sur with your stuff? I am missing this passage and I don’t want to make a mess…
The technique used by Hax6.dylib can indeed be used for malicious purposes as well, so ClamXAV is right in issuing the warning.Possible Trojan virus delivered with Patched Sur patch? Has anyone else experienced this?
iMac14,2, Quad-Core Intel Core i7, 3.5 GHz (2013) - Operation system is on 1GB SSD, Home folder is on hard disk HGST 8TB (this is NOT a "Fusion Drive" arrangement)
A month ago, I successfully upgraded my iMac to macOS Big Sur Version 11.2.3 by using Patched Sur. Everything went smoothly. At that time I installed the "Patched Sur" app.
A couple of days ago I wanted to upgrade to Big Sur version 11.4. First I upgraded the app to Patched Sur v0.1.2 (64) and followed every step (including Terminal use) as described. I solely used Patched Sur v0.1.2 for downloading the necessary files for my upgrade.
This ended with an error screen saying Error 1x255 (see uploaded screenshot) I also tried to download and install USB on a USB thumb drive (64GB), but screen instructions did not show the thumb drive, but instead indicated that I should erase one of my hard disks.
Giving up until I could collect more information, I ran a virus scan with ClamXAV 3.3 and found the existence of a Trojan.OSX.Flashback which showed up for the first time. I also ran a confirmation wider range scan overnight, but found hat this was the only virus present. It was quarantined by ClamXAV and I proceeded to trash and delete it.
However, the interesting part is the information that came out about the path of this virus:
File Name Infection Name Status Current Path Original PathHax6.dylib Trojan.OSX.Flashback
Deleted /usr/local/lib/Patched-Sur-Patches/InstallerHax/Hax6/Hax6.dylib /usr/local/lib/Patched-Sur-Patches/InstallerHax/Hax6/Hax6.dylib
I hope to hear from others who also may have experienced this? And I am also wondering how to proceed with updating Big Sur to 11.4 after this? Obviously I am not eager to download more copies of this Trojan to my iMac.
Thanks, tomorrow I'll make further investigations on this iMac. I know that the cousin of my friend, made some improvement, but I still don't know what he did. (if he changed only the RAM or also something else ) Once I find more infos, i will see. And maybe I can provide them here or throught Discord channel. Thanks for the reply.As far as I can tell without actually having this machine, you will have to replace the CPU (it's socketed, not soldered) with a Penryn type Core 2 Duo. Second requirement is a Nvidia or 2xxx/4xxx series AMD/ATI GPU. You can check both present setups by running the latest supported macOS (OS X) and see system infos...
Seems to me you failed to collect any.Giving up until I could collect more information
Interestingly enough the latest version of ClamXAV as of Jun 1st 2021 is 3.2 build 8776I ran a virus scan with ClamXAV 3.3
Thank you, Internetzel. This was useful. However, even more useful for me would have been to get some advice from more experienced users than myself regarding the Error 1x255 situation.The technique used by Hax6.dylib can indeed be used for malicious purposes as well, so ClamXAV is right in issuing the warning.
In our case Hax6.dylib is used to enable you to use an unmodified Apple OS installer on your unsupported machine.
Generally, more RAM helps a bit once you get the OS up and running after a CPU swap. But most impact will be accomplished by installing a SSD drive.Thanks, tomorrow I'll make further investigations on this iMac. I know that the cousin of my friend, made some improvement, but I still don't know what he did. (if he changed only the RAM or also something else ) Once I find more infos, i will see. And maybe I can provide them here or throught Discord channel. Thanks for the reply.![]()
Thank you, Internetzel. This was useful. However, even more useful for me would have been to get some advice from more experienced users than myself regarding the Error 1x255 situation.
After upgrading three ancient Macs with OLCP 0.1.5 (Mac Mini 5,1 MacBook 8,1, iMac 8,1), I finally got up the courage to upgrade my two Mac Pro 3,1s, on of which is the house media server with an old Geforce 8800 card, and my "daily driver" Mac Pro with a metal-capable GTX 680 card. Both were running the dosdude1 patch for Catalina. After several reboots (as expected), the media server came to life and the main applications (Plex, Roon) came online without incident. The only real problem is that I couldn't convince the Legacy Patcher tool to install the non-metal graphics drivers, but honestly, it's a server and graphics performance is not a real concern. And I really wasn't seeing accelerated graphics on this old 8800 card under Catalina either. The problem with the patcher seems that it doesn't corrected recognize if SIP and SecureBootModel are disabled or not.
For my daily driver Mac Pro, I had an issue with dosdude1's patchupdaterd daemon kept crashing so I had to find it and delete it. And since the graphics card was Metal capable anyway, no other patching was necessary. And I have to say that this machine is remarkably stable. No real downsides to this upgrade. Even running Catalina on this machine was a little weird, but Big Sur seems to work better than anticipated.
Thank you "K two" for trying to be helpful. Neither of the two suggestions are true, because I always stayed within the Patched Sur app and the on-screen pop-ups provided, and I never downloaded anything outside GitHub. Fighting through another sleepless night, I managed to create a USB installer, and finally I succeeded in installing 11.4. Notice that I am grateful to BenSova for the wonderful Patched Sur (which I feel is still short from perfect, and could benefit from further "polishing"). The version of Patched Sur was the right one, and the same that produced the final success.Your error is likely an out-of-date Patched Sur? Or the patcher used was acquired from a source other than: https://github.com/BenSova/Patched-Sur/releases
This is exactly what happened in my case (even though others here said it did not happen to them, and that their unpaid trial versions of ClamXAV did not report a "virus"). I understand now that using Hax6.dylib is "a technique" that can indeed (also) be used for malicious purposes. This was a learning experience for me as "a newbie" even if I joined this Forum in November 2007, so I have been here longer than most ;-)😇The technique used by Hax6.dylib can indeed be used for malicious purposes as well, so ClamXAV is right in issuing the warning.
In our case Hax6.dylib is used to enable you to use an unmodified Apple OS installer on your unsupported machine.
Booting from firewire devices is broken since Catalina.Re: External drive for backups/booting (New OS like BigSur,Catalina)
As we have older macs with Unsupported OS running, our old hardware has USB 2.0/ Firewire 400/800 ports. Could anyone tell if these ports are supported with new OS like BigSur/Catalina for Time Machine Backups and can external drive be booted from these ports.
I was wanting to purchase a SSD for backups so wanted some inputs as to what is the compatibility scenario and best option. I have an old HDD enclosure having firewire 800/usb 3.0 ports. Can I use it for backups without any issue or crashes.
Thanks for your inputs.
So that means if I decide to boot unsupported Mac OS on my 2009 Minis from FW800 SSDs I can't go past Mojave and will have to ignore Catalina, Big Sur and whatever follows. That is a shame.Booting from firewire devices is broken since Catalina.
Especially the launch/startup daemons that come along from previous Mojave/Catalina patches have to be removed. Otherwise, they keep crashing every few seconds, which can be monitored running the console app.Actually, all of the dosdude1 items imported/migrated into Big Sur can be safely removed. 🧐
It's a known issue, sorry. I've been putting off fixing it because I rarely use dual monitors and been working on some other stuff, but I'll try to investigate it soon.Has anybody found a workaround or solution to the "track and chase" anomaly of menu bar icons when using OpenGL GPUs with BS (11.4 and 11.5beta, but might have been problematic ever since 11.0) on more than one screen? The items should always display on both/all screens and should be accessible on the screen with the current app/window focus.
With the patches for non-metal cards they have a weird appearance: Only one menu bar on one screen has clickable icons, and they disappear on screens without focus, sometimes when actually clicking them.
Any ideas what could be done, i.e. with additional tools? (I tried some menu bar mod tools, but nothing really works so far).
Any progress on hd 3000 intel acceleration on mabook air 4,2 as its still broken even after applying legacy patch. Cant open photos or images as it creates color distortion. Tks for all your efforts appreciate what you have done for us old mac owners.Also, for anyone not on the Discord servers, we -- myself, OCLP devs, and @moosethegoose2213 -- have been recently experimenting with AMD Radeon 5xxx/6xxx accel.
View attachment 1785619
Consider it pre-alpha at this point, but hopefully it'll be a viable upgrade from High Sierra in the foreseeable future.
Noted. Yeah post #467 if Catalina thread gave me lots of insight to this issue. That means we are now downgraded as we have only usb2.0 ports and todays external usb enclosure comes with usb3.0 but the write/read speed we will get will be poor specially while using BigSur or Catalina.Booting from firewire devices is broken since Catalina.
Is there a list of daemons to remove?Especially the launch/startup daemons that come along from previous Mojave/Catalina patches have to be removed. Otherwise, they keep crashing every few seconds, which can be monitored running the console app.
I missed that until I installed OCLP on such an BS-upgraded (lower end) machine that kept CPU usage way above normal idle behaviour.
Wow, that's great. I manage four 21.5" 2011 iMacs and am disappointed that they are stuck on High Sierra (even though I almost always have them booted to Windows 10). Somehow despite being used for years (though not for anything that intensive) they have working graphics cards. I'm in no rush (would like something done well rather than half-baked) but look forward to giving this a try. Hope it will work with my setup of booting off a TB3 NVMe drive (I'm concerned about the possibility of breaking the iMacs if I open them up, so need something like the hard drive or coin battery to fail probably before I'll take that risk). I'm currently booting the machine I use off a TB3 NVMe drive but plan to boot the others off those as well, especially if booting Big Sur becomes a viable option.Also, for anyone not on the Discord servers, we -- myself, OCLP devs, and @moosethegoose2213 -- have been recently experimenting with AMD Radeon 5xxx/6xxx accel.
View attachment 1785619
Consider it pre-alpha at this point, but hopefully it'll be a viable upgrade from High Sierra in the foreseeable future.