There are problems doing this if I install the very easy to use Patched Sur. My main problem now is what method to use to upgrade to Big Sur in a way that makes it easy or even possible to upgrade to Monterey. I read somewhere that with these upgrades my MacBook still won't be as fast as a 2018 Mac, but all I can say to that is "What's the hurry?" I think it will be faster than most if not all Windows laptops sold in 2022. Thanks to easy plug-and-play RAM modules available today, anyone can upgrade the memory in their MacBook Pro 2012/2011 model, without much difficulty at all. I didn't manage to do anything else such as run Cinebench, edit a video with iMovie, or create a track using Logic Pro, though. While it was still working, I went into some department stores which were selling Apple Silicon Macs, visited some websites and noticed the difference in speed. This means that after I upgrade to Big Sur I'll be getting better performance than from my liquid damaged MacBook Air which lots of users online told me didn't have enough RAM. What I know so far is that it's already a lot faster than it was before and last year I used a MacBook Air with 4Gb (early 2014) to edit some videos with iMovie and create some music with Logic Pro.
After the installation, I'll be running the Cinebench test and I might run another test as well to see how fast or slow my MacBook Pro (mid 2012) Model 9.2 is.
I plan to watch some videos before attempting to install it. It comes with stickers which have printed on them the company name and the text "Warranty Void if Removed", so that's great. I paid extra for a Special Delivery and the RAM arrived on January 11. Eventually, I decided I couldn't get the kind of RAM I wanted for less than that price, so I gave in and bought some from a local company. I was looking around for some time for 2 X 8Gb RAM sticks at a price less than about €70 or US$80. Thanks for your advice everyone! I'm in a part of Europe I don't want to mention which has developed a bad reputation, but I had nothing to do with causing this.
0 kommentar(er)
