MBP UEFI WINDOWS SOUND FIXED!!!!

xAndrewH1993x wrote:

https://www.bbc.com/news/technology-51413724 must I say anything else..... Have a great day.

Did you read this part

"The practice was confirmed after a customer shared performance tests on Reddit, suggesting their iPhone 6S had slowed down considerably as it had aged, but had suddenly speeded up again after the battery had been replaced."

Also,

• https://www.apple.com/batteries/maximizing-performance/
• https://www.apple.com/batteries/why-lithium-ion/
• Determine battery cycle count for Mac notebooks - Apple Support
• About the battery usage on your iPhone, iPad, and iPod touch - Apple Support

Regarding Apple being fined, so has Microsoft, Google,... (choose your company name here) been...

I have expressed myself more than enough, I'm here to help people see the truth and fix there MacBook Pros that Apple "decided" not to support. If that's offensive sorry buddy.

Let me quote a previous post, and highlight the tradeoff...

"I have been working on that problem for quite a while with varied results (though none actually getting the thunderbolt bridge to be recognized) -- the strangest attempt was doing a BIOS install of windows and looking at how it mapped the memory (since thunderbolt works with CSM layer of bootcamp) and creating a DSDT based on those memory ranges; strangely, even without a qword entry, the sound worked but now there were different devices that windows could not allocate into memory -> The HD3000 graphics, a couple of system devices etc.....what I am attempting now is to study the lspci output from linux to see how it maps the devices into memory and perhaps create a dsdt to reflect that ---I am hoping someone in the linux community can teach me how to create a dsdt extrapolated from the ouptut of lspci --- in the hackintosh world we often create a SSDT (secondary system description table) to get thunderbolt working -- but I don't believe Windows can use a modified SSDT -- so maybe we can crack the nut - hoping to do so "

Device drivers are very sensitive beasts. Memory allocation for various needs of the devices is non-trivial. You step out of bounds and device(s) stop working. Memory holes are waiting-to-be-exploited Security holes. Buffer overruns are the bane of a device driver writer. Just be careful what you step into.

The point is do not 'fix' something, and break something else.

I think we are all big boys and know how to handle our security 😉 Thanks. I've been in the wireless industry for 8 years now, from experience I've seen the worst of iOS products and let me tell you it doesn't take 15-30 minutes to restore a phone accept an iPad in an iPhone (this is including downloading the ipsw). So again you can sit here and defend them until your blue in the face but I will never be converted after being screwed out of my money. I can use Samsung smart switch restore my phone back to where it was and be done with it. Includes restoring my backup and firmware within 30mins. If you are really smart you can use Odin to restore the devices and be done within 5 minutes. I can definitely say Apple needs to work on the consideration for people who has to troubleshoot their devices especially when you are working through one of the carriers and you got that stubborn customer that won't leave because they can't comprehend that they have to go through Apple. Hahaha when it's a simple factory reset that you have to do through iTunes just to remove the passcode lock. Haha.... Now let's move on... This forum is apparently not to your liking, I don't care if this is a iForum or a Apple Forum. We are "fixing" a unsupported product, it's the end user's responsibility to continue to use a end of life product and know the risks. Good day to you sir.

xAndrewH1993x wrote:

Thanks. I've been in the wireless industry for 8 years now,

👏

from experience I've seen the worst of iOS products and let me tell you it doesn't take 15-30 minutes to restore a phone accept an iPad in an iPhone (this is including downloading the ipsw).

How often does a normal user restore their phone?

So again you can sit here and defend them until your blue in the face but I will never be converted after being screwed out of my money.

I am not defending anyone here. You are not being converted either. You can spend your money any way you want.

I can definitely say Apple needs to work on the consideration for people who has to troubleshoot their devices especially when you are working through one of the carriers and you got that stubborn customer that won't leave because they can't comprehend that they have to go through Apple.

You are confusing Subsidy locks of carriers with Apple iOS security. I personally refuse to buy a phone through a carrier.

Hahaha when it's a simple factory reset that you have to do through iTunes just to remove the passcode lock. Haha....

iTunes is also an Apple product, right?

Now let's move on... This forum is apparently not to your liking, I don't care if this is a iForum or a Apple Forum. We are "fixing" a unsupported product, it's the end user's responsibility to continue to use a end of life product and know the risks.

A preUEFI Mac is not an EoL product. You seem to confuse 'vintage' and 'obsolete' terminology. See Vintage and obsolete products - Apple Support for reference.

Good day to you sir.

Good day to you as well!

TGIK wrote:

It appears Loner T has the sort of 'myopic Apple fan boy' point of view because he (or she I suppose) never wants to point out any inadequacies on Apple's part, which is fundamentality an intellectually disingenuous position to have....

I point Apple's inadequacies to Apple, and not in a public Apple forum (see https://feedbackassistant.apple.com). Not supporting UEFI on a 2011 Mac (9 years old) is a product decision. 2012 Macs are preUEFI and still supported. Also, there is a very public set of articles documenting Apple's failures on Nvidia and AMD GPUs and batteries which does not need repeating.

Or maybe it's all in good fun and he has a strange sense of humor and finds the 'copy-what-you-wrote-and-editorialize' style responses charming......

It is indeed in good fun. 😉

I commend his work helping other people, but again, he has provided very little substance in this discussion other then the occasional snarky missive...which I find mildly amusing

