> Brian, I don't recall WARNF requiring the console.

I suspect it requires that you could have issued a regular WARN command if
you wanted to, i.e. you have to be the console, or have the command :ALLOWed
to you.

In any case this is going to be a privileged operation, so the options are
to either use MPEX or find/develop (or have developed) a priv mode program
that can do this for you.  Maybe there's something out there in the CSL
already.

The cheesy way to do it is to start with PM, programmatically :ALLOW
yourself the :WARN command and give yourself SM and then open up
CATALOG.PUB.SYS, then temporarily replace the OPERATOR WARNING: message
catalog text with the escape sequence that writes to the function key area
of the terminal, then do a :WARN of your message, then put the original
OPERATOR WARNING: text back and remove the capabilities that you added.

The parameter that you pass to the :WARN command has any escape characters
you try to include stripped (with the exception of <ESC>&Dx where "x" is "@"
through "P" I think) but the message catalog text is not stripped of escape
sequences.

G.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *