nu/TPU README files' contents: READ_ME nu/TPU files and directories Use of environment variables Using VAX/VMS developed programs User defaults file Screen attributes Compiling nu/TPU source code License lock management Keyboard drivers nu/TPU installation verifier nu/TPU support policies Version differences SI issues Differences from VAX EVE sample interface nu/TPU source files si keypad, EVE, EDT, and others Known problems -------------------------------------------------------------------------- Getting Help a/Soft Development, Inc. 24 Eastman Ave. Bedford, NH 03110 603.666.6699 603.666.6460 Fax If you have problems installing nu/TPU, technical support can be reached at (603)666-6699. Calling while you are working at the computer will provide the fastest possible service. When you call, please have ready your nu/TPU serial number and the type of computer you are working on. IMPORTANT: After installation, review the read me files for machine-specific information, known bugs, VMS differences, and other important information. -------------------------------------------------------------------------- nu/TPU files and directories After the installation process is complete, the following directories and files will be installed on your system. [THE DIRECTORY YOU SPECIFIED DURING INSTALLATION] [nu_tpu] read_me Installation and last minute notes nu_tpu.def User defaults file nu_tpu.win Menu file for windows version [OS_specific] tpu_v5.exe Windows95 or NT console version wtpu_v5.exe Windows executable file tpu_dos.exe DOS only version license.lok Serial management file makeseri.exe Program to fix/create license file makehelp.exe Program to create help indexes [dev] Various keyboard files enhanced.w32 Default keyboard [common] si.ini Simple interface section file tpu_v5.hlp Help file for windows version. *.hlb, *.idx Help files for DOS version. [source] si interface TPU source files -------------------------------------------------------------------------- Use of environment variables nu/TPU uses environment variables to define the hardware and the location of files to be used by nu/TPU. Normally these variables are set in your login or tpu script files. Refer to your UNIX documentation if you are unfamiliar with use of environment variables. Variable Use Values HOME Optional The location of the user home directory. KEYBOARD Optional The type of keyboard to be used. Must match one of the files in the nu_tpu\dev directory. TPU_DEFAULTS_FILE Optional Name of file containing session information. If a full file name is not provided, the file is assumed to exist in the c:\nu_tpu or TPU_HOME directory. The default name is nu_tpu.def. TPU_HOME Optional The name of the directory containing the nu_tpu directory. This variable is REQUIRED if the directory is not c:\nu_tpu. -------------------------------------------------------------------------- Using VAX/VMS developed programs Source code used with TPU on Digital VAX/VMS systems can be compiled with nu/TPU. User defaults file \nu_tpu\nu_tpu.def An example of a defaults file is in the appendix of the nu/TPU manual. A defaults file is not required, however a warning message will always appear if one cannot be found at run time. Normally the only thing defined in the defaults file is the type of keyboard you are using. Defaults file entries are superseded by command line switches. Screen attributes nu/TPU supports the following screen attributes: NORMAL, BOLD, BLINK, REVERSE, and UNDERLINE; and colors: BLACK, BLUE, GREEN, RED, MAGENTA, CYAN, YELLOW, and WHITE. Not all computers or monitors support all of the above attributes. Compiling nu/TPU source code nu/TPU can compile code from either a command file or a buffer using the EXTEND TPU command. Command file code is compiled before the user interface is started. The EXTEND TPU command should also be reviewed. Compiling code instead of using initialization files will improve startup time. License lock management nu/TPU can be installed on a network file server. Each time nu/TPU runs, the license file is verified. If a lock is available (the default number of locks for MS-DOS is 1), then a new session is started. The lock is returned when the program is finished. If the lock file becomes damaged, run the makeseri program with the -reset option. Keyboard drivers Keyboard files define the relationships between the character sequences or key codes sent from the keyboard and the edit functions for the nu/TPU interface. nu/TPU works on various platforms and operating systems. The outcome of all that versatility is that there is a wide variety of keyboards nu/TPU has to work with. The keyboard files that have been predefined are located in the nu_tpu\dev directory. For more specific information on the keyboard file syntax, operation, and customization, see keyboard files under the nu/TPU Files section in the reference manual. -------------------------------------------------------------------------- nu/TPU Installation Verifier COMMON PROBLEMS & ERRORS Using the verifier. The following text is set up in a progressive format. After entering the requested command, if your results match the text shown, proceed directly to the next verification phase. If your results do not match, the common problems and corrections are shown. Problems resulting from installation and normal use are presented together. Assumptions: The installation directory is assumed to be c:\nu_tpu. In examples, '???' is not literal, but should be replaced by your data. The section file used is si.ini, off the distribution media. VERIFICATION PHASE 1 Problems preventing nu/TPU from starting. SHELL PROMPT $ tpu -env ABORT_2_CONTROL_C:1 BACKUPS:0 CREATE:1 COMMAND_FILE:tpuini.tpu DEBUG_FILE:common/debug.tpu DISPLAY:1 ESCAPE_IS_SHIFT:0 FILE_STYLE:DOS HANDLE_ESCAPE:1 INITIALIZATION_FILE: JOURNAL_FILE: KEYBOARD:enhanced.nt WIDTH:0 LENGTH:0 LANGUAGE:USA_ENGLISH MESSAGE_FILE: MODIFY:0 OUTPUT_FILE: READ_ONLY:0 RECOVER:0 SECTION_FILE:c:\nu_tpu\common\si.ini START_RECORD:1 START_CHARACTER:1 STACK_SIZE:1000 SWITCH_STYLE:- TERM_TYPE: TPU_DEFAULTS_FILE:nu_tpu.def WRITE:1 INTERFACE: # Serial Number:0000000000000000 # nu/TPU Version 5 - a/Soft Development - 603.666.6699 Proceed to Phase 2 of verification if the above text was displayed; an exact match of the text is not required. If you did not get the proper display, check the common errors below and rerun Phase 1. Program file not found An executable file named tpu could not be located in your current path. 1) Add the installation directory to your search path. set PATH=%PATH%;c:\nu_tpu 2) Move the tpu executable to a directory that is in your path. copy c:\nu_tpu\dos386\tpu_v5.exe c:\bin 3) Specify the entire path every time you use nu/TPU. c:\nu_tpu\dos386\tpu_v5.exe '???\nu_tpu' is not a properly installed nu/TPU location. You receive this message if nu/TPU is not in the directory /usr/local/ and the environment variable TPU_HOME is not properly defined. The '???' is the directory containing the nu_tpu directory. It is recommended to add the following line to your tpu shell script. set TPU_HOME=??? Unable to read license file: '???\license.lok' The license file must be read/write enabled. If mounted on a network, file-system must also be read/write enabled. If the license file does not exist, proceed with the following license.lok damaged instructions. License file: license.lok damaged The license.lok is located in the same directory as the 'tpu_v5' program. If you are unsure of the location, it is specified in the 'tpu' batch file. cd \nu_tpu\dos386 makeseri -reset If this problem persists, the license.lok was corrupted by an outside utility. Use the makeseri utility with your serial number as the argument. makeseri ????-????-?????-??? Missing Section file '???' The requested section file does not exist. The default section filename is c:\nu_tpu\common\si.ini. It is possible to request a different section file on the command line or in your nu/TPU defaults file. When specifying a section name, if an absolute or relative path name is not provided, the section file is assumed to exist in the directory c:\nu_tpu\common. Undefined keyboard: '???' The keyboard file '???' does not exist in the nu_tpu\dev directory. The default keyboard file is enhanced.w32. The keyboard file can be specified in the nu/TPU defaults file or through the environment variable KEYBOARD. The environment variable takes precedence. VERIFIER PHASE 2 Problems preventing the si interface from starting SHELL PROMPT $ tpu Invoking the nu/TPU editor creates a screen with the bottom two lines of the window being used for displaying messages and command/prompt input. The remainder of the screen is used by the edit window and a status line indicating the current buffer name is 'main'. If your screen display does not match the description above, either the section file off the distribution tape is not being used or environment variable TERM is set to something that does not update your screen properly. Section files from versions prior to version 5 can not be used with version 5. Internal nu/TPU error, on signal 11 The file requested is either not a section file, a section file from non-supported version, or a damaged section file. If the section file is user-defined, it must be rebuilt. If the section file is from the distribution media, nu/TPU must be reinstalled. VERIFIER PHASE 3 Problems defining keyboard From within a nu/TPU session, press the Control-K key. A keymap dialog will appear. Press any key you wish, to see their definition. The keyboard file is specified by the following methods. Keyboard files are located in the directory nu_tpu\dev 1) Setting the KEYBOARD environment variable. set KEYBOARD=??? 2) If not set by method 1, then by adding a KEYBOARD entry in your nu/TPU defaults file. c:\nu_tpu.def or c:\nu_tpu\nu_tpu.def. See the appendix in the reference manual for the syntax defaults files. 3) If not set by method 2, enhanced.w32 is assumed. If a different key mapping is preferred nu/TPU contains many predefined key mappings. The default key-map positions keys to approximate the Digital EDT editor. Refer to the SET KEYPAD commands in your reference manual to select other key mappings. It is also possible for you to create a user-defined key mapping. VERIFIER PHASE 4 Problems using specific keys When the help keypad is displayed, pressing a key will display a short description of the function assigned to that key. The description of a highlighted function is displayed by pressing the GOLD key then the key of interest. If all the keys show the proper help description, go to Phase 5. If a whole group of keys do not work, refer to your machine- specific installation instructions. nu/TPU provides an escape hatch for special cases. Hitting the interrupt key twice aborts the current nu/TPU session. No attempt is made to save any work. Normally the interrupt key is assigned to Control-C, but sometimes the backspace key is used. The following command sets Control-C to its assumed behavior on UNIX. stty intr ^C Some or all video attributes do not work. Check that your system supports attributes like BLINK, UNDERLINE, and BOLD. Almost all systems support REVERSE, and some substitute REVERSE when others are requested. To change the video attributes used for the FIND and SEARCH operations, set the si$x_found_highlighting and si$x_select_highlighting variables to the desired attribute value. License lock delays are time consuming. Under no circumstances will data be lost while completing a license verification, but delays can be up to 5 minutes under some circumstances. User message about license limit exceeded. Either nu/TPU is at its session limit or one or more nu/TPU sessions were halted prematurely by improper terminal settings, system crashes, program aborts, or other similar failures. Premature system terminations do not return license locks to the available pool. License locks lost to terminated sessions can be recovered by running the makeseri program. This program is located in the same directory as the nu/TPU executable. Note: running makeseri will cause license lock delays for currently active users. The following commands will reset all the license locks. # cd c:\nu_tpu\dos386 # makeseri -reset -------------------------------------------------------------------------- nu/TPU Support Policies a/Soft Development's nu/TPU support policy includes user hot-line support and upgrades to new versions of nu/TPU. To be eligible for these services, we must receive your completed nu/TPU registration card. For the first year after receiving nu/TPU, you can take advantage of our free hot-line support to help you resolve any processing problems. For questions on more complex nu/TPU interface extensions, we may request a diskette copy of your code in order to provide you with the most thorough and accurate support possible. If a new release of nu/TPU is made available within 90 days of your purchase, you will receive the new release free of charge. You must have registered your original version of nu/TPU with a/Soft to receive the free update. Our technical support staff can be reached at: MAIL : User Services a/Soft Development, Inc. 24 Eastman Ave. Bedford, NH 03110 VOICE : (603)666-6699 FAX : (603)666-6460 -------------------------------------------------------------------------- Changes in nu/TPU from v4.1 to v5 - Windows version Win95, Win32s and Windows/NT now feature support for: Multiple document interface (MDI) CREATE_PROCESS SET( SENTINEL,, ) Improved scroll bars. Registry settings for, Last current directory, window sizes, Background/Foreground colors,and Text edit font. New show key dialog New Define Key dialog Support for long file names. - Memory Leaks Numerous leaks plugged. TPU langauge string manipulation (REPLACE was a big offender) Recursive/Repetitive user procedures using input/output arguments. - Files with large number of lines (~10K and greater) preformance fix. - Compilation a large number of procedures ~2K defined in a single session fixed. - String based CASE statements now function properly - Local occlusion of global variables and constants matches VMS. - Zero assignment of MARKERS, RANGES, and PATTERNS now match VMS. - input/output procedure argument behavior now match VMS. - Interface function name changes eve_extend -> eve_extend(;a) eve_set_function_keys_decwindows -> eve_set_function_keys_motif eve_set_function_keys_nodecwindows -> eve_set_function_keys_nomotif si_replace_all -> si_global_replace eve_set_function_keys_decwindows -> eve_set_function_keys_motif si_set_select_color( attribute ) si_set_found_color( attribute ) - SET(screen_update) returns previous setting. Caused flashing when replacing. - COPY_TEXT returns range of text inserted to match VMS. - CREATE_BUFFER: called with default buffer/read_only and file name. Now reads file name. Changes in nu/TPU from v4 to v4.1 - Windows version uses Microsoft's standalone HELP viewer. - Dialogs added for keypad help, show, attributes, lists. - Improved screen updating. - End user interface in SI made more VMS EVE-like. - Performance improvements. Changes in nu/TPU from v3 to v4 - New simple interface (SI) with sources. - Improved windows integration. - Screen updating and larger file performance improvements. - New UNDO built in function, allows unlimited undo. - New CHOICE builtin in function. - Improved process control. - Buffer names are no longer forced to uppercase. - The evebox section file (VMS 5.4 and later EVE) is no longer supported. This section file is superceded by the new SI section file. - VI support is no longer separate, but integrated in the SI interface. - BOX range type added. - BACKUPS qualifier added to nu_tpu.def. Allows user to control number of backup copies to be retained. Range 0-99 copies. - Keys program to aid in the customization of keyboard drivers. - Window resize for character cell is added. -------------------------------------------------------------------------- Simple Interface (SI) usage Version 4 began the release the of the a/Soft (S)imple (I)nterface. Complete sources are included in the nu_tpu/source directory. You are free to make modifications and distribute those modifications to your friends and family royalty free. We would love to hear about, see, use, and/or distribute any modifications you make to the SI sources. The intent of the SI interface is to provide a smaller, faster, and less VMS dependent interface for nu/TPU customers. Instructions for extending SI are contained within the source. We hope the smaller size and modular keypad design will make the SI interface easier to enhanced than the EVE for VMS. SI interface does not support modifying the menu bar from the command line. -------------------------------------------------------------------------- nu/TPU v4.1 vs. DECTPU VMS 5.5 Differences between VMS DECTPU and nu/TPU Version 4: - Only the source files are compatible not the compiled section files. - File naming conventions are different. - nu/TPU does not support the following DECTPU builtin functions: get_info( buffer_variable, "journal_file/name" ) get_info( COMMAND_LINE, "character" ) get_info( COMMAND_LINE, "work_file" ) get_info( DEBUG, "procedure" ) get_info( SCREEN, "decwindows" ) get_info( window_variable, "key_map_list" ) set( KEYSTOKE_RECOVERY ) RECOVER_BUFFER - DECTPU does not support the following nu/TPU builtin functions: get_info( ENVIRONMENT, "" ) get_info( SCREEN, "term" ) get_info( SCREEN, "windows" ) get_info( SYSTEM, "box_range" ) get_info( widget_variable, "get_child", integer ) get_info( window_variable, "text_widget" ) set( INPUT_FOCUS, widget, integer ) CHOICE HELP_KEYPAD UNDO - DECTPU does not support the following nu/TPU concepts Status line button bar Buffer name case-sensitivity Video color display - ATTACH nu/TPU does not provide VMS functionality. - CALL_USER nu/TPU does not provide VMS functionality. - CONVERT return values differ, see documentation. - DELETE The definition of the current_buffer after deleting the current_buffer differ between DECTPU and nu/TPU. - DELETE( integer-value ) DECTPU sets variable referenced in argument one to UNSPECIFIED, nu/TPU the variable reference is unchanged. - FAO nu/TPU expresses numeric overflows as ****, DECTPU expresses them as the largest possible number to fit in the field. - FAO nu/TPU the width specifier is only valid for the fao immediately following specification. - GET_INFO(buffer,"name") VAX: Return is always uppercase. nu/TPU: Case sensitive return matches CREATE_BUFFER argument. - GET_INFO( window, "current_row" ) & GET_INFO( window, "current_column" ) VMS/TPU only updates these values during the refresh process. nu/TPU updates these values for every buffer and/or window change. nu/TPU returns zero if the window is not visible. - LOCATE_MOUSE return values differ, see documentation. - SCAN, SCANL, SPAN, SPANL: VAX allows a second directional argument REVERSE|FORWARD nu/TPU allows only the first argument. - SET( POST_KEY_PROCEDURE ) - SET( PRE_KEY_PROCEDURE ) Invalid third argument, turns off function only in DECTPU. Zero as third argument, turns off function in both. - SLEEP DECTPU allows fractional seconds, nu/TPU does not. - STR nu/TPU range value is -2,147,483,648 to +2,147,483,647. - STR(F16) & STR(DO) Under DECTPU both return "DO" Under nu/TPU both return "F16" - STR(BS_KEY) & STR(CTRL_H_KEY) Under DECTPU both return "BS_KEY" Under nu/TPU both return "CTRL_H_KEY" - DEFINE_WIDGET_CLASS No support for third parameter in nu/TPU. - Arrays and array elements can not be used as output arguments with nu/TPU. - Constants must be define before being used under nu/TPU, this restriction does not apply to DECTPU. - All statements must end with a semicolon in nu/TPU. DECTPU requires semicolons only to separate statements. - Undefined procedures cause DECTPU to step to the next statement after error handling, nu/TPU will continue with the current statement. - Error from bad argument counts to user procedures generated at run-time under DECTPU, and at compile time under nu/TPU. - Unmapping then remapping must cause a text scroll in nu/TPU. - The /nomodify command line switch does not prohibit modifing text retrived with READ_FILE later in the session under nu/TPU. - Buffers with the NO_WRITE flag set cannot be written with WRITE_FILE in nu/TPU. DECTPU only uses the NO_WRITE flag to determine writing of file at exit time. - No UIL support for builtins in nu/TPU: CREATE_WIDET SET( DRM_HIERARCHY ) SET( ICON_PIXMAP ) SET( ICONIFY_PIXMAP ) - Different time units: DECTPU uses seconds, UNIX uses milliseconds get_info( SCREEN, "time", GLOBAL_SELECT ) - DECTPU has a more extensive default global selection behavior: If no global selection routine is registered in DECTPU, it "knows" about property names "FILE_NAME", "FONT", and "LINE_NUMBER" and returns this information to asking application. nu/TPU doesn't do this to save on server memory. To get this functionality in nu/TPU, register your own global selection behavior. - HELP_MODIFIED mouse button event not supported in nu/TPU. - MARKERS and RANGES in different buffers can only be compared with the boolean operators = and <>, relative boolean operators >, >=, <, and <= return unpredictable results in nu/TPU. - SI does not provide the WPS paginate feature at the command line. - nu/TPU renames the following DECTPU keywords. EVE$_CANTCREADCL --> EVE$CANTCREASHELL EVE$_CREATESHELL --> EVE$CREATESHELL EVE$_SHELLPROMPT --> EVE$SHELLPROMPT EVE$_NODCLCMD --> EVE$NOSHELLCMD - nu/TPU adds the following keywords BACKGROUND BLACK BLUE BOL_TEXT BOX_RANGE CYAN ENVIRONMENT ESCAPE F21 - F40 FOREGROUND GREEN MAGENTA RED SIGNAL TPU$_REQUIRESWINDOWS WHITE YELLOW EXECUTE_KEY FIND_KEY FRONT_KEY HELP_KEY HOME_KEY INSERT_CHAR_KEY INSERT_KEY INSERT_LINE_KEY KP_ADD KP_COMMA KP_DIVIDE KP_ENTER KP_EQUAL KP_MINUS KP_MULTIPLY KP_PERIOD KP_SPACE KP_TAB LINEFEED_KEY MENU_KEY NEXT_EKY NUM_LOCK_KEY OPEN_KEY PASTE_KEY PAUSE_KEY PRINT_KEY PRIOR_KEY PROPS_KEY REDO_KEY REMOVE_KEY RESET_KEY RETURN_KEY SCROLL_LOCK_KEY SELECT_KEY SYSTEM_KEY UNDO_KEY USER_KEY - COMPILER differences CASE with no explicit range. VAX: 0 is OUTrange nu/TPU: 0 is INrange LSE$_*NOTDEF keywords: VAX: All generate LSE$_NOTDEFINED keyword ID nu/TPU: Generate keyword id matching name. Assignment of a constant procedure argument VAX: Generate BADDELETE error, No assignemt. nu/TPU: No error generated, Assignment made. LOCAL statement in unbounded MODULE area VAX: Allows module locals nu/TPU: Does not; use VARIABLE statement. EQUIVALENCE statements nu/TPU: Not supportted Multiple character operators: VAX: Allows intervening space(s). Example ": =" nu/TPU: Does NOT. Null variable definition. VARIABLE; VAX: Generates an error. nu/TPU: Ignores the statement. Spacing around logical operators AND OR NOT XOR VAX: 3AND1 fails to compile. "3 AND 1" is OK. nu/TPU: 3AND1 compiles and yields 1. Null statement bodies; IF, LOOP, ON_ERROR, CASE: Example Loop; VAX: Generates and error. nu/TPU: Ignores statement. Null statements in conditionals EXAMPLE %ifdef A_VALUE %then %ifdef UNDEFINED_VALUE %then exit; %endif %else COPY_TEXT( "Error" ); %endif VAX: No code generated nu/TPU: COPY_TEXT call generated when A_VALUE is undefined. -------------------------------------------------------------------------- READ_ME.SI si.ini differences from tpusec.ini SI (Simple Interface) TPU source files Differences in how SI.INI works compared to TPUSEC.INI: The SI code is much smaller and easier to modify than TPUSEC! - new method of defining attributes: The array 'si$_attributes' holds the current settings. Column three is a list of functions that will change the attributes settings. Some of these calls require a parameter. Notice that if you are running a windows version, some dialogs will also change these settings. The initial values can be changed by saving a new section file. Attribute Name: Initially: Function used to Change: ------------------------------------------------------------------- 'box_pad' OFF set box pad 'box_select' OFF set box select 'cursor_bound' ON set cursor bound 'default_command_file' "" set default command file set nodefault command file 'default_section_file' "" set default section file set nodefault section file 'exit_attributes_check' ON set exit attribute check 'find_auto_reverse' OFF set find auto reverse 'find_case_exact' OFF set find case exact 'find_cross_buffer' ON set find cross buffer 'find_whitespace' OFF set find whitespace 'find_wildcard' OFF set find wildcard 'function_keys_decwindows' OFF set function keys decwindows 'items_cross_buffer' ON set items cross buffer 'journaling' ON set journaling set nojournaling 'keypad' "si" set keypad 'paragraph_indent' 0 set paragraph indent 'pending_delete' ON set pending delete 'scroll_margin' 0 set scroll margins 'section_file_prompting' ON set section file prompting set nosection file prompting 'tab_spaces' OFF set tabs spaces set tabs insert 'tab_visible' OFF set tabs visible set tabs invisible 'undo' ON set undo 'use_clipboard' OFF set clipboard 'wildcard' "UNIX" set wildcard UNIX set wildcard VMS ------------------------------------------------------------------- - "@" command replaced by "execute file" - find works differently: Does not reverse the search if text not found in current direction. Find operation may cross buffers. - tpu show (show_option) No INFO_WINDOW exists in SI. Thus can not automatically map the show buffer to the INFO_WINDOW. To see the output from the SHOW command, follow the command with: [DO] "buffer show" The windows based version of SI display as show dialog. - RECALL works like DO. - No CHOICES window brought up if you mistype a command. - Buffer names are the whole path name. To get buffers to be only the filename, use the si command "cd" to change to that directory and "get" to get the file without the path proceeding the name. - Default cursor is BOUND instead of FREE (change with the line in an initialization file, "set cursor free"). ------------------------------------------------------------------------- SI (Simple Interface) TPU source files We started a/Soft Development and wrote nu/TPU to provide VAX/VMS users an emulation of VMS TPU for UNIX and DOS computers. One of our objectives then was to allow VAX TPU interfaces regardless of the source, to recompile and run with nu/TPU with little or no modification. After listening to the suggestions of customers and reviewing over a million lines of TPU code from customers, VMS example code, and DECUS submissions. We have designed a nu/TPU interface with the following criteria. 1. To provide a state of the art editing interface. 2. A single interface to provide both windowed and character editing. 3. Command set modeled after the EVE interface. 4. Simple code design, to facilitate end-user extentions. 5. Operating system independent. 6. Compatibility with existing nu/TPU and VAXTPU extensions. 7. Portable to VAXTPU. We believe we have met the first 5 objectives completely. Compatibility with existing nu/TPU and VAXTPU extensions is true only for extensions written to be compatible with the VAXTPU examples provided with VAX 5.4, and use either the EVE command line or procedures beginning EVE_ for customization. EVE$ and EVE$$ variables and procedures are not supported in this interface. This interface does NOT port to VAXTPU for the following reasons. 1. BOX modifier for RANGE types. 2. CHOICE builtin function. 3. Color support in video attributes. 4. HELP_KEYPAD builtin function. 5. Strings not buffers are used to restore removed lines, ranges, etc. We love suggestions(complaints). Please remember this interface was created because of user comments. -------------------------------------------------------------------------- Known bugs GENERAL problems Combining SELECTION and FIND highlighting can produce improper video highlighting. Compile errors can cause the editor to issue memory exhausted messages and die. Possible conditions are, missing then on if, missing endif, or unmatching parenthesis. SI.INI specific problems Replace doesn't apply the case of the original text to the new substitution text. SET FIND AUTO REVERSE: Should search in forward and reverse directions, but when positioned on a previous match, searches that should change direction don't. No message is displayed and cursor does not move.