There is a 'fully' supported method to run Windows on a 2011 (and older) Mac, which does not need any changes. You have an alternative 'method', borne out of intellectual/academic curiosity, which you admit does cause new issues, but is fine, if users do not care about such.

macOS has used EFI (1.x) for many years, which is not anything new. Most Linux distribution methods have also supported EFI 1.x.

Whether you (or anyone else) on this discussion dislikes Apple for their business practices, it is their problem, not necessarily Apple's.

Great! I almost gave up and luckly I found your post as my last resort. I once tried some approaches like patching bootmgfw.efi but all failed, is that theoretically feasible? Since that seems better than registry hack, or is there a similar approach for grub2 which is already my boot loader.

Thanks!

Hey TGIK!

Hey I was wondering if you can help me push this out to the public to see if we can get some help on this! There is a company out that will data mine for Cancer, Alzheimer Disease, Huntington Disease, Parkinson Disease, AND COVID-19 / 2019-NCOV (Corona Virus Pandemic). This is a similar process to crypto-mining but for a different cause through MacOS.

"We need your help! Folding@home is joining researchers around the world working to better understand the 2019 Coronavirus (2019-nCoV) to accelerate the open science effort to develop new life-saving therapies. By downloading Folding@Home, you can donate your unused computational resources to the Folding@home Consortium, where researchers working to advance our understanding of the structures of potential drug targets for 2019-nCoV that could aid in the design of new therapies. The data you help us generate will be quickly and openly disseminated as part of an open science collaboration of multiple laboratories around the world, giving researchers new tools that may unlock new opportunities for developing lifesaving drugs."

"Folding@home is a project focused on disease research. The problems we’re solving require so many computer calcul­ations — and we need your help to find the cures!

The Folding@home software allows you to share your unused computer power with us — so that we can research even more potential cures.

Folding refers to the way human protein folds in the cells that make up your body. We rely on the proteins to keep us healthy and they assemble themselves by folding. But when they misfold, there can be serious consequences to a person’s health.

The journey started in the year 2000, at Stanford University. The Pande Lab, directed by professor Vijay Pande, founded the Folding@home project. Ever since, the team has been researching protein folding, computational drug design and other types of molecular dynamics."

More information:

https://9to5mac.com/2020/03/04/coronavirus-cure/ - where I found this article

https://foldingathome.org/2020/02/27/foldinghome-takes-up-the-fight-against-covid-19-2019-ncov/ - the companies' site

fah-installer_7.5.1_x86_64.mpkg.zip - Virustotal scan (Online Virus Scan) (Clean) - https://www.virustotal.com/gui/file/94fd47ff55120c1c869d0dfbf366ae418406a3b47b0fa1bcf94014777abb72a6/detection

Want to participate?!

You can download the app here. The control and viewer apps both look like they were created by a Windows programmer in about 1990, but they do the job…

Once installed, you can use the FAHControl app to choose whether the app works all the time, or only when your Mac is idle — and you can choose how much of your Mac CPU power it uses. It defaults to the lowest priority, and light usage. You can also pause it at any time, for example, while running an app that needs all the power it can get.

Please make sure you do this: Join the 9to5Mac team, enter team number 235955 when prompted. This will combine the data together within the teams' data to get a faster result.

GustavoPi wrote:

Standard BIOS mode does not have the newer features of EFI, you can't install Win10 as you please.

W10 can be installed using either CSM-BIOS or EFI, depending on your specific Mac model.

Besides, may not work anyway, I have a BIOS install and does not have audio either.

This depends on the BIOS/EFI mode and if your specific Mac supports one or the other or both.

• 2012 and older Macs support legacy BIOS using CSM-BIOS because these are preUEFI (EFI 1.x)
• Late 2013 and 2014 models support both EFI and BIOS modes (UEFI - EFI 2.x and CSM-BIOS)
• 2015 and later models only support EFI (UEFI - EFI 2.x). Catalina only supports W10

I have mid 2012 macbook pro with two drives (no optical drive anymore). When I try to install Windows, something always go wrong. This time, the windows installer could not proceed into the bootcamp NTFS partition (side by main macOS Catalina) because the partition schema was GPT. It seems a dead end, buy some guy discovered the solution - just format the bootcamp as Mac OS and let the Windows Installer format it again. This time, the installer did all the stuff needed and voila... So I really don't know how things works in my SSD...

I did't find this "Valor". What is this and where do I get it?

TGIK wrote:

Simple perhaps...but you are asking him to open the chassis twice, disconnect delicate flat cabling etc....

GustavoPi has experience of having completed the task successfully, since the second drive was installed (presumably) by the respondent. 😉

it is all good brother, it was a playful tease -----

NP!

personally since I don't use thunderbolt on the windows side, have no use for a second monitor (I have plenty of desktops)--

Others may, so a case-by-case basis recommendation is warranted!

and besides my boot loader screen looks way more interesting then you ever could do with BIOS emulation where even if it is a linux disk you have the boring hard disk icon and the title of ‘WINDOWS’ 

Beauty (and elegance) lies in the eye of the Beholder!

Hi TGIK, I've just bought an used MBP early 2011, the "a1286" 15 inch version, succesfully installed High Sierra OS, then installed Win10 1909 64bit version (UEFI) and I got the audio & both video cards problem.......(sad), is your (super!) workaround still valid for this version of MBP? I'm not so skilled.... sorry to boring you.... :-(

Many thanks!

Daniele

ps: attached the link to my MBP's spec.