Jump to content

JaI Haze

Members
  • Posts

    72
  • Joined

  • Last visited

Posts posted by JaI Haze

  1. yea I can 100% confirm that with the coffee lake cpu's it does not work, or any of the quad cores. It does work on the mac mini and even on catalina. So whoever is coding this, if you want to make it open source or send me the files I can also help code it to be more compatiable. Not 100% sure when I can get to it, but I do have a strong coding background

  2. 6 hours ago, DJT said:

    They have done already, but I don't think it's common knowledge!

    I use this version (SP20) on Mojave with no problems whatsoever - https://downloads.evolvapor.com/SetupEScribe2_SP20_INT.pkg - This is the International version as I'm in the UK,  delete the "INT" from the link if you don't require that version.

    Hope that helps you out.

    yeah neither the int or the us version works for me. Its due to the cpu im using, its the coffee lake. I can get it work on my dual cpu from 2017 just not the 2018 model with 4 cores

  3. On 12/19/2018 at 2:12 PM, Monotremata said:

    SP19 just bounces a few times for me, then crashes right away. No dialog box or anything but this is the console's output:

    
    Dec 19 11:04:04 Chriss-Mac-Pro com.apple.xpc.launchd[1] (com.apple.imfoundation.IMRemoteURLConnectionAgent): Unknown key for integer: _DirtyJetsamMemoryLimit
    Dec 19 11:04:15 Chriss-Mac-Pro mono-sgen64[7382]: DEPRECATED USE in libdispatch client: dispatch source activated with no event handler set; set a breakpoint on _dispatch_bug_deprecated to debug
    Dec 19 11:04:15 Chriss-Mac-Pro com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.pid.mono-sgen64.7382): Could not resolve origin of domain. XPC services in this domain's bundle will not be bootstrapped: error = 107: Malformed bundle, taint = missing executable
    Dec 19 11:04:15 Chriss-Mac-Pro com.apple.xpc.launchd[1] (com.apple.imfoundation.IMRemoteURLConnectionAgent): Unknown key for integer: _DirtyJetsamMemoryLimit

     

    This is a day old fresh install of Mojave on a 2010 Mac Pro.. I haven't been able to use Escribe at all since about SP17 and one of the High Sierra updates.. It opened fine, but backing up or sending a config to my HCigar DNA75C took FOREVER, and actually hung and soft-bricked my DNA a couple times. Opening up a theme in the Theme Editor, will almost immediately crash it as well. I had to install it under Win 10 on my Bootcamp partition to restore it when I bricked it while it was attempting to upload a theme. Windows worked just fine but no luck on the Mac for awhile now..

    you and me both, every new version or even the old ones do not work. I sent in a ticket and they told me they were working on it

  4. 4 hours ago, DutchDK said:

     

    I doubt a mojave specific version is needed - it runs fine on the public beta version.

    The only thing I would suspect being needing code changes, is if escribe should support the new MacOS Mojave Dark mode fully - but thats just a pure cosmetic change. All functionality in escribe works fine with the public beta, and I doubt that will change with the release version.

    There is. Mac changed from high Sierra to Mojave’s to a 64bit. Almost every app had to remake.  Escribe starts but that’s it. 

  5. 37 minutes ago, ajoe said:

    I have two DNA250c devices from two different manufacturers, both are running the default Evolve theme.

    I have never seen this behavior. 

    Do you have a custom theme installed? If so, perhaps reverting to the default theme would help.

    I checked the Escribe docs and can't find any settings to control such behavior.

    Sorry I can't be of more help. Maybe someone else has run into this.

    the problem is this happens even on default themes.  It basically asks for resistance every time it goes into standby mode and I fire it

×
×
  • Create New...