SamuriHL
UHD Guru
- Joined
- Jan 28, 2007
- Messages
- 15,044
- Likes
- 2,549
Yes. I'm running it on my MacBook pro 16 m2 max without issue.I knew it would work because in my first post I said the following.
Sent from my SM-G998U1 using Tapatalk
Yes. I'm running it on my MacBook pro 16 m2 max without issue.I knew it would work because in my first post I said the following.
I see the error, but can't figure out the reason.Still no joy whereas the Mouse and Mr Max are concerned.
Attached is a logfile created directly after the failed login attempts.
It's unlikely to be an M2 issue. Rosetta really works great, it's good stuff.It works on my Intel Mac, but I can't get it to start on my M2 Mac.
Other Intel apps are running, so Rosetta seems to be installed.
I found the message in console.app.
I hope this will be helpful.
works fine on my M1 iMac.That's because M1/M2 is arm and anything doesn't work on arm (yet)
Beside my current login issues the Anystream runs just fine on an M1 Mac Mini.That's because M1/M2 is arm and anything doesn't work on arm (yet)
Sent from my Pixel 7 Pro using Tapatalk
Will do. Back later -ish.I see the error, but can't figure out the reason.
If possible, can you do a login procedure on Windows and also send a log file? It might help, if I can compare your failed log to a working one.
This is later and well, this isn't going all that well.Will do. Back later -ish.
I started it by double-clicking the /Applications/AnyStream icon.Did you get the initial setup dialog (the wizard, where you select the language and the providers you want to use)?
Well a bit more later and after a lot of updates to the virtual Windows 11 installation Anystream starts without an instant crash.This is later and well, this isn't going all that well.
The closest thing to Windows I have available is an emulated instance of Win 11 (ARM) running under Parallels on an M1 Mac Mini.
It has previously worked/played really well with Anystream but...
I installed the latest Windows version of Anystream and it crashed on first sight...so to speak.
Then I managed-with some sleight of hand- to close the Max Tab and then it didn't crash, it just turned unresponsive.
On next attempt it crashes momentarily, even the error dialogue is sort of really unresponsive.
Only thing I got out of this are a bunch of crash dumps. Interested?
Can you please tell me your version of Mac OS X?I started it by double-clicking the /Applications/AnyStream icon.
Can not be displayed.
The app bounces a few times on the Dock and ends.
I looked for the message again in console.app.
I wrote it out to a file.
Most likely a bug. Does the about box actually display your license?I did notice that even after importing my license I still see the warning about features available during trial that won't be when the trial expires... do I need a separate license for the Mac version? Or is that a bug?
Ok, don't bother, if I had known, that it's that much trouble, I wouldn't have asked.ell a bit more later and after a lot of updates to the virtual Windows 11 installation Anystream starts without an instant crash.
Thing is that now I can log into Max but the Mouse login issue still remains. Addendum: Now the MacOS version behaves the same still no Mouse but Max.
See attached logfile for more info.
I started it by double-clicking the /Applications/AnyStream icon.
It turns out that someone I know had changed a password without telling...an error of sorts but not related to Anystream.Well a bit more later and after a lot of updates to the virtual Windows 11 installation Anystream starts without an instant crash.
Thing is that now I can log into Max but the Mouse login issue still remains. Addendum: Now the MacOS version behaves the same still no Mouse but Max.
See attached logfile for more info.
See this post for an explanation...to at least the mouse-service issue. It wasn't an error, more like a communications f-up. Sorry to have wasted your time.Ok, don't bother, if I had known, that it's that much trouble, I wouldn't have asked.
I thought, since you're a member here, you already had a working Windows version.
Now - I would suggest, at least as a test, that you change your Disney password, so that it only contains 7-bit ASCII codes.
As a rule, I'd actually always refrain from using characters outside that range for passwords, because their encoding is, even in times when Unicode is a very old and wide-spread idea, often system dependent.
From what I see, when playing around with Disney, they in particular seem to have messed this up.
When logging in from the browser, they send the credentials without a given encoding and seem to use the system code page (which can be one of dozens of different encodings), but don't include the information which one it is. AnyStream uses UTF8 which is the recommended standard when sending JSON.
That said, I was able to logon with both a local code page, as well as when using UTF8 and the only explanation I have for that, is that Disney's servers seem to work around their faulty implementation by trying a number of code pages.
But still - those characters seem like a probable cause.
macOS Ventura 13.3.1Can you please tell me your version of Mac OS X?
Now supports "unsigned" applications.dumb question, but you have already "⌘ opened" it (needed first time only as it's unsigned)?