Hi Gerald.

28-Nov-02 16:34:08, Gerald Miller wrote to Jasen Betts


 GM> Hello Jasen,

 GM> Remember when I asked about:

 GM>   on errormsg (log /w %{at}path[%{at}search[%0]]%{at}upper[%{at}name[%0]].ERR)

 GM> ???  Well, I've had some form of results....  I put that line in one of
 GM> the
 GM> batch files that was misfiring sporadically when called from xboot3.btm.
 GM> I
 GM> have an error log file that is 27 lines long; each line starts with the
 GM> date and time, then has a 4dos btm code segment (from the misbehaving
 GM> btm);
 GM> BUT, no 4dos error message, no line numbers, and the log file even
 GM> contains
 GM> some commands from 4EXIT.BTM.

That what logging does. I don't think it's the solution you need.

 GM> I think I will experiment with some of the following to see what will
 GM> happen:

 GM>   on errormsg ? (log /w %{at}path[%{at}search[%0]]%{at}upper[%{at}name[%0]].ERR)
 GM>   on errormsg ?? (log /w %{at}path[%{at}search[%0]]%{at}upper[%{at}name[%0]].ERR)
 GM>   on errormsg _? (log /w %{at}path[%{at}search[%0]]%{at}upper[%{at}name[%0]].ERR)
 GM>   on errormsg _syserr (log /w
 GM> %{at}path[%{at}search[%0]]%{at}upper[%{at}name[%0]].ERR)

 GM> Any opinions or suggestions?

I don't think those will work.. I think the the ? ?? _? _syserr is wrong.

on errormsg ( pause %=%+ set | *list /s %=%+ quit )

  that should freeze the btm at the error and report the contents of all
  variables.

on errormsg 4dos

 that'll do the same sort of thing, but it'll also let you play a bit too, but
 changes made to variables won't be retained, type exit to continue the
 btm.

 -=> Bye <=-

---