su4man.pdf

HIT

TRSDOS 1.3 codes the SYSTEM files in the last 32 bytes of the HIT table, and
TRSDOS 2.7DD in the last 48 bytes. Because of the fact that they do not have any standard
directory entries, these bytes will be left untouched by Super Utility 4 during a HIT repair,
since without standard entries, it is not possible to reconstruct a HIT entry. If these bytes
have been corrupted, you must use the ZAP utility to effect repairs. If the bytes look
obviously invalid to you, enter FF in all 32 slots (48 for TRSDOS 2.7DD).

DELETING

The usefulness of this procedure with TRSDOS 1.3 and TRSDOS 2.7DD is
questionable, since these systems automatically zero out directory entries when a file is
removed.

SYSTEM FILES

TRSDOS 1.3 codes the SYSTEM files in the last 32 bytes of the HIT table, and
TRSDOS 2.7DD in the last 48 bytes. Because of the fact that they do not have any standard
directory entries, these bytes will be left untouched by Super Utility 4 during a HIT repair,
since without standard entries, it is not possible to reconstruct a HIT entry. If these bytes
have been corrupted, you must use the ZAP utility to effect repairs. If the bytes look
obviously invalid to you, enter FF in all 32 slots (48 for TRSDOS 2.7DD).

PASSWORDS

If you are copying a file from a TRSDOS 1.3 or 2.7DD formatted disk to a formatted
disk created by another system or vice versa, Super Utility 4 will deliberately strip any
passwords which may have been set for the source file. The reason for this is that Model
III TRSDOS 1.3 and 2.7DD compute passwords differently from other operating systems
and if the encoded passwords were copied over, even if you gave the correct password, it
would not be recognized. If you have any password-protected files on your source disk,
you must reassign the passwords using the ATTRIB command of the operating system on
the destination disk after the copy routine is completed, or use Super Utility 4's CHANGE
FILE PARAMETERS procedure.

This routine will allow you to either encode or decode passwords using the algorithms
employed by the DOS. When this option is selected, you will be asked whether you want to
encode or decode a password. To encode a password simply enter E. You will be asked for
the password to encode. Type it in, and the routine will return the 2-byte hash of that
password. The algorithm used by this routine will depend on the configuration of drive 0.
If drive 0 is configured for TRSDOS 1.3 (T3D) then the TRSDOS 1.3 algorithm will be
used; if drive 0 is configured to T1D, then the TRSDOS 2.7DD algorithm will be used. For
all others, the standard algorithm will be used. You may have to enter the configuration
routine to alter the settings for drive 0 to get a correct encode of your passwurd. There are
no overrides for the compute passwords routine.

DATES

Copying a file to a TRSDOS 1.3 or 2.7DD disk from some other system will result in
garbage being displayed for the file’s creation date when a DIR is done under these two
systems. The reason for this is the fact that TRSDOS 1.3 and 2.7DD, unlike all other
systems which maintain file dates, do not maintain the dates in a bit-coded fashion, rather
they reserve one byte for the month and one byte for the year. These bytes usually contain
some other information, and are not changed by Super Utility 4 when it constructs the
destination file entry; hence garbage may appear for the date. If you wish to change the
date on these, display the directory entry for the file and modify relative bytes 1 and 2 of
the directory entry. Relative byte 1 contains the month in hexadecimal, and relative byte
two contains the two-digit year in hexadecimal.
