Jump to content

Mac Suppport


Recommended Posts

  • 8 months later...
2 hours ago, Wayneo said:

@NavyChiefRetired My daughter has an M1, I'll see if she'll let me borrow it. Did it ever work on that Air, or was this a first time try?

I'm going to load the latest SP50 INTL version.

First time installing it on this computer 2020 M1 MacBook Air running Ventura 13.4.1. It'll start up just fine but as it's downloading the mods settings (Paranormal DNA 250) Escribe just shuts down without showing any errors. Escribe SP50 runs perfectly fine on my old Intel MacBook Pro with the same mod and usb cable.

Edited by NavyChiefRetired
Link to comment
Share on other sites

  • 2 weeks later...
  • 10 months later...
  • 6 months later...

Hello,

I would like to share my experience installing and using the latest version of eScribe SP57 INT on my 2024 Mac mini (M4/32GB, macOS Sequoia 15.1.1). The installation process itself went smoothly, with no issues encountered during setup.

However, I faced a recurring issue when attempting to connect my new (New Old Stock) Evolv DNA 100 Color device, which was paired with a brand-new Samsung 40T 21700 battery (4000mAh, ~15% charge). I used a high-quality Anker USB-C to USB-C cable to connect the device to my Mac. Upon connection, eScribe successfully recognized the device and initiated the settings download. The download progressed as expected until it reached 100%, but then I encountered a persistent error message: “Crash Log Failed – Unable to log Crash”. Clicking “OK” would return me to the main interface, but the only available option was to retry the connection and download, which resulted in the same crash each time.

To troubleshoot, I switched to a Windows 11 Virtual Machine, installed the Windows version of eScribe, and connected the same device via USB. This approach worked flawlessly—the settings download completed without issues, and I was able to update the firmware to 1.1 SP55.1 INT without further complications.

Given this, I am unsure if the issue on macOS was caused by the low initial battery level (~15%) or perhaps a compatibility problem specific to the macOS version or USB interface. It’s worth noting that after some time connected to the Mac mini, the device likely charged slightly, which may have contributed to more stable behavior when switching to the Windows environment.

I would prefer to avoid using a virtual machine for routine updates or tweaks, so I hope future updates might address this behavior on macOS. Despite this hiccup, I appreciate the robust functionality of eScribe on Windows and the flexibility it provides once properly connected.

Thank you for your ongoing support and development of this software. If additional logs or details would help in diagnosing the issue, I am happy to provide them.

image.thumb.png.93ea4364c3ba13d7bb054032a341f160.png

Warm regards

 

Edited by JAB
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...