smb big sur

hello everyone, just bought a splendid air m1. Just turned on and the maximum battery capacity status reports 75%. Is it a big sur 11.0.1 bug? How can you find out?

I just released an app update for Mac that is optimized for the new M1 Macs and Big Sur. App Review rejected the app because I mentioned pre-release Apple products, so I had to remove references to Big Sur and M1. I assumed since they were on the Apple site they weren’t a secret anymore. Does anyone know how long we have to wait to be able to mention our apps are designed for new technologies? Right now I have a nebulous “designed for future Macs and macOS systems” which is far from ideal for customer recognition.

I know this is a bit late in the Sonoma beta-program, but I wanted to ask here, since I got directed here by Apple support, even though it appears I got Sonoma-14.0 release a day before the non-beta users. And/or I want leave a marker for others with the same needs. I have a 2019 Mac Pro with a dual-port 100GbE ATTO card in it. I run Adobe Premiere, DaVinci Resolve and Autodesk Flame. I would like to do editing and color correcting 4K and 8K frame-based video. 8K video is 4.5GB/sec per DPX stream. (not Gigabit). I connect to a SMB server which is all flash, and runs SMB-Multichannel. This same NIC in a windows box can run 9GB/sec. but in the MacPro, it gets about 3GB/sec. if you run netstat, smbutil, or nettop (the builtin MacOS utility) it shows only ONE TCP socket talking to my server on port 445. This is the reason it goes no faster than 3GB/sec. Windows shows 8 or 16, whatever I set it to number of RSS channels, and goes full speed of the NIC. When is MacOS SMB-Multi-channel goi

I had been using @available( macOS 11.0, * ) to test for Big Sur, but as of the Xcode 12 GM, that doesn't seem to work any more. Whereas @available( macOS 10.16, * ) does work. Is that the right thing to use, or is it a bug?

Why is my screen flickering/glitching after MacOS Big Sur update?

I have 3 problems in this post. hv_vm_create() fails I recently got the BigSur beta (I'm on the latest) to try out some hypervisor app I've been working on, however hv_vm_create() - https://developer.apple.com/documentation/hypervisor/1441424-hv_vm_create fails. 2. Killed: 9 when signing with Hypervisor entitlements I figured Big Sur might be enforcing entitlements, so I signed it with the same entitlements from xyhve - https://github.com/machyve/xhyve/blob/master/src/xhyve-entitlements.plist (and updated it as per the documentation - https://developer.apple.com/documentation/bundleresources/entitlements/com_apple_vm_hypervisor) but this time I was getting. Killed: 9 Do I have to request permission to use those entitlements? That's the conclusion I'm coming to because HypervisorKit just doesn't work; and nothing happens on macOS for no reason. 3. HypervisorKit in beta? This is what confuses me the most. Why are HypervisorKit functions that have existed since 10.10 in beta? And why does the d

In Big Sur, I noticed that the open command no longer distinguishes different copies of an application. For example, if I have /Applications/AppV1.app and /AppicationsAppV2.app, and AppV1.app is running, then open /Applications/AppV2.app is simply bring AppV1.app rather than opening AppV2.ap. I have to use the -n flag to open the second version. This seemed like a regression to me (I filed FB8806330 about it), but perhaps intentional, or at least justifiable. But now I've discovered a much worse symptom. If App.app and Bpp.app is another application by my company, then open /Applications/Bpp.app brings App.app to the foreground rather than opening Bpp.app. All the applications have distinct bundle identifiers. Indeed open -b com.Company.Bpp will also bring App.app to the foreground. This is just a crazy bug, right? Any ideas what it might be keying off? It can certainly tell the difference between our apps and, say, Safari. So I'm not sure why it can't tell our applications apart. And if any

I have mac pro that was working on High Seirra OS, today I started installing Big Sur on it, the installation process was smooth until I reached this loading circle, this took much time the way that the total installation time is more than an hour and didn't finish until now, it keeps loading. Should I wait for more time or this means there is an issue? And if there is an issue how can I fix it?

Hi all. I recently upgraded to Big Sur Beta 10. Since then, my Kindle Reading App crashes. It opens but as soon as I open a book it crash and brings up a crash report. I deregistered, removed and reinstalled it but it behaves the same. It will download a book but as soon as it tries to open it, it will crash. Is this behaviour know under beta 10? Is there any work around? Thank you.

I am working on an emulator for some legacy hardware. I recently changed the emulator to use the vmnet framework for network access rather than the old Berkley packet filter (/dev/bpf) device. It works just fine in macOS Catalina. In Big Sur beta 6, the vmnet_start_interface completion handler is never invoked unless the call to start the interface failed. I've submitted FB8648370 to report this. Here's some sample code that demonstrates the problem. Compile it with -framework vmnet and run it with privileges via sudo. On Big Sur, it will timeout after 1 minute. vmnet.c - https://developer.apple.com/forums/content/attachment/f4a79dd9-f801-4171-b1d0-d62fdad38df0

After migration from Catalina to Big Sur 11.1 I noticed that an Automator PrintPlugin does not work anymore. It is rather simple and consists of a single action: NewMailMessage. Mac Analytics Data - https://developer.apple.com/forums/content/attachment/5fb4f6a8-e83f-42c6-be5c-84bf1a7501b9 Running the same action from an Automator quickaction on files works as expected: Mail gets generated with selected files attached. regards Hans-Peter

After updating to big sur I've noticed that there are some cases where ui elements get automatically selected (focused?) in my MacCatalyst app. This is problematic for me in a couple of cases where there is app logic that gets triggered when a textview is initially selected and calls didBeginEditing. The two areas where it seems prevalent are: dismissing modal views and reloading tables. I've poked around into the focus engine and tried to extend textviews to not be focusable to no avail. Anyone else seeing this problem?

Big Sur is missing Battery Percentage options FB7875382 In the menubar “Show Percentage” Is missing Users need to see the exact battery percentage like in previous macOS versions and iOS.

Since I Installed Big Sur OS my Mac doesn't recognise my Kindle. I tried restarting both devices, plugging and unplugging. I saw other messages from 2 months ago but no answer.

Has anyone see an issue where certain contacts do not have a text entry field on Big Sur when selecting them in the list of conversations? I am able to get a field to send a message if I act as if I am starting a new conversation with them.