home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.barnyard.co.uk
/
2015.02.ftp.barnyard.co.uk.tar
/
ftp.barnyard.co.uk
/
robot-pd
/
12400.ZIP
/
12400B.DSK
/
manual01.txt
< prev
next >
Wrap
Text File
|
1998-04-30
|
9KB
|
236 lines
C H A P T E R O N E
Introducing Centrox
There are two main parts to Centrox. The first is called
the Kernel and it is this that is responsible for
management of system resources. The kernel stays in memory
at all times.
The second part of Centrox is called the Shell. This
program can be either permanent or transient. The Shell is
responsible for interfacing between the user and the
Kernel.
1.1 Documentation Conventions
In this manual, the following conventions apply:-
Items enclosed in chevrons `<...>' should not be typed as
read. Instead the comments inside the brackets describe
the type of information that should be entered.
Square brackets enclose items which can be omitted. The
text will describe what happens if such items are omitted.
Curly brackets enclose a list of items from which one AND
ONLY ONE item may be chosen.
The prefix `++' indicates possible repetitions of the
following item.
1.2 Shell Command Line
Using the above convention, the general form of the Shell
command line can be given as:-
[++<Statement>;]
This means that the line takes the form of an optional
list of statements, each separated from the next by a
semicolon. A pair of semicolons will be translated into a
single semicolon, which will be treated as an normal
character.
Eg; "LF /COM;LF .." is two commands.
"Echo This (;;) is a semi colon" is one command, but
note that the double semi colon IS converted into a single
semi colon.
"Echo Test;;;LF /COM" is two commands, with the first
consisting of "Echo Test;;" followed by "LF /COM". Again,
the EFFECTIVE first command is "Echo Test;".
1.3 Shell Command Statement
The format of a Shell statement is:-
<Command name> [&++<Selector>] [++<Argument>]
The <Selector>s can be thought of as switches. They allow
certain options to be switched on or off, hence tailoring
the operation of the command. The <Argument>s can be file
names, numbers or any other construct.
The Shell allows the user to abbreviate internal commands.
The abbreviation is entered as a truncated version of the
command name, terminated by a dot.
1.4 Halting Or Pausing A Program
A program can be paused by holding down [CONTROL] and [S],
the program can be restarted by pressing [CONTROL] and [Q]
when ready. The notation ^<letter> is used to represent
such a sequence of keys, eg; ^Q => CONTROL+Q.
^C ([CONTROL] and [C]) will usually stop a program if held
down for about one second. Note, however, that the Shell
may in some cases take longer to respond to the
interruption. When it recognises the signal, it will emit
a `Bleep'.
1.5 Disk Structure
Centrox provides the means to set up a relational disk
partitioning system. This allows you to divide the disk
into different areas for each topic you use the computer
for. Each of these areas has a position relative to other
areas.
Each of these areas are known as DIRECTORIES. A typical
directory structure as shown below:-
/
|
+---------+---------+
| |
COM Jim
|
+-------------------+
| |
Programs letters
If the Kernel is to access a particular file, it needs to
be told where it is stored. This is done by giving the
Shell a description of the PATH to the required directory.
The Shell recognises two methods of describing the path.
Directories can be stored on any of up to ten disks, and
can be either data or system directories. Data directories
are read from drive B: (except on single drive systems)
whilst system directories are read from drive A:. AMSDOS
can't deal with disk swapping while files are open. For
this reason, single drive users may experience problems
from time to time.
All the Centrox programs have been written to either
overcome this problem (see COPY, next chapter), or else
will refuse to allow such a situation to arise (see COMP,
chapter five).
1.6 Using File Paths
1.6.1 Description
File paths take the form:-
<directory path list>/<CP/M file name>
In the example "/Jim/letters/mum.let" the file "mum.let"
is being referred to. "Jim" and "letters" are the names of
directories. Centrox knows that "mum.let" is a file
because it is the last item in the list. If the list was
simply "mum.let" then Centrox would accept that no
directories had been mentioned.
But so what? Why should Centrox allow us to give a list of
directories? The reason is that the list is a description
of the path that must be taken to get to the area of the
disk that "mum.let" is stored in.
The above example means; first go into the "Jim"
directory. When you arrive, look for a directory called
"letters" which branches off from "Jim". When you find it,
look in it for the file "mum.let".
This system allows you to organise your disks better than
AMSDOS and CP/M. No longer will a letter to your mother be
stored along with a program. Of course, CP/M and AMSDOS do
allow you to separate your disks into sixteen areas, but
these are all at the same "level". Centrox allows
directories to branch off other directories.
1.6.2 Describing Paths To Centrox
I'm now going to ignore file paths and concentrate on
directory paths. File paths are, after all, simply
directory paths with a CP/M / AMSDOS file name appended.
Centrox evaluates directory paths by walking along the
path "in its mind". The first step is for Centrox to
choose a starting point on the directory "tree". If the
path starts with a "/" then Centrox starts walking from
the "top" of the tree, otherwise it starts from your
current directory (more on that later).
For the sake of this discussion, I'll refer to the
directory that Centrox starts walking from as the CWSD
(Centrox Walk Start Directory!). The next step is to get
the first directory name. Centrox then looks in the CWSD
for a directory with that name. If it finds such a
directory it "walks" into it, making it the new CWSD.
Centrox then fetches the next directory name and repeats
the operation 'till all names have been dealt with. After
finishing the list, the CWSD is the target of the path.
The following directory names work differently:-
".." makes Centrox backtrack up the tree. In case this
confuses you, bare in mind that, like humans, directories
can only have one set of parents. Going back to the first
example, ".." from "letters" takes us to "fred".
"-" causes Centrox to "teleport" into your home directory.
This directory is the directory that you start from when
you first log onto Centrox.
"." causes Centrox to teleport into the current directory.
This directory is used to save time. Without it, you would
have to give Centrox a complete directory path every time
you wanted a file..imagine the tedium of typing
"/Jim/letters/mum.let" every time you want to write a
letter!
By making "/Jim/letters" the current directory, you can
simply type "mum.let". If you go back to Centrox's little
stroll, remember that without the "/" at the start of the
path, Centrox starts looking from the current directory.
Since only a file name has been given, Centrox doesn't
actually "walk" anywhere, it just starts from
"/Jim/letters" and looks for the file immediately.
Centrox uses the name "/(TOP)" to refer to the root
directory. This is for (stupid) historical reasons, I
suggest that you ignore it. The path "/" ALWAYS refers to
the root directory. Oddly enough, neither "/(TOP)" nor
"(TOP)" can ever be given legally..they will always
generate the error "No such directory"..try to work out
why.
1.7 Directory Names
Directory names can be any length, but they may only share
names with another directory if they have different
parents. Directory names cannot be abbreviated.
1.7 File Names
These must obey the normal AMSDOS conventions and again,
files may only share names if they are in different
directories. File names cannot be abbreviated.
╔Introducing CentroxΘ
There are two main parts to Centro