Bulletin number: 26 Products affected: D700E Description: Information about screen handling in TDS3 Component: iterm Date: Fri Mar 9 11:58:16 GMT 1990 ----- Here is some information about the use of iterm in TDS3 for those who are having difficulties. TDS3 needs the following screen control sequences to be able to work at all: Up, down, left, right, gotoxy, clear eol, beep. If any of these are undefined a textual message will appear on the screen each time the code is required. The message consists of "", etc. One could live without beep, but not the others. The code of the TDS can accommodate the situation that insert/delete char and insert/delete line are undefined. If either insert char or delete char is undefined then the TDS will repaint the rest of the line instead. If either insert line or delete line is undefined then the TDS will repaint the rest of the screen instead - this gives barely acceptable performance. If EXEs send tt.ins.char etc, when these codes are not defined then the textual message will appear instead. The final complication is clear to end of screen, which is implemented in BANSI.SYS and not in NANSI.SYS (nor in ANSI.SYS). For historical reasons (because the toolset debugger only ever uses clear.eos at the top left corner of the screen) there exist ITERMs which put the code for clear.screen in the line for clear.eos. Accordingly the TDS decides whether clear.eos is defined by saying "clear.eos is undefined if the code for clear.eos is identical to that for clear.screen, or the code for clear.eos is undefined". With this knowledge it performs clear.eos by a single clear.eos code or a sequence of clear.eol *c*n as appropriate. I trust that with this information anyone will be able to create a suitable ITERM for any PC.