home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.barnyard.co.uk
/
2015.02.ftp.barnyard.co.uk.tar
/
ftp.barnyard.co.uk
/
cpm
/
walnut-creek-CDROM
/
BEEHIVE
/
ZSUS
/
Z3HELP-3.LBR
/
N.LBR
/
NDRS.HZP
/
NDRS.HLP
Wrap
Text File
|
2000-06-30
|
5KB
|
134 lines
;
NDRs
Size (recs) CRC Version Author/Latest Issue Disk
n/a n/a n/a n/a n/a Z3HLP1
1- Overview 2- Memory-Based NDRs 3- Help File
The Named Directory concept under ZCPR3 is an association of a mnemonic
name with a logical directory, which is a disk and user area. With this
facility, the user is permitted to refer to any directory by a mnemonic name,
and this greatly improves the user interface over having to remember disk
letters and numbers.
:1
Overview:
Under ZCPR3, an environment can be set up in which the following name
assignments are made:
A15: = ROOT A0: = BASE
B0: = BBASE B1: = JEFF
B2: = ROBERT B3: = LINDA
With the named directory facility enabled, the ZCPR3 utilities can refer
to these directories by either the DU: form (disk and user number) or by the
name:
XDIR ROOT: is the same as XDIR A15:
Overview (continued):
Most of the ZCPR3 utilities recognize named directories if the facility is
enabled, and, since these utilities function to provide interfaces between the
directories, they create a good working environment for use of the
conventional CP/M utilities as well. In other words, the ZCPR3 utilities
which can deal with named directories are the only utilities with which one
should cross directory boundaries in a ZCPR3 system and conventional
utilities, like an editor or an assembler, should be used in only one
directory and deal with files in the current directory and on drive A in the
same user number (A$ in the vernacular).
Many ZCPR3 tools are provided to act as a bridge between directories,
and they were created with this purpose in mind. Commonly-used functions had
to be made available to the ZCPR3 user to provide this bridge; such functions
include:
Overview (continued):
o File
Copying
Renaming
Erasing
Unerasing
Protecting
Typing to Console
Printing to Printer
Search
o Directory Display
Overview (continued):
For instance, to edit a file in the ZCPR directory with Word Master, copy
the file into a working directory which has the WM.HLP file in A: in the same
user area and edit there. Then copy it back when done:
B1>mcopy b1:=zcpr:file.txt
...
B1>wm file.txt
...
B1>mcopy zcpr:=file.txt
Overview (continued):
Many commercial programs, like Word Master and WordStar, are already
programmed to look on A: if they do not find the overlay they need in the
current directory. Word Master, for instance, has a WM.HLP file which
provides online documentation, and by working on drive B: in the same user
that a WM.HLP file exists on A:, if a user asks for Help, Word Master will
find it.
Named Directories can provide a more human-oriented working environment.
The user need no longer remember that his commands are in directory A15: --
he need only remember that ROOT contains his commands, HELP contains his help
files, ROBERT is his name and that is where he places the files he is working
on, BDSC is where his C compiler is, etc.
Overview (continued):
Named Directories are supported by the ZCPR3 utilities and by ZCPR3 itself.
Several utilities are specifically designed to deal with Named Directories,
and the rest of the utilities can access Named Directories manipulated by
these and use them.
The ZCPR3 utilities which deal directly with Named Directories are:
MKDIR -- creates a Named Directory
PWD -- prints Working Directory and all NDRs
CD -- logs into a Named Directory
EDITND -- edits the system Named Directory
SAVNDR -- writes a reloadable copy of the resident
NDR module to a disk file
NAME -- renames or deletes a Named Directory
:2
Memory-Based Named Directories
Named Directories are implemented by loading a *.NDR file created by MKDIR
into the ZCPR3 memory buffer reserved to contain the named directory
definition. Once loaded, all directory-to-DU associations in the file are
made effective, and any ZCPR3 command can make use of them.
One of the many purposes of LDR is to load a *.NDR file into memory. LDR
recognizes the NDR file type to refer to named directory files, and it loads
the file, doing a quick format check to ensure that it is a valid named
directory file.
:3
NDIRS.HLP
Size (recs) CRC Version Author/Latest Issue Disk
16k (123) A2E8 n/a n/a Z3HLP1
==============================================================================
Z-System HELP file for Named Directories.
ßσ~÷Çwß╤┴π⌡|═'±ß╔═'