Editing TRSDOS (section)

==Features and capabilities==
RadioShack's Z80-based line of TRS-80 computers ([[TRS-80|Models I/III]] and [[TRS-80 Model 4|Model 4]]) support up to four physical floppy (mini-diskette) drives which (as sold) use [[Floppy disk|5¼-inch diskettes]]. The original TRSDOS for the Model I supported only single-sided disks with 35 [[Track (disk drive)|tracks]] formatted in single density ([[disk sector|sectors]] are encoded using the [[frequency modulation]] technique). Model III TRSDOS (culminating in version 1.3) supported 40-track disks formatted in double density (using [[modified frequency modulation]]). Model Is retrofitted with double density controllers and Models I/III equipped with 80-track drives or double-sided drives could not use TRSDOS; RadioShack sold Logical System's LDOS operating system which could control these types of drives. The Model 4's TRSDOS 6 is a development of LDOS and has the same capabilities.

Hard disk drives (then also known as [[winchester drive]]s) required custom [[device driver|driver]] software supplied by their manufacturers. These drivers permitted any TRSDOS installation to access them with up to eight possible drive [[disk partition|partitions]], each assigned to drive numbers zero through seven. Actually, a large hard drive could be formatted with more than eight partitions, but TRSDOS can only access eight during any one session. Hard drives could have some partitions formatted under TRSDOS and others under the CP/M OS. Each floppy drive in the system would also take up one drive number assignment. The Model 4, with its ability to set up a [[ramdisk]] (Memdisk), also required a drive number assignment for this.

All versions of TRSDOS use [[Overlay (programming)|overlays]] to satisfy most system requests and disk directories are not maintained in memory. This has two implications for system performance. First, upon initial file access the DOS always references the disk directory to obtain information giving the physical mapping of disk space allocated to the file (including its extents, if any). After the initial access this information is maintained in a File Control Block, the memory space for which is supplied by the calling application. Further references do not need to read the disk directory (unless the file is written to and more disk space needs to be allocated). For this reason system performance depends greatly on how close a file's allocated disk space(s) is/are to the directory cylinder, and how [[disk fragmentation|fragmented]] (extents located in non-contiguous space(s)) the file is as a whole. The farther away the directory cylinder is, the more the drive's [[read/write head]] will need to move, which slows disk access and produces more mechanical wear on the drive. TRSDOS has commands permitting the user to optimize placement of particular files on the disk's physical space, and the {{keypress|FREE}} command to display a map of a file's physical placement on a drive.

The second implication of the overlay-based architecture is that a disk containing TRSDOS system files (file extension /SYS) must always be present in whichever drive is assigned as [[logical drive]] number zero. (On the Model 4 this may be the Memdisk, thus freeing physical drive zero be used for a non-system data disk). LDOS and TRSDOS 6 have a SYSRES command which loads selected system files into Z80 RAM, thus freeing space on the system disk for non-system data. All versions have variants of the SYSTEM command which can reassign logical drive numbers to physical drives. It is possible to assign drive numbers such that a physical drive is unassigned a logical drive number; this is sometimes useful to guarantee that the drive cannot be accessed for security or safety ([[write protection]]) purposes. Drives may be set to be write protected by the DOS, also.

===Disk management===
The primary function of any [[disk operating system]] is to provide the user with a facility for managing and accessing files stored on disk storage devices. Since the user must not be burdened with the physical details of the storage devices themselves, it is the operating system's responsibility to translate file record access requests into specific drive, track, sector, and head parameters that pinpoint the storage location of each record.

The system also maintains in Z80 memory within TRSDOS a '''Drive Control Table''' that stores the parameters associated with each of the eight logical drives. Disk drive parameters refer to how the total storage space on a drive is divided up into addressable units. The layer(s) of magnetic particles on the surface of the disk media are magnetized (during the format process) into concentric circles of storage areas called '''TRACKS'''. Each track is divided into 256-byte sub-areas called '''SECTORS'''. Each sector is uniquely identified by a pattern of information preceding each sector called an '''ID FIELD'''. Although the number of sectors per track may vary from one media type to another, the number of sectors in each track of the same media (and in each granule) must always be a constant.

Disks are organized as follows: each track is formatted into a specific number of 256-byte sectors with a maximum capacity of 32 sectors per track. Sectors are grouped into blocks called '''granules''' which vary in size according to total track capacity of the disk media, though granule size for each disk format is constant. For forty-cylinder disks formatted in double density, standard for the drives installed in the TRS-80 Models III and 4, the granule size is six 256-byte sectors, or 1.5 KB. Each track has three granules for 4.5 KB of storage. Each side (surface) of the disk is normally formatted with 40 tracks, yielding 180 KB per side. The Model 4D, with its double-sided drives, yields 360 KB of storage. Whenever additional disk space is needed for a file (such as extending a file while being written to), an additional granule is allocated. The granule thus becomes the minimum size storage unit.

TRSDOS assigns numbers to every sector, every track, and every surface. Surfaces are numbered consecutively starting from zero. Tracks are numbered consecutively starting from zero at the outermost edge of the disk giving the innermost track the highest number. Where multiple headed drives are in use, the track numbers on a surface are duplicated on each surface with all similarly numbered tracks constituting a '''cylinder'''. For a double-sided floppy disk as formatted on a Model 4D, track zero of surface zero and track zero of surface one are grouped together into cylinder zero. Cylinder capacities also have an upper limit of 256 sectors per cylinder or eight granules per cylinder, while the system supports (for hard drives with multiple platters of storage media) a maximum of eight heads per drive.

The disk's directory cylinder is placed during the format process on the middle-numbered cylinder; thus a standard 40 cylinder disk has its directory installed on cylinder 20. This reduces the average distance (and access time) that the drive's read/write head must move to access the directory. The first sector of the disk directory contains the Granule Allocation Table ('''GAT'''). The GAT is bit mapped to each granule of space on the drive. Other fields in the GAT contain the PACK NAME, DATE of creation (when the disk was formatted), pack PASSWORD, and data pertaining to the configuration of the drive.

When a file is to be opened for access, the system needs to search the directory for its directory record. Search time is minimized by using a hashing technique to reduce the 11-character string formed from the file name and extension to a one byte value. The hash code for each file is stored in a '''Hash Index Table''' (HIT) which is the second sector of the directory. Each position in this table corresponds to a specific directory entry record. The hash table, being one sector in length, can index a maximum of 256 directory records or files. The directory itself is sized according to disk capacity by being a maximum of one cylinder (up to 34 sectors). Thus, the larger the disk storage capacity, the larger its directory, and the greater the number of file names that can be stored on the disk.

The directory record contains information such as the date the file was last modified, its update and access password codes, its access level, and other attributes such as whether it is a SYStem or PDS (Partitioned Data Set) file and if a backup has been made, the relative number of the last sector in the file, and the last byte within the last sector (or End Of File). The record also contains the physical area(s) in use by the file, by pointing to the cylinder, relative starting granule, and number of contiguous granules for each extent comprising the file. When a file has more than four extents, additional directory records are used as required with forward and backward pointers linking each record of each file. Thus the theoretical maximum of 256 files possible on a floppy diskette is realizable only if there is no file fragmentation.

When TRSDOS formats a disk, all of the parameters associated with the diskette are predetermined. Thus the number of sectors per track, number of sectors per granule and thus the granules per track, number of sides (surfaces), and number of cylinders are all designated, as well as the density of the media. Some of these figures (density, sides, granules per track) are written to fields in the Granule Allocation Table which is part of the disk directory. Others (sectors per track, sectors per granule, in addition to the former quantities) are part of the Drive Control Table fields. When the system attempts to open a file on a disk, it uses the @CKDRV SVC to ascertain the availability of the disk, and then logs the disk once it finds it available. This "logging" function will update the DIRCYL field, then update the DBLBIT and MAXCYL fields based on information stored in the GAT. This procedure frees the user from having to manually log a newly inserted disk; he is at liberty to change differently formatted disks in any drive without concern that the system will incorrectly access it.

