smb big sur

I have an MacBook Pro 15 2018 and I can't install the beta 4 version of Big Sur no matter what I do installing in safe mode , reset NVRAM, SMC reset, Single user mode, setting the time, try out another user, recovery mode, try deleted and download a new one and bootable drive. My Mac still won't install the beta version of Big Sur.

Greetings everyone, A few days ago I downloaded Big Sur to give it a try. As it is still in Beta it is really buggy at some points and I could not work on my art works, that is why I decided to go back to Catalina and wait until Big Sur will release. I used Option+Command+R to get in the recovery mode for Catalina version. I agreed to terms and when I needed to choose a disc - I could not do it because my disc was locked. How do I unlock that disc?

Because I'm just an absolute daredevil, I have Big Sur running as a fresh install from b1 in a brand new APFS container with no other OS's or partitions on-disk. I've tried to partition in BootCamp, Disk Utility, and Disk Utility via Recovery. No dice. Is this blocked by System Integrity?

Before macOS Big Sur, one could create an ad-hoc WiFi network using CWInterface's -startIBSSModeWithSSID: security: channel: password: error: But this appears to no longer function on Big Sur: The operation couldn’t be completed. (com.apple.coreWLAN.error error -3930.) What is the Big Sur way of programmatically establishing an ad-hoc network?

How much space required to install macOS Big Sur. While starting update shows 16 gb required.

my MacBook startup getting slow after updating latest macOS Big Sur what action required to fix it ?

Is there a new way in Big Sur, running on an M1, to enable and utilize large memory pages? I've done a lot of searching on the internet and many tests, but haven't been able to figure it out. Closest I've come to insight is thinking there might be a conflict with JIT preventing the usage of it? This is what used to work in C++: void *mem = mmap(0, size, PROT_READ | PROT_WRITE, MAP_PRIVATE | MAP_ANON, VM_FLAGS_SUPERPAGE_SIZE_2MB, 0); Also tried: void *p = mmap((void *) 0x000200000000, 8 * 1024 * 1024, PROT_READ | PROT_WRITE, MAP_ANON | MAP_FIXED | MAP_PRIVATE, VM_FLAGS_SUPERPAGE_SIZE_2MB, 0); Maybe there's an alternative way to accomplish Huge pages.

I just upgraded to the Big Sur update and now my iMessage is extremely laggy. Everything else works fine. What can I do to fix this problem?

I have MBP 2018 and upgraded to Big Sur, immediately problem with battery. the battery run out from 100% to 50% only took 30 Minutes and the MBP temperature was getting hot. Apple has to fix the problem immediately. I think many other thousands got affected due to the same problem and dissapointed on this product.

I'm interested in testing the Auto Advance features in Big Sur in our lab and wanted to see if there is any documentation on what is needed to be done on the ABM side and the computer side to set it up. Also wanted to see if there is any special network ports or other requirements that we need to have in place to make this work.

I have three computers, two running Mojave with no problems and one new macbook pro with Big Sur. The internet speeds on the Big Sur computer are ~8Mbps while on the others ~100Mbps. The router is new, other devices are fine, just the macbook. I reinstalled the OS and did all the checking and troubleshooting advised on other message boards, but still no solution. I don't have a VPN, etc. I'm at a complete loss. Has anyone else been able to solve this issue?

After installing Big Sur Public Beta 4, Mail was stuck perpetually at Mail Upgrade. Fixed the problem by going to folder ~Library/Mail and renaming the directory for the mailboxes from V7, which was Catalina's version to V8 which apparently was what Big Sur mail was looking for. Apparently the rename didn't occur during the Upgrade. Restarted Mail and it then completed the Upgrade, went to Optimizing, and Mail loaded and is functioning properly.

The entire view is erased whatever rect is passed to self.needsDisplayInRect thus making this call totally useless. If the view is set top non opaque, then its the windows that erases everything. This is a VERY SERIOUS BUG and makes Appkit almost UNUSABLE for efficient graphics/ redraws. Already starting 10.14 the OS was erasing all View behind our back. But at least one could make a cleaver use of needsDisplayInRect to still be able to do partial redraws. Now on Big Sur even that doesn’t work, forcing us to either redraw everything all the time or to use an extra buffer which is obviously a huge waste of CPU and memory. Plus my experience with that solution is performances gets catastrophic on huge screens… If anybody knows a work around... Eric Wenger, Bryce,Metasynth,ArtMatic father

Safari not opening on macOS big sur I'm using macbook pro 16

I have just updated to Big Sur on my Mac book and I now cannot connect to the internet either through wifi or an ethernet cable.