
.de ec
\fR\(br\|ENTER\|\(br\h'-.02i'\l'|0\(rn'\h'-.001i'\l'|0\(ul'\|\fP\|\c
..
.de en
\fR\(br\|ENTER\|\(br\h'-.02i'\l'|0\(rn'\h'-.001i'\l'|0\(ul'\|\fP\|
..
.de bc
\fR\(br\|\\$1\|\(br\h'-.02i'\l'|0\(rn'\h'-.001i'\l'|0\(ul'\|\fP\|\c
..
.de bx
\fR\(br\|\\$1\|\(br\h'-.02i'\l'|0\(rn'\h'-.001i'\l'|0\(ul'\|\fP\|
..
.de up
\fR\(br\|\s8\(ua\s12\|\(br\h'-.02i'\l'|0\(rn'\h'-.001i'\l'|0\(ul'\|\fP\|
..
.de dn 
\fR\(br\|\s8\(da\s12\|\(br\h'-.02i'\l'|0\(rn'\h'-.001i'\l'|0\(ul'\|\fP\|
..
.de ux
\fR\(br\|\s8\(ua\s12\|\(br\h'-.02i'\l'|0\(rn'\h'-.001i'\l'|0\(ul'\|\fP\|\c
..
.de dx 
\fR\(br\|\s8\(da\s12\|\(br\h'-.02i'\l'|0\(rn'\h'-.001i'\l'|0\(ul'\|\fP\|\c
..
.sp .5i
.lg 0
.ps 18
.vs 20
.ce
LS-DOS\u\s8TM\s18\d 6.3 UPDATE FOR TRSDOS\u\s8\(rg\s18\d 6.2.X

.ps 12
.vs 12
.fi
The \fILS-DOS 6.3\fR release is an upgrade for the TRSDOS 6.2 operating system.
Several important changes have been made to extend and enhance the operating
system and its utilities.  The date ranging has been expanded to accept
dates through the year 1999.  Files will now carry a modification time
as well as a date.  The \fIDATECONV/CMD\fR program is provided to translate
version 6.2 or earlier disks to the 6.3 style dating.  The \fBuser\fR password
has been eliminated from the system.  The \fBowner\fR password still remains.
The library command \fIID\fR was added to display a customer service number.
Several enhancements have been made to \fIBASIC\fR.  The new \fIDISKCOPY/CMD\fR program
will duplicate 5" double density floppy disks.

Because
the \fILS-DOS 6.3\fR update is a series of enhancements to \fITRSDOS 6.2\fR, the
primary documentation remains the 6.2 manual and Technical Reference manual.
If you have a version of TRSDOS earlier than 6.2, you can obtain the manuals
from Radio Shack under the catalog numbers 26-0316 (\fITRSDOS Version 6\fR [6.2 DOS manual and disk]),
26-2110 (\fIModel 4/4D [6.2] Technical Reference Manual\fR), or 26-1117 (6.2 DOS manual only).
This documentation should be treated as an addendum to the TRSDOS 6.2
information.

.ps 16
.vs 18
LS-DOS 6.3 installation instructions
.ps 12
.vs 12

Before performing the upgrade,
it is recommended that you make several backup copies of the 6.3 master
disk.  The simplest way to do this is to boot your system using the 6.3 diskette, insert a
blank diskette to receive the copy in drive 1, and type the command:

        \fLDISKCOPY :0 :1\fR\c
.en

When the copy finishes, you can insert another destination diskette and make
another copy.

.ce
\fBIMPORTANT NOTE\fR

It is important that you \fIDO NOT\fR switch between version 6.3 and any earlier
version system disk in drive 0 without rebooting the computer.

To update your existing TRSDOS 6.2 disks, boot up with a fresh copy of your
new 6.3 system disk.  The 6.3 system disk should remain in drive 0 throughout the
update procedure.  There are two separate methods for updating 6.2 floppy
disks, depending on whether they are system disks or data disks.

.ps 14
.vs 16
Updating DATA disks
.ps 12
.vs 12

Place the DATA disk in drive 1 and issue the command:

        \fLDATECONV :1\fR\c
.en

This completes the conversion of the data disk.

.ps 14
.vs 16
Updating SYSTEM disks
.ps 12
.vs 12

Updating system disks may take two or three steps.  Place the 6.2 disk in
drive 1, and issue the command:

        \fLBACKUP :0 :1 (I,S,OLD)\fR\c
.en

If you wish to use the new BASIC enhancements, type the command:

        \fLBACKUP BASIC:0 :1 (I)\fR\c
.en

.sp .4i
.ce
Page 1
.bp
.sp .7i
Once the backups are completed, give the command:

        \fLDATECONV :1\fR\c
.en

This completes the updating of a system disk.  At this time, you can add
any of the new utility files you wish. 

IMPORTANT NOTE:  If you have
sysgened a configuration file, you will have to re-create it the next time
you boot the disk.

.ps 14
.vs 16
Updating HARD disks
.ps 12
.vs 12

For most hard disk installations, the following instructions can be used.
Boot up the hard disk as you normally would.  Typically your system
will have the hard disk
as drive 0, and the first floppy drive as drive 4.  Place the 6.3 disk in
drive 4, and type the following commands:

.nf
        \fLBACKUP :4 :0 (I,S)\c
.en
        DATECONV :0\fR\c
.en

.fi
Remove the 6.3 disk from drive 4, and insert your normal hard disk boot diskette. Type
the following commands:

.nf
        \fLBACKUP :0 :4 (I,S,OLD)\c
.en
        DATECONV :4\c
.en
        MEMORY (A=X'3B',B=0)\c
.en
        MEMORY (A=X'85',B=99)\c
.en
        MEMORY (A="Y",B=255)\c
.en
        SYSGEN (D=4)\fR\c
.en

.fi
Now, reboot the system and use \fIDATECONV\fR on your other 6.2 hard drive
partitions.  

IMPORTANT NOTE: If your hard drive configuration has system files sysgened
in memory, you will have to re-create the configuration file after putting the
6.3 operating system on your hard drive and on your booting floppy disk.

.ps 14
.vs 16
Reformatting hard drives
.ps 12
.vs 12

If you ever have to reformat a hard drive using the \fITRSFORM6/CMD\fR
program that comes with TRSDOS 6.2, you should use the \fIDATECONV\fR utility
after formatting is complete.  This will make sure the hard drive is
marked as being version 6.3.  Alternatively, you can apply the following
patch to \fITRSFORM6/CMD\fR that will permanently alter it to format
version 6.3 partitions.

.nf
        \fL.Patch TRSFORM6/CMD.UTILITY for 6.3 compatibility
        D04,C0=88
        F04,C0=80
        D05,01=63
        F05,01=62
        D09,2B=33
        F09,2B=32
        D0D,AA=63
        F0D,AA=62\fR

.sp 1.1i
.ce
Page 2
.bp
.sp .5i
.fi
.ps 16
.vs 18
VERSION 6.3 UPDATE INFORMATION
.ps 12
.vs 12

This section describes the changes to existing commands, and explains the
new commands and utility programs.  You can continue to use your 6.2
disks with version 6.3 as long as you update them as explained in the
installation instructions.  The following is a brief guide to version
compatibility.

USING 6.2 OR EARLIER DISKS WITH 6.3 - Disks from earlier versions of TRSDOS
should be converted with the new \fIDATECONV/CMD\fR program before being used
with 6.3.  Unconverted disks, will work, but the time and date information
will not be correct.  If a disk that was written on by 6.3 is used with an earlier
version DOS, it may appear to have an unknown user password.  If the file
was previously password protected, access may not be possible without knowing
the owner password.  To prevent this, use the \fICOPY\fR library command with the
\fB(CLONE=NO)\fR parameter when moving from version 6.3 to earlier versions.

USING 6.3 DISKS WITH EARLIER VERSIONS - This normally should not be done if
the disk is to be used again with 6.3, as the year and time information will
not be correct if the disk is written on.

USING LDOS DISKS WITH 6.3 - Files can be moved from LDOS 5.1 disks to 6.3
disks with either the \fICOPY\fR library command or with a backup by class.
When moving files from 6.3 to LDOS 5.1 disks, with the \fICOPY\fR command,
the parameter \fB(CLONE=NO)\fR should be used.  The \fIDATECONV\fR program will
not work on LDOS 5.1 disks.

.ps 14
.vs 16
Boot up changes
.ps 12
.vs 12

Since version 6.3 now stores a modification time as well as a date,  you will
be prompted for the time when booting the computer.  You can enter the hours,
minute, and seconds, or just the hours and minutes.  Pressing only \c
.bc ENTER
 for this prompt will start the time at 00:00:00.  If you wish to suppress
the time prompt, give the command \fBSYSTEM (TIME=OFF)\fR once the \fLDOS Ready\fR prompt
appears.  If you wish to reactivate the prompt after you have turned it off,
use the command \fBSYSTEM (TIME=ON)\fR.  These commands do not have to be sysgened.

.ps 14
.vs 16
Library command changes
.ps 12
.vs 12

\fBATTRIB\fR - The user password field has been removed from all files, so the \fBUSER\fR
parameter is no longer accepted.  The system now assumes a blank user password
for all files.  If a protection level has not been assigned to a file, full
access will automatically be granted regardless of any owner password.  The
owner password will still be required for full access on password protected
files that have a protection level other than \fBFULL\fR.  To have a file that
allows no access whatsoever without the use of the owner password, change the
protection level to \fBNO\fR (or \fBNONE\fR).  Although the documentation for the \fIATTRIB\fR library
command lists \fBEXEC\fR as the highest protection level, the use of \fBNO\fR is
valid and provides the highest level of protection.

\fBCOPY\fR - When copying from a 6.2 or earlier version disk to a 6.3 disk, the
old user password (if any) will be removed and the 6.3 style date/time
information field will be established, with the time being set to \fB12:00am\fR.

\fBDATE\fR - The acceptable range of dates is from January 1, 1980 to December 31,
1999.

\fBDIR\fR - The directory display now shows a \fBmod time\fR immediately following the
\fBmod date\fR for all 6.3 diskettes. The time will be in 12-hour format, with
AM or PM indicated.  Disks from earlier versions of TRSDOS will display
a blank time field.

\fBID\fR - A new library command that displays a customer service number.  This
number is installed when a master disk is manufactured, and is linked to the serial
number that displays on boot up and to other embedded numbers.  You must
have this number when calling or writing for customer service on
LS-DOS 6.3.

.ce
Page 3
.bp
.sp .7i

\fBTIME\fR - The time may now be entered with the seconds being optional.  The full syntax for the \fBTIME\fR command is:

        \fBTIME\fR [\fIHH:MM\fR[\fI:SS\fR]] [\fR(\fBCLOCK=\fR\fION\fR|\fIOFF\fR)]

.ps 14
.vs 16
Utility Program changes
.ps 12
.vs 12

\fBBACKUP\fR - When doing a backup by class from a 6.2 or earlier version disk
to a 6.3 disk, the \fBuser\fR password (if any) will be removed and the 6.3 style
date/time information will be established.  It will \fINOT\fR be permissible to
backup SYSTEM files from a 6.2 or earlier disk to a 6.3 disk during a
backup by class.

\fBDATECONV/CMD\fR - Converts pre-6.3 version data (non-system) disks to use the new
time/date format.  The syntax is:

        \fBDATECONV :\fId\fR

There are no parameters for this program.  If conversion of a 
SYSTEM disk is attempted, an appropriate error message will be
displayed.  To convert this type of disk, you must first use \fIBACKUP\fR to move
6.3 system files onto it before using \fIDATECONV\fR.  For example,

        \fBBACKUP :\fIs\fB :\fId\fB (S,I,OLD)\fR

Data disks from versions earlier than 6.3 will be converted in all cases and
marked as a 6.3 type disk.

Conversion of LDOS 5.1 formatted disks is not allowed.  Although these
disks can be read and written to, the time and year will not be updated
on modified files.  Files should be copied or backed-up onto 6.3 formatted
disks.

\fIDATECONV\fR does not normally need to be used on a 6.3 disk, since the \fICOPY\fR and
\fIBACKUP\fR commands automatically adjust the time/date storage when moving
from LDOS or TRSDOS 6.x to 6.3.  For this reason you should \fINEVER\fR move files
to a 6.3 disk when booted up under any earlier version.  If you do use
\fIDATECONV\fR on a 6.3 disk, only those files that have an old style blank
user password will be changed.  This is to protect the time stamp on
proper 6.3 files.

\fBDISKCOPY/CMD\fR - Performs a single-pass format and copy of a 5" double density
floppy disk.  It will duplicate both single and double sided disks.
Attempting to copy other types of disks will
abort the program with an appropriate error message.
The syntax is:

        \fBDISKCOPY :\fIs\fB :\fId\fR

The \fI:s\fR and \fI:d\fR are the \fIsource\fR and \fIdestination\fR drive numbers, respectively,
and cannot be the same drive.  After starting \fIDISKCOPY\fR, you will be prompted
to insert the source and destination disks. 

After the copy is complete, you will be prompted to do another copy.  If you
wish to copy another disk, press the \c
.bc Y
 key.  You can change both the source
and destination disks at this point if you desire.  Pressing \c
.bc N
 will exit
back to \fLDOS Ready\fR.

If an error is encountered during the copy, 
the program will display the error and return to \fLDOS Ready\fR.

.sp .8i
.ce
Page 4
.bp
.sp .5i
.ps 16
.vs 18
TED - ASCII Text Editor
.ps 12
.vs 12

The Text EDitor (TED) is a full screen "quick" text editor with typical
word-processing type features (four-directional) cursor movement; 
bi-directional scrolling; text directional delete; large text buffer; etc);
however, TED was not designed to be a full featured word processor.  TED
was designed for you to be able to rapidly enter a full-screen text editing
environment while accomplishing many of your text file editing tasks.

Summary of editing commands

The following are the command keys and their functions as used in TED.
Once you become familiar with the operation of TED, this section may be
all you need to refer to from to time to time to jog your memory.

.nf
.vs 13
        Action                                                  Key Entry
        ---------------------------------------------           -----------------------
        Move the cursor one position left                       \c
.bc \(<-
 or \c
.bc CTRL
.bx H
        Move the cursor one position right                      \c
.bc \(->
 or \c
.bc CTRL
.bx I
        Move the cursor one position down                       \c
.dx
 or \c
.bc CTRL
.bx J
        Move the cursor one position up                 \c
.ux
 or \c
.bc CTRL
.bx K
        Move the cursor to the beginning of the line    \c
.bc SHIFT
.bx \(<-
        Move the cursor to the end of the line          \c
.bc SHIFT
.bx \(->
        Move the cursor to the end of the text          \c
.bc SHIFT
.dn
        Move the cursor to the beginning of the text    \c
.bc SHIFT
.up
        Toggle overstrike/insert modes                  \c
.bc CTRL
.bx A
        Specify a BLOCK...                                      \c
.bc CTRL
.bx B
        Specify DELETE                                  \c
.bc CTRL
.bx D
        FILE the text buffer to disk                            \c
.bc CTRL
.bx F
        Go find the next search string match            \c
.bc CTRL
.bx G
        LOAD a text file into the buffer                        \c
.bc CTRL
.bx L
        Command confirmation or advance to next line    \c
.bc ENTER
 or \c
.bc CTRL
.bx M
        Go to the NEXT video page                               \c
.bc CTRL
.bx N
        REPLACE searched string with new string         \c
.bc CTRL
.bx R
        SEARCH for a string                                     \c
.bc CTRL
.bx S
        Go UP to the previous video page                        \c
.bc CTRL
.bx U
        EXIT the text editor                                    \c
.bc CLEAR
.bc SHIFT
.bx =
.fi

.ps 14
.vs 16
Invoking TED
.ps 12
.vs 12

TED is invoked via the command:

        \fLTED\fR

TED will display a welcome message on the bottom line of the display.
This line will also be used for the display of status, prompting,
and error messages.  TED displays three different types of messages during
its operation.  Error messages are indicated by a trailing exclamation
point, \fL!\fR.  Queries which need a response are indicated by a trailing
question mark, \fL?\fR.  All other messages are informative messages.
Thus, \fLMarker!\fR is an error, \fLString?\fR is a query,
and \fLBlock\fR is informative.

.sp 1.5i
.ce
Page 5
.bp
.sp .5i
.ps 14
.vs 16
Text entry modes
.ps 12
.vs 12

TED will accept only displayable ASCII characters in the range 20H through
7FH for text entry.  Any other character will be interpreted as a
command entry.  

TED operates in two text entry modes: overstrike and insert.  The initial
mode established when TED is first invoked is the "overstrike" mode.  While
TED is in "overstrike" mode, it will use an underscore as the cursor
character.  When you toggle to "insert" mode, the cursor is changed to a
full graphics block.  You toggle from one mode to the other via the \c
.bc CTRL
.bc A
 command.

When TED is in "overstrike" mode, any acceptable character that is typed
is written over the character which appears under the blinking cursor.
You can overstrike a newline character (i.e. \c
.bc ENTER
, which is displayed as
small graphics block).  You can also overstrike either a "begin" block
marker or an "end" block marker.  You can be in overstrike mode when you
come to the end of the text (or starting from an empty text buffer, for
that matter) and still be able to enter text in this mode.

When you switch to "insert" mode, anytime you enter acceptable text,
the existing text will be pushed down one position starting
from the character under the cursor to make room for the inserted
character.  The display will be constantly updated as text is inserted.

The text entry mode is only changed via the \c
.bc CTRL
.bc A
 command.  Going into
"delete" mode does not change the mode of text entry.

.ps 14
.vs 16
Loading a text file
.ps 12
.vs 12

The \c
.bc CTRL
.bc L
 command is used to load a text file into TED.
When you enter \c
.bc CTRL
.bc L
, you will be prompted for the name of the file. 
If the extension is omitted from your entry, "/TXT"
will be automatically provided.

The LOAD command will not automatically clear any text remaining in the text
buffer prior to the LOAD.  The new text is not inserted at the cursor
position but rather is appended to the end of the current text.  If you wish
to load the new file over the old text, simply invoke the command sequence,
.bc SHIFT
.ux
 followed by \c
.bc CTRL
.bc D
  then \c
.bc SHIFT
.dx
\&.  This will delete the entire text buffer.

If the file is too large to fit into the available text buffer, the error
message \fLNo room!\fR will be displayed and no text will be loaded.  If any disk
read error is encountered while reading the text file into the text buffer,
the message \fLI/O error!\fR will be displayed.  The text which was loaded up
to the point of encountered the error will be retained in the text buffer.

.sp 3.2i
.ce
Page 6
.bp
.sp .5i
.ps 14
.vs 16
Entering text
.ps 12
.vs 12

Entering text is easy, you just type away.  If you already have text in the
buffer and wish to enter new text at the end of the document, just move the cursor to 
the bottom (via the \c
.bc SHIFT
.dx
 key),  then type in your text.  If
you wish to enter text at some other point, just position the cursor,
toggle to the \fIinsert\fR mode, then type away.  TED will stay in \fIinsert\fR
mode until explicitly toggled back to \fIoverstrike\fR mode.

As you are entering text, any word which is too long to fit at the end of
a video line will be split at the 80th column and continued onto the next
line.  These long words are not automatically moved onto the next
line, as is the case with the typical word processor.

.ps 14
.vs 16
Cursor positioning manipulations
.ps 12
.vs 12

The ARROW keys are the primary tools to move the cursor.  They will move the
cursor in the direction indicated by the arrow.  The shifted keys will be
interpreted as cursor movement commands unless TED is in the DELETE or
BLOCK modes.

The \c
.bc SHIFT
.bc \(<-
 command will move the cursor to the first column of
the current line.  The \c
.bc SHIFT
.bc \(->
 command will move the cursor to
the last character of the current line.  You can position the cursor to the
first character of the text buffer by using \c
.bc SHIFT
.ux
\&.  Finally, \c
.bc SHIFT
.dx
 positions to the end of text.

The page up, \c
.bc CTRL
.bc U
, command will redraw the video screen so that the 
first displayed line is twenty one lines previous to the current first
displayed line.  The page next command, \c
.bc CTRL
.bc N
, will redraw the video screen
so that the first line displayed is the last line of the current
displayed text.  If the video display has fewer than 22 lines of text
displayed, the page next request will be ignored.

.ps 14
.vs 16
Text deletion
.ps 12
.vs 12

TED provides five forms of text deletion in addition to the block deletion
discussed later.  To delete the single character which appears under the
cursor, invoke the delete command via \c
.bc CTRL
.bc D
\&.  This action will get rid of
the character and all text which follows that character will be pulled
back one position.  The \c
.bc CTRL
.bc D
 command also puts you into DELETE mode which
is made apparent by the display of the word \fLDelete\fR in the status line.
The DELETE mode is active for only the next keyboard entry.  There are
only four subcommands associated with the DELETE mode: delete to
beginning of line (bol), delete to end of line (eol), delete to top, and
delete to bottom.  TED will always prompt before performing one of these
operations.

.nf
        Deletion desired        Command sequence
        ----------------------  -------------------------------------
        delete to bol           \c
.bc CTRL
.bc D
 then \c
.bc SHIFT
.bx \(<-
        delete to eol           \c
.bc CTRL
.bc D
 then \c
.bc SHIFT
.bx \(->
        delete to top           \c
.bc CTRL
.bc D
 then \c
.bc SHIFT
.up
        delete to bottom        \c
.bc CTRL
.bc D
 then \c
.bc SHIFT
.dn
.fi

After typing \c
.bc CTRL
.bc D
, the character now under the cursor is the
character which was to the right of the deleted character.  Since in
the case of delete to bol and delete to top, you are deleting text which is
in front of the cursor, you really don't want to delete the character
which is under the cursor after the \c
.bc CTRL
.bc D
\&.  Well, you don't have to worry
about that because those two subcommands properly back up one position
before continuing the deletion.

.sp 1.2i
.ce
Page 7
.bp
.sp .5i
.ps 14
.vs 16
Block operations
.ps 12
.vs 12

The BLOCK command, \c
.bc CTRL
.bc B
, has five subcommands: Begin, End, Copy, Delete,
and Move,  These subcommands are specified by entering the first letter
of the subcommand word (\c
.bc B
, \c
.bc E
, \c
.bc C
, \c
.bc D
, or \c
.bc M
).  The letter may be in
either upper or lower case.  Note that these subcommands are NOT control
key combinations but normal alphabetic single-key entries.  When you
invoke the BLOCK command, the word \fLBlock\fR will be displayed in the status
line.

Any time you need to deal with a block; say to copy it, move it, or delete it,
you have to first mark it.  The beginning and ending positions of a block are
marked by first positioning the cursor over the first character of the block
and then entering the two command sequence, \c
.bc CTRL
.bc B
 followed by \c
.bc B
\&.  This is
followed up be positioning the cursor over the character immediately
following the last character of the block and then entering the 
sequence, \c
.bc CTRL
.bc B
 followed by \c
.bc E
\&.  The beginning positioning will be indicated
on the display by a "begin" marker which is inserted by TED into the text.
The marker is displayed as a graphic left bracket.  The ending position will
be indicated on the display by an "end" marker which is also inserted by TED
into the text.  The marker is displayed as a graphic right bracket.  These
markers occupy ordinary text positions; thus they may be deleted or
overstriked.  Any remaining in the text buffer at the time a FILE command
is performed will be written to the disk file just as if they were ordinary
text characters.

Although you can mark as many blocks as your heart desires, TED provides no
way to differentiate between marked blocks in other than the BLOCK-DELETE
function.  For copying and moving blocks, the first block marked in the text
is the one chosen for copying or moving.  On the other hand, a
BLOCK-DELETE request requires that the cursor be positioned within the
interior of the marked block which is to be deleted.

To COPY the first marked block in the text to some other position, simply
mark the beginning and end of the block as discussed above, move the cursor
to the position in the text where you want the marked block copied into,
then invoke the block copy command via the sequence, \c
.bc CTRL
.bc B
 followed by \c
.bc C
\&.
Note that the block which will be copied is the first marked block found
in the text buffer,  A few things could go wrong with your request.  If TED
can find no properly marked block, it will display the error message
\fLMarker!\fR and terminate the block mode.  Another error which could occur
is when the position you wish the block copied into happens to be in the
interior of the block itself!  Such a block copy can not occur.  You will
be informed of this by a display of the error message \fLCursor!\fR.

The successful block copy operation only copies the marked text; the markers
are not copied as well.  If fact, the marked text remains in its original
position relative to the text which surrounds it.  The cursor position
relative to the text will be unchanged after the block is copied; however,
the screen may be redrawn and the physical location of the cursor on the
screen may be different.

A block of text may be MOVED from one position to another by a command
sequence similar to the block copy.  In this case, simply mark the
beginning and end of the block as discussed above, move the cursor to
the position in the text where you want the marked block moved to, then
invoke the block MOVE command via the sequence, \c
.bc CTRL
.bc B
 followed by \c
.bc M
\&.
Again note that the block which will be moved is the first marked block
found in the text buffer.  This operation is essentially one of copying
and automatic deleting without the double check prompt.  As in the case
of the BLOCK-COPY, the same errors are possible with similar diagnostic
messages when things are not as they should be.  With the BLOCK-MOVE
command, the new cursor position will be the new position of the moved
block.  The screen may be redrawn and the physical cursor position
altered to accommodate this request.

.sp 1i
.ce
Page 8
.bp
.sp .5i


This last block operation is deletion.  Similar to the above functions,
you first must mark the block's beginning and ending positions.  You
must then position the cursor to the interior of the marked block and
invoke the command with the sequence, \c
.bc CTRL
.bc B
 followed by \c
.bc D
\&. As a
safety check, TED will prompt you before deleting the block.  It is 
necessary to depress \c
.bc ENTER
 to affirm your intentions.  Any other
character entry (including a \c
.bc Y
) will cause TED to ignore the block
delete request.

The same errors as for copy and move can occur; however, the messages may not
be for the same reasons.  When a block delete is required, TED will first look
for an ending block marker starting from the cursor position.  If none is
found, the error displayed will be \fLMarker!\fR.  This doesn't mean
necessarily that a properly marked block is missing.  On the other hand,
if an ending marker is found past the cursor position, TED next scans
forward for a beginning block marker.  A \fLMarker!\fR error will also be posted
if none is found.  If a marker is found but is also past the cursor position,
a \fLCursor!\fR error will be posted.

.ps 14
.vs 16
Filing away your text to a disk file
.ps 12
.vs 12

The \c
.bc CTRL
.bc F
 command is used to save the contents of the text buffer area into a
disk file.  When you depress \c
.bc CTRL
.bc F
, you will be prompted for the name of the
file.  If the file specification you wish to use has an extension of "/TXT",
you do not have to enter the extension.  If the extension is omitted from
your entry, "/TXT" will be automatically provided.

The FILE command will save the entire text buffer, excluding the terminating
NULL but including any block markers, into the disk file identified by your
input.  If any disk write error is encountered while saving the text buffer
into the disk file, the message \fLI/O error!\fR will be displayed.  In any case,
the text buffer is left undisturbed.

.ps 14
.vs 16
Text search
.ps 12
.vs 12

TED provides the SEARCH command to scan the text buffer for a specified string
of characters.  You specify the search by invoking the command with \c
.bc CTRL
.bc S
\&.
TED then prompts you for the search string with the query message \fLString?\fR.

You can enter up to 23 characters to be used for the search string.  Terminate
your search string with an \c
.bc ENTER
 (the \c
.bc ENTER
 character code is not
included as one of the 23 characters).  TED will then look for the string
starting with the first character immediately following the cursor.  The
matching is case sensitive which means that characters entered in upper case
must be found in upper case and characters entered in lower case must be
found in lower case.  If the search string cannot be found, the message
\fLCan't!\fR will be displayed.  At this point, the cursor location remains
unchanged.  If, on the other hand, a matching string of text is found
in the text buffer, it will be displayed.  The display window will be redrawn
starting with the line which contains that string.  The cursor will be
positioned to the first character of the matching string.

If you press \c
.bc ENTER
 only in response to the \fLString?\fR query, then the
search will proceed with the last entered search string, provided one was
available.  Using this procedure, you can advance the cursor to each
occurrence of the search strings in question.

Another way to find each occurrence of a string is with the GO command,
.bc CTRL
.bc G
\&.  Each depression of \c
.bc CTRL
.bc G
 is identical to the sequence, \c
.bc CTRL
.bc S
 followed by \c
.bc ENTER
\&.

.sp 1.3i
.ce
Page 9
.bp
.sp .5i
.ps 14
.vs 16
Text search and replace
.ps 12
.vs 12

TED also provides the capability of replacing a text string matching a
search string with a different string - the replacement string.
When the REPLACE command is invoked via \c
.bc CTRL
.bc R
, the query message \fLString?\fR
will be displayed.  Although the message is the same as for SEARCH, this
query is asking you for the replacement character string.  You can enter
up to 23 characters to be used for the replacement string.  Terminate your
string with an \c
.bc ENTER
 (the \c
.bc ENTER
 character code is not included as one
of the 23 characters).  TED will then look for the currently pending SEARCH
string starting with the first character IMMEDIATELY under the cursor.
If the SEARCH string cannot be found, the message \fLCan't!\fR will
be displayed.  At this point, the cursor location remains unchanged.
If, on the other hand, a matching string of text is found in the text
buffer, it will be replaced with the REPLACE string.  The display window
will be redrawn starting with the line which contained the string
which was replaced.  The cursor will be repositioned to the first character
immediately following the replacement string.

If you wish to replace the next occurrence of text which matches up with the
SEARCH string with that same REPLACEMENT string, all you need do is enter
.bc CTRL
.bc R
 and 
.bc ENTER
\&.

The GO command, \c
.bc CTRL
.bc G
, still functions to find the next occurrence of
the SEARCH string.  Knowing this, if the next occurrnce of the search string
is beyond the text currently displayed on the screen and you wish to
confirm its replacement, simply GO to the next occurrence
then REPLACE, as necessary.

.ps 14
.vs 16
Printing text
.ps 12
.vs 12

TED provides no facility for printing your text file.  The most reasonable
way of accommodating that function is with the LIST command provided
as part of your DOS.

.ps 14
.vs 16
Exiting from TED
.ps 12
.vs 12

It is easy to exit TED and return to DOS Ready.  The \c
.bc CLEAR
.bc SHIFT
.bc =
 command
tells TED you wish to exit.  If the text buffer is empty, TED will
immediately terminate.  However, if there is any text in the buffer, you
are provided an opportunity to retract your request.  TED will display
the prompt message,

        \fLPress ENTER to exit\fR

.ps 14
.vs 16
Text recovery
.ps 12
.vs 12

There may be times when you exit the TED application inadvertantly without
saving the edited text to a disk file.  TED 
permits you to re-enter with the asterisk parameter which
provides a chance to recover you text.
Instead of automatically clearing the text buffer as \fBTED\fR does,
\fBTED *\fR will display whatever is in the text buffer memory area.  Thus,
if you have not altered any of the information in that memory area, you can
always go back and recapture it.

Caution:  Since all of the text pointers normally established
by TED will not be initialized when invoking TED via the \fB*\fR parameter, it will be
necessary to scroll through the text until reaching its last character
prior to doing any other operation.  This may also be performed using
NEXT PAGE.

.sp 1.7i
.ce
Page 10
.bp
.sp .5i

.ps 18
.vs 20
Changes and Additions to BASIC
.ps 12
.vs 12

The changes and additions to BASIC involve a new parameter for the renumber
command, the addition of several "immediate action" keys, single letter
abbreviations, high speed load and save, and an interface to DOS SVCs.

The RENUM statement now allows for a fourth line number to be used.  If used,
it will be the last line of the program to be renumbered.  For example:

        RENUM 1000,500,10,600\fR

This will renumber the lines between 500 and 600 only, making new line numbers
starting at 1000 with an increment of 10.  All other restrictions of the
current renumber command still apply.  For moving blocks of lines in a
program, see the \fBC\fR and \fBM\fR commands describing below.

There are 6 "immediate" keys that will function when pressed as the first
character of a line.  The up and down arrows list the previous and next line
of a program, respectively.  The left arrow lists the first program line, and
the right arrow lists the last program line.  The period lists the current
line, and the comma enters the edit mode for the current line.

Several single letter commands have been added to BASIC.  Four of these are
abbreviations for existing commands.

.nf
        \fBA \fR-\fB AUTO
        D \fR-\fB DELETE
        E \^\fR-\fB EDIT
        L \fR-\fB LIST\fR
.fi

These commands work exactly as their full length counterparts, except that
no space is necessary between the letter and the line numbers.  For example,
"L100-300" is the same as "LIST 100-300".

The following four commands are contained in the BASIC/OV2 file.  This file
must be present when using one these commands, or a \fLFile not found\fR error
will occur.  Like other BASIC editing commands, the use of these will clear
all variable values and close any open files.

.nf
        \fBC\fR\| - Copy a single line
        \fBF\fR\|\| - Find all references to a line, variable or keyword
        \fBM\fR - Move a block of lines
        \fBS\fR\|\| - Search and display a reference to a line, variable, or keyword.
.fi

The Copy command syntax is:     \fBC \fINum1,Num2\fR

\fINum1\fR is an existing line number to be copied.  \fINum2\fR is the line number to
create, and must NOT already exist.  No renumbering will be done after
the copy.  If the line numbers are incorrect, an \fLIllegal function call\fR error
will occur.

The Find command syntax is:     \fBF \fIObject\fR

\fIObject\fR is either a line number, variable, or keyword.  The space after
the F is mandatory when finding keywords.  The resulting display will be
all line numbers containing the referenced object.  When finding variables,
only the first 10 characters of the variable name will be significant.  Also,
type declarations !,%,#,$,( must be used.  For example, the command "F A"
would not find A$ or A().

.sp .6i
.ce
Page 11
.bp
.sp .5i


The Move command syntax is:     \fBM \fINum1,Num2,Num3\fR

\fINum1\fR and \fINum2\fR are existing line numbers and define the block of lines to be
moved.  \fINum2\fR must be greater or equal to \fINum1\fR.  \fINum3\fR is an existing line
number and is the line to insert the moved block after.  The moved block of
lines will be renumbered by one, and all references to these lines (if any)
will be corrected.  If there is not enought room in memory to move the lines,
an \fLout of memory\fR error will occur.  If this happens, do multiple moves
of smaller pieces.  If the line numbers are non-existant or if there is
not enough room between Num3 and its following line to fit the block, an
\fLIllegal function call\fR error will occur.  For example, if you had program
lines 100 and 110, a block of lines moved after line 100 could be no more
than 9 lines long.

The Search command syntax is:   \fBS \fIObject\fR  or  \fBS\fR

\fIObject\fR is a line number, variable or keyword.  The first line containing
the object will be displayed.  The space after the S is mandatory when
searching for keywords.  The S with no object following will search for the
next occurrence of the previous object.  Like the Find command, variables
are limited to 10 significant characters, and any explicit type definitions
must be used.

.ps 14
.vs 16
High speed Load and Save
.ps 12
.vs 12

When using the normal SAVE or LOAD program commands, execution should be two
to three times faster then before.  Programs saved with the ASCII
parameter will not enjoy this speed increase, either when saving or when
loading.

.ps 14
.vs 16
New user interface to SVC's
.ps 12
.vs 12

A user interface to the DOS SVC functions is now provided via the USR
statement in BASIC.  To use this interface, establish an INTEGER array with
the first 6 elements containing the following information that may be
needed by the SVC:

.nf
        Element 0:      SVC number (Always needed!)
        Element 1:      Value for register pair HL
        Element 2:      Value for register pair DE
        Element 3:      Value for register pair BC
        Element 4:      Value for register pair IY
        Element 5:      Value for register pair IX
.fi

The interface is accomplished by using a normally out of range USR
argument, USR11.  To execute the SVC, use the syntax USR11(VARPTR(ARRAY(0))).
No DEF USR statement is required.  After the SVC executes, the register
pairs will be unloaded back into the array.  The AF register pair will be
placed in array position 0.  If the array is not an integer type, or if
the SVC number is either zero or greater than 127, an \fLIllegal function
call\fR error will occur.

The return condition of the SVC can be tested by checking the bits in
ARRAY(0).  Doing an "AND 64" will produce a non-zero value if the Z flag
is set.  Doing an "AND 1" will produce a non-zero value if the Carry Flag
is set.  For further explanation of DOS SVC usage and returned values,
refer to the \fITRSDOS 6.2 Technical Reference Manual.\fR  The following is a short
example of using the SVC interface.

.sp 1.2i
.ce
Page 12
 