Tips for polishing TAM application programs running under ETI

To enable the code in your TAM application program to run smoothly under ETI, you should do the following:

• remove code that would be executed if a low-level iswind function call returned a non-zero value, that is, TRUE. Under the TAM transition library, iswind always returns FALSE.

• remove all TAM calls to mouse management routines and the calls wicon, wicoff, and wrastop, because they will translate to null operations.

• remove all machine-specific code, because the TAM transition library does not translate system calls specifically tailored to the UNIX PC or calls (such as ioctl(2)) that have no meaning under ETI. These calls fail under the TAM transition library on all machines except the UNIX PC.

• note that all calls to track map to the low-level function wgetc.

• remove all references to TAM calls that bear the same name as ETI calls because calls that have the same names in both systems have different effects.

• remove all arbitrary ANSI escape sequences for display output. For example, the TAM transition library does not recognize the escape sequence used on the UNIX PC in the command echo "\033[J", which clears the screen. Instead, you should use equivalent ETI routines (here, clear).