Bob and Rob, Perhaps the security was the problem. I temporarily changed the security to allow ANY application, so no last second question would be needed after launch. I still got denied by a new message which said something about the sandbox disallowing the application (I'm sorry about not having the exact message but when I IMMEDIATELY tried to repeat the launch, that message was no longer made.) But the good news is that the second time, jconsole opened perfectly using Command+O on the red jcon icon in brian/j64-807/ .
I am typing this during my long wait "Installing Qt library..." but will report whether that salvages jQt for me, too. I just hope new users are not having this problem because it is very discouraging. And I want to remind the J team about the missing link at jsoftware.com/stable.htm . Thanks very much for helping me with this problem. (Ok, the wait is over. jQt works, too.) On Sun, Feb 17, 2019 at 4:27 PM 'Rob Hodgkinson' via General < [email protected]> wrote: > Brian/Bob, just to weigh in: > > I too am running Mojave, but Release-a (the same release candidate you > just downloaded in the zip file Brian). > > I confirm that Release-a does not have the bug you reported (your script > runs clean on my system): > > JVERSION > Engine: j807/j64/darwin > Release-a: commercial/2019-01-11T11:43:43 > Library: 8.07.22 > Qt IDE: 1.7.9/5.9.7 > Platform: Darwin 64 > Installer: J807 install > InstallPath: /users/rob/j64-807 > Contact: www.jsoftware.com <http://www.jsoftware.com/> > > > ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
