Eric, I tried your suggestion, and nothing new. FYI, I had not earlier cd'ed to the bin directory and then had a time getting macos-fix.command to work, but finally with the correct prefix it did work but did not fix anything.
I am not using Catalina or Sierra, so in the past I don't think a "fix command" was necessary because OS X prompted me with a question of whether I wanted to open such a downloaded executable. Anyhow, below is my newest Terminal session. Last login: Tue Jan 14 17:00:21 on ttys008 server:~ brian$ cd /Users/brian/j901/bin server:bin brian$ open ./macos-fix.command The file /Users/brian/j901/bin/macos-fix.command does not exist. server:bin brian$ open .macos-fix.command The file /Users/brian/j901/bin/.macos-fix.command does not exist. server:bin brian$ open ..macos-fix.command The file /Users/brian/j901/bin/..macos-fix.command does not exist. server:bin brian$ open ../macos-fix.command server:bin brian$ When the above runs, I get a new terminal which reports as follows. Last login: Tue Jan 14 17:12:19 on ttys008 server:~ brian$ /Users/brian/j901/macos-fix.command ; exit; logout Saving session... ...copying shared history... ...saving history...truncating history files... ...completed. [Process completed] On Tue, Jan 14, 2020 at 5:09 PM Eric Iverson <[email protected]> wrote: > I think you need to run macos-fix.command (as Julian pointed out). > > Not sure of the details but you could: > 1. use finder to get to the j901/bin folder and click that command > or > 2. start a terminal windows, cd j901/bin, and then enter > ./macos-fix.command (not that the ./ is important) > run ./macos-fix.command > > > ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
