It could be a config file issue with wsjtx. Try renaming the config to a
.conf.bak and re-starting wsjtx, then proceed as if you've installed wsjtx
for the first time (enter callsign, location, rig control config, etc)...
I haven't run into this issue myself, but maybe it's worth a try?

73 de AI8W, Chris

On Thu, Dec 20, 2018 at 8:13 PM Jim Kennedy <jimkenn...@hawaii.rr.com>
wrote:

> Hi Steve:
>
> Thanks for you thoughts!
>
> I did do John, G4KLA's procedure quite some time ago when the Mac Mini
> first came on line (as it was necessary).
>
> I have reviewed that again, and the values haven’t change on the Mini, (or
> the desktop and laptop which are working fine with OS 10.13.6).
>
> My results are:
> $ sysctl -a | grep sysv.shm
> kern.sysv.shmmax: 33554432
> kern.sysv.shmmin: 1
> kern.sysv.shmmni: 128
> kern.sysv.shmseg: 32
> kern.sysv.shmall: 8129
>
> The is significantly larger that what is working for you (although the
> last line is smaller), and the error message is not the same as one that
> the current message is producing.
>
> My next step seems to be ripping out 10.14.2 and drop back to 10.13.6, and
> see if that even has anything to do with it.
>
> 73,
>
> Jim
> K6MIO/KH6
>
> > On Dec 20, 2018, at 12:02 PM, Steven Franke via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
> >
> >> I seem to recall that there was a point, previously, during which some
> Macs needed to have a memory range tricked out.  That was done with the Mac
> Mini, and it then worked fine with earlier versions of both the OS and the
> WJST package.
> >>
> >> Is that still an issue.  Did the OS update wipe it out?
> >
> > Hi Jim,
> >
> > You may need to increase the shared memory allocation if you are running
> the stock configuration of MacOS. The instructions can be found in
> src/Darwin/ReadMe.txt file, which was prepared by John, G4KLA. Here’s a
> relevant excerpt from that file:
> >
> > 'After the reboot you should re-open the Terminal window as before and
> you can check that the change has been made by typing:
> >
> >  sysctl -a | grep sysv.shm
> >
> > If shmmax is not shown as 14680064 then ... WSJT-X will fail to load with
> > an error message: "Unable to create shared memory segment”.'
> >
> > Here’s what I get on this laptop, which is running MacOS 10.14.2 and
> which runs WSJT-X just fine:
> >
> > $ sysctl -a | grep sysv.shm
> > kern.sysv.shmmax: 14680064
> > kern.sysv.shmmin: 1
> > kern.sysv.shmmni: 128
> > kern.sysv.shmseg: 32
> > kern.sysv.shmall: 17920
> >
> > If your shmmax parameter is smaller than 14680064, I recommend that you
> follow the procedure that is explained in the ReadMe.txt file.
> >
> > Regards,
> > Steve k9an
> >
> > _______________________________________________
> > wsjt-devel mailing list
> > wsjt-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to