home *** CD-ROM | disk | FTP | other *** search
- ID v1.01 J. Elliott, 12 December 1993.
- ================================================================================
-
- ID is a program allowing CP/M to inspect the "identity" record of LocoScript
- (and other) files. The command is:
-
- ID d:filename.typ { n } { >d:listfile.typ }
-
- The first filename can be ambiguous. 'n' is a number from 0-15.
-
- If there is a number, this refers to the CP/M user number ("group"), so that
- the command
-
- ID A:*.* 2
-
- would show a listing of all files in group 2 of the disc in drive A:, with their
- "identities" (see below). The group number can also be ambiguous; if you use the
- command
-
- ID *.* *
-
- this will show the "identities" of all files in all groups.
- If there is a "listfile" specified, the entire "ID" listing is sent to the
- listfile as well as the screen. If there is a user number in the command line,
- then the listfile will go to this number, eg:
-
- ID B:*.DOC 3 >B:INDEX.ASC
-
- will do a listing of all files ending with .DOC in Drive B, group 3 -
- directing the output to the screen and the file INDEX.ASC also in Drive B,
- Group 3. The listfile produced can then be inserted into a LocoScript document
- using the f1=Actions menu (f7=Modes for LocoScript 1). If you do this in all
- groups, you get an index file in each group, which some people find useful. The
- command:
-
- ID C:*.* * >C:CONTENTS
-
- will produce a file called CONTENTS on drive C:, group 0, containing a list of
- every file on C:.
-
- Each file will appear in the listing as
-
- nnD:FILENAME.TYP - What type this file is
- | | | Information specific to this file (eg LocoScript identity)
- | | +----Filename
- | +------Drive
- +--------User number
-
- ID will attempt to classify the file under various categories (eg Document,
- Settings, Dictionary etc.). LocoScript files have their category given in the
- first three bytes; I cannot guarantee that I have successfully divined the
- correct interpretations of all of these.
-
- If the file is not LocoScript, ID can also detect:
- ╝ Sinclair +3DOS files.
- ╝ Mallard BASIC programs, and can tell if they are protected.
- ╝ Microsoft BASIC programs, and can tell if they are protected.
- ╝ Mallard BASIC Jetsam files.
- ╝ PICture files from DR.LOGO.
- ╝ CP/M utility programs written by Digital Research (eg PIP, SHOW, DUMP).
- ╗ (but not machine-specific programs like PALETTE, SETKEYS).
- ╝ Console Command Processor (CCP) files.
- ╝ Files containing RSX modules.
- ╝ Archive (.ARC/.ARK) files.
- ╝ Compiled batch files produced by CHN.COM.
- ╝ Compiled text files produced by WTXT.COM.
- ╝ MSDOS EXE files.
- ╝ Squeezed (.xQx) files.
- ╝ Crunched (.xZx) files.
- ╝ Multiface 3 datafiles.
- ╝ GIF (PC clip art) files.
- ╝ VFONTs (variable size fonts).
-
- If the file is none of these, ID will try to print whatever is printable in
- the first 128 bytes of a file. Some well-behaved binary files (like ID.COM
- itself) will produce recognisable text this way; some (eg SETSIO.COM) will be
- readable if a bit untidy and some (eg JnnCPM3.EMS) won't. If the questionable
- file is a textfile, the first few lines will be seen.
- If ID produces the message "File size=0k" then the file in question is empty
- and is probably either a LocoScript group name, an old-style CP/M disc name
- (some PD software suppliers put these on the disc) or a listfile under
- construction.
- ________________________________________________________________________________
-
- New features in v1.01 are:
-
- 1. Different user numbers are available.
- 2. Listfiles can be generated.
- 3. Added detection abilities:
- Squeezed files;
- Crunched files;
- Compiled textfiles;
- Multiface 3 datafiles;
- GIF files;
- VFONTs.
- 4. High bits on filenames are ignored, so all filenames display correctly.
- 5. The first 7 RSX names are printed.
- 6. The screen output is paged.
-