880.0.1
(Windows/ATE) Implement more ZTERM ESC sequences:
LABEL WINDOW
?CHR(27);CHR(13);TITLE$;CHR(0);
SET WINDOW STATE
?CHR(27);CHR(25);CMD$ !(CMD$ is M, X, R, or N)
FLASH WINDOW
?CHR(27);CHR(16);"1" ! start flashing
?CHR(27);CHR(16);"0" ! stop flashing
SET FTP LOGIN NAME/PASSWORD
?CHR(27);CHR(29);NAME$;CHR(0);PW$;CHR(0);
880.0.2
(Windows/ATE) ZTERM ESC sequences can now use chr(128) in place of chr(0) for the delimiter bytes.
880.0.3
(Windows/ATE) New TAB(-10,x) sequences. (Note that these may be used in place of the corresponding ZTERM ESC sequences when running under UNIX with ATE on the client, as well as under standard A-Shell/Windows.)
Set window State:
?TAB(-10,27);STATE$;CHR(127);
STATE$ may be M, X, R, or N (as in the ZTERM ESC sequence
above, or "1" thru "10" (as in MIAMEX,77)
Flash Window:
?TAB(-10,28);"0";chr(127); ! turn flashing off
?TAB(-10,28);"1";chr(127); ! turn flashing on
Set FTP name / password:
?TAB(-10,29);NAME$;chr(126);PASSWORD$;chr(127);
880.0.4
(UNIX) Operations which scan directories (such as DIR and PPN) no longer abort when hitting a directory entry which causes an error other than end-of-directory (such as protection violation). This should eliminate mysterious and frustrating situations, caused by an inaccessible directory entry, where you can log to a PPN but not see it in the directory. Note that if you suspect such a situation, you can use SET TRACE SYSERR ON to display the offending entry and the corresponding error. Such errors will also be logged to the ashlog.log file.
880.0.5
(WINDOWS) Report directory scanning errors as described above, both to the screen (if SET TRACE SYSERR ON) and to the ashlog file.
880.0.6
(ATE) FTP transfers now pop up a "transfer in progress" box. There is no current option to cancel the transfer and you probably will rarely see anything beyond a flicker, except when transferring very large files. Messages corresponding to errors occurring during transfer are now displayed.
