;known problems: ; ; Both known problems are VT100 related, and are VERY rare. ; The first happens to me every 2 or 3 weeks (and I do a lot ; of editing), while the second has happened to me only 2 or ; 3 times. ; ; ; 1. Occasionally, the scrolling down stops working. This ; is a VT100 internal problem and is reset by a VT100 ; hard reset (Setup 0) ; ; ; 2. As above, sometimes the alternate character set does ; not work. This will be evident when form feeds print ; as lower case 'c's and the keypad display from GOLD ; H fails to print in the alternate set (solid lines). ; The problem is the VT100, and fixed as noted above. ; The GOLD Q command, used to spool a select range ; or the current page if there is no active range, ; defaults to LP0 for ppn < (8,*) and to LP2 for ; everybody else. The example shown patches the ; unit for bot h to LP1 and changes the ppn limit ; to 255 (which will treat everyone the same). File to patch? X.RTS Base address? Q.NOPR Offset address? -1 Base Offset Old New? 126571 177777 000 ? 126571 000000 002 ? 1 126571 000001 000 ? ^Z Offset address? ^Z Base address? Q.PRIV Offset address? -1 Base Offset Old New? 126572 177777 001 ? 126572 000000 000 ? 1 126572 000001 010 ? ^Z Offset address? ^Z Base address? Q.PPN Offset address? -1 Base Offset Old New? 126573 177777 001 ? 126573 000000 010 ? 255. 126573 000001 010 ? ^Z Offset address? ^Z Base address? ^Z File to patch? ^Z ; The default fill (for /WRAP and the CENTER,PARA and FILL ; commands is 72. The following patch shows changing it to ; 66. File to patch? X.RTS Base address? SCDFIL Offset address? 0 Base Offset Old New? 126650 000000 000110 ? 66. 126650 000002 154204 ? ^Z Offset address? ^Z Base address? ^Z File to patch? ^Z ; patch removed 04-jan-81 ; ; skip this patch ; The command SCOPE and VTEDIT use slightly different keypad ; layouts. The preferred command is VTedit, to take advantage ; of the new keypad layout. The following patch changes the ; 'SCOPE' command to be the same as the VTEDIT command. ; The old keypad layout was kept only for a transition and ; will eventually go away. File to patch? X.RTS Base address? EDSCOP Offset address? 0 Base Offset Old New? 127532 000000 042767 ? 127532 000002 000020 ? 127532 000004 050766 ? 127532 000006 000403 ? 240 127532 000010 052767 ? ^Z Offset address? ^Z Base address? ^Z File to patch? ^Z ; Version 7.1 of RSTS has a new feature knowm as multiple ; private delimiters. While TED is smart enough to know ; if you either are runnning 7.0 still or chose not to ; include this useful feature during SYSGEN (you really ; should have if not), the FT2 field test release has a ; bug in this feature. The bug is that the RSTFQ function ; of CALFIP, which all RTS's give at entry to reset various ; things like files still open, does not clear the bitmask ; for this feature. While TED always clears it on a normal ; exit, it is possible to exit TED (control C on a file of ; five lines or less) and NOT get the mask cleared, leaving ; the terminal unusable. ; This bug in RSTS is supposed to be fixed by the final re- ; lease of 7.1 File to patch? X.RTS Base address? SETDLM Offset address? 0 Base Offset Old New? 155626 000000 000240 ? 207 155626 000002 012700 ? ^Z Offset address? ^Z Base address? ^Z File to patch? ^Z ! patch the default scope type. The example shows ! changing the default of VT100 to VT52. File to patch? X.RTS Base address? VTDFL Offset address? 0 Base Offset Old New? 163756 000000 000006 ? VT52 163756 000002 005067 ? ^Z Offset address? 0 Base Offset Old New? 163756 000000 000010 ? ^Z Offset address? ^Z Base address? ^Z File to patch? ^Z ********************************************************************* ! ! patch the terminal read modifier. ! ! This patch is not needed for v7.0 of RSTS, but may be needed ! in future releases of RSTS. Normal KB: reading uses a special ! 'RSX' mode read modifier, which could change in the future. ! This patch simply removes it and uses the usual 'record 0'. File to patch? X.RTS Base address? ..KBMD Offset address? 0 Base Offset Old New? 111306 000000 001000 ? 0 111306 000002 067144 ? ^Z Offset address? ^Z Base address? ^Z File to patch? ^Z ********************************************************************* ! patch terminal timeout waits for error message printing ! when a scope type is set, and patch the help continuation ! timeout value. ! ! @..HMTO = help timeout in seconds (30) ! @..ETMO = error printing timeout in seconds (5) ! ! The example changes the help timeout to 60 seconds and ! the error timeout to 10 seconds. File to patch? X.RTS Base address? ..HTMO Offset address? 0 Base Offset Old New? 132642 000000 000036 ? 60. 132642 000002 000404 ? ^Z Offset address? ^Z Base address? ..ETMO Offset address? 0 Base Offset Old New? 132654 000000 000005 ? 10 132654 000002 162706 ? ^Z Offset address? ^Z Base address? ^Z File to patch? ^Z ********************************************************************* ! patch the teco mode line reading module to assume the ! use of teco mode reads if no scope type has currently ! been set. This will also assume that the vt terminal ! default @ vtdfl is correct for your environment. By ! installing this patch, some commands which use the ! teco read mode will also then have to use the default ! line erase escape sequences, which are set by patch- ! global vtdfl. You should NOT put this patch in unless ! all you scope terminals are the same type, all vt100s ! or all vt52s. Teco mode will be ignored if the scope ! bit in the kbddb was not set (SET NO SCOPE). File to patch? X.RTS Base address? ..TECR Offset address? 0 Base Offset Old New? 165276 000000 001421 ? 240 165276 000002 105767 ? ^Z Offset address? ^Z Base address? ^Z File to patch? ^Z ********************************************************************* ! patch the default scope command bits. The normal default ! is '.KED' , which means to use the keypad in special ! keypad application mode. If you patch this, you should ! always include '.KED', as the following example does. ! ! defaults that can be set: ! ! symbol purpose ! ! .LIN enable line numbers (assumed unless .NOLIN) ! .NOLIN do not print line numbers scope editor. ! .VT52 assume a vt52 for the default (overrides VTFDL) ! .VT100 assume vt100 for the default (overrides VTDFL) ! .NOLC disables lc input (also messes up the keypad) ! .PDEL changes the way rubout key works ! .PRI causes immediate eof after typing a delimiter ! ! the example sets '.KED', '.NOLIN' and '.PDEL' File to patch? X.RTS Base address? ..SCDF Offset address? 0 Base Offset Old New? 142604 000000 000200 ? .KED!.NOLIN!.PDEL 142604 000002 000040 ? ^Z Offset address? ^Z Base address? ^Z File to patch? ^Z ********************************************************************* ! Patch the character that the VT52 sends out upon ! receiving ESCAPE Z (identify). This is used to be ! able to tell if the terminal is a VT52 in case the ! default of VT100 is enabled (default) so the scope ! command will not mess up a vt52 by mistake. ! ! You should not change this unless you have a vt52 ! lookalike that sends something different. Note that ! the current setting works for both VT52's and H19's File to patch? X.RTS Base address? VT52CH Offset address? 0 Base Offset Old New? 156532 000000 000113 ? ^Z Offset address? ^Z Base address? ^Z File to patch? ^Z ********************************************************************* ! patch TED startup defaults. You should not change this ! but you can if need be. The most important one to look ! at is the 'DF$32' bit as this, when set, tells TED to ! create it's temp file with a large clustersize which ! on small systems (RK05,RK06 types) may be undersirable ! as small disks may not have enough free disk clusters ! of large size. ! The other useful bit if DF$TMP. This, when set, causes ! the temp file to be created at the logical name EDRT: ! which you can point to a private pack at a specific ! ppn. Using this requires temporary privs. It is the ! default. ! You can also set DF$BAK bit to ALWAYS rename the input ! file to a .BAK extension (filetype????). File to patch? X.RTS Base address? $FLAGS Offset address? 0 Base Offset Old New? 171070 000000 000107 ? DF$TMP!DF$32!DF$CRE 171070 000002 046130 ? ^Z Offset address? ^Z Base address? ^Z File to patch? ^Z ********************************************************************* ! patch the 'jump to scope mode' check. ! If TED (edrt) is entered at line 2 (i.e., @#firqb+fqent=2) ! the first command is automatically 'SCOPE'. At U of Toledo ! we do this: ! ! UT CCL TED=EDRT:EDIT.EDI;PRIV 1 ! UT CCL SED=EDRT:EDIT.EDI;PRIV 2 ! ! there is really no reason to patch this unless you are ! worried about some user bypassing things and getting ! into trouble. File to patch? X.RTS Base address? ..DOSC Offset address? 0 Base Offset Old New? 176324 000000 000001 ? 0 176324 000002 002045 ? ^Z Offset address? ^Z Base address? ^Z File to patch? ^Z ********************************************************************* ! The '$' and '$systemccl' commands spawn and create a job ! on a PK. This is very useful for system hackers as you ! can be editing along and pop out for a moment to run PIP ! or do a systat or whatever, and then come back in without ! affecting your editing. The command does check the user's ! ppn first though, and does an 'ERROR T.ILLCMD' if the ppn ! is out of range. The default range is: ! ! execute '$' if userpriv or (ppn<8) or (ppn>159) ! ! the lower value is patchable @ ..pklo, and the other one ! is patchable @ ..pkhi. If you want ONLY (1,*) to be able ! to use this, patch as follows: File to patch? X.RTS Base address? ..PKLO Offset address? 0 Base Offset Old New? 136720 000000 000007 ? 1 136720 000002 101406 ? ^Z Offset address? ^Z Base address? ..PKHI Offset address? 0 Base Offset Old New? 136730 000000 000240 ? 377 136730 000002 103002 ? ^Z Offset address? ^Z Base address? ^Z File to patch? ^Z ********************************************************************* ! when a scope mode is active each command (outside of the ! scope edit mode 'scope cmd') will cause a reprint of the ! top line on a vt100. This may be undesirable and can be ! eliminated by the following patch. What the patch does ! is change the call to TM$OUT to CLRB @#TMO ! Note that offset 2 from ..ctmo may change as it is only ! a relative offset address. File to patch? X.RTS Base address? ..CTMO Offset address? 0 Base Offset Old New? 165036 000000 004767 ? 105037 165036 000002 000720 ? ..TMOA 165036 000004 000207 ? ^Z Offset address? 0 Base Offset Old New? 165036 000000 105037 ? 165036 000002 000370 ? ^Z Offset address? ^Z Base address? ^Z File to patch? ^Z ******************************************************************** ! wildcard directory lookup is currently limited to ! accounts with programmer number < 127. To remove ! this restriction, patch global STDUIC offset 0 to ! 377 from 200. File to patch? X.RTS Base address? STDUIC Offset address? -1 Base Offset Old New? 172472 177777 000 ? 172472 000000 200 ? 377 172472 000001 000 ? ^Z Offset address? ^Z Base address? ^Z File to patch? ^Z