The SVC disk primitives are funneled through common system routines contained in the driver software installed for each type of disk storage device. The driver for Model III or Model 4 floppy drives is named {{mono|$FD}} and is located in the TRSDOS low memory region. Hard disk drives are supplied with their own driver software, and are usually installed in high memory (main 64K Z80 RAM) above the system {{mono|HIGH$}} pointer, since room in the low memory region is usually insufficient (especially on the Model 4 since software needed to access its external memory banks cannot reside in high Z80 RAM memory because that region exists in the banked RAM swap area). These driver routines establish a linkage protocol between the application requesting disk access and the computer's Floppy Disk Controller hardware. TRS-80s use controller chips from the [[Western Digital]] series: the WD1791 in the Model 4 non-gate array version, and the WD1773 in the Model 4 Gate Array version. When an I/O request is invoked by a higher level SVC, such as a request to READ a file record, the request is translated to that disk primitive (FDC command or status report) needed to satisfy the function request. The linkage protocol is uniform across all disk devices that are connected to the system. This makes the access of files transparent to size or nature of the disk device within the scope of the parameters stored in the DCT for that drive.<ref>{{cite web |last1=Soltoff |first1=Roy |title=Programmer's Guide to TRSDOS 6 |url=https://www.tim-mann.org/trs80/doc/prgguide.pdf |website=timm-mann dot org |publisher=Misosys Inc. |accessdate=November 4, 2019}}</ref>

===File management===
Disk files are supported with two types of access: Record I/O and character I/O. Logical records of from one to 256 bytes in length can be read or written using the @READ or @WRITE SVC requests. Record I/O can be random access (by position SVC requests prior to READ/WRITE) or sequential access using repetitive READs or WRITEs. Character (or byte) I/O is accomplished by @GET and @PUT SVC requests and is essentially the same as record I/O with a ''Logical Record Length'' (LRL) equal to one. (Physical access to a disk storage device is always in units of 256 byte sectors. This is fixed by the TRS-80 disk controller hardware). However, if GET or PUT are used to implement sequential access, then a file can be considered a character I/O device just like a printer, a [[serial port]], or a video display device. A byte I/O request is therefore independent of the physical device "connected" to the control block which is requesting the I/O. This makes the system "device independent".

Filenames are limited to eight [[alphanumeric]] characters (the first character must be alpha) which are [[case insensitive]] (only capital letters are used; any lowercase letters entered are capitalized). File extensions are up to three characters and obey the same rules. File passwords are up to eight characters obeying the same rules (TRSDOS 6 versions up to 6.2 support both owner and user passwords). Entire diskettes can also be assigned master passwords, which may limit user access via the BACKUP and PURGE commands.

Under TRSDOS and LDOS the system is never "logged in" to any current drive as with [[CP/M]], [[PC DOS]] and [[MS-DOS]]. The system prompt is always {{samp|TRSDOS Ready}}. All file access requests (whether issued by the user at the console or a program being executed) are satisfied by searching the directory of the first drive specified (taken as drive zero if no drive number is given) and, if the requested file is not found, then searching the next (higher numbered) drive in the system. This continues until the file is found or all the drives in the system have been searched (but see below for variations on this rule). 

Drive numbers are specified with a colon {{kbd|:}} followed immediately with the drive number. The colon is optional unless the drive specification is used as a suffix for a filename. Using the {{kbd|DIR}} directory command as an example: 

* {{kbd|DIR}} displays all files starting with logical drive zero, then drive one, and so on.
* {{kbd|DIR :4}} or {{kbd|DIR 4}} searches logical drive four (for all files, as always when no filename is given).
* {{kbd|DIR :4-6}} or {{kbd|DIR 4-6}} searches logical drives four, five, and six.
* {{kbd|DIR :4-}} or {{kbd|DIR 4-}} searches logical drives four, five, six and seven.
* {{kbd|DIR FILENAME:2}} searches for FILENAME on logical drive two.
* {{kbd|DIR FILENAME:2-}} searches for FILENAME on all logical drives starting from drive two.

As seen, the dash character {{kbd|-}} is used to specify a range of drive numbers. The {{kbd|DIR}} and {{kbd|CAT}} (catalog) commands display all file specifications ('''filespecs''') matching the query on all drives. Other commands/utilities such as {{kbd|BACKUP}}, {{kbd|COPY}} and {{kbd|PURGE}}, and drive searches initiated by programs being executed, stop searching at the first drive found to match. If the same filespec exists on multiple drives, then those files on higher-numbered drives will be excluded. 

File access by partial filenames ('''partspecs'''), file extensions, and file dates are supported. For example:

* {{kbd|DIR SAMPLE}} will select files SAMPLE, SAMPLE1, SAMPLE23 and SAMPLEIT.
* {{kbd|DIR /BAS}} will select files SAMPLE/BAS, TEST/BAS, EXAMPLE/BAS, etc.

As with the {{kbd|DIR}} example earlier, drive specifications ('''drivespecs''') may be appended to filespecs. These examples assume the selected files have not be made invisible in the disk directory. File access requests issued by applications programs running under TRSDOS work the same way.

===Command-line interface===
Under TRSDOS/LS-DOS 6.x, the standard system [[command interpreter]] (SYS1/SYS) can be functionally replaced with a custom interpreter by copying the new interpreter to the system file SYS13/SYS (which in an unmodified installation is a dummy file). This can be any machine code /CMD program file. This is referred to in the documentation as an "Extended Command Interpreter" or ECI.

TRSDOS/LS-DOS 6.x support [[wildcard character]]s in filenames, both the single character ? and multicharacter *.

TRSDOS (version II) was notable for the inclusion of ''noise'' words, similar to the 1959 [[COBOL]] specification. These made commands more English-like. For example, the following commands functioned identically:
*{{kbd|COPY filea fileb}}
*{{kbd|COPY filea TO fileb}}
<!-- :**COPY fileb FROM filea -->

Since TRSDOS does not have the notion of ''redirection'' for disk files as [[UNIX]]/[[Linux]] and [[MS-DOS]] do, the APPEND command is somewhat different in concept than the UNIX or MS-DOS notion of appending via output redirection. TRSDOS/LS-DOS 6.x do provide I/O redirection for system devices (keyboard *KI, display screen *DO, printer *PR, serial port *CL), as well as for between devices and disk files. The DEVICE command displays a map of I/O links and routes.
Under DOS and UNIX printing a file can be done with redirection; under UNIX it is normally done by spooling the file to the "[[line printer]]" (using the ''lpr'' command) because UNIX is conventionally a multi-user system. TRSDOS/LS-DOS 6.x print jobs can be redirected (such as to a disk file) by applying the LINK or ROUTE commands to the system *PR device.

TRSDOS/LS-DOS 6.x do not support [[subdirectories]] or user areas. However, the DIR and CAT (Catalog) commands for displaying file data support the usual partial filenames, suffixes, and file dates.
Under TRSDOS/LS-DOS 6.x files can be made invisible to the DIR and CAT commands, and can be displayed with the INV parameter (unless any files are password protected and the correct p/w is not given).

TRSDOS/LS-DOS 6.3 can dump the video screen to the line printer by pressing {{key press|CTRL|:}}.

Many versions support a simple password security for files and programs, with separate Read/Execute and full access capabilities. ex: ''filename/ext.password:drive#''. TRSDOS 6.x supports both Owner and User passwords (8 characters max) for disk files. LS-DOS 6.3 uses the space for the User password for its extended dating scheme (past December 31, 1987). Both Model 4 OSes can set various file access levels and permit software write protection for disk files and entire disks.

==== Commands ====
Although MS-DOS owes its heritage most closely to CP/M and thence to [[TOPS-10]], many of the file manipulation commands are similar to those of TRSDOS. 
Some of the following TRSDOS commands exist on disk as distinct program files (DIR/CMD, FORMAT/CMD, BACKUP/CMD) while all others exist as modules condensed into the library files (technically Partitioned Data Sets or PDSs) SYS6/SYS, SYS7/SYS and SYS8/SYS; these include the TRSDOS commands CAT, COPY, LIST, REMOVE, RENAME etc.
Some typical TRSDOS utilities:

{| class="wikitable"
|+ TRSDOS commands and counterparts in other operating systems
|-----
! Command
! [[DOS]], [[OS/2]], [[Microsoft Windows|Windows]]
! [[Unix]], [[Unix-like]]
! Description
|-----
! style="font-family:monospace;" |  APPEND
| style="font-family:monospace;" | [[TYPE (DOS command)|type]] ''file1'' '''>>''' ''file2'' || style="font-family:monospace;" | [[cat (Unix)|cat]] ''file'' '''>>''' ''file2''
| Under TRSDOS 6.x, the source of the appended data may be a system input device such as *KI. Thus whatever is typed at the keyboard will be appended to the target file. Use RESET *KI to end this function.
|-----
! style="font-family:monospace;" |  ATTRIB
| style="font-family:monospace;" | [[attrib]] || style="font-family:monospace;" | [[chmod]]
| ATTRIB, PROT, and the ''chmod'' UNIX command are all somewhat different in their semantics. UNIX/Linux is multi-user and each user can control read, write, and execute [[File-system permissions|permissions]] on his or her own files and directories. MS-DOS is single user and the file attributes for "read-only," "hidden," and "system" are advisory in nature. TRSDOS was single user. TRSDOS 6.x ATTRIB can modify protection status of all files on a disk volume if the disk's master password is given. All user and owner passwords on visible files can be removed with a single ATTRIB command.
|-----
! style="font-family:monospace;" |  AUTO
| style="font-family:monospace;" | [[AUTOEXEC.BAT]] || style="font-family:monospace;" | ~/.profile or ~/.login or /etc/rc*
| The AUTO command sets an automatic command to be executed on TRSDOS boot; under MS-DOS the special, reserved file named '''AUTOEXEC.BAT''' contained a list of such commands. TRSDOS/LS-DOS 6.x support Job Control Language in which any text file with the suffix /JCL could batch process (using the '''DO''' command) any number of executable program files. Such a file could be the object of an AUTO command. On UNIX a set of one or more '''''rc''''' files under ''/etc/'' are a set of boot time "'''r'''un '''c'''ommands" and special "dot files" in a user's home directory are run for each time that a given user logs into the system. UNIX supports many other "dotfiles" for many of its commands which are akin to the [[Macintosh]] "preferences" folder contents.
|-----
! style="font-family:monospace;" |  BACKUP
| style="font-family:monospace;" | [[diskcopy]], [[tar (computing)|tar]] || style="font-family:monospace;" | tar, [[cpio]], [[pax (command)|pax]], (many others)
| TRSDOS/LS-DOS 6.x include the BACKUP/CMD utility which can mass copy files specified by partial filename matches, file suffixes (e.g. such as /CMD or /BAS), or by file date. BACKUP can be made to first query for permission to copy each file with the ''(Q=Y))'' parameter. On single drive computers the X parameter will permit copying between two disks by prompting the user when to switch disks in the drive.
|-----
! style="font-family:monospace;" |  CAT
|
|
| The TRSDOS CATalog command displays one line giving information on the selected drive (disk name, capacity, date) and a listing of the filenames with their extensions present on the disk. This is an abbreviated version of the DIRectory command, which permits more file information to be presented on a single video screen with less need for scrolling to view the contents of the entire disk. CAT uses the same parameters as DIR for viewing INVisible and SYStem files.
|-----
! style="font-family:monospace;" |  CLOCK
| style="font-family:monospace;" | [[prompt (computing)|prompt]] $t * || style="font-family:monospace;" | in some shells: PS1="...\t..." *
| CLOCK installs an interrupt task that shows the system time in the upper corner of the display; no exactly corresponding feature exists in MS-DOS or UNIX, though many programs provided similar features for DOS and the common UNIX shells could embed the time into their user-defined "prompt string".
|-----
! style="font-family:monospace;" |  CLS
| style="font-family:monospace;" | [[cls (command)|cls]] || style="font-family:monospace;" | [[clear (Unix)|clear]]
| Clear video display and home cursor
|-----
! style="font-family:monospace;" |  COMM
|
|
| Under TRSDOS 6.x, COMM/CMD is a [[terminal program]] that establishes communications between the Model 4's [[RS-232C]] serial port and that of another computer, a modem or serial printer/plotter. Must first install the driver for the serial port, COM/DVR using the SET command, which establishes the system *CL (Comm Line) device. Use SETCOM/CMD to set parameters for communication.
|-----
! style="font-family:monospace;" |  COPY
| style="font-family:monospace;" | [[copy (command)|copy]] || style="font-family:monospace;" | [[cp (Unix)|cp]]
| Under TRSDOS 6.x, the COPY command can be used to transfer information between system devices as well as disk files. For example, COPY *KI *PR will turn the computer (if connected to an active line printer) into a typewriter, as each character typed at the keyboard is sent to the *PR device as well as the *DO device. This is effectively the same as the TRSDOS command LINK *KI *PR. Use RESET *KI to turn off this function.
|-----
! style="font-family:monospace;" |  DEBUG
| style="font-family:monospace;" | [[debug (command)|debug]] || style="font-family:monospace;" |
| Optional ''filespec'' also performs LOAD function on a target /CMD machine code program; ''(ext)'' loads additional debugger commands from system file SYS9/SYS
|-----
! style="font-family:monospace;" |  DEVICE
|
|
| Displays the status of the system drives and system logical devices, as well as the existing ROUTEs and LINKs between them.
|-----
! style="font-family:monospace;" |  DIR
| style="font-family:monospace;" | [[dir (command)|dir]] || style="font-family:monospace;" | [[ls]]
| DIR displays the same files that would be selected by the BACKUP command, and so is useful as a preview tool. Parameter ''(p)'' sends the directory listing to the line printer, which in turn can be ROUTEd or LINKed to a disk file.
|-----
! style="font-family:monospace;" |  DISKCOPY
| style="font-family:monospace;" | [[diskcopy]] || style="font-family:monospace;" |
| LS-DOS 6.3 includes the DISKCOPY/CMD utility which makes an exact copy of a source disk by formatting and copying to a blank destination disk.
|-----
! style="font-family:monospace;" |  FILTER
|
|
| FILTER is used to attach a /FLT filter program to a system device. Three included with TRSDOS 6.x are FORMS/FLT which is used for formatted printing, KSM/FLT which is a keyboard macro facility, and CLICK/FLT which causes the Model 4 speaker to beep every time a key is pressed.
|-----
! style="font-family:monospace;" |  FORMAT
| style="font-family:monospace;" | [[format (command)|format]] || style="font-family:monospace;" | [[mkfs]]
| Defaults to 40 track, single-sided on Models III and 4, double-sided on Model 4D. Number of tracks per side can be specified using parameter (CYL=''nn''). All Model 4Ds and most Model 4s can format 42 tracks although drives supplied by Radio Shack are nominally 40 track.
|-----
! style="font-family:monospace;" |  FORMS
|
|
|Under TRSDOS 6.x, sets parameters for data sent to the system *PR device after the FORMS filter has been attached to the *PR device. These include number of characters per printed line, lines per page, margins, added linefeed characters, etc.
|-----
! style="font-family:monospace;" |  FREE
| style="font-family:monospace;" | [[chkdsk]] || style="font-family:monospace;" | [[df (Unix)|df]]
| TRSDOS 6.x displays [[ASCII]] map showing disk granules occupied by active files with xxxxxx; the directory cylinder is shown as DDDDDD.
|-----
! style="font-family:monospace;" |  GETDISK/GETTAPE
| {{dunno}} || style="font-family:monospace;" | [[dd (Unix)|dd]]
|
|-----
! style="font-family:monospace;" |  KILL
| style="font-family:monospace;" | [[del (command)|del]] || style="font-family:monospace;" | [[rm (Unix)|rm]]
| Starting with TRSDOS 6.0 KILL was replaced by REMOVE (per LSI Journal article "Thou Shalt Not Kill")
|-----
! style="font-family:monospace;" |  LIST
| style="font-family:monospace;" | [[TYPE (DOS command)|type]] || style="font-family:monospace;" | [[cat (Unix)|cat]]
| Under TRSDOS/LS-DOS 6.x, the LIST command can display or print the contents of non-ASCII files with the HEX parameter. The listing can be paused using {{key press|SHIFT|@}}.
|
|-----
! style="font-family:monospace;" |  LOAD ''filespec''
| {{no2|(no equivalent)}} || {{no2|(no equivalent)}}
| Program invocation under TRSDOS, DOS and UNIX is done by filename; no explicit '''LOAD''' command is required for normal binary executables nor for text command files ([[batch file]]s in DOS and [[shell script]]s in UNIX/Linux). The '''LOAD''' command under TRSDOS would load a binary program into memory, but would not execute it; neither DOS nor UNIX has an equivalent. '''LOAD''' under TRSDOS is almost always used to make a machine code Z80 program (/CMD file) available to the system debugger for examination or modification.
|-----
! style="font-family:monospace;" |  MEMORY
|
|
| The MEMORY command shows the names and sizes of memory resident modules. It is also used to modify system flag bytes. For example, flag A is the DOS Allocation byte, which the BACKUP command uses to specify the beginning cylinder of a disk to start copying files. This gives the user control over the physical placement of files on disks, which is important to minimize movement of the drive's read/write head during file access.
|-----
! style="font-family:monospace;" |  PATCH
| {{dunno}} || style="font-family:monospace;" | [[patch (Unix)|patch]]
| All versions of TRSDOS include the PATCH/CMD utility. This permits modification of machine code /CMD files using patch data supplied by a /FIX file in [[hexadecimal]] ASCII format.
|-----
! style="font-family:monospace;" |  PRINT
| style="font-family:monospace;" | [[TYPE (DOS command)|type]] ''file'' >> [[PRN:|prn]] || style="font-family:monospace;" | [[Line Printer Daemon protocol|lpr]]
| Under TRSDOS 6.x an interrupt task is provided to dump the current video display to a line printer at any time. This is activated using {{key press|CTRL|:}}. If the system *PR device is ROUTED or LINKED to a disk file it will be sent there.
|-----
! style="font-family:monospace;" |  PURGE
|
|
| TRSDOS/LS-DOS 6.x support the PURGE command which will mass delete files specified by partial filename, file suffixes, or file dates. PURGE will query the user for permission to delete each file unless the ''(Q=N)'' parameter is given.
|-----
! style="font-family:monospace;" |  RENAME
| style="font-family:monospace;" | [[ren (command)|ren]] or [[ren (command)|rename]] || style="font-family:monospace;" | [[mv (Unix)|mv]]
| Under TRSDOS 6.x the user may rename individual files or the entire diskette.
|-----
! style="font-family:monospace;" |  TAPE100
| 
|
| TAPE100/CMD reads and writes cassette tapes recorded by the [[TRS-80 Model 100]] laptop as TRSDOS 6.x disk files. This requires use of the Model 4 cassette interface, which the Model 4P transportable lacks.
|}