I hope you will go on to find out what is wrong with allolddefs, or at
least post it so we can all see it. I don't remember it.
Henry Rich
On 5/22/2022 5:03 PM, 'Michael Day' via Beta wrote:
Success?
I had tried that, initially on Friday,with jconsole.bat but didn't see
any clues.
Also, as I said, I'd tried commenting out stuff in startup.ijs,
which also didn't
apparently change anything.
Now, however, I embedded echo statements in startup.ijs They did indeed
stop appearing before the end of the script. This suggested that
checking
old definitions was at fault; I rather think Henry must have recommended
or requested we use it. This is the relevant snippet from startup.ijs:
load'~user/olddefs.ijs'
echo LF,'CHECKING OLD DEFINITIONS'
allolddefs 1
echo 'startup: have checked old definitions'
This echo had not appeared in the jconsole/cmd.exe log.
Commenting out the call to "allolddefs" results in a successful load
of either
jconsole or jqt.
Sorry - I thought I'd already tried disabling this call, but perhaps
I'd trusted
a J-supplied script!
As it is, it appears to be unwise to check for "Old Definitions."
Thanks for all the help,
Mike
On 22/05/2022 21:18, Raul Miller wrote:
On Sun, May 22, 2022 at 2:59 PM 'Michael Day' via Beta
<[email protected]> wrote:
Starting jconsole with admin privileges briefly shows a window which
then disappears.
Try starting it from a command shell
That way, the window will remain and any potential error message
should be readable.
Thanks,
--
This email has been checked for viruses by AVG.
https://www.avg.com
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
