Change carriage returns into linefeeds in all the Help files, without making any edits yet.
This commit is contained in:
Dave Lyons
parent
cac960e4e4
commit
797df9534f
|
|
@ -1 +1,35 @@
|
|||
alias -- display or modify command aliases
syntax: alias [-s] [-l] [-r] <alias-name> <expansion>
ex: alias
alias foo "cat -am"
alias -r foo
alias -s
alias -l
With no parameters, displays a list of all current aliases.
These are stored in the file %aliases (which you can edit
with a text editor if you want).
Given two strings, 'alias' creates a new alias so that the
first string, when used as a command, expands into the second
string. If there are blanks in the second string, you need
to put quotation marks around it. If the named alias already
exists, 'alias' asks for permission to replace it.
Given -r and a single string, 'alias' removes an existing
alias.
Creating or removing an alias does not automatically save it to
disk. To save your aliases to %aliases, use 'alias -s'. (Note
that if you create or remove an alias and use -s in the same
command, the saving happens -after- any changes to your aliases.)
To re-load your aliases from %aliases, use 'alias -l'. Davex
automatically loads aliases from there, so this is not normally
needed.
See Davex.Doc for an explanation of aliases and a description
of the pre-made aliases provided.
|
||||
|
||||
alias -- display or modify command aliases
|
||||
|
||||
syntax: alias [-s] [-l] [-r] <alias-name> <expansion>
|
||||
|
||||
ex: alias
|
||||
alias foo "cat -am"
|
||||
alias -r foo
|
||||
alias -s
|
||||
alias -l
|
||||
|
||||
With no parameters, displays a list of all current aliases.
|
||||
These are stored in the file %aliases (which you can edit
|
||||
with a text editor if you want).
|
||||
|
||||
Given two strings, 'alias' creates a new alias so that the
|
||||
first string, when used as a command, expands into the second
|
||||
string. If there are blanks in the second string, you need
|
||||
to put quotation marks around it. If the named alias already
|
||||
exists, 'alias' asks for permission to replace it.
|
||||
|
||||
Given -r and a single string, 'alias' removes an existing
|
||||
alias.
|
||||
|
||||
Creating or removing an alias does not automatically save it to
|
||||
disk. To save your aliases to %aliases, use 'alias -s'. (Note
|
||||
that if you create or remove an alias and use -s in the same
|
||||
command, the saving happens -after- any changes to your aliases.)
|
||||
|
||||
To re-load your aliases from %aliases, use 'alias -l'. Davex
|
||||
automatically loads aliases from there, so this is not normally
|
||||
needed.
|
||||
|
||||
See Davex.Doc for an explanation of aliases and a description
|
||||
of the pre-made aliases provided.
|
||||
|
|
|
|||
|
|
@ -1 +1,24 @@
|
|||
blist -- list a BAS file in ASCII (EXTERNAL) [v1.2]
syntax: blist <pathname> [-w <integer>]
ex: blist this
como &;blist ?:bas -w70
como edit.this;blist myprog
List a BAS file in readable form. Wildcards are allowed.
Intended for redirecting to a TXT file to allow editing with
a word processor. The edited file can then be EXECed in
BASIC.SYSTEM, turning it back into an Applesoft program
which can be SAVEd and RUN.
The -w option specifies the wrap margin. 'blist' will start
a new line and indent 6 spaces when this margin is hit, or
when a blank is printed within 10 columns of the margin.
If you are using 'blist' to send a listing to your printer,
you may need to use -w to prevent long lines from overprinting
themselves.
Version 1.2 fixes a spacing bug in REM and DATA statements that
didn't begin with a blank.
|
||||
|
||||
blist -- list a BAS file in ASCII (EXTERNAL) [v1.2]
|
||||
|
||||
syntax: blist <pathname> [-w <integer>]
|
||||
|
||||
ex: blist this
|
||||
como &;blist ?:bas -w70
|
||||
como edit.this;blist myprog
|
||||
|
||||
List a BAS file in readable form. Wildcards are allowed.
|
||||
Intended for redirecting to a TXT file to allow editing with
|
||||
a word processor. The edited file can then be EXECed in
|
||||
BASIC.SYSTEM, turning it back into an Applesoft program
|
||||
which can be SAVEd and RUN.
|
||||
|
||||
The -w option specifies the wrap margin. 'blist' will start
|
||||
a new line and indent 6 spaces when this margin is hit, or
|
||||
when a blank is printed within 10 columns of the margin.
|
||||
If you are using 'blist' to send a listing to your printer,
|
||||
you may need to use -w to prevent long lines from overprinting
|
||||
themselves.
|
||||
|
||||
Version 1.2 fixes a spacing bug in REM and DATA statements that
|
||||
didn't begin with a blank.
|
||||
|
|
|
|||
|
|
@ -1 +1,35 @@
|
|||
brun -- run a BIN file
syntax: brun pathname
ex: brun myprogram
'brun' is a SYS file that accepts a parameter (in its startup buffer).
The pathname must specify a BIN file. 'brun' will load and execute the
BIN file at its auxiliary type address. Many BIN files are intended
to be executed in a certain environment, such as BASIC.SYSTEM. 'brun'
is useful only for BIN files that do NOT expect an environment to be
set up for them. Kyan Pascal programs, for example, can be run with
'brun'.
Be careful! Not all BIN files are suitable for running with 'brun'.
If you're not sure if a particular BIN file will run OK or not,
write-protect your disks (turn off a hard drive, save RAM disks to
real disks, etc) before trying to run it.
If a ProDOS error occurs while 'brun' is loading the BIN file, a
two-digit error code is displayed, and you will be returned to
Davex (if you ran 'brun' from there) when you hit a key. To find
out what the error was, you can type "err $xx" from Davex.
If the specified file is not a BIN file, error $FF is reported.
Note: 'brun' with a last-modified date of 12-Dec-87 or later
supports BIN files that RTS or JMP to $3D0, $3D3, or $BE00 rather
than doing a ProDOS QUIT. Previous versions worked only with
BIN files that did a QUIT.
Also, 'brun' stores a BRK instruction at $BE03 and $BE70. If you
get dropped into the monitor at $BE03 or $BE70, the BIN file you
were trying to run probably requires BASIC.SYSTEM.
|
||||
|
||||
brun -- run a BIN file
|
||||
|
||||
syntax: brun pathname
|
||||
|
||||
ex: brun myprogram
|
||||
|
||||
'brun' is a SYS file that accepts a parameter (in its startup buffer).
|
||||
The pathname must specify a BIN file. 'brun' will load and execute the
|
||||
BIN file at its auxiliary type address. Many BIN files are intended
|
||||
to be executed in a certain environment, such as BASIC.SYSTEM. 'brun'
|
||||
is useful only for BIN files that do NOT expect an environment to be
|
||||
set up for them. Kyan Pascal programs, for example, can be run with
|
||||
'brun'.
|
||||
|
||||
Be careful! Not all BIN files are suitable for running with 'brun'.
|
||||
If you're not sure if a particular BIN file will run OK or not,
|
||||
write-protect your disks (turn off a hard drive, save RAM disks to
|
||||
real disks, etc) before trying to run it.
|
||||
|
||||
If a ProDOS error occurs while 'brun' is loading the BIN file, a
|
||||
two-digit error code is displayed, and you will be returned to
|
||||
Davex (if you ran 'brun' from there) when you hit a key. To find
|
||||
out what the error was, you can type "err $xx" from Davex.
|
||||
|
||||
If the specified file is not a BIN file, error $FF is reported.
|
||||
|
||||
Note: 'brun' with a last-modified date of 12-Dec-87 or later
|
||||
supports BIN files that RTS or JMP to $3D0, $3D3, or $BE00 rather
|
||||
than doing a ProDOS QUIT. Previous versions worked only with
|
||||
BIN files that did a QUIT.
|
||||
|
||||
Also, 'brun' stores a BRK instruction at $BE03 and $BE70. If you
|
||||
get dropped into the monitor at $BE03 or $BE70, the BIN file you
|
||||
were trying to run probably requires BASIC.SYSTEM.
|
||||
|
|
|
|||
|
|
@ -1 +1,19 @@
|
|||
boot -- boot the system
syntax: boot [-s<slotnum>] [-i]
ex: boot
boot -s6
Boots the system. If -s is given, boots from the specified
slot, which should contain a disk controller. Otherwise the
system scans for a startup device the same way it does at
power-up.
The -i option is meaningful only on a IIgs. If present, an ICE
COLD reboot is done, erasing everything in RAM (including /RAM5).
-s is ignored when -i is used. [NOTE--'boot -i' takes advantage
of an undocumented aspect of the keyboard microcontroller and is
NOT guarranteed to work in the future. Test it with any hardware
or system software upgrades before trusting it.]
|
||||
|
||||
boot -- boot the system
|
||||
|
||||
syntax: boot [-s<slotnum>] [-i]
|
||||
|
||||
ex: boot
|
||||
boot -s6
|
||||
|
||||
Boots the system. If -s is given, boots from the specified
|
||||
slot, which should contain a disk controller. Otherwise the
|
||||
system scans for a startup device the same way it does at
|
||||
power-up.
|
||||
|
||||
The -i option is meaningful only on a IIgs. If present, an ICE
|
||||
COLD reboot is done, erasing everything in RAM (including /RAM5).
|
||||
-s is ignored when -i is used. [NOTE--'boot -i' takes advantage
|
||||
of an undocumented aspect of the keyboard microcontroller and is
|
||||
NOT guarranteed to work in the future. Test it with any hardware
|
||||
or system software upgrades before trusting it.]
|
||||
|
|
|
|||
17
doc/help/Bye
17
doc/help/Bye
|
|
@ -1 +1,16 @@
|
|||
bye -- quit Davex
syntax: bye
ex: bye
Quits Davex. (Does a ProDOS QUIT to whatever Quit code was
in place when you entered Davex.) If you have different
copies of Davex in different directories, you can run one
copy from another one, and Quit will return you to the one
you were in previously.
(The old quit code is stored in %config when you enter
Davex. When you quit, it loads the old quit code from
%config, so you need to have your Davex disk online.)
|
||||
|
||||
bye -- quit Davex
|
||||
|
||||
syntax: bye
|
||||
|
||||
ex: bye
|
||||
|
||||
Quits Davex. (Does a ProDOS QUIT to whatever Quit code was
|
||||
in place when you entered Davex.) If you have different
|
||||
copies of Davex in different directories, you can run one
|
||||
copy from another one, and Quit will return you to the one
|
||||
you were in previously.
|
||||
|
||||
(The old quit code is stored in %config when you enter
|
||||
Davex. When you quit, it loads the old quit code from
|
||||
%config, so you need to have your Davex disk online.)
|
||||
|
|
|
|||
56
doc/help/Cat
56
doc/help/Cat
|
|
@ -1 +1,55 @@
|
|||
cat -- display directory
syntax: cat [pathname] [-t] [-s] [-f filetype] [-a sort_keys] [-i]
ex: cat
cat -a
cat /disk -it
cat -fbas
cat /mydisk -tfSYS
cat .62 -s
cat ?:dir
Displays the contents of the directory specified by pathname; wildcards are
allowed. (If no pathname is given, displays the contents of the current
directory.) The following options are available:
-t: tree format--show contents of directories indented under the directory
names
-i: show files and directories even if they are invisible (use the 'touch'
command to make a file visible or invisible)
-s: short form--display name and filetype only
-f: show only files of given type (if -t is given, DIRs are also shown)
-a: arrange--sort the listing according to the characters following '-a'.
If no characters follow, the listing is sorted alphabetically by
filename. The following sorting keys may be combined by listing the
most significant keys first. Capitalizing a letter reverses the order
of the sort on that key.
n: name (a to z)
m: modified date/time (newest to oldest)
f: filetype ($00 to $ff)
t: same as f
s: size in bytes (largest to smallest)
x: auxiliary type ($0000 to $ffff)
b: list files needing backup before files not needing backup
Examples:
cat -a
cat -an
arrange by name from a to z
cat -aN
arrange by name from z to a
cat -afX
arrange by increasing filetype and decreasing auxiliary type within
each filetype
Note that '-t' is ignored when '-a' is used.
|
||||
|
||||
cat -- display directory
|
||||
|
||||
syntax: cat [pathname] [-t] [-s] [-f filetype] [-a sort_keys] [-i]
|
||||
|
||||
ex: cat
|
||||
cat -a
|
||||
cat /disk -it
|
||||
cat -fbas
|
||||
cat /mydisk -tfSYS
|
||||
cat .62 -s
|
||||
cat ?:dir
|
||||
|
||||
Displays the contents of the directory specified by pathname; wildcards are
|
||||
allowed. (If no pathname is given, displays the contents of the current
|
||||
directory.) The following options are available:
|
||||
|
||||
-t: tree format--show contents of directories indented under the directory
|
||||
names
|
||||
|
||||
-i: show files and directories even if they are invisible (use the 'touch'
|
||||
command to make a file visible or invisible)
|
||||
|
||||
-s: short form--display name and filetype only
|
||||
|
||||
-f: show only files of given type (if -t is given, DIRs are also shown)
|
||||
|
||||
-a: arrange--sort the listing according to the characters following '-a'.
|
||||
If no characters follow, the listing is sorted alphabetically by
|
||||
filename. The following sorting keys may be combined by listing the
|
||||
most significant keys first. Capitalizing a letter reverses the order
|
||||
of the sort on that key.
|
||||
|
||||
n: name (a to z)
|
||||
m: modified date/time (newest to oldest)
|
||||
f: filetype ($00 to $ff)
|
||||
t: same as f
|
||||
s: size in bytes (largest to smallest)
|
||||
x: auxiliary type ($0000 to $ffff)
|
||||
b: list files needing backup before files not needing backup
|
||||
|
||||
Examples:
|
||||
|
||||
cat -a
|
||||
cat -an
|
||||
arrange by name from a to z
|
||||
|
||||
cat -aN
|
||||
arrange by name from z to a
|
||||
|
||||
cat -afX
|
||||
arrange by increasing filetype and decreasing auxiliary type within
|
||||
each filetype
|
||||
|
||||
Note that '-t' is ignored when '-a' is used.
|
||||
|
|
|
|||
14
doc/help/Cls
14
doc/help/Cls
|
|
@ -1 +1,13 @@
|
|||
cls -- clear screen
syntax: cls
ex: cls
como &;cls -- new page on printer
Clears the screen. If redirected to the printer, as in the
last example, begins a new page.
('cls' just outputs a Ctrl-L.)
|
||||
|
||||
cls -- clear screen
|
||||
|
||||
syntax: cls
|
||||
|
||||
ex: cls
|
||||
como &;cls -- new page on printer
|
||||
|
||||
Clears the screen. If redirected to the printer, as in the
|
||||
last example, begins a new page.
|
||||
|
||||
('cls' just outputs a Ctrl-L.)
|
||||
|
||||
|
|
|
|||
|
|
@ -1 +1,35 @@
|
|||
The following features are available during line input:
Ctrl-B = move to beginning of line
Ctrl-D = delete character at cursor
Ctrl-E/Ctrl-N = move to end of line
Ctrl-F = find forward; press ESC to exit
Ctrl-H (left arrow) = move left
Ctrl-I (tab) = insert (cancelled by arrows or Ctrl-D)
Ctrl-J (down arrow) = move down on the list of previous commands
Ctrl-K (up arrow) = move up on the list of previous commands
Ctrl-L = toggle Caps-lock on/off for Apple II+
Ctrl-M = return (accept whole line, even the part after the cursor)
Ctrl-O = if the following character is a control character, inserts it
(control characters can't normally be entered). If the
following character is "K" to "O" or "k" to "o", a special
character is inserted (useful only on the II+ keyboard):
K L M N O k l m n o
[ \ ] ^ _ { | } ~ DEL
Ctrl-Q = accept portion of line before cursor
Ctrl-R = re-edit previous input
Ctrl-U (right arrow) = move cursor right
Ctrl-X = cancel input
Ctrl-Y = erase from cursor to end of line
DELETE = erase character before cursor
Apple-< = move to beginning of line
Apple-> = move to end of line
Apple-E = switch between insert and overstrike ("exchange")
Apple-Y = erase from cursor to end of line (same as Ctrl-Y)
Apple-H = print hardcopy of screen
Apple-Space = advance printer one line
Apple-Return = advance printer to next page
|
||||
|
||||
The following features are available during line input:
|
||||
|
||||
Ctrl-B = move to beginning of line
|
||||
Ctrl-D = delete character at cursor
|
||||
Ctrl-E/Ctrl-N = move to end of line
|
||||
Ctrl-F = find forward; press ESC to exit
|
||||
Ctrl-H (left arrow) = move left
|
||||
Ctrl-I (tab) = insert (cancelled by arrows or Ctrl-D)
|
||||
Ctrl-J (down arrow) = move down on the list of previous commands
|
||||
Ctrl-K (up arrow) = move up on the list of previous commands
|
||||
Ctrl-L = toggle Caps-lock on/off for Apple II+
|
||||
Ctrl-M = return (accept whole line, even the part after the cursor)
|
||||
Ctrl-O = if the following character is a control character, inserts it
|
||||
(control characters can't normally be entered). If the
|
||||
following character is "K" to "O" or "k" to "o", a special
|
||||
character is inserted (useful only on the II+ keyboard):
|
||||
|
||||
K L M N O k l m n o
|
||||
[ \ ] ^ _ { | } ~ DEL
|
||||
|
||||
Ctrl-Q = accept portion of line before cursor
|
||||
Ctrl-R = re-edit previous input
|
||||
Ctrl-U (right arrow) = move cursor right
|
||||
Ctrl-X = cancel input
|
||||
Ctrl-Y = erase from cursor to end of line
|
||||
DELETE = erase character before cursor
|
||||
|
||||
Apple-< = move to beginning of line
|
||||
Apple-> = move to end of line
|
||||
Apple-E = switch between insert and overstrike ("exchange")
|
||||
Apple-Y = erase from cursor to end of line (same as Ctrl-Y)
|
||||
Apple-H = print hardcopy of screen
|
||||
Apple-Space = advance printer one line
|
||||
Apple-Return = advance printer to next page
|
||||
|
|
|
|||
|
|
@ -1 +1,46 @@
|
|||
combine -- combine files together (EXTERNAL) [v1.0]
Written by Jeff Ding
syntax: combine <input pathname1> [<input pathname2..5>]
[-o<output pathname>] [-w<margin>]
ex: combine text -m60
combine game.part1 game.part2 game.3 -o game
combine =.header =.doc -o documents
'Combine' combines files together. The input file is always appended to
the output file. A total of 5 input files on the same command line is
supported. Wildcards are supported in the first two input files only.
When using an output pathname, it is sometimes useful to use a wildcard in
the input pathname. This allows you to append several files onto one
output pathname.
A special case happens when using two wildcards in the input files. The
text matching the first wildcard is substituted into the second wildcard.
This makes it possible to include a special header or footer file for each
actual input file. The third example above demonstrates the use of a
header file.
Combine will work with any file type, but the files are treated only
as raw collections of bytes. This means, for example, that if you
combine two complete AWP files you will get a big mess. However,
you can always use 'combine' to reconstruct files that have been
split up using 'split'.
Options are as follows:
-o <pathname>: Copy of input file gets saved to this file. If
not specified, output goes to the screen. If the
file exists, the data will be appended and the type
not modified. If the output file does not exist,
it will be created with the same type as the original
file.
-w <margin>: wrap margin. Affects output to the screen only. This
forces a carriage return when either the margin or
a space within 9 characters of the margin is reached.
Allowed values are 0 through 255. A 0 value has the
same effect as not using the option.
(see also: split)
|
||||
|
||||
combine -- combine files together (EXTERNAL) [v1.0]
|
||||
Written by Jeff Ding
|
||||
|
||||
syntax: combine <input pathname1> [<input pathname2..5>]
|
||||
[-o<output pathname>] [-w<margin>]
|
||||
|
||||
ex: combine text -m60
|
||||
combine game.part1 game.part2 game.3 -o game
|
||||
combine =.header =.doc -o documents
|
||||
|
||||
'Combine' combines files together. The input file is always appended to
|
||||
the output file. A total of 5 input files on the same command line is
|
||||
supported. Wildcards are supported in the first two input files only.
|
||||
When using an output pathname, it is sometimes useful to use a wildcard in
|
||||
the input pathname. This allows you to append several files onto one
|
||||
output pathname.
|
||||
|
||||
A special case happens when using two wildcards in the input files. The
|
||||
text matching the first wildcard is substituted into the second wildcard.
|
||||
This makes it possible to include a special header or footer file for each
|
||||
actual input file. The third example above demonstrates the use of a
|
||||
header file.
|
||||
|
||||
Combine will work with any file type, but the files are treated only
|
||||
as raw collections of bytes. This means, for example, that if you
|
||||
combine two complete AWP files you will get a big mess. However,
|
||||
you can always use 'combine' to reconstruct files that have been
|
||||
split up using 'split'.
|
||||
|
||||
Options are as follows:
|
||||
|
||||
-o <pathname>: Copy of input file gets saved to this file. If
|
||||
not specified, output goes to the screen. If the
|
||||
file exists, the data will be appended and the type
|
||||
not modified. If the output file does not exist,
|
||||
it will be created with the same type as the original
|
||||
file.
|
||||
|
||||
-w <margin>: wrap margin. Affects output to the screen only. This
|
||||
forces a carriage return when either the margin or
|
||||
a space within 9 characters of the margin is reached.
|
||||
Allowed values are 0 through 255. A 0 value has the
|
||||
same effect as not using the option.
|
||||
|
||||
(see also: split)
|
||||
|
|
|
|||
170
doc/help/ConP
170
doc/help/ConP
File diff suppressed because one or more lines are too long
|
|
@ -1 +1,57 @@
|
|||
config -- display or change Davex configuration
syntax: config [-p slot] [-b y|n] [-4 y|n] [-c y|n]
[-h string] [-q integer]
ex: config -- show current settings
config -p1 -- printer slot 1
config -by -- use system bell
config -p7 -bn -- printer slot 7, "blat" bell
config -4n -cy -- 80 columns, show IIgs clock
config -h .62help -- set location of help directory
config -q2 -- don't print "welcome" message
'config' with no parameters displays the current values of all options
that you can set with this command.
The -p option sets the default printer slot. This slot number is used
when you specify "&" as the pathname for a "como" or ">" command. Also,
'spool' and Apple-H (hardcopy of screen) always print to the slot you
set with 'config'.
-b is a yes/no option that determines whether the system beep will be
used. If -bn is given, the standard ProDOS buzz is used. IIgs users
especially may want to use -by, since the pitch is configurable through
the control panel (or through the 'conp' external command).
-4 is a yes/no option. When set to yes, it restricts your display to
40 columns (while in Davex) even if you have an 80-column card. Note
that some things are not formatted well in 40 columns--most notably, the
help files. (The new display setting takes effect when you hit RESET or
re-enter Davex.)
-c is a yes/no option that has effect only on an Apple IIgs. When set
to Yes, the date and time that appear when you hit Return without typing
a command will include seconds and will be in the format you have selected
in the Control Panel.
-h sets the pathname of the Help directory. The default is "%help". The
string can be a full pathname, or it can start with "%" or with a slot/
drive specification (ex: ".62help"). This option is useful if several
people are running Davex from separate directories on the same hard drive
and want to keep just one copy of the help files.
-q controls whether the "welcome" message is printed when you enter Davex.
The default is 0, and the message is always printed. Set to 2 and the
message will not be printed; set to 1 and it will be printed only if no
speech synthesizer is being used.
IIgs users: If your machine is on an AppleTalk network with a LaserWriter
and you have the appropriate files in your SYSTEM/SYSTEM.SETUP directory
and you have run CHOOSER.II (supplied on your system disk) to download the
ImageWriter emulator to the LaserWriter, you can treat the LaserWriter as an
ImageWriter in slot 7. (Slot 7 must be set to "Built-in Appletalk," not
"Your card.")
(see also: como, spool)
|
||||
|
||||
config -- display or change Davex configuration
|
||||
|
||||
syntax: config [-p slot] [-b y|n] [-4 y|n] [-c y|n]
|
||||
[-h string] [-q integer]
|
||||
|
||||
ex: config -- show current settings
|
||||
config -p1 -- printer slot 1
|
||||
config -by -- use system bell
|
||||
config -p7 -bn -- printer slot 7, "blat" bell
|
||||
config -4n -cy -- 80 columns, show IIgs clock
|
||||
config -h .62help -- set location of help directory
|
||||
config -q2 -- don't print "welcome" message
|
||||
|
||||
'config' with no parameters displays the current values of all options
|
||||
that you can set with this command.
|
||||
|
||||
The -p option sets the default printer slot. This slot number is used
|
||||
when you specify "&" as the pathname for a "como" or ">" command. Also,
|
||||
'spool' and Apple-H (hardcopy of screen) always print to the slot you
|
||||
set with 'config'.
|
||||
|
||||
-b is a yes/no option that determines whether the system beep will be
|
||||
used. If -bn is given, the standard ProDOS buzz is used. IIgs users
|
||||
especially may want to use -by, since the pitch is configurable through
|
||||
the control panel (or through the 'conp' external command).
|
||||
|
||||
-4 is a yes/no option. When set to yes, it restricts your display to
|
||||
40 columns (while in Davex) even if you have an 80-column card. Note
|
||||
that some things are not formatted well in 40 columns--most notably, the
|
||||
help files. (The new display setting takes effect when you hit RESET or
|
||||
re-enter Davex.)
|
||||
|
||||
-c is a yes/no option that has effect only on an Apple IIgs. When set
|
||||
to Yes, the date and time that appear when you hit Return without typing
|
||||
a command will include seconds and will be in the format you have selected
|
||||
in the Control Panel.
|
||||
|
||||
-h sets the pathname of the Help directory. The default is "%help". The
|
||||
string can be a full pathname, or it can start with "%" or with a slot/
|
||||
drive specification (ex: ".62help"). This option is useful if several
|
||||
people are running Davex from separate directories on the same hard drive
|
||||
and want to keep just one copy of the help files.
|
||||
|
||||
-q controls whether the "welcome" message is printed when you enter Davex.
|
||||
The default is 0, and the message is always printed. Set to 2 and the
|
||||
message will not be printed; set to 1 and it will be printed only if no
|
||||
speech synthesizer is being used.
|
||||
|
||||
IIgs users: If your machine is on an AppleTalk network with a LaserWriter
|
||||
and you have the appropriate files in your SYSTEM/SYSTEM.SETUP directory
|
||||
and you have run CHOOSER.II (supplied on your system disk) to download the
|
||||
ImageWriter emulator to the LaserWriter, you can treat the LaserWriter as an
|
||||
ImageWriter in slot 7. (Slot 7 must be set to "Built-in Appletalk," not
|
||||
"Your card.")
|
||||
|
||||
(see also: como, spool)
|
||||
|
|
|
|||
|
|
@ -1 +1,41 @@
|
|||
copy -- copy files or directories
syntax: copy <pathname1> <pathname2> [-f] [-d] [-b]
ex: copy thing /otherdisk/blah
copy this /backup
copy %= /backup/= -fb
copy /system.disk/system /ram5/system
Copies files from first path to second path. Unless -f
(force) is given, ask for permission to replace the old
copy. If the old file is LOCKED (access is not "rwnd"),
copy asks for permission even if you use -f.
-d deletes the original after a successful copy. -b clears
the backup bit of the original after a successful copy.
If the first pathname refers to a file and the second
pathname refers to a directory, 'copy' puts the file INTO
the directory. (It does not replace the directory with the
file.)
If you omit the second pathname completely, 'copy' behaves
as though you supplied the current prefix. Result: "copy
pathname" copies a file into the current directory, using
the original file's filename.
If the first pathname refers to a DIRECTORY, the directory
and everything in it (files and/or directories) is copied to
the second pathname. The second pathname must not refer to
an existing directory ("ProDOS error: duplicate file" results).
'copy' will copy sparse files, but the new files will no
longer be sparse.
'copy' can't copy extended files (storage type 5). You get
a "bad storage type" error for trying. (Extended files have
two forks and are created under GS/OS.)
(see also: update)
|
||||
|
||||
copy -- copy files or directories
|
||||
|
||||
syntax: copy <pathname1> <pathname2> [-f] [-d] [-b]
|
||||
|
||||
ex: copy thing /otherdisk/blah
|
||||
copy this /backup
|
||||
copy %= /backup/= -fb
|
||||
copy /system.disk/system /ram5/system
|
||||
|
||||
Copies files from first path to second path. Unless -f
|
||||
(force) is given, ask for permission to replace the old
|
||||
copy. If the old file is LOCKED (access is not "rwnd"),
|
||||
copy asks for permission even if you use -f.
|
||||
|
||||
-d deletes the original after a successful copy. -b clears
|
||||
the backup bit of the original after a successful copy.
|
||||
|
||||
If the first pathname refers to a file and the second
|
||||
pathname refers to a directory, 'copy' puts the file INTO
|
||||
the directory. (It does not replace the directory with the
|
||||
file.)
|
||||
|
||||
If you omit the second pathname completely, 'copy' behaves
|
||||
as though you supplied the current prefix. Result: "copy
|
||||
pathname" copies a file into the current directory, using
|
||||
the original file's filename.
|
||||
|
||||
If the first pathname refers to a DIRECTORY, the directory
|
||||
and everything in it (files and/or directories) is copied to
|
||||
the second pathname. The second pathname must not refer to
|
||||
an existing directory ("ProDOS error: duplicate file" results).
|
||||
|
||||
'copy' will copy sparse files, but the new files will no
|
||||
longer be sparse.
|
||||
|
||||
'copy' can't copy extended files (storage type 5). You get
|
||||
a "bad storage type" error for trying. (Extended files have
|
||||
two forks and are created under GS/OS.)
|
||||
|
||||
(see also: update)
|
||||
|
|
|
|||
|
|
@ -1 +1,11 @@
|
|||
create -- create a directory or other file
syntax: create <path>[:<filetype>]
ex: create mydir
create myfile:sys
create something:bad
Creates a file with the given filetype or, if no filetype is
given, of type DIR.
|
||||
|
||||
create -- create a directory or other file
|
||||
|
||||
syntax: create <path>[:<filetype>]
|
||||
|
||||
ex: create mydir
|
||||
create myfile:sys
|
||||
create something:bad
|
||||
|
||||
Creates a file with the given filetype or, if no filetype is
|
||||
given, of type DIR.
|
||||
|
|
|
|||
|
|
@ -1 +1,23 @@
|
|||
doscat -- catalog a DOS 3.3 disk (EXTERNAL)
by Kevin Cooper and Dave Lyons
syntax: doscat <device> [-v] [-f filetypes] [-l y|n] [-o string]
ex: doscat .61
doscat .62 -v -fTA -ly
'doscat' displays the catalog listing of a 5.25" DOS 3.3 disk.
-v stops the volume number from appearing.
-f restricts the listing to files of the specified types (the
eight possible filetypes are called T, I, A, B, S, R, X, and Y).
-ly ("locked yes") restricts the listing to files that are locked,
and -ln ("locked no") restricts the listing to files that are
not locked.
-o takes a string and prints it for each filename selected,
substituting the filename for all "=" signs in the string.
See "help =" to see how this can be useful.
|
||||
|
||||
doscat -- catalog a DOS 3.3 disk (EXTERNAL)
|
||||
by Kevin Cooper and Dave Lyons
|
||||
|
||||
syntax: doscat <device> [-v] [-f filetypes] [-l y|n] [-o string]
|
||||
|
||||
ex: doscat .61
|
||||
doscat .62 -v -fTA -ly
|
||||
|
||||
'doscat' displays the catalog listing of a 5.25" DOS 3.3 disk.
|
||||
|
||||
-v stops the volume number from appearing.
|
||||
|
||||
-f restricts the listing to files of the specified types (the
|
||||
eight possible filetypes are called T, I, A, B, S, R, X, and Y).
|
||||
|
||||
-ly ("locked yes") restricts the listing to files that are locked,
|
||||
and -ln ("locked no") restricts the listing to files that are
|
||||
not locked.
|
||||
|
||||
-o takes a string and prints it for each filename selected,
|
||||
substituting the filename for all "=" signs in the string.
|
||||
See "help =" to see how this can be useful.
|
||||
|
|
|
|||
14
doc/help/DT
14
doc/help/DT
|
|
@ -1 +1,13 @@
|
|||
dt -- print date and time (if available)
syntax: dt
ex: dt
como %log;dt
Prints date and time. This is fairly useless used alone,
since you can get the same information by just hitting
RETURN. But it may be handy if output is redirected. The
second example above, if placed in %AUTOEXEC, will keep a
log of all times Davex was entered.
|
||||
|
||||
dt -- print date and time (if available)
|
||||
|
||||
syntax: dt
|
||||
|
||||
ex: dt
|
||||
como %log;dt
|
||||
|
||||
Prints date and time. This is fairly useless used alone,
|
||||
since you can get the same information by just hitting
|
||||
RETURN. But it may be handy if output is redirected. The
|
||||
second example above, if placed in %AUTOEXEC, will keep a
|
||||
log of all times Davex was entered.
|
||||
|
|
|
|||
21
doc/help/DU
21
doc/help/DU
|
|
@ -1 +1,20 @@
|
|||
du -- summarize disk usage (EXTERNAL) [v1.4]
syntax: du [pathname]
ex: du
du /mydisk
du .61
du %
When used without the optional pathname, 'du' prints a table showing
K free and percent used for all online volumes; then totals the K
free and % used and prints the number of volumes online.
If a pathname is given, du prints the name of the volume specified
in the pathname; then it prints the number of free blocks, used
blocks, and total blocks on the volume.
Note that a "K" is 1024 bytes (characters) of storage space, which is
the same as 2 blocks on a ProDOS disk; a block is 512 bytes.
|
||||
|
||||
du -- summarize disk usage (EXTERNAL) [v1.4]
|
||||
|
||||
syntax: du [pathname]
|
||||
|
||||
ex: du
|
||||
du /mydisk
|
||||
du .61
|
||||
du %
|
||||
|
||||
When used without the optional pathname, 'du' prints a table showing
|
||||
K free and percent used for all online volumes; then totals the K
|
||||
free and % used and prints the number of volumes online.
|
||||
|
||||
If a pathname is given, du prints the name of the volume specified
|
||||
in the pathname; then it prints the number of free blocks, used
|
||||
blocks, and total blocks on the volume.
|
||||
|
||||
Note that a "K" is 1024 bytes (characters) of storage space, which is
|
||||
the same as 2 blocks on a ProDOS disk; a block is 512 bytes.
|
||||
|
|
|
|||
|
|
@ -1 +1,70 @@
|
|||
date -- interactive date and time setting program (EXTERNAL) [v1.2]
Written by Jeff Ding
syntax: date [-p] {[-s] [-d] [-t]} [-f<pathname>]
ex: date
date -p
date -s -t
date -s -t -f"%time.stamp"
'Date' is a program to set the date and time of your computer if you do
not have a clock built in to your computer. This program will not change
the date on your clock but only change the bytes in ProDOS. This program
was designed to be included in the %autoexec file. For example, add the
following line to your file: "date -s." See below for the explanation of
the -s option.
With no options, 'date' will print the current date and time and ask for
the new date and the new time. The format for the date is DD-MMM-YY. The
format for the time is HH:MM in 24 hour format. If the date or time is
entered incorrectly, or you just press return when prompted, 'date' will not
change the current values. Options are as follows:
-p: print only -- When this option is used, 'date' will only print
the date and time currently on the system.
-s: set date/time only if not already set -- This option will only
prompt you to set the date and time if the date and time have not
already been set. This option is useful in the %autoexec startup
file. You will be prompted once on bootup to set the date and time.
When you re-enter Davex after quitting from an application, 'date'
will not ask you to change the date since you already set it on
bootup.
-d: date -- Use this option in conjunction with the -s option.
This will force the program to always set the date even if the
date has already been set. Time setting remains the same as
with the -s option.
-t: time -- Use this option in conjunction with the -s option.
This will force the program to always set the time even if the
time has already been set. Date setting remains the same as
with the -s option.
-f: get date/time stamp from file -- This option will set your system's
date and time equal to the last modification date and time field
from the file given after the option. This option is only effective
when the date and time is not set. Use this option in your autoexec
file to set the your system time on bootup. Example autoexec file:
date -s -t -f"%time.stamp"
touch %time.stamp
The first line will grab the time from the file "time.stamp" in the
Davex directory when first booting up the computer. Every time you
rerun Davex after exiting from a sys program, you will be prompted
to change only the time. The second line keeps the date current
on the file "time.stamp" so it reads in the most current date when
you reboot the computer.
Notes: If the -p option is included along with the -s option, 'date' will
ignore the -s option and only print the date and time.
When you use the -t option and the newly entered hour is less
than the current hour, 'date' version 1.2 will increment the
date by one day, changing the month and year if necessary.
The command 'date -s -d -t' performs the same functions as the
command 'date' with no options.
|
||||
|
||||
date -- interactive date and time setting program (EXTERNAL) [v1.2]
|
||||
Written by Jeff Ding
|
||||
|
||||
syntax: date [-p] {[-s] [-d] [-t]} [-f<pathname>]
|
||||
|
||||
ex: date
|
||||
date -p
|
||||
date -s -t
|
||||
date -s -t -f"%time.stamp"
|
||||
|
||||
'Date' is a program to set the date and time of your computer if you do
|
||||
not have a clock built in to your computer. This program will not change
|
||||
the date on your clock but only change the bytes in ProDOS. This program
|
||||
was designed to be included in the %autoexec file. For example, add the
|
||||
following line to your file: "date -s." See below for the explanation of
|
||||
the -s option.
|
||||
|
||||
With no options, 'date' will print the current date and time and ask for
|
||||
the new date and the new time. The format for the date is DD-MMM-YY. The
|
||||
format for the time is HH:MM in 24 hour format. If the date or time is
|
||||
entered incorrectly, or you just press return when prompted, 'date' will not
|
||||
change the current values. Options are as follows:
|
||||
|
||||
-p: print only -- When this option is used, 'date' will only print
|
||||
the date and time currently on the system.
|
||||
|
||||
-s: set date/time only if not already set -- This option will only
|
||||
prompt you to set the date and time if the date and time have not
|
||||
already been set. This option is useful in the %autoexec startup
|
||||
file. You will be prompted once on bootup to set the date and time.
|
||||
When you re-enter Davex after quitting from an application, 'date'
|
||||
will not ask you to change the date since you already set it on
|
||||
bootup.
|
||||
|
||||
-d: date -- Use this option in conjunction with the -s option.
|
||||
This will force the program to always set the date even if the
|
||||
date has already been set. Time setting remains the same as
|
||||
with the -s option.
|
||||
|
||||
-t: time -- Use this option in conjunction with the -s option.
|
||||
This will force the program to always set the time even if the
|
||||
time has already been set. Date setting remains the same as
|
||||
with the -s option.
|
||||
|
||||
-f: get date/time stamp from file -- This option will set your system's
|
||||
date and time equal to the last modification date and time field
|
||||
from the file given after the option. This option is only effective
|
||||
when the date and time is not set. Use this option in your autoexec
|
||||
file to set the your system time on bootup. Example autoexec file:
|
||||
|
||||
date -s -t -f"%time.stamp"
|
||||
touch %time.stamp
|
||||
|
||||
The first line will grab the time from the file "time.stamp" in the
|
||||
Davex directory when first booting up the computer. Every time you
|
||||
rerun Davex after exiting from a sys program, you will be prompted
|
||||
to change only the time. The second line keeps the date current
|
||||
on the file "time.stamp" so it reads in the most current date when
|
||||
you reboot the computer.
|
||||
|
||||
Notes: If the -p option is included along with the -s option, 'date' will
|
||||
ignore the -s option and only print the date and time.
|
||||
|
||||
When you use the -t option and the newly entered hour is less
|
||||
than the current hour, 'date' version 1.2 will increment the
|
||||
date by one day, changing the month and year if necessary.
|
||||
|
||||
The command 'date -s -d -t' performs the same functions as the
|
||||
command 'date' with no options.
|
||||
|
|
|
|||
|
|
@ -1 +1,20 @@
|
|||
delete -- destroy files or directories
syntax: delete <pathname> [-u]
ex: delete this
delete =.0 -u
delete ?:dir
Permanently destroys the specified file or directory. Wildcards
are allowed.
Before destroying a directory, the 'size' command is automatically
used to compute the total size of the directory and everything in
it, and you are given a chance NOT to destroy the directory.
-u unlocks a file before trying to destroy it. When deleting a
directory, -u unlocks each file before it is destroyed; otherwise
any locked file in a directory will cause delete to stop with only
some of the files deleted.
|
||||
|
||||
delete -- destroy files or directories
|
||||
|
||||
syntax: delete <pathname> [-u]
|
||||
|
||||
ex: delete this
|
||||
delete =.0 -u
|
||||
delete ?:dir
|
||||
|
||||
Permanently destroys the specified file or directory. Wildcards
|
||||
are allowed.
|
||||
|
||||
Before destroying a directory, the 'size' command is automatically
|
||||
used to compute the total size of the directory and everything in
|
||||
it, and you are given a chance NOT to destroy the directory.
|
||||
|
||||
-u unlocks a file before trying to destroy it. When deleting a
|
||||
directory, -u unlocks each file before it is destroyed; otherwise
|
||||
any locked file in a directory will cause delete to stop with only
|
||||
some of the files deleted.
|
||||
|
|
|
|||
|
|
@ -1 +1,30 @@
|
|||
deschw -- describe hardware (EXTERNAL) [v1.2]
syntax: deschw [-c] [-s] [-t]
ex: deschw
deschw -t
deschw -ct
deschw -s
Describes system hardware. Giving no options has the same
effect as giving them all.
-t displays the system type. Possible types are:
Apple IIgs; ROM version $xx [Machine ID = $xx]
(reports total RAM, too)
Apple IIe (enhanced)
Apple IIe (unenhanced)
Apple ][+
Apple /// (in emulation mode)
Apple IIc (version 1: original)
Apple IIc (version 2: 3.5" disk ROM)
Apple IIc (version 3: memory expandable)
Apple IIc (version 4: revised mem. expandable)
Apple IIc Plus
-c tries to identify the cards (and/or ports) in your system.
-s displays information about all SmartPort (=Protocol Converter)
cards/ports in your system, and all devices in their chains.
|
||||
|
||||
deschw -- describe hardware (EXTERNAL) [v1.2]
|
||||
|
||||
syntax: deschw [-c] [-s] [-t]
|
||||
|
||||
ex: deschw
|
||||
deschw -t
|
||||
deschw -ct
|
||||
deschw -s
|
||||
|
||||
Describes system hardware. Giving no options has the same
|
||||
effect as giving them all.
|
||||
|
||||
-t displays the system type. Possible types are:
|
||||
Apple IIgs; ROM version $xx [Machine ID = $xx]
|
||||
(reports total RAM, too)
|
||||
Apple IIe (enhanced)
|
||||
Apple IIe (unenhanced)
|
||||
Apple ][+
|
||||
Apple /// (in emulation mode)
|
||||
Apple IIc (version 1: original)
|
||||
Apple IIc (version 2: 3.5" disk ROM)
|
||||
Apple IIc (version 3: memory expandable)
|
||||
Apple IIc (version 4: revised mem. expandable)
|
||||
Apple IIc Plus
|
||||
|
||||
-c tries to identify the cards (and/or ports) in your system.
|
||||
|
||||
-s displays information about all SmartPort (=Protocol Converter)
|
||||
cards/ports in your system, and all devices in their chains.
|
||||
|
|
|
|||
24
doc/help/Dev
24
doc/help/Dev
|
|
@ -1 +1,23 @@
|
|||
dev -- list, add, or remove ProDOS devices
syntax: dev [-r<devnum>] [-a<devnum>] [-z]
ex: dev
dev -z
dev -r.62
dev -a.32
With no options, prints list of device numbers ProDOS scans
when looking for an unknown volume. With -r, removes the
specified device from the list. With -a, adds the specified
device to the list.
-z (zap) scans all devices in the device list and REMOVES
the ones that don't have ProDOS volumes mounted. This is
especially useful if you have Disk IIs that you will not use
for a while. (The next time you re-enter ProDOS 8, all your
disk devices will again be present in ProDOS's scan list.)
Note: with -a, the low nybble of the device number is
always set to 0. This is not usually a problem.
|
||||
|
||||
dev -- list, add, or remove ProDOS devices
|
||||
|
||||
syntax: dev [-r<devnum>] [-a<devnum>] [-z]
|
||||
|
||||
ex: dev
|
||||
dev -z
|
||||
dev -r.62
|
||||
dev -a.32
|
||||
|
||||
With no options, prints list of device numbers ProDOS scans
|
||||
when looking for an unknown volume. With -r, removes the
|
||||
specified device from the list. With -a, adds the specified
|
||||
device to the list.
|
||||
|
||||
-z (zap) scans all devices in the device list and REMOVES
|
||||
the ones that don't have ProDOS volumes mounted. This is
|
||||
especially useful if you have Disk IIs that you will not use
|
||||
for a while. (The next time you re-enter ProDOS 8, all your
|
||||
disk devices will again be present in ProDOS's scan list.)
|
||||
|
||||
Note: with -a, the low nybble of the device number is
|
||||
always set to 0. This is not usually a problem.
|
||||
|
|
|
|||
|
|
@ -1 +1,31 @@
|
|||
dump -- display file contents in hex/ASCII (EXTERNAL) [v1.2]
syntax: dump <pathname> [-a] [-h] [-o] [-s <start_pos>] [-e <end_pos>]
ex: dump that.file
dump ?:sys -o
dump my.file -s$100 -e512
'dump' displays the contents of a file in hex and/or ASCII. Wildcards
are allowed.
-h display in hex
-a display in ASCII
If neither -h nor -a is given, the dump is in BOTH hex and ASCII.
Non-printable characters in the ASCII dump are displayed as periods.
Each line begins with an "offset" in hex from the beginning of the
file (the first byte has offset 0). Use -o to stop the offsets from
appearing.
You can use the -s option to begin the dump somewhere other than the
beginning of the file (offset 0), and you can use -e to end the dump
somewhere other than the end of the file.
Note: 'dump' is useful for looking at the exact contents of
directories (both subdirectories and volume directories),
not just for standard files. (This is no extra work for
'dump'; ProDOS simply allows directories to be opened and
read the same way as other files.)
|
||||
|
||||
dump -- display file contents in hex/ASCII (EXTERNAL) [v1.2]
|
||||
|
||||
syntax: dump <pathname> [-a] [-h] [-o] [-s <start_pos>] [-e <end_pos>]
|
||||
|
||||
ex: dump that.file
|
||||
dump ?:sys -o
|
||||
dump my.file -s$100 -e512
|
||||
|
||||
'dump' displays the contents of a file in hex and/or ASCII. Wildcards
|
||||
are allowed.
|
||||
|
||||
-h display in hex
|
||||
-a display in ASCII
|
||||
|
||||
If neither -h nor -a is given, the dump is in BOTH hex and ASCII.
|
||||
Non-printable characters in the ASCII dump are displayed as periods.
|
||||
|
||||
Each line begins with an "offset" in hex from the beginning of the
|
||||
file (the first byte has offset 0). Use -o to stop the offsets from
|
||||
appearing.
|
||||
|
||||
You can use the -s option to begin the dump somewhere other than the
|
||||
beginning of the file (offset 0), and you can use -e to end the dump
|
||||
somewhere other than the end of the file.
|
||||
|
||||
Note: 'dump' is useful for looking at the exact contents of
|
||||
directories (both subdirectories and volume directories),
|
||||
not just for standard files. (This is no extra work for
|
||||
'dump'; ProDOS simply allows directories to be opened and
|
||||
read the same way as other files.)
|
||||
|
|
|
|||
|
|
@ -1 +1,31 @@
|
|||
echo -- echo string to output
syntax: echo <string> [-n]
ex: echo "This is a test of ECHO"
como %n;echo "Don't forget to feed the dog!"
echo "scan -a" -n; = %
'echo' just outputs the same string you give it. The -n
option prevents a carriage-return from being printed after
the string.
'echo' is useful only when output is redirected to a file
or to a printer. For example, if your %autoexec file
contains "pg %n", you can use
como %n;echo "text here"
to record a message you will see whenever you enter the
shell. If you do something like that, you may want to
create an alias called "note" (for example) that stands
for
como %n;echo "
This alias could be used like this:
note Finish report for saturday!
[No closing quote is necessary.]
(see also: como, alias)
|
||||
|
||||
echo -- echo string to output
|
||||
|
||||
syntax: echo <string> [-n]
|
||||
|
||||
ex: echo "This is a test of ECHO"
|
||||
como %n;echo "Don't forget to feed the dog!"
|
||||
echo "scan -a" -n; = %
|
||||
|
||||
'echo' just outputs the same string you give it. The -n
|
||||
option prevents a carriage-return from being printed after
|
||||
the string.
|
||||
|
||||
'echo' is useful only when output is redirected to a file
|
||||
or to a printer. For example, if your %autoexec file
|
||||
contains "pg %n", you can use
|
||||
|
||||
como %n;echo "text here"
|
||||
|
||||
to record a message you will see whenever you enter the
|
||||
shell. If you do something like that, you may want to
|
||||
create an alias called "note" (for example) that stands
|
||||
for
|
||||
como %n;echo "
|
||||
|
||||
This alias could be used like this:
|
||||
note Finish report for saturday!
|
||||
|
||||
[No closing quote is necessary.]
|
||||
|
||||
(see also: como, alias)
|
||||
|
|
|
|||
|
|
@ -1 +1,19 @@
|
|||
eject -- eject a volume or all volumes from SmartPort
syntax: eject [pathname]
ex: eject
eject /mydisk
eject .52
Ejects the specified 3.5" volume from a UniDisk 3.5 or Apple
3.5 drive. If no volume name is given, all 3.5" disks are
ejected.
Note that the parameter is a PATHNAME, so a command like
"eject .52" makes Davex try to find the name of the volume in
slot 5, drive 2 before searching all drives to find that volume.
So 'eject' will not help you eject individual non-ProDOS disks
or individual plastic shipping disks.
|
||||
|
||||
eject -- eject a volume or all volumes from SmartPort
|
||||
|
||||
syntax: eject [pathname]
|
||||
|
||||
ex: eject
|
||||
eject /mydisk
|
||||
eject .52
|
||||
|
||||
Ejects the specified 3.5" volume from a UniDisk 3.5 or Apple
|
||||
3.5 drive. If no volume name is given, all 3.5" disks are
|
||||
ejected.
|
||||
|
||||
Note that the parameter is a PATHNAME, so a command like
|
||||
"eject .52" makes Davex try to find the name of the volume in
|
||||
slot 5, drive 2 before searching all drives to find that volume.
|
||||
So 'eject' will not help you eject individual non-ProDOS disks
|
||||
or individual plastic shipping disks.
|
||||
|
||||
|
|
|
|||
|
|
@ -1 +1,50 @@
|
|||
= -- print a complete pathname or a string built from a template
syntax: = <pathname> [<template>]
ex: = %
= xyz
como my.list;= =:bas
= .61prodos
Prints a complete pathname. Wildcards are allowed. The
first example prints the pathname of the Davex directory.
The second builds a complete pathname by appending the given
partial path to the current prefix. The third prints, into
a file called "my.list", complete pathnames for all BAS
files in the current directory. The fourth prints the
pathname of a file PRODOS in slot 6, drive 1.
When '=' is used without wildcards, as in the fourth
example, files with the printed pathnames do not necessarily
exist.
The Power of Templates
When the second parameter is given, wildcard expansion still takes
place on the first parameter, but the _second_ parameter is printed,
once all wildcard characters have been replaced.
Suppose you want to use the "blist" external command to list a group
of BAS files into TXT files with corresponding names in another
directory.
como cmd.file;= ?:bas "como /disk/listings/=;blist ="
If this looks complicated, don't worry--it is. First, ">" is used to
redirect output to the file "cmd.file"--we are building a list of
commands to be executed with "exec cmd.file" later. The rest of the line
is a single use of the "=" command. The first parameter is "?:bas"--so
you are prompted yes or no for each bas file. For the ones you respond
Yes to, a string is printed to cmd.file. The string is bulit from the
third parameter to "=", which is "como /disk/listings/=;blist =".
Suppose you responded Yes to three files: grapes, apples, and banjos.
Then cmd.file would contain the following:
como /disk/listings/grapes;blist grapes
como /disk/listings/apples;blist apples
como /disk/listings/banjos;blist banjos
|
||||
|
||||
= -- print a complete pathname or a string built from a template
|
||||
|
||||
syntax: = <pathname> [<template>]
|
||||
|
||||
ex: = %
|
||||
= xyz
|
||||
como my.list;= =:bas
|
||||
= .61prodos
|
||||
|
||||
Prints a complete pathname. Wildcards are allowed. The
|
||||
first example prints the pathname of the Davex directory.
|
||||
The second builds a complete pathname by appending the given
|
||||
partial path to the current prefix. The third prints, into
|
||||
a file called "my.list", complete pathnames for all BAS
|
||||
files in the current directory. The fourth prints the
|
||||
pathname of a file PRODOS in slot 6, drive 1.
|
||||
|
||||
When '=' is used without wildcards, as in the fourth
|
||||
example, files with the printed pathnames do not necessarily
|
||||
exist.
|
||||
|
||||
|
||||
The Power of Templates
|
||||
|
||||
When the second parameter is given, wildcard expansion still takes
|
||||
place on the first parameter, but the _second_ parameter is printed,
|
||||
once all wildcard characters have been replaced.
|
||||
|
||||
Suppose you want to use the "blist" external command to list a group
|
||||
of BAS files into TXT files with corresponding names in another
|
||||
directory.
|
||||
|
||||
como cmd.file;= ?:bas "como /disk/listings/=;blist ="
|
||||
|
||||
If this looks complicated, don't worry--it is. First, ">" is used to
|
||||
redirect output to the file "cmd.file"--we are building a list of
|
||||
commands to be executed with "exec cmd.file" later. The rest of the line
|
||||
is a single use of the "=" command. The first parameter is "?:bas"--so
|
||||
you are prompted yes or no for each bas file. For the ones you respond
|
||||
Yes to, a string is printed to cmd.file. The string is bulit from the
|
||||
third parameter to "=", which is "como /disk/listings/=;blist =".
|
||||
|
||||
Suppose you responded Yes to three files: grapes, apples, and banjos.
|
||||
Then cmd.file would contain the following:
|
||||
|
||||
como /disk/listings/grapes;blist grapes
|
||||
como /disk/listings/apples;blist apples
|
||||
como /disk/listings/banjos;blist banjos
|
||||
|
||||
|
|
|
|||
19
doc/help/Err
19
doc/help/Err
|
|
@ -1 +1,18 @@
|
|||
err -- print ProDOS error message
syntax: err <integer>
ex: err 70
err $46
Prints the ProDOS error message corresponding to the given
error code. 'err 0' prints a list of all the errors in the
table.
Davex never prints an error number if a message is available
instead. This command is useful if you get an error code
from a program that doesn't have a table of ProDOS error
messages built in. (Applications created by 'sysalias' will
print two-digit error codes if something goes wrong; use
"err $xx" to see what they mean.)
|
||||
|
||||
err -- print ProDOS error message
|
||||
|
||||
syntax: err <integer>
|
||||
|
||||
ex: err 70
|
||||
err $46
|
||||
|
||||
Prints the ProDOS error message corresponding to the given
|
||||
error code. 'err 0' prints a list of all the errors in the
|
||||
table.
|
||||
|
||||
Davex never prints an error number if a message is available
|
||||
instead. This command is useful if you get an error code
|
||||
from a program that doesn't have a table of ProDOS error
|
||||
messages built in. (Applications created by 'sysalias' will
|
||||
print two-digit error codes if something goes wrong; use
|
||||
"err $xx" to see what they mean.)
|
||||
|
|
|
|||
|
|
@ -1 +1,23 @@
|
|||
exec -- get keyboard input from a file
syntax: exec <pathname>
ex: exec foo.bar
Makes keyboard input come from the specified file until an
error occurs or until end of file is reached. Wildcards are
allowed. The file must be of type TXT ($04), SRC ($B0),
or $C6/$8001 (Davex 8 Script).
If %autoexec exists, Davex automatically execs it on entry.
(If another pathname is passed to Davex in its startup buffer,
Davex attempts to exec the specified file instead of %autoexec.)
Command prompts and commands will not appear on the screen
while the file is being exec'ed (but the commands DO get
stored in the History buffer, so you can use the up arrow to
see what commands were executed; this is useful if an error
occurs during the exec).
(see also: setstart)
|
||||
|
||||
exec -- get keyboard input from a file
|
||||
|
||||
syntax: exec <pathname>
|
||||
|
||||
ex: exec foo.bar
|
||||
|
||||
Makes keyboard input come from the specified file until an
|
||||
error occurs or until end of file is reached. Wildcards are
|
||||
allowed. The file must be of type TXT ($04), SRC ($B0),
|
||||
or $C6/$8001 (Davex 8 Script).
|
||||
|
||||
If %autoexec exists, Davex automatically execs it on entry.
|
||||
(If another pathname is passed to Davex in its startup buffer,
|
||||
Davex attempts to exec the specified file instead of %autoexec.)
|
||||
|
||||
Command prompts and commands will not appear on the screen
|
||||
while the file is being exec'ed (but the commands DO get
|
||||
stored in the History buffer, so you can use the up arrow to
|
||||
see what commands were executed; this is useful if an error
|
||||
occurs during the exec).
|
||||
|
||||
(see also: setstart)
|
||||
|
|
|
|||
|
|
@ -1 +1,30 @@
|
|||
expand -- Expand tabs (EXTERNAL) [v1.1]
Written by Jeff Ding
syntax: expand <pathname> [-c<ascii number>] [-t<number>]
[-s"<tabstop 1,tabstop 2,tabstop 3,....,tabstop 16>"]
ex: expand file.w.tabs
expand merlin.s -c160 -s"14,20,35"
> file.no.tabs ; expand file
'Expand' expands up to 16 definable tab stops per line in the given
pathname. Line lengths of up to 255 characters are supported. Longer
lines are split into multiple lines. Use output redirection on the
command line to save output in a file (last example). The second
example works great for viewing Merlin source files.
Options are as follows:
-c: character for tab. Enter the ascii value of the character
to use for the tab expansion. The default character is value 9
for ctrl-I. The tab character is hi-bit sensitive.
-t: tab spaces. This is the number of spaces between two consecutive
tab stops, normally 8. Can be any number from 1 to 255.
-s: tab stops. Up to 16 tab stops can be defined manually. Each stop
must be greater than the previous with no value exceeding 255.
If less than 16 stops are defined, the remaining stops are
constructed from the defined tab spaces.
|
||||
|
||||
expand -- Expand tabs (EXTERNAL) [v1.1]
|
||||
Written by Jeff Ding
|
||||
|
||||
syntax: expand <pathname> [-c<ascii number>] [-t<number>]
|
||||
[-s"<tabstop 1,tabstop 2,tabstop 3,....,tabstop 16>"]
|
||||
|
||||
ex: expand file.w.tabs
|
||||
expand merlin.s -c160 -s"14,20,35"
|
||||
> file.no.tabs ; expand file
|
||||
|
||||
'Expand' expands up to 16 definable tab stops per line in the given
|
||||
pathname. Line lengths of up to 255 characters are supported. Longer
|
||||
lines are split into multiple lines. Use output redirection on the
|
||||
command line to save output in a file (last example). The second
|
||||
example works great for viewing Merlin source files.
|
||||
|
||||
Options are as follows:
|
||||
|
||||
-c: character for tab. Enter the ascii value of the character
|
||||
to use for the tab expansion. The default character is value 9
|
||||
for ctrl-I. The tab character is hi-bit sensitive.
|
||||
|
||||
-t: tab spaces. This is the number of spaces between two consecutive
|
||||
tab stops, normally 8. Can be any number from 1 to 255.
|
||||
|
||||
-s: tab stops. Up to 16 tab stops can be defined manually. Each stop
|
||||
must be greater than the previous with no value exceeding 255.
|
||||
If less than 16 stops are defined, the remaining stops are
|
||||
constructed from the defined tab spaces.
|
||||
|
|
|
|||
|
|
@ -1 +1,77 @@
|
|||
ffind -- find files by name/filetype/auxtype/etc (EXTERNAL) [v1.2]
syntax: ffind [<pathname>] [-n <string>] [-e] [-f <filetype>]
[-x <integer>] [-o <string>] [-q] [-p] [-d] [-b y|n]
[ -i y|n] [-s <integer>]
ex: ffind .61 -n foo --find pathnames of all files on volume
in slot 6, drive 1 with names containing
"foo"
ffind . -fsys --find all sys files in current directory
ffind --find all files on all volumes
'ffind' is a flexible command for locating files. It is especially
useful if you have a lot of subdirectories, since it will look
inside any subdirectories it finds.
The various options can be combined in a large number of useful ways;
no attempt is made here to illustrate all the possible combinations.
pathname: Tells 'ffind' where to look. If you leave this out, it
looks on all the ProDOS volumes in your system. Wildcards are
not currently allowed.
-n: Specifies a string which must be contained in a filename
before 'ffind' will print it. Example: ffind -n copy
finds all files having "copy" somewhere in their names.
-e: Forces -n to find only exact matches (not files whose names
merely *contain* the specified string). [This option is
meaningful only if you use -n.]
-f: Tells 'ffind' what filetype to look for. Example:
ffind -fawp finds AppleWorks Word Processor files.
-x: Tells 'ffind' what auxiliary type to look for. Example:
ffind -fbin -x$800 finds binary files that load at $800.
-b: Tells 'ffind' to look for files that have their "need
backup" flag set (-by) or clear (-bn). (The backup bit is
displayed in 'cat' listings and by the 'info' command; it
gets set whenever a file is changed, and you can clear it
with the -b option of the 'copy', 'update', or 'touch'
commands.)
-d: 'ffind' normally prints detailed information on each
match found, like this:
filetype auxtype last-modified-date pathname
The -d option tells 'ffind' NOT to print this detailed
information about each file. (Note that earlier versions
of 'ffind' defaulted to no detailed information, and the -d
option forced its inclusion.)
-q: Stands for "query"--forces 'ffind' to stop after every
match and ask "Continue search? (y/n)"
-p: Sets your prefix to the directory containing the last
match found.
-o: The string following "-o" will be printed for each pathname
found, but the pathname found will be printed in place of any
"=" characters in the string. [This is useful for generating
script files to be 'exec'ed later. See 'help =' for more
discussion, since the '=' command has a similar feature.]
-i: Tells 'ffind' to look for files that have their "invisible"
flag set (-iy) or clear (-in). (The invisible flag is
displayed in 'cat' listings (use -i to see invisible files)
and by the 'info' command. You can set or clear it with the
-i option of the 'touch' command.)
-s: Tells 'ffind' what storage type to look for. Example:
ffind -s5 finds all GS/OS "extended" files. This might
come in handy when copying lots of files, since Davex (and
ProDOS 8) can't work with extended files.
|
||||
|
||||
ffind -- find files by name/filetype/auxtype/etc (EXTERNAL) [v1.2]
|
||||
|
||||
syntax: ffind [<pathname>] [-n <string>] [-e] [-f <filetype>]
|
||||
[-x <integer>] [-o <string>] [-q] [-p] [-d] [-b y|n]
|
||||
[ -i y|n] [-s <integer>]
|
||||
|
||||
ex: ffind .61 -n foo --find pathnames of all files on volume
|
||||
in slot 6, drive 1 with names containing
|
||||
"foo"
|
||||
ffind . -fsys --find all sys files in current directory
|
||||
ffind --find all files on all volumes
|
||||
|
||||
'ffind' is a flexible command for locating files. It is especially
|
||||
useful if you have a lot of subdirectories, since it will look
|
||||
inside any subdirectories it finds.
|
||||
|
||||
The various options can be combined in a large number of useful ways;
|
||||
no attempt is made here to illustrate all the possible combinations.
|
||||
|
||||
pathname: Tells 'ffind' where to look. If you leave this out, it
|
||||
looks on all the ProDOS volumes in your system. Wildcards are
|
||||
not currently allowed.
|
||||
|
||||
-n: Specifies a string which must be contained in a filename
|
||||
before 'ffind' will print it. Example: ffind -n copy
|
||||
finds all files having "copy" somewhere in their names.
|
||||
|
||||
-e: Forces -n to find only exact matches (not files whose names
|
||||
merely *contain* the specified string). [This option is
|
||||
meaningful only if you use -n.]
|
||||
|
||||
-f: Tells 'ffind' what filetype to look for. Example:
|
||||
ffind -fawp finds AppleWorks Word Processor files.
|
||||
|
||||
-x: Tells 'ffind' what auxiliary type to look for. Example:
|
||||
ffind -fbin -x$800 finds binary files that load at $800.
|
||||
|
||||
-b: Tells 'ffind' to look for files that have their "need
|
||||
backup" flag set (-by) or clear (-bn). (The backup bit is
|
||||
displayed in 'cat' listings and by the 'info' command; it
|
||||
gets set whenever a file is changed, and you can clear it
|
||||
with the -b option of the 'copy', 'update', or 'touch'
|
||||
commands.)
|
||||
|
||||
-d: 'ffind' normally prints detailed information on each
|
||||
match found, like this:
|
||||
|
||||
filetype auxtype last-modified-date pathname
|
||||
|
||||
The -d option tells 'ffind' NOT to print this detailed
|
||||
information about each file. (Note that earlier versions
|
||||
of 'ffind' defaulted to no detailed information, and the -d
|
||||
option forced its inclusion.)
|
||||
|
||||
-q: Stands for "query"--forces 'ffind' to stop after every
|
||||
match and ask "Continue search? (y/n)"
|
||||
|
||||
-p: Sets your prefix to the directory containing the last
|
||||
match found.
|
||||
|
||||
-o: The string following "-o" will be printed for each pathname
|
||||
found, but the pathname found will be printed in place of any
|
||||
"=" characters in the string. [This is useful for generating
|
||||
script files to be 'exec'ed later. See 'help =' for more
|
||||
discussion, since the '=' command has a similar feature.]
|
||||
|
||||
-i: Tells 'ffind' to look for files that have their "invisible"
|
||||
flag set (-iy) or clear (-in). (The invisible flag is
|
||||
displayed in 'cat' listings (use -i to see invisible files)
|
||||
and by the 'info' command. You can set or clear it with the
|
||||
-i option of the 'touch' command.)
|
||||
|
||||
-s: Tells 'ffind' what storage type to look for. Example:
|
||||
ffind -s5 finds all GS/OS "extended" files. This might
|
||||
come in handy when copying lots of files, since Davex (and
|
||||
ProDOS 8) can't work with extended files.
|
||||
|
|
|
|||
48
doc/help/FP
48
doc/help/FP
|
|
@ -1 +1,47 @@
|
|||
fp -- text formatter (EXTERNAL)
(Based on an early version of FreePrinter by Elliot Lifson)
syntax: fp <wildpath> [-1] [-c]
ex: como &;fp mypaper -1
fp -c
[Note--'fp' is offered in its current form because it is better
than nothing. It isn't cleanly implemented and may have some
problems. It isn't going to crash your system or fry your disk,
but I wouldn't recommend trying to print your thesis with it.]
Outputs formatted text generated from text and imbedded "dot
commands" in a file. -c prints credits; -1 is the same as
including ".sp1" in the file.
The dot commands 'fp' recognizes are similar to the ones
AppleWriter recognizes. They are (defaults in parentheses):
.lm# (10) -- left margin
.rm# (70) -- right margin
.pm# (0) -- paragraph margin (may be negative)
.tm# (0) -- top margin
.tl ("") -- top line text (*=delimeter)
.li# (1) -- line spacing (NOT IMPLEMENTED)
.sp# (0) -- single page (1=prompt for each page)
.pi# (66) -- page interval: # of lines per page
.pl# (60) -- printed lines per page
.lj -- left justify (default)
.cj -- center justify
.rj -- right justify
.fj -- fill justify (left and right)
.ff -- formfeed -- begin new page
.ff# -- begin new page if fewer than # lines remain on
this page
# is a number from 0 to 255. Most values can be ADJUSTED up
or down by putting a "+" or "-" in front of the number.
Example:
.lm+5 moves left margin right 5 spaces
|
||||
|
||||
fp -- text formatter (EXTERNAL)
|
||||
(Based on an early version of FreePrinter by Elliot Lifson)
|
||||
|
||||
syntax: fp <wildpath> [-1] [-c]
|
||||
|
||||
ex: como &;fp mypaper -1
|
||||
fp -c
|
||||
|
||||
[Note--'fp' is offered in its current form because it is better
|
||||
than nothing. It isn't cleanly implemented and may have some
|
||||
problems. It isn't going to crash your system or fry your disk,
|
||||
but I wouldn't recommend trying to print your thesis with it.]
|
||||
|
||||
Outputs formatted text generated from text and imbedded "dot
|
||||
commands" in a file. -c prints credits; -1 is the same as
|
||||
including ".sp1" in the file.
|
||||
|
||||
The dot commands 'fp' recognizes are similar to the ones
|
||||
AppleWriter recognizes. They are (defaults in parentheses):
|
||||
|
||||
.lm# (10) -- left margin
|
||||
.rm# (70) -- right margin
|
||||
.pm# (0) -- paragraph margin (may be negative)
|
||||
|
||||
.tm# (0) -- top margin
|
||||
.tl ("") -- top line text (*=delimeter)
|
||||
.li# (1) -- line spacing (NOT IMPLEMENTED)
|
||||
|
||||
.sp# (0) -- single page (1=prompt for each page)
|
||||
.pi# (66) -- page interval: # of lines per page
|
||||
.pl# (60) -- printed lines per page
|
||||
|
||||
.lj -- left justify (default)
|
||||
.cj -- center justify
|
||||
.rj -- right justify
|
||||
.fj -- fill justify (left and right)
|
||||
|
||||
.ff -- formfeed -- begin new page
|
||||
.ff# -- begin new page if fewer than # lines remain on
|
||||
this page
|
||||
|
||||
# is a number from 0 to 255. Most values can be ADJUSTED up
|
||||
or down by putting a "+" or "-" in front of the number.
|
||||
Example:
|
||||
|
||||
.lm+5 moves left margin right 5 spaces
|
||||
|
|
|
|||
|
|
@ -1 +1,28 @@
|
|||
ftype -- display or update your filetype name table
syntax: ftype [-r<ftype>] [-a<string> -v<ftype>] [-z]
ex: ftype
ftype -rbas
ftype -r1
ftype -aLNK -v$F8
ftype -z
Davex has two lists of filetype names: one is in your %config
file (maximum of 63 entries), and the other one is built into
Davex. Entries in your table can override built-in entries.
'ftype' with no options displays all filetypes in your %config
file, followed by all the filetypes in the internal list.
-r removes the given filetype from your list.
-a and -v are used together to add one filetype to your list.
Case is unimportant when looking for a filetype in the table,
BUT the types are displayed with the case you use in the -a
option.
'ftype -z' (zap) wipes out any extra filetypes you have
added (with ftype -a) to your %config file, leaving only
the built-in table.
|
||||
|
||||
ftype -- display or update your filetype name table
|
||||
|
||||
syntax: ftype [-r<ftype>] [-a<string> -v<ftype>] [-z]
|
||||
|
||||
ex: ftype
|
||||
ftype -rbas
|
||||
ftype -r1
|
||||
ftype -aLNK -v$F8
|
||||
ftype -z
|
||||
|
||||
Davex has two lists of filetype names: one is in your %config
|
||||
file (maximum of 63 entries), and the other one is built into
|
||||
Davex. Entries in your table can override built-in entries.
|
||||
|
||||
'ftype' with no options displays all filetypes in your %config
|
||||
file, followed by all the filetypes in the internal list.
|
||||
|
||||
-r removes the given filetype from your list.
|
||||
|
||||
-a and -v are used together to add one filetype to your list.
|
||||
Case is unimportant when looking for a filetype in the table,
|
||||
BUT the types are displayed with the case you use in the -a
|
||||
option.
|
||||
|
||||
'ftype -z' (zap) wipes out any extra filetypes you have
|
||||
added (with ftype -a) to your %config file, leaving only
|
||||
the built-in table.
|
||||
|
|
|
|||
|
|
@ -1 +1,17 @@
|
|||
filetype -- change file's type (& auxtype)
syntax: filetype <pathname> <filetype> [-x<integer>]
ex: filetype myfile sys
filetype ? bin -x$2000
Changes the file type (NOT the storage type) of a file. If
-x is given, also sets the auxiliary type (subtype) as
specified.
NOTE: Although you can change a DIR file into another type,
and you can change a non-DIR file into a DIR file,
this changes ONLY the file type and will cause much
confusion--it is not recommended. (The storage type
is not affected.)
|
||||
|
||||
filetype -- change file's type (& auxtype)
|
||||
|
||||
syntax: filetype <pathname> <filetype> [-x<integer>]
|
||||
|
||||
ex: filetype myfile sys
|
||||
filetype ? bin -x$2000
|
||||
|
||||
Changes the file type (NOT the storage type) of a file. If
|
||||
-x is given, also sets the auxiliary type (subtype) as
|
||||
specified.
|
||||
|
||||
NOTE: Although you can change a DIR file into another type,
|
||||
and you can change a non-DIR file into a DIR file,
|
||||
this changes ONLY the file type and will cause much
|
||||
confusion--it is not recommended. (The storage type
|
||||
is not affected.)
|
||||
|
|
|
|||
|
|
@ -1 +1,56 @@
|
|||
find -- search a file for lines containing a string (EXTERNAL) [v1.1]
syntax: find <pathname> [<string>] [-L<integer>] [-w<integer>]
[-c] [-n]
ex: find phones frank
find .61= -n
find /info/addresses "John S" -L5
'find' searches files for lines containing a specified string.
Each matching line (each one containing the string) is displayed
(non-printable characters appear as periods).
pathname: Specifies what file to search. Wildcards are allowed.
Note: 'find' is appropriate for searching (AppleWorks Word
Processor (AWP) files as well as "plain text" files (TXT and
SRC, for example).
string: Specifies what to search for. If this string contains
blanks or begins with a "-", you must put quotation marks
around it (use either ["] or [']). (If you omit the
string, all lines in the file will be counted as matches.)
Uppercase and lowercase letters are considered the same.
-c: Count the number of matching lines instead of displaying
them. (Use -L1 to display matches *and* the count.)
-L: Specifies the number of consecutive lines to display starting
with each matching line. If you do not give this option, only
the matching lines are displayed. (If -c is given, no lines
are displayed unless you also use -L.)
[An additional line printed after a match may itself be a
matching line. In cases like this, 'find' continues printing
lines until the requested number of lines have been printed
after the last match.]
-n: Causes line numbers to appear before every line displayed.
The line numbers may not correspond exactly to the line
numbers you see in AppleWorks, since 'find' ignores lines
containing formatting commands.
-w: Sets the wrap margin for breaking a file into lines. You will
probably have no need for this option unless the files you are
searching use carriage-return to mark *paragraphs* rather than
lines (for example, most AppleWriter files).
The wrap margin defaults to 70. You can specify your own margin
with the -w option (your margin must be in the range 11 to 254).
A line ends when (1) it hits the wrap margin, (2) at a carriage
return, or (3) at a blank within 9 characters of the wrap margin
(whichever comes first).
[Note--find v1.0 failed to find strings at the beginning of a line.]
|
||||
|
||||
find -- search a file for lines containing a string (EXTERNAL) [v1.1]
|
||||
|
||||
syntax: find <pathname> [<string>] [-L<integer>] [-w<integer>]
|
||||
[-c] [-n]
|
||||
|
||||
ex: find phones frank
|
||||
find .61= -n
|
||||
find /info/addresses "John S" -L5
|
||||
|
||||
'find' searches files for lines containing a specified string.
|
||||
Each matching line (each one containing the string) is displayed
|
||||
(non-printable characters appear as periods).
|
||||
|
||||
pathname: Specifies what file to search. Wildcards are allowed.
|
||||
Note: 'find' is appropriate for searching (AppleWorks Word
|
||||
Processor (AWP) files as well as "plain text" files (TXT and
|
||||
SRC, for example).
|
||||
|
||||
string: Specifies what to search for. If this string contains
|
||||
blanks or begins with a "-", you must put quotation marks
|
||||
around it (use either ["] or [']). (If you omit the
|
||||
string, all lines in the file will be counted as matches.)
|
||||
Uppercase and lowercase letters are considered the same.
|
||||
|
||||
-c: Count the number of matching lines instead of displaying
|
||||
them. (Use -L1 to display matches *and* the count.)
|
||||
|
||||
-L: Specifies the number of consecutive lines to display starting
|
||||
with each matching line. If you do not give this option, only
|
||||
the matching lines are displayed. (If -c is given, no lines
|
||||
are displayed unless you also use -L.)
|
||||
|
||||
[An additional line printed after a match may itself be a
|
||||
matching line. In cases like this, 'find' continues printing
|
||||
lines until the requested number of lines have been printed
|
||||
after the last match.]
|
||||
|
||||
-n: Causes line numbers to appear before every line displayed.
|
||||
The line numbers may not correspond exactly to the line
|
||||
numbers you see in AppleWorks, since 'find' ignores lines
|
||||
containing formatting commands.
|
||||
|
||||
-w: Sets the wrap margin for breaking a file into lines. You will
|
||||
probably have no need for this option unless the files you are
|
||||
searching use carriage-return to mark *paragraphs* rather than
|
||||
lines (for example, most AppleWriter files).
|
||||
|
||||
The wrap margin defaults to 70. You can specify your own margin
|
||||
with the -w option (your margin must be in the range 11 to 254).
|
||||
|
||||
A line ends when (1) it hits the wrap margin, (2) at a carriage
|
||||
return, or (3) at a blank within 9 characters of the wrap margin
|
||||
(whichever comes first).
|
||||
|
||||
[Note--find v1.0 failed to find strings at the beginning of a line.]
|
||||
|
|
|
|||
|
|
@ -1 +1,39 @@
|
|||
gsbuff -- examine or set sizes of IIgs serial port buffers
syntax: gsbuff <portnum> [-i <integer>] [-o <integer>]
ex: gsbuff 1 --shows printer buffer info
gsbuff 2 --shows moddem buffer info
gsbuff 1 -o 20000 --sets printer output buffer size
to 20000 bytes
gsbuff 2 -i 65535 --sets modem input buffer size to
65535 bytes
'gsbuff' lets you change the size of the input and output
buffers on the Apple IIgs serial ports (normally, port 1
is used for a printer and port 2 is used for a modem).
You should turn on buffering in the control panel (under
Printer Port or Modem Port) before setting up buffers with
'gsbuff'. (When you do this, the ROM allocates bufers that
are only 2048 bytes long.)
Use -i to set the input buffer size and -o to set the
output buffer size. Buffer sizes must be in the range 1
to 65535 bytes. Note that 'gsbuff' always allocates NEW
memory for buffering and never frees up previously-allocated
memory.
After allocating a buffer with 'gsbuff', it is recommended
that you use Apple-Ctrl-RESET or "boot -i" if you restart
your system (rather than "PR#n" from BASIC or "boot -sn"
from Davex). This will insure that the ROM does not try
to use a buffer that is no longer present.
NOTE: Printer buffering has very limited usefullness with
the current Apple IIgs ROM (version 01; see 'deschw'), since
the ROM empties your printer buffer whenever something new
is printed. If you are willing to always wait until your
previous document is done printing before printing anything
else, then buffering will be useful to you.
|
||||
|
||||
gsbuff -- examine or set sizes of IIgs serial port buffers
|
||||
|
||||
syntax: gsbuff <portnum> [-i <integer>] [-o <integer>]
|
||||
|
||||
ex: gsbuff 1 --shows printer buffer info
|
||||
gsbuff 2 --shows moddem buffer info
|
||||
gsbuff 1 -o 20000 --sets printer output buffer size
|
||||
to 20000 bytes
|
||||
gsbuff 2 -i 65535 --sets modem input buffer size to
|
||||
65535 bytes
|
||||
|
||||
'gsbuff' lets you change the size of the input and output
|
||||
buffers on the Apple IIgs serial ports (normally, port 1
|
||||
is used for a printer and port 2 is used for a modem).
|
||||
|
||||
You should turn on buffering in the control panel (under
|
||||
Printer Port or Modem Port) before setting up buffers with
|
||||
'gsbuff'. (When you do this, the ROM allocates bufers that
|
||||
are only 2048 bytes long.)
|
||||
|
||||
Use -i to set the input buffer size and -o to set the
|
||||
output buffer size. Buffer sizes must be in the range 1
|
||||
to 65535 bytes. Note that 'gsbuff' always allocates NEW
|
||||
memory for buffering and never frees up previously-allocated
|
||||
memory.
|
||||
|
||||
After allocating a buffer with 'gsbuff', it is recommended
|
||||
that you use Apple-Ctrl-RESET or "boot -i" if you restart
|
||||
your system (rather than "PR#n" from BASIC or "boot -sn"
|
||||
from Davex). This will insure that the ROM does not try
|
||||
to use a buffer that is no longer present.
|
||||
|
||||
NOTE: Printer buffering has very limited usefullness with
|
||||
the current Apple IIgs ROM (version 01; see 'deschw'), since
|
||||
the ROM empties your printer buffer whenever something new
|
||||
is printed. If you are willing to always wait until your
|
||||
previous document is done printing before printing anything
|
||||
else, then buffering will be useful to you.
|
||||
|
|
|
|||
16
doc/help/Hdr
16
doc/help/Hdr
|
|
@ -1 +1,15 @@
|
|||
hdr -- print a file's header (the first n lines) (EXTERNAL)
syntax: hdr <pathname> [-Ln]
ex: hdr thatfile
hdr %help/= -L2
Displays lines from the beginning of a file. Wildcards are
allowed. If -L is given, the specified number of lines is
displayed. If -L is omitted, the first 5 lines are
displayed.
'hdr' works for AWP files and for any file type that contains
plain text (for example, txt or src).
|
||||
|
||||
hdr -- print a file's header (the first n lines) (EXTERNAL)
|
||||
|
||||
syntax: hdr <pathname> [-Ln]
|
||||
|
||||
ex: hdr thatfile
|
||||
hdr %help/= -L2
|
||||
|
||||
Displays lines from the beginning of a file. Wildcards are
|
||||
allowed. If -L is given, the specified number of lines is
|
||||
displayed. If -L is omitted, the first 5 lines are
|
||||
displayed.
|
||||
|
||||
'hdr' works for AWP files and for any file type that contains
|
||||
plain text (for example, txt or src).
|
||||
|
|
|
|||
|
|
@ -1 +1,33 @@
|
|||
help | ? -- display command information
syntax: help [string]
ex: help
?
help topics
?cat
'help' or '?' alone prints a list of built-in commands.
'help' or '?' followed by a command name or topic prints information
on that command or topic. Type "help topics" for a list of available
help topics.
It is not necessary to put a blank after the '?' command.
Note about ALIASES: 'help' doesn't currently understand aliases.
To get help on a "command" like "dir" (really an alias for 'cat')
you have to type "help cat" (or "?cat"), not "help dir". ['Help'
may be more intelligent about aliases in a future version of Davex;
for now, you'll have to type "alias" to see what the real name for
your command is.]
To save disk space, most of the help files have been compressed and
included in the file "indexed.help" in the help directory. The
help directory is normally %help, but the 'config' command can be
used to put the help somewhere else. When you ask for help on a
given topic, 'help' always looks for a file with the same name in
the help directory before consulting the indexed help file.
(see also: config, "help topics")
|
||||
|
||||
help | ? -- display command information
|
||||
|
||||
syntax: help [string]
|
||||
|
||||
ex: help
|
||||
?
|
||||
help topics
|
||||
?cat
|
||||
|
||||
'help' or '?' alone prints a list of built-in commands.
|
||||
|
||||
'help' or '?' followed by a command name or topic prints information
|
||||
on that command or topic. Type "help topics" for a list of available
|
||||
help topics.
|
||||
|
||||
It is not necessary to put a blank after the '?' command.
|
||||
|
||||
Note about ALIASES: 'help' doesn't currently understand aliases.
|
||||
To get help on a "command" like "dir" (really an alias for 'cat')
|
||||
you have to type "help cat" (or "?cat"), not "help dir". ['Help'
|
||||
may be more intelligent about aliases in a future version of Davex;
|
||||
for now, you'll have to type "alias" to see what the real name for
|
||||
your command is.]
|
||||
|
||||
To save disk space, most of the help files have been compressed and
|
||||
included in the file "indexed.help" in the help directory. The
|
||||
help directory is normally %help, but the 'config' command can be
|
||||
used to put the help somewhere else. When you ask for help on a
|
||||
given topic, 'help' always looks for a file with the same name in
|
||||
the help directory before consulting the indexed help file.
|
||||
|
||||
(see also: config, "help topics")
|
||||
|
|
|
|||
44
doc/help/IW2
44
doc/help/IW2
|
|
@ -1 +1,43 @@
|
|||
iw2 -- set options for ImageWriter II (EXTERNAL) [v1.1]
syntax: iw2 [-n] [-1 y|n] [-b y|n] [-u y|n] [-8 y|n]
[-s y|n] [-l <integer>] [-p <integer>]
[-r y|n] [-q <integer>] [-c <integer>]
[-0 y|n] [-h <integer>] [-f <integer>]
[-i y|n] [-e <integer>] [-t] [-x]
ex: iw2 -n
iw2 -p12 -by -un
iw2 -sy -1n -l10
Sets print options, assuming an ImageWriter II is connected to
the printer slot (see 'config'). Each option is explained below:
-n (normal) reinitialize printer to power-up state
-1 y|n -1y set unidirectional printing; -1n sets bidirectional
-b y|n boldface: yes or no
-u y|n underlining: yes or no
-8 y|n eight lines per inch: yes or no (no=6 lines per inch)
-s y|n skip to new page every 60 lines: yes or no
-l # set left margin in characters (normally 0)
-p # set pitch; may be 4..10, 12, 13, 15, 17
-r y|n reverse formfeed direction; y=reverse, n=forward
-q # print quality (0=standard, 1=draft, 2=near-letter-quality)
-c # color (0..6)
-0 y|n slashed zeroes: yes or no
-t set top of form to here
[ -h nnnn form height (in n/144 inches) NOT IMPLEMENTED ]
-f # font (0=American...7=Spanish)
-x cancel unprinted text (send ctrl-x)
-i y|n ignore out-of-paper sensor: yes or no
-e # 0: enable ROM character set; 1=enable downloaded charset,
low half; 2=enable downloaded charset, high half
Note: -s and -n reset the printer's top of form, so they should be
used only when the printer is at the top of a page.
Note: In version 1.0 of 'iw2', the -f, -x, -i and -e options did
not work. Now they do.
(see also: config)
|
||||
|
||||
iw2 -- set options for ImageWriter II (EXTERNAL) [v1.1]
|
||||
|
||||
syntax: iw2 [-n] [-1 y|n] [-b y|n] [-u y|n] [-8 y|n]
|
||||
[-s y|n] [-l <integer>] [-p <integer>]
|
||||
[-r y|n] [-q <integer>] [-c <integer>]
|
||||
[-0 y|n] [-h <integer>] [-f <integer>]
|
||||
[-i y|n] [-e <integer>] [-t] [-x]
|
||||
|
||||
ex: iw2 -n
|
||||
iw2 -p12 -by -un
|
||||
iw2 -sy -1n -l10
|
||||
|
||||
Sets print options, assuming an ImageWriter II is connected to
|
||||
the printer slot (see 'config'). Each option is explained below:
|
||||
|
||||
-n (normal) reinitialize printer to power-up state
|
||||
-1 y|n -1y set unidirectional printing; -1n sets bidirectional
|
||||
-b y|n boldface: yes or no
|
||||
-u y|n underlining: yes or no
|
||||
-8 y|n eight lines per inch: yes or no (no=6 lines per inch)
|
||||
-s y|n skip to new page every 60 lines: yes or no
|
||||
-l # set left margin in characters (normally 0)
|
||||
-p # set pitch; may be 4..10, 12, 13, 15, 17
|
||||
-r y|n reverse formfeed direction; y=reverse, n=forward
|
||||
-q # print quality (0=standard, 1=draft, 2=near-letter-quality)
|
||||
-c # color (0..6)
|
||||
-0 y|n slashed zeroes: yes or no
|
||||
-t set top of form to here
|
||||
[ -h nnnn form height (in n/144 inches) NOT IMPLEMENTED ]
|
||||
-f # font (0=American...7=Spanish)
|
||||
-x cancel unprinted text (send ctrl-x)
|
||||
-i y|n ignore out-of-paper sensor: yes or no
|
||||
-e # 0: enable ROM character set; 1=enable downloaded charset,
|
||||
low half; 2=enable downloaded charset, high half
|
||||
|
||||
Note: -s and -n reset the printer's top of form, so they should be
|
||||
used only when the printer is at the top of a page.
|
||||
|
||||
Note: In version 1.0 of 'iw2', the -f, -x, -i and -e options did
|
||||
not work. Now they do.
|
||||
|
||||
(see also: config)
|
||||
|
|
|
|||
|
|
@ -1 +1,24 @@
|
|||
index -- create, add to, and view sections of indexed files
[EXTERNAL] (v1.0)
syntax: index <pathname> [-s <index-size>] [-a <filename>]
[-e <string>] [-v <string>]
ex: index %help/indexed.help -s1200
index %help/indexed.help -aprefix -ecd
index %help/indexed.help -vprefix
'index' is used to build the %indexed.help file containing most of the
help files for Davex. Use the -s (size) option to create a new file,
reserving the specified number of bytes for the index. Use the -a option
with a filename to append the contents of a file to an existing indexed
file. The -e option is used if you want to add an alternative key to
the index for a file--the second example above adds the contents of a
file called "prefix" to an index file, and the text can later be accessed
with a key of either "prefix" or "cd", since "cd" appears after the -e
(extra key) option.
The -v option lets you look up things in an indexed file; it's equivalent
to what the 'help' command does with %help/indexed.help if it doesn't
find a particular file first.
|
||||
|
||||
index -- create, add to, and view sections of indexed files
|
||||
[EXTERNAL] (v1.0)
|
||||
|
||||
syntax: index <pathname> [-s <index-size>] [-a <filename>]
|
||||
[-e <string>] [-v <string>]
|
||||
|
||||
ex: index %help/indexed.help -s1200
|
||||
index %help/indexed.help -aprefix -ecd
|
||||
index %help/indexed.help -vprefix
|
||||
|
||||
'index' is used to build the %indexed.help file containing most of the
|
||||
help files for Davex. Use the -s (size) option to create a new file,
|
||||
reserving the specified number of bytes for the index. Use the -a option
|
||||
with a filename to append the contents of a file to an existing indexed
|
||||
file. The -e option is used if you want to add an alternative key to
|
||||
the index for a file--the second example above adds the contents of a
|
||||
file called "prefix" to an index file, and the text can later be accessed
|
||||
with a key of either "prefix" or "cd", since "cd" appears after the -e
|
||||
(extra key) option.
|
||||
|
||||
The -v option lets you look up things in an indexed file; it's equivalent
|
||||
to what the 'help' command does with %help/indexed.help if it doesn't
|
||||
find a particular file first.
|
||||
|
|
|
|||
|
|
@ -1 +1,27 @@
|
|||
info -- print info on file, directory, or volume
syntax: info <pathname>
ex: info myfile
info =:sys
info .61
info %help/=
Displays info for file, subdirectory, or volume. Wildcards are allowed.
The information printed is:
* complete pathname
* device number of the drive containing the file/directory
* storage type (seedling, sapling, tree, Pascal area, extended,
directory, or volume)
* file type
* access (r=read, w=write, n=rename, d=delete, B=changed since backup,
I=invisible)
* auxilary type (default load address for BIN, record length for
TXT, saved location for BAS; total blocks for VOLUME)
* number of blocks used
* date/time created (for a volume, even!)
* date/time last modified
(see also: size, what)
|
||||
|
||||
info -- print info on file, directory, or volume
|
||||
|
||||
syntax: info <pathname>
|
||||
|
||||
ex: info myfile
|
||||
info =:sys
|
||||
info .61
|
||||
info %help/=
|
||||
|
||||
Displays info for file, subdirectory, or volume. Wildcards are allowed.
|
||||
The information printed is:
|
||||
|
||||
* complete pathname
|
||||
* device number of the drive containing the file/directory
|
||||
* storage type (seedling, sapling, tree, Pascal area, extended,
|
||||
directory, or volume)
|
||||
* file type
|
||||
* access (r=read, w=write, n=rename, d=delete, B=changed since backup,
|
||||
I=invisible)
|
||||
* auxilary type (default load address for BIN, record length for
|
||||
TXT, saved location for BAS; total blocks for VOLUME)
|
||||
* number of blocks used
|
||||
* date/time created (for a volume, even!)
|
||||
* date/time last modified
|
||||
|
||||
(see also: size, what)
|
||||
|
|
|
|||
|
|
@ -1 +1,31 @@
|
|||
init -- initialize a ProDOS disk (EXTERNAL) [v1.2]
syntax: init device-number [volume-name] [-p] [-b] [-1] [-w]
ex: init .52 /mydisk
init .61 -b
init .61 -p
init .51 -1 -b
init .71 -w
Initializes a ProDOS volume. If the volume in the specified device
has already been initialized, init warns you that the existing volume
will be destroyed.
If no volume name is specified, the new volume is named "/blank".
If -p is given, init prompts you to insert the disk to be formatted.
If -b ("batch") is given, 'init' prompts you to insert another disk
after each successful format.
If -1 is given and a disk in an Apple 3.5 or Unidisk 3.5 drive is
being formatted, the disk will be formatted SINGLE SIDED and will
have a capacity of 400K (800 blocks).
If -w is given, no formatting is done--instead, just the "boot
blocks" (blocks 0 and 1) are written to the disk. This is
necessary, for example, to make a RAM disk (or a disk formatted
in AppleWorks) bootable. (The program contained in blocks 0 and
1 finds and loads a file called PRODOS in the main directory of
the disk.)
|
||||
|
||||
init -- initialize a ProDOS disk (EXTERNAL) [v1.2]
|
||||
|
||||
syntax: init device-number [volume-name] [-p] [-b] [-1] [-w]
|
||||
|
||||
ex: init .52 /mydisk
|
||||
init .61 -b
|
||||
init .61 -p
|
||||
init .51 -1 -b
|
||||
init .71 -w
|
||||
|
||||
Initializes a ProDOS volume. If the volume in the specified device
|
||||
has already been initialized, init warns you that the existing volume
|
||||
will be destroyed.
|
||||
|
||||
If no volume name is specified, the new volume is named "/blank".
|
||||
|
||||
If -p is given, init prompts you to insert the disk to be formatted.
|
||||
If -b ("batch") is given, 'init' prompts you to insert another disk
|
||||
after each successful format.
|
||||
|
||||
If -1 is given and a disk in an Apple 3.5 or Unidisk 3.5 drive is
|
||||
being formatted, the disk will be formatted SINGLE SIDED and will
|
||||
have a capacity of 400K (800 blocks).
|
||||
|
||||
If -w is given, no formatting is done--instead, just the "boot
|
||||
blocks" (blocks 0 and 1) are written to the disk. This is
|
||||
necessary, for example, to make a RAM disk (or a disk formatted
|
||||
in AppleWorks) bootable. (The program contained in blocks 0 and
|
||||
1 finds and loads a file called PRODOS in the main directory of
|
||||
the disk.)
|
||||
|
|
|
|||
|
|
@ -1 +1,12 @@
|
|||
lock -- make a file read-only
syntax: lock <pathname>
ex: lock this
lock =:txt
Disallows rename, delete, and write for file. Wildcards are
allowed.
(see also: unlock, prot)
|
||||
|
||||
lock -- make a file read-only
|
||||
|
||||
syntax: lock <pathname>
|
||||
|
||||
ex: lock this
|
||||
lock =:txt
|
||||
|
||||
Disallows rename, delete, and write for file. Wildcards are
|
||||
allowed.
|
||||
|
||||
(see also: unlock, prot)
|
||||
|
|
|
|||
|
|
@ -1 +1,28 @@
|
|||
mx80 -- set up print options for Epson MX80 (EXTERNAL) [v1.1]
syntax: mx80 [-z] [-n] [-1 y|n] [-b y|n] [-e y|n] [-i y|n] [-u y|n]
[-8 y|n] [-s <integer>] [-l <integer>] [-p <integer>]
ex: mx80 -z
mx80 -p17 -by -in -uy
mx80 -s6
Set print options, assuming an Epson MX80 is connected. Each option
is explained below:
-z (zap) set all options to power-up defaults (including top
of form)
-n (normal) turn off special modes and set 10 cpi
-1 y|n -1y set unidirectional printing; -1n sets bidirectional
-b y|n boldface: yes or no
-e y|n emphasized: yes or no (double strike)
-i y|n italics: yes or no
-u y|n underlining: yes or no
-8 y|n eight lines per inch: yes or no (no=6 lines per inch)
-s # set number of lines to skip over at end of page
-l # set page size in lines (normally 66)
-p # set pitch; may be 5, 8 (really 8.5), 10, or 17 (really
17.16)
'mx80' v1.0 didn't work with recent versions of Davex.
|
||||
|
||||
mx80 -- set up print options for Epson MX80 (EXTERNAL) [v1.1]
|
||||
|
||||
syntax: mx80 [-z] [-n] [-1 y|n] [-b y|n] [-e y|n] [-i y|n] [-u y|n]
|
||||
[-8 y|n] [-s <integer>] [-l <integer>] [-p <integer>]
|
||||
|
||||
ex: mx80 -z
|
||||
mx80 -p17 -by -in -uy
|
||||
mx80 -s6
|
||||
|
||||
Set print options, assuming an Epson MX80 is connected. Each option
|
||||
is explained below:
|
||||
|
||||
-z (zap) set all options to power-up defaults (including top
|
||||
of form)
|
||||
-n (normal) turn off special modes and set 10 cpi
|
||||
-1 y|n -1y set unidirectional printing; -1n sets bidirectional
|
||||
-b y|n boldface: yes or no
|
||||
-e y|n emphasized: yes or no (double strike)
|
||||
-i y|n italics: yes or no
|
||||
-u y|n underlining: yes or no
|
||||
-8 y|n eight lines per inch: yes or no (no=6 lines per inch)
|
||||
-s # set number of lines to skip over at end of page
|
||||
-l # set page size in lines (normally 66)
|
||||
-p # set pitch; may be 5, 8 (really 8.5), 10, or 17 (really
|
||||
17.16)
|
||||
|
||||
'mx80' v1.0 didn't work with recent versions of Davex.
|
||||
|
|
|
|||
|
|
@ -1 +1,30 @@
|
|||
modchk -- compare modification dates on pairs of files (EXTERNAL)
syntax: modchk <pathname1> <pathname2> [-q] [-o] [-n] [-s]
ex: modchk thisfile thatfile
modchk /disk/= /backup/= -o -n
modchk =.s = -n
Checks the last-modification dates on a pair of files. Wildcards
are allowed. If none of -o (older), -n (newer), or -s (same) is
given, a message of the form
<pathname1> <relation> <pathname2>
is displayed. Relation is "<" (older), "=" (same), or ">"
(newer). If one or more of -o, -n, or -s appears, pathname1 is
displayed only if the files satisfy one of the specified
conditions.
The second example above displays the names of files on /disk
which are older OR newer than the files with the same names on
/backup. The third example above displays the names of ".s"
files that have been modified since their corresponding files
without the ".s" suffix. This is useful for insuring that you
have not changed an assembly language source file without
recompiling it.
If -q (quiet) is given, no complaint is displayed if the second
file doesn't exist.
|
||||
|
||||
modchk -- compare modification dates on pairs of files (EXTERNAL)
|
||||
|
||||
syntax: modchk <pathname1> <pathname2> [-q] [-o] [-n] [-s]
|
||||
|
||||
ex: modchk thisfile thatfile
|
||||
modchk /disk/= /backup/= -o -n
|
||||
modchk =.s = -n
|
||||
|
||||
Checks the last-modification dates on a pair of files. Wildcards
|
||||
are allowed. If none of -o (older), -n (newer), or -s (same) is
|
||||
given, a message of the form
|
||||
|
||||
<pathname1> <relation> <pathname2>
|
||||
|
||||
is displayed. Relation is "<" (older), "=" (same), or ">"
|
||||
(newer). If one or more of -o, -n, or -s appears, pathname1 is
|
||||
displayed only if the files satisfy one of the specified
|
||||
conditions.
|
||||
|
||||
The second example above displays the names of files on /disk
|
||||
which are older OR newer than the files with the same names on
|
||||
/backup. The third example above displays the names of ".s"
|
||||
files that have been modified since their corresponding files
|
||||
without the ".s" suffix. This is useful for insuring that you
|
||||
have not changed an assembly language source file without
|
||||
recompiling it.
|
||||
|
||||
If -q (quiet) is given, no complaint is displayed if the second
|
||||
file doesn't exist.
|
||||
|
|
|
|||
15
doc/help/Mon
15
doc/help/Mon
|
|
@ -1 +1,14 @@
|
|||
mon -- enter the Monitor
syntax: mon
ex: mon
Dumps you into your Apple's monitor. Ctrl-Y or RESET or
3D0G will get you back to Davex. (On an Apple IIgs, Q will
do it, too.)
(If the only kind of "monitor" you care about is the one
you're looking at right now, this command isn't for
you--it's for people addicted to machine language.)
|
||||
|
||||
mon -- enter the Monitor
|
||||
|
||||
syntax: mon
|
||||
|
||||
ex: mon
|
||||
|
||||
Dumps you into your Apple's monitor. Ctrl-Y or RESET or
|
||||
3D0G will get you back to Davex. (On an Apple IIgs, Q will
|
||||
do it, too.)
|
||||
|
||||
(If the only kind of "monitor" you care about is the one
|
||||
you're looking at right now, this command isn't for
|
||||
you--it's for people addicted to machine language.)
|
||||
|
|
|
|||
|
|
@ -1 +1,17 @@
|
|||
move -- copy, deleting the original Alias for: copy -d
syntax: move <source pathname> [<dest pathname>]
ex: move this.file that.dir
move =.0 /disk2/extras
move /disk1/that
'move' is an alias for 'copy -d'. It has the effect of "moving"
a file from one directory to another, on a different volume or
the same volume. Wildcards are allowed.
Note: Before Davex v1.25, move was a built-in command, but it
still worked exactly like 'copy -d'.
(see also: copy)
|
||||
|
||||
move -- copy, deleting the original Alias for: copy -d
|
||||
|
||||
syntax: move <source pathname> [<dest pathname>]
|
||||
|
||||
ex: move this.file that.dir
|
||||
move =.0 /disk2/extras
|
||||
move /disk1/that
|
||||
|
||||
'move' is an alias for 'copy -d'. It has the effect of "moving"
|
||||
a file from one directory to another, on a different volume or
|
||||
the same volume. Wildcards are allowed.
|
||||
|
||||
Note: Before Davex v1.25, move was a built-in command, but it
|
||||
still worked exactly like 'copy -d'.
|
||||
|
||||
(see also: copy)
|
||||
|
|
|
|||
11
doc/help/Num
11
doc/help/Num
|
|
@ -1 +1,10 @@
|
|||
num -- print a number in decimal and hex
syntax: num <integer>
ex: num $FF1800
num 65385
'num' accepts a number from 0 to 16777215 and prints it
in base 10 and base 16.
|
||||
|
||||
num -- print a number in decimal and hex
|
||||
|
||||
syntax: num <integer>
|
||||
|
||||
ex: num $FF1800
|
||||
num 65385
|
||||
|
||||
'num' accepts a number from 0 to 16777215 and prints it
|
||||
in base 10 and base 16.
|
||||
|
|
|
|||
|
|
@ -1 +1,16 @@
|
|||
online -- show names of online volumes
syntax: online [-o]
ex: online
online -o
Shows names and locations of online volumes. If -o is given,
only ProDOS volumes are shown.
Sample output:
.32 = /ram
.61 = /thatdisk
.62 = <not ProDOS volume>
|
||||
|
||||
online -- show names of online volumes
|
||||
|
||||
syntax: online [-o]
|
||||
|
||||
ex: online
|
||||
online -o
|
||||
|
||||
Shows names and locations of online volumes. If -o is given,
|
||||
only ProDOS volumes are shown.
|
||||
|
||||
Sample output:
|
||||
|
||||
.32 = /ram
|
||||
.61 = /thatdisk
|
||||
.62 = <not ProDOS volume>
|
||||
|
|
|
|||
|
|
@ -1 +1,13 @@
|
|||
origin | or -- set prefix to the volume Davex is running from
Alias for "%;top"
syntax: origin
ex: origin
or
This is just an alias for "%;top"--it sets your prefix to the
top directory of the disk Davex is running from.
(see also: prefix, over, top, up)
|
||||
|
||||
origin | or -- set prefix to the volume Davex is running from
|
||||
Alias for "%;top"
|
||||
|
||||
syntax: origin
|
||||
|
||||
ex: origin
|
||||
or
|
||||
|
||||
This is just an alias for "%;top"--it sets your prefix to the
|
||||
top directory of the disk Davex is running from.
|
||||
|
||||
(see also: prefix, over, top, up)
|
||||
|
|
|
|||
|
|
@ -1 +1,12 @@
|
|||
over -- move to another directory Alias for: up;prefix
syntax: over <pathname>
ex: over that
over a/b
Changes prefix to another directory at the same level. 'over'
does an 'up' and then does 'down <path>'.
(see also: up, down, prefix, origin)
|
||||
|
||||
over -- move to another directory Alias for: up;prefix
|
||||
|
||||
syntax: over <pathname>
|
||||
|
||||
ex: over that
|
||||
over a/b
|
||||
|
||||
Changes prefix to another directory at the same level. 'over'
|
||||
does an 'up' and then does 'down <path>'.
|
||||
|
||||
(see also: up, down, prefix, origin)
|
||||
|
|
|
|||
42
doc/help/PG
42
doc/help/PG
|
|
@ -1 +1,41 @@
|
|||
pg -- display plain text or AWP file a page (screen) at a time
syntax: pg <pathname> [-h] [-f] [-u] [-l] [-t tab_string]
ex: pg this
pg ?:txt -h
como newfile;pg oldfile -l
pg that -t" "
Types contents of a file (any type, not just TXT). Wildcards are
allowed. -h generates a header giving the date/time the file was last
modified. -f disables filtering of control characters; normally they
are filtered out.
-u and -l force all alphabetic characters to display in uppercase or
lowercase, respectively.
-p begins a new page after the file is printed.
-t lets you specify a string to be printed in place of each TAB
character (Ctrl-I). You may want to make an alias for 'pg' with
a tab string.
At the bottom of each screen, you are prompted
--- xx% --- more? (Y/N)
where xx is the percent of the file (calculated by counting
characters, not lines) you have read so far.
When output is redirected to a file or to the printer, no prompting
takes place.
Note: many file types do not contain plain text. This command
knows how to interpret AWP files, but simply displays all other
files byte-for-byte. If you type a SYS file, for example, you
will get a lot of garbage and (probably) a few readable
messages.
(see also: type, como, strings, alias)
|
||||
|
||||
pg -- display plain text or AWP file a page (screen) at a time
|
||||
|
||||
syntax: pg <pathname> [-h] [-f] [-u] [-l] [-t tab_string]
|
||||
|
||||
ex: pg this
|
||||
pg ?:txt -h
|
||||
como newfile;pg oldfile -l
|
||||
pg that -t" "
|
||||
|
||||
Types contents of a file (any type, not just TXT). Wildcards are
|
||||
allowed. -h generates a header giving the date/time the file was last
|
||||
modified. -f disables filtering of control characters; normally they
|
||||
are filtered out.
|
||||
|
||||
-u and -l force all alphabetic characters to display in uppercase or
|
||||
lowercase, respectively.
|
||||
|
||||
-p begins a new page after the file is printed.
|
||||
|
||||
-t lets you specify a string to be printed in place of each TAB
|
||||
character (Ctrl-I). You may want to make an alias for 'pg' with
|
||||
a tab string.
|
||||
|
||||
At the bottom of each screen, you are prompted
|
||||
|
||||
--- xx% --- more? (Y/N)
|
||||
|
||||
where xx is the percent of the file (calculated by counting
|
||||
characters, not lines) you have read so far.
|
||||
|
||||
When output is redirected to a file or to the printer, no prompting
|
||||
takes place.
|
||||
|
||||
Note: many file types do not contain plain text. This command
|
||||
knows how to interpret AWP files, but simply displays all other
|
||||
files byte-for-byte. If you type a SYS file, for example, you
|
||||
will get a lot of garbage and (probably) a few readable
|
||||
messages.
|
||||
|
||||
(see also: type, como, strings, alias)
|
||||
|
|
|
|||
|
|
@ -1 +1,27 @@
|
|||
pset -- set up print options for NEC8023/ProWriter/Imagewriter
(EXTERNAL)
syntax: pset [-n] [-1 y|n] [-b y|n] [-u y|n] [-8 y|n]
[-s y|n] [-l <integer>] [-p <integer>]
[-r y|n]
ex: pset -n
pset -p12 -by -un
pset -sy -1n -l10
Sets print options, assuming a NEC 8023 or ProWriter or ImageWriter is
connected. Each option is explained below:
-n (normal) turn off special modes and set 10 cpi
-1 y|n -1y set unidirectional printing; -1n sets bidirectional
-b y|n boldface: yes or no
-u y|n underlining: yes or no
-8 y|n eight lines per inch: yes or no (no=6 lines per inch)
-s y|n skip to new page every 60 lines: yes or no
-l # set left margin in characters (normally 0)
-p # set pitch; may be 5, 6, 8, 10, 12, or 17
-r y|n reverse formfeed direction; y=reverse, n=forward
Note: -s and -n reset the printer's top of form, so they should be
used only when the printer is at the top of a page.
|
||||
|
||||
pset -- set up print options for NEC8023/ProWriter/Imagewriter
|
||||
(EXTERNAL)
|
||||
|
||||
syntax: pset [-n] [-1 y|n] [-b y|n] [-u y|n] [-8 y|n]
|
||||
[-s y|n] [-l <integer>] [-p <integer>]
|
||||
[-r y|n]
|
||||
|
||||
ex: pset -n
|
||||
pset -p12 -by -un
|
||||
pset -sy -1n -l10
|
||||
|
||||
Sets print options, assuming a NEC 8023 or ProWriter or ImageWriter is
|
||||
connected. Each option is explained below:
|
||||
|
||||
-n (normal) turn off special modes and set 10 cpi
|
||||
-1 y|n -1y set unidirectional printing; -1n sets bidirectional
|
||||
-b y|n boldface: yes or no
|
||||
-u y|n underlining: yes or no
|
||||
-8 y|n eight lines per inch: yes or no (no=6 lines per inch)
|
||||
-s y|n skip to new page every 60 lines: yes or no
|
||||
-l # set left margin in characters (normally 0)
|
||||
-p # set pitch; may be 5, 6, 8, 10, 12, or 17
|
||||
-r y|n reverse formfeed direction; y=reverse, n=forward
|
||||
|
||||
Note: -s and -n reset the printer's top of form, so they should be
|
||||
used only when the printer is at the top of a page.
|
||||
|
|
|
|||
|
|
@ -1 +1,12 @@
|
|||
ptype -- display a Pascal Text file ($03) (EXTERNAL)
syntax: ptype <pathname>
ex: ptype foo.bar
ptype .61=:$03
'ptype' displays the contents of a Pascal Text file (filetype
$03). The first 1024 bytes are ignored; the rest of the file
is plain text except that Ctrl-P ($10) means the next byte
represents a number of blanks.
|
||||
|
||||
ptype -- display a Pascal Text file ($03) (EXTERNAL)
|
||||
|
||||
syntax: ptype <pathname>
|
||||
|
||||
ex: ptype foo.bar
|
||||
ptype .61=:$03
|
||||
|
||||
'ptype' displays the contents of a Pascal Text file (filetype
|
||||
$03). The first 1024 bytes are ignored; the rest of the file
|
||||
is plain text except that Ctrl-P ($10) means the next byte
|
||||
represents a number of blanks.
|
||||
|
|
|
|||
|
|
@ -1 +1,19 @@
|
|||
SHORTHAND FOR PATHNAMES
'%' stands for the name of the directory Davex is in.
A period (.) followed by a slot and drive number stands for
the name of the volume in the specified slot and drive.
'.' stands for the current directory, and '..' stands for
the directory above the current one.
Examples:
info .61/prodos
info .61prodos
../help
..help
info %/davex
info %davex
ffind . -f sys
|
||||
|
||||
SHORTHAND FOR PATHNAMES
|
||||
|
||||
'%' stands for the name of the directory Davex is in.
|
||||
|
||||
A period (.) followed by a slot and drive number stands for
|
||||
the name of the volume in the specified slot and drive.
|
||||
|
||||
'.' stands for the current directory, and '..' stands for
|
||||
the directory above the current one.
|
||||
|
||||
Examples:
|
||||
info .61/prodos
|
||||
info .61prodos
|
||||
../help
|
||||
..help
|
||||
info %/davex
|
||||
info %davex
|
||||
ffind . -f sys
|
||||
|
|
|
|||
|
|
@ -1 +1,39 @@
|
|||
prefix -- change prefix
syntax: prefix <pathname>
ex: prefix /disk/dir
prefix x/y
prefix %help
prefix .62blah
prefix m=
/mydisk/dir1
.61
Changes the prefix (which is displayed as your prompt in
Davex). (Typing 'prefix' with no pathname makes your prefix
empty; this is not usually desirable.)
Note that an IMPLIED prefix command is done if you type a
complete pathname (including one starting with "%" or ".xx"),
or if a partial pathname is found in your scan list.
If a partial pathname is given, it is appended to the
current prefix. So "prefix letters" when your prefix is
already "/disk" will make your prefix "/disk/letters".
You can also set your prefix just by typing the name of a
directory. The process is not quite the same--if you type a
partial pathname, Davex uses your scan list to find the
directory. It follows the same rules as for launching SYS
or S16 files, but if it finds a DIR, it just sets your
prefix.
For example, if the first entry in your scan list is "*",
you can always change to a subdirectory of the current
directory just by typing the subdirectory's name (unless
that name is an internal Davex command!).
(see also: origin, up, top, over, scan)
|
||||
|
||||
prefix -- change prefix
|
||||
|
||||
syntax: prefix <pathname>
|
||||
|
||||
ex: prefix /disk/dir
|
||||
prefix x/y
|
||||
prefix %help
|
||||
prefix .62blah
|
||||
prefix m=
|
||||
/mydisk/dir1
|
||||
.61
|
||||
|
||||
Changes the prefix (which is displayed as your prompt in
|
||||
Davex). (Typing 'prefix' with no pathname makes your prefix
|
||||
empty; this is not usually desirable.)
|
||||
|
||||
Note that an IMPLIED prefix command is done if you type a
|
||||
complete pathname (including one starting with "%" or ".xx"),
|
||||
or if a partial pathname is found in your scan list.
|
||||
|
||||
If a partial pathname is given, it is appended to the
|
||||
current prefix. So "prefix letters" when your prefix is
|
||||
already "/disk" will make your prefix "/disk/letters".
|
||||
|
||||
You can also set your prefix just by typing the name of a
|
||||
directory. The process is not quite the same--if you type a
|
||||
partial pathname, Davex uses your scan list to find the
|
||||
directory. It follows the same rules as for launching SYS
|
||||
or S16 files, but if it finds a DIR, it just sets your
|
||||
prefix.
|
||||
|
||||
For example, if the first entry in your scan list is "*",
|
||||
you can always change to a subdirectory of the current
|
||||
directory just by typing the subdirectory's name (unless
|
||||
that name is an internal Davex command!).
|
||||
|
||||
(see also: origin, up, top, over, scan)
|
||||
|
||||
|
|
|
|||
|
|
@ -1 +1,15 @@
|
|||
prot -- protect file
syntax: prot <pathname> [-r] [-w] [-n] [-d]
ex: prot this
prot ? -rwn
Allows only the specified rights to a file: r)ead, w)rite,
ren)ame, and d)elete. Wildcards are allowed.
prot x -r = lock x
prot x -rwnd = unlock x
(see also: lock, unlock)
|
||||
|
||||
prot -- protect file
|
||||
|
||||
syntax: prot <pathname> [-r] [-w] [-n] [-d]
|
||||
|
||||
ex: prot this
|
||||
prot ? -rwn
|
||||
|
||||
Allows only the specified rights to a file: r)ead, w)rite,
|
||||
ren)ame, and d)elete. Wildcards are allowed.
|
||||
|
||||
prot x -r = lock x
|
||||
prot x -rwnd = unlock x
|
||||
|
||||
(see also: lock, unlock)
|
||||
|
|
|
|||
|
|
@ -1 +1,46 @@
|
|||
ram3 -- disable/enable ram drive (EXTERNAL) [v1.1] Written by Jeff Ding
syntax: ram3 {[-r] [-f]} {[-a] [-vxxxxx] [-ixx]}
ex: ram3
ram3 -r -f
ram3 -a
ram3 -a -v65280 -i15
'ram3' is used to disable the ram driver in slot 3 drive 2. Once
disabled, you can then use the auxiliary memory in your computer
for programs or for double hi-res.
'ram3' with no options will tell you if it is installed or not.
Other options are as follows:
-r: remove -- This option will remove the driver in slot 3 drive
2. You will be notified and asked to remove the volume if it
is not empty. If the vector or the identification of
the ram driver is different from the standard, it will be
printed along with a message stating the driver has been
removed. See -v and -i for the description of the vector
and identification. Be sure to keep track of these values
so that when you want to re-install the driver you can use
the original values.
-f: force removal -- This option used in connection with the
-r option will remove the driver even if the volume is
not empty. Use this option with caution!
-a: add -- This option alone will re-install the standard ProDOS
64k /ram driver. This option alone will not work on a II+ because
it does not have the necessary auxiliary memory and driver. If you
want to install a driver for a third party ram card on a II+, you
must use the -a option in conjunction with the -v option.
-v: vector -- This option used in connection with the -a option
will allow you to install a driver at a specific location
xxxxx. This vector points to the entry point of the driver
routine. The location for the standard /ram driver is 65280.
-i: identification -- This option used in connection with the -a
option will allow you to set the identification of the /ram
drive. The identification is the lower nybble of the device
number. The standard identification is 15.
|
||||
|
||||
ram3 -- disable/enable ram drive (EXTERNAL) [v1.1] Written by Jeff Ding
|
||||
|
||||
syntax: ram3 {[-r] [-f]} {[-a] [-vxxxxx] [-ixx]}
|
||||
|
||||
ex: ram3
|
||||
ram3 -r -f
|
||||
ram3 -a
|
||||
ram3 -a -v65280 -i15
|
||||
|
||||
'ram3' is used to disable the ram driver in slot 3 drive 2. Once
|
||||
disabled, you can then use the auxiliary memory in your computer
|
||||
for programs or for double hi-res.
|
||||
|
||||
'ram3' with no options will tell you if it is installed or not.
|
||||
Other options are as follows:
|
||||
|
||||
-r: remove -- This option will remove the driver in slot 3 drive
|
||||
2. You will be notified and asked to remove the volume if it
|
||||
is not empty. If the vector or the identification of
|
||||
the ram driver is different from the standard, it will be
|
||||
printed along with a message stating the driver has been
|
||||
removed. See -v and -i for the description of the vector
|
||||
and identification. Be sure to keep track of these values
|
||||
so that when you want to re-install the driver you can use
|
||||
the original values.
|
||||
|
||||
-f: force removal -- This option used in connection with the
|
||||
-r option will remove the driver even if the volume is
|
||||
not empty. Use this option with caution!
|
||||
|
||||
-a: add -- This option alone will re-install the standard ProDOS
|
||||
64k /ram driver. This option alone will not work on a II+ because
|
||||
it does not have the necessary auxiliary memory and driver. If you
|
||||
want to install a driver for a third party ram card on a II+, you
|
||||
must use the -a option in conjunction with the -v option.
|
||||
|
||||
-v: vector -- This option used in connection with the -a option
|
||||
will allow you to install a driver at a specific location
|
||||
xxxxx. This vector points to the entry point of the driver
|
||||
routine. The location for the standard /ram driver is 65280.
|
||||
|
||||
-i: identification -- This option used in connection with the -a
|
||||
option will allow you to set the identification of the /ram
|
||||
drive. The identification is the lower nybble of the device
|
||||
number. The standard identification is 15.
|
||||
|
|
|
|||
|
|
@ -1 +1,22 @@
|
|||
rename -- change name of file, directory, or volume
syntax: rename <pathname> <pathname>
ex: rename this that
rename /blank /mydisk
rename letter= ltr.=
Changes the name of a file, directory, or volume. Wildcards
are allowed, as in the third example. A wildcard in the
second pathname expands to the same text the wildcard in the
first pathname is matching. The third example changes the
names of files beginning with "letter" to begin with "ltr."
instead.
If you change the name of an AppleWorks file (filetypes AWP,
ADB, and ASP) from Davex, you may find the capitalization to
be strange. This is because AppleWorks stores the
capitalization information in the file's Auxiliary type,
which is not affected by this command. Use Apple-N while
editing the file in Appleworks to fix the capitalization.
|
||||
|
||||
rename -- change name of file, directory, or volume
|
||||
|
||||
syntax: rename <pathname> <pathname>
|
||||
|
||||
ex: rename this that
|
||||
rename /blank /mydisk
|
||||
rename letter= ltr.=
|
||||
|
||||
Changes the name of a file, directory, or volume. Wildcards
|
||||
are allowed, as in the third example. A wildcard in the
|
||||
second pathname expands to the same text the wildcard in the
|
||||
first pathname is matching. The third example changes the
|
||||
names of files beginning with "letter" to begin with "ltr."
|
||||
instead.
|
||||
|
||||
If you change the name of an AppleWorks file (filetypes AWP,
|
||||
ADB, and ASP) from Davex, you may find the capitalization to
|
||||
be strange. This is because AppleWorks stores the
|
||||
capitalization information in the file's Auxiliary type,
|
||||
which is not affected by this command. Use Apple-N while
|
||||
editing the file in Appleworks to fix the capitalization.
|
||||
|
|
|
|||
17
doc/help/Rep
17
doc/help/Rep
|
|
@ -1 +1,16 @@
|
|||
rep -- repeat: execute a command several times
syntax: rep <integer>
ex: rep 10;echo "Ten!"
como &;rep 5;type handout= -p
Executes the next command the specified number of times.
'rep 0' has no effect, and the largest number 'rep' accepts
is 65535. 'rep' will not repeat another 'rep' command.
The second example prints 5 copies of all files beginning in
"handout" to the printer. All repetitions are executed for
each file matching the wildcard before Davex looks for
another wildcard match.
|
||||
|
||||
rep -- repeat: execute a command several times
|
||||
|
||||
syntax: rep <integer>
|
||||
|
||||
ex: rep 10;echo "Ten!"
|
||||
como &;rep 5;type handout= -p
|
||||
|
||||
Executes the next command the specified number of times.
|
||||
'rep 0' has no effect, and the largest number 'rep' accepts
|
||||
is 65535. 'rep' will not repeat another 'rep' command.
|
||||
|
||||
The second example prints 5 copies of all files beginning in
|
||||
"handout" to the printer. All repetitions are executed for
|
||||
each file matching the wildcard before Davex looks for
|
||||
another wildcard match.
|
||||
|
|
|
|||
|
|
@ -1 +1,29 @@
|
|||
scan -- examine or change the scan list
syntax: scan [-r<string>] [-a<string>] [-z]
ex: scan
scan -z
scan -a /ram
scan -a *
scan -a .61
scan -a .62utils
scan -r /hard2/sys/
With no options, prints the list of directories Davex scans when
you type something that isn't an internal command.
Use the -a and -r options to add or remove a paths from the list.
The special path '*' in the scan list tells Davex to scan the
directory your prefix is set to.
Use 'scan -z' to reset the scan list to the default (the default
is "%" followed by "*").
Note: If '%' and '.##' shorthand forms are used in the scan
list, they are expanded during scanning, not when they are entered
into the list. This lets you specify that Davex should scan
certain _drives_ (or directories on whatever volumes are found in
them) rather than certain volumes.
|
||||
|
||||
scan -- examine or change the scan list
|
||||
|
||||
syntax: scan [-r<string>] [-a<string>] [-z]
|
||||
|
||||
ex: scan
|
||||
scan -z
|
||||
scan -a /ram
|
||||
scan -a *
|
||||
scan -a .61
|
||||
scan -a .62utils
|
||||
scan -r /hard2/sys/
|
||||
|
||||
With no options, prints the list of directories Davex scans when
|
||||
you type something that isn't an internal command.
|
||||
|
||||
Use the -a and -r options to add or remove a paths from the list.
|
||||
|
||||
The special path '*' in the scan list tells Davex to scan the
|
||||
directory your prefix is set to.
|
||||
|
||||
Use 'scan -z' to reset the scan list to the default (the default
|
||||
is "%" followed by "*").
|
||||
|
||||
Note: If '%' and '.##' shorthand forms are used in the scan
|
||||
list, they are expanded during scanning, not when they are entered
|
||||
into the list. This lets you specify that Davex should scan
|
||||
certain _drives_ (or directories on whatever volumes are found in
|
||||
them) rather than certain volumes.
|
||||
|
|
|
|||
|
|
@ -1 +1,20 @@
|
|||
setdate -- a crude way to set the date
syntax: setdate <month> <day> <year> <hours> <minutes> [-p]
ex: setdate 4 10 88 22 40 --April 10, 1988 at 10:40 pm
setdate 4 10 88 10 40 -p --same date
setdate 3 28 67 0 10 --March 28, 1967 at 12:10 am
'setdate' is a straightforward command for setting the
ProDOS date and time. -p means "p.m." and is the same as
adding 12 to the hours value.
'setdate' is useful only if your Apple does not have a clock
card. (The Apple IIgs has a clock built in; if ProDOS does not
know the time on your GS, it's because you are using ProDOS 1.1.1
or earlier.)
If you want to be weird, you can type BF06:60 from the monitor
to disconnect the clock driver from ProDOS.
|
||||
|
||||
setdate -- a crude way to set the date
|
||||
|
||||
syntax: setdate <month> <day> <year> <hours> <minutes> [-p]
|
||||
|
||||
ex: setdate 4 10 88 22 40 --April 10, 1988 at 10:40 pm
|
||||
setdate 4 10 88 10 40 -p --same date
|
||||
setdate 3 28 67 0 10 --March 28, 1967 at 12:10 am
|
||||
|
||||
'setdate' is a straightforward command for setting the
|
||||
ProDOS date and time. -p means "p.m." and is the same as
|
||||
adding 12 to the hours value.
|
||||
|
||||
'setdate' is useful only if your Apple does not have a clock
|
||||
card. (The Apple IIgs has a clock built in; if ProDOS does not
|
||||
know the time on your GS, it's because you are using ProDOS 1.1.1
|
||||
or earlier.)
|
||||
|
||||
If you want to be weird, you can type BF06:60 from the monitor
|
||||
to disconnect the clock driver from ProDOS.
|
||||
|
|
|
|||
|
|
@ -1 +1,33 @@
|
|||
setstart -- examine or set a SYS file's startup path
syntax: setstart <pathname> [-s <string>]
ex: setstart /disk1/basic.system
setstart my.program -s /disk1/foo.bar
Displays or changes the default startup pathname of the
specified SYS file. Wildcards are allowed.
If the -s parameter is given, the default startup path is
changed to the string you specify.
Example:
setstart basic.system
would print
Startup path is "startup"
on an unmodified copy of BASIC.SYSTEM, because STARTUP is
the file BASIC.SYSTEM tries to run when you don't specify
another path.
To make BASIC.SYSTEM run a different file by default, use
setstart basic.system -s your.prog.name
Possible errors (in addition to ProDOS errors):
*** not a SYS file
*** SYS file does not have a startup buffer
*** path too long for the startup buffer
|
||||
|
||||
setstart -- examine or set a SYS file's startup path
|
||||
|
||||
syntax: setstart <pathname> [-s <string>]
|
||||
|
||||
ex: setstart /disk1/basic.system
|
||||
setstart my.program -s /disk1/foo.bar
|
||||
|
||||
Displays or changes the default startup pathname of the
|
||||
specified SYS file. Wildcards are allowed.
|
||||
|
||||
If the -s parameter is given, the default startup path is
|
||||
changed to the string you specify.
|
||||
|
||||
Example:
|
||||
setstart basic.system
|
||||
|
||||
would print
|
||||
|
||||
Startup path is "startup"
|
||||
|
||||
on an unmodified copy of BASIC.SYSTEM, because STARTUP is
|
||||
the file BASIC.SYSTEM tries to run when you don't specify
|
||||
another path.
|
||||
|
||||
To make BASIC.SYSTEM run a different file by default, use
|
||||
|
||||
setstart basic.system -s your.prog.name
|
||||
|
||||
Possible errors (in addition to ProDOS errors):
|
||||
*** not a SYS file
|
||||
*** SYS file does not have a startup buffer
|
||||
*** path too long for the startup buffer
|
||||
|
|
|
|||
|
|
@ -1 +1,11 @@
|
|||
$ -- print copyright notice and shareware notice
syntax: $
ex: $
The '$' command prints a copyright notice and a shareware
notice for Davex. You may want to type Apple-H when the
notice is on your screen to print a hard copy to your
printer.
|
||||
|
||||
$ -- print copyright notice and shareware notice
|
||||
|
||||
syntax: $
|
||||
|
||||
ex: $
|
||||
|
||||
The '$' command prints a copyright notice and a shareware
|
||||
notice for Davex. You may want to type Apple-H when the
|
||||
notice is on your screen to print a hard copy to your
|
||||
printer.
|
||||
|
|
|
|||
|
|
@ -1 +1,27 @@
|
|||
size -- show size of file or directory
syntax: size <pathname>
ex: size this
size =:sys
size .61=:dir
For a non-directory file, prints file size in blocks and in
bytes. For a directory, compute and print the sum of the
sizes of all the files and directories within the directory.
Wildcards are allowed.
The total size in BYTES of a directory is often MUCH smaller
than 512 times its size in BLOCKS, even though all blocks
are 512 bytes long. This is because not all the bytes of a
file's last block are used. As an extreme example, a
directory containing 12 files of one byte each would have a
size of 13 blocks (1 for the directory and 1 each for the
files), but only 524 bytes (512 for the directory block and
1 each for the files).
(Note that the size reported for a volume directory includes
actual directory blocks but omits the 2 boot blocks and the
bitmap block(s). There is one bitmap block for every 4096
blocks on the volume.)
|
||||
|
||||
size -- show size of file or directory
|
||||
|
||||
syntax: size <pathname>
|
||||
|
||||
ex: size this
|
||||
size =:sys
|
||||
size .61=:dir
|
||||
|
||||
For a non-directory file, prints file size in blocks and in
|
||||
bytes. For a directory, compute and print the sum of the
|
||||
sizes of all the files and directories within the directory.
|
||||
Wildcards are allowed.
|
||||
|
||||
The total size in BYTES of a directory is often MUCH smaller
|
||||
than 512 times its size in BLOCKS, even though all blocks
|
||||
are 512 bytes long. This is because not all the bytes of a
|
||||
file's last block are used. As an extreme example, a
|
||||
directory containing 12 files of one byte each would have a
|
||||
size of 13 blocks (1 for the directory and 1 each for the
|
||||
files), but only 524 bytes (512 for the directory block and
|
||||
1 each for the files).
|
||||
|
||||
(Note that the size reported for a volume directory includes
|
||||
actual directory blocks but omits the 2 boot blocks and the
|
||||
bitmap block(s). There is one bitmap block for every 4096
|
||||
blocks on the volume.)
|
||||
|
|
|
|||
|
|
@ -1 +1,69 @@
|
|||
split -- split off sections of files (EXTERNAL) [v1.1]
Written by Jeff Ding
syntax: split <input pathname> [<output pathname>] [-s<number>]
[-e<number>|-l<number>] [-b y|n] [-f] [-d<number>]
[-w<margin>]
ex: split infile outfile -s0 -e1023
split infile -s50 -e100 -bn
split file1 -s50 -l100 -bn -m60
'Split' splits off a section of the input file into the output file.
If the output file is not specified, output goes to the screen. The
input file is never modified. Wildcards are supported.
'Split' works with any file type, but the input file is always treated
as a raw collection of bytes. This means, for example, that you can
split off a piece of an AWP file, but the resulting smaller file will
not be a valid AWP file. However, you can always use 'combine' to put
a big file back together from pieces created with 'split'.
The starting position is determined by the number after -s. The ending
position is determined by either -e (end) or -l (length). Note that
length = end - start + 1.
The starting/ending/length parameters are measured in either bytes or
lines. Use the -b (count by bytes) parameter with a yes/no value to
choose: -by to count by bytes; -bn to count by lines. If you don't
use the -b option, 'split' counts by bytes.
Options are as follows:
output pathname: split section is saved to this file. If not
specified, output goes to the screen. The output
file type will always be the same as the input
file type.
-s: starting offset position. The first byte in a file has an
offset of 0. The first line in a file has an offset of 1.
If not specified, the start position is set to the beginning
of the file.
-e: ending offset position. Maximum offset is 16777214. If not
specified, the ending position is set to the end of the file.
-l: length of section. Maximum length is 16777214. Use either
-e OR -l. If -e is given, -l is ignored.
-b y|n: measurement in bytes (yes) or lines (no). Bytes is the
default.
-f: force overwrite. Skips the "Okay to overwrite" question if
the output file already exists.
-d <ascii number>: this determines what character is used for the line
delimiter. Use the ascii value for the character.
-w <margin>: wrap margin. Affects output to the screen only. This
will force a carriage return when either the margin or
a space within 9 characters of the margin is reached.
Allowed values are 0 through 255. A 0 value has the same
effect as not using the option.
Version 1.1 fixes a bug when specifying an output file and not using
the -e option.
(see also: combine)
|
||||
|
||||
split -- split off sections of files (EXTERNAL) [v1.1]
|
||||
Written by Jeff Ding
|
||||
|
||||
syntax: split <input pathname> [<output pathname>] [-s<number>]
|
||||
[-e<number>|-l<number>] [-b y|n] [-f] [-d<number>]
|
||||
[-w<margin>]
|
||||
|
||||
ex: split infile outfile -s0 -e1023
|
||||
split infile -s50 -e100 -bn
|
||||
split file1 -s50 -l100 -bn -m60
|
||||
|
||||
'Split' splits off a section of the input file into the output file.
|
||||
If the output file is not specified, output goes to the screen. The
|
||||
input file is never modified. Wildcards are supported.
|
||||
|
||||
'Split' works with any file type, but the input file is always treated
|
||||
as a raw collection of bytes. This means, for example, that you can
|
||||
split off a piece of an AWP file, but the resulting smaller file will
|
||||
not be a valid AWP file. However, you can always use 'combine' to put
|
||||
a big file back together from pieces created with 'split'.
|
||||
|
||||
The starting position is determined by the number after -s. The ending
|
||||
position is determined by either -e (end) or -l (length). Note that
|
||||
length = end - start + 1.
|
||||
|
||||
The starting/ending/length parameters are measured in either bytes or
|
||||
lines. Use the -b (count by bytes) parameter with a yes/no value to
|
||||
choose: -by to count by bytes; -bn to count by lines. If you don't
|
||||
use the -b option, 'split' counts by bytes.
|
||||
|
||||
Options are as follows:
|
||||
|
||||
output pathname: split section is saved to this file. If not
|
||||
specified, output goes to the screen. The output
|
||||
file type will always be the same as the input
|
||||
file type.
|
||||
|
||||
-s: starting offset position. The first byte in a file has an
|
||||
offset of 0. The first line in a file has an offset of 1.
|
||||
If not specified, the start position is set to the beginning
|
||||
of the file.
|
||||
|
||||
-e: ending offset position. Maximum offset is 16777214. If not
|
||||
specified, the ending position is set to the end of the file.
|
||||
|
||||
-l: length of section. Maximum length is 16777214. Use either
|
||||
-e OR -l. If -e is given, -l is ignored.
|
||||
|
||||
-b y|n: measurement in bytes (yes) or lines (no). Bytes is the
|
||||
default.
|
||||
|
||||
-f: force overwrite. Skips the "Okay to overwrite" question if
|
||||
the output file already exists.
|
||||
|
||||
-d <ascii number>: this determines what character is used for the line
|
||||
delimiter. Use the ascii value for the character.
|
||||
|
||||
-w <margin>: wrap margin. Affects output to the screen only. This
|
||||
will force a carriage return when either the margin or
|
||||
a space within 9 characters of the margin is reached.
|
||||
Allowed values are 0 through 255. A 0 value has the same
|
||||
effect as not using the option.
|
||||
|
||||
|
||||
Version 1.1 fixes a bug when specifying an output file and not using
|
||||
the -e option.
|
||||
|
||||
(see also: combine)
|
||||
|
|
|
|||
|
|
@ -1 +1,43 @@
|
|||
spool -- spool files for later printing
syntax: spool [<pathname>] [-z] [-x <int1>]
ex: spool ?:txt
spool
spool -z
spool -x3
Queues files for background printing. Wildcards are allowed. You
must remain in Davex until the printing completes, and you may not
redirect output to the printer (see 'como'), since that would make a
mess.
Use the 'config' command to set the slot 'spool' will print to.
'spool -z' Zaps the spool queue (cancels printing of all spooled
files) and formfeeds the printer.
'spool' shows a numbered list of files waiting to print.
'spool -x' cancels one file in the queue by number.
NOTE: The text of spooled files is sent directly to the printer.
This is fine for TXT files (and SRC files, and possibly some
other filetypes). It is NOT fine for AWP files (try it if you
want...it's sort of entertaining).
A future Davex version will probably support spooling AWP
files. For now, create a temporary file, 'pg' the AWP file
into it, and spool the temporary file. Example:
como temp;pg my.awp.file
spool temp
Spool does not work well with speech synthesizers; Davex does not have
control while the system is waiting for keyboard input. Speech
synthesizer users can use the 'wait' command to let spooled files
print.
(SPOOL stands for Simultaneous Peripheral Operation On-Line.)
|
||||
|
||||
spool -- spool files for later printing
|
||||
|
||||
syntax: spool [<pathname>] [-z] [-x <int1>]
|
||||
|
||||
ex: spool ?:txt
|
||||
spool
|
||||
spool -z
|
||||
spool -x3
|
||||
|
||||
Queues files for background printing. Wildcards are allowed. You
|
||||
must remain in Davex until the printing completes, and you may not
|
||||
redirect output to the printer (see 'como'), since that would make a
|
||||
mess.
|
||||
|
||||
Use the 'config' command to set the slot 'spool' will print to.
|
||||
|
||||
'spool -z' Zaps the spool queue (cancels printing of all spooled
|
||||
files) and formfeeds the printer.
|
||||
|
||||
'spool' shows a numbered list of files waiting to print.
|
||||
|
||||
'spool -x' cancels one file in the queue by number.
|
||||
|
||||
|
||||
NOTE: The text of spooled files is sent directly to the printer.
|
||||
This is fine for TXT files (and SRC files, and possibly some
|
||||
other filetypes). It is NOT fine for AWP files (try it if you
|
||||
want...it's sort of entertaining).
|
||||
|
||||
A future Davex version will probably support spooling AWP
|
||||
files. For now, create a temporary file, 'pg' the AWP file
|
||||
into it, and spool the temporary file. Example:
|
||||
|
||||
como temp;pg my.awp.file
|
||||
spool temp
|
||||
|
||||
Spool does not work well with speech synthesizers; Davex does not have
|
||||
control while the system is waiting for keyboard input. Speech
|
||||
synthesizer users can use the 'wait' command to let spooled files
|
||||
print.
|
||||
|
||||
(SPOOL stands for Simultaneous Peripheral Operation On-Line.)
|
||||
|
|
|
|||
|
|
@ -1 +1,16 @@
|
|||
strings -- find printable strings in a file (EXTERNAL) [v1.0]
syntax: strings <pathname> [-L <minimum_length>] [-o] [-m]
ex: strings thatfile
strings ?:sys -o -l10
Searches for and displays possibly readable ASCII strings in a file
of any type. Wildcards are allowed.
The -L option specifies the minimum number of consecutive printable
characters that qualifies as a printable string; the default is 6.
The -o option stops the offsets of the found strings from being
displayed. The -m option allows strings to have mixed low-ASCII (bit
7 clear) and high-ASCII (bit 7 set) characters in them.
|
||||
|
||||
strings -- find printable strings in a file (EXTERNAL) [v1.0]
|
||||
|
||||
syntax: strings <pathname> [-L <minimum_length>] [-o] [-m]
|
||||
|
||||
ex: strings thatfile
|
||||
strings ?:sys -o -l10
|
||||
|
||||
Searches for and displays possibly readable ASCII strings in a file
|
||||
of any type. Wildcards are allowed.
|
||||
|
||||
The -L option specifies the minimum number of consecutive printable
|
||||
characters that qualifies as a printable string; the default is 6.
|
||||
The -o option stops the offsets of the found strings from being
|
||||
displayed. The -m option allows strings to have mixed low-ASCII (bit
|
||||
7 clear) and high-ASCII (bit 7 set) characters in them.
|
||||
|
|
|
|||
|
|
@ -1 +1,62 @@
|
|||
sysalias -- create an alias for a SYS or S16 file (EXTERNAL) [v1.3]
syntax: sysalias <existing_program> <alias_to_create> [-p prefix]
[-s startpath]
ex: sysalias /disk/davex/davex.system /disk/dvx.system
sysalias davex.dir/davex /disk/start.system
sysalias /disk/awks/aplworks.system %aw
sysalias /work/applewr/awd.system %awr -p /work/applewr
sysalias /disk1/basic.system basic -s /disk1/tons.o.fun
sysalias /awgs.program/appleworks.gs awgs -s /ss/my.budget
Creates a one-block program file (name = alias_to_create) which
runs a given SYS or S16 file (name = existing_program). Wildcards are
allowed. This allows program files to appear to be in more than one
place at a time without taking up much extra disk space. (S16 files
are useful only on the Apple IIgs.)
In most cases, you will want to specify a complete pathname for
<existing_program>. If you specify a partial pathname, the
one-block SYS or S16 file created may or may not be able to find the
program it's looking for, depending on the prefix at run time.
If you use -p, the file created will set the prefix as specified before
running its program file.
When you sysalias a SYS file that has a startup buffer, the alias will
have one, too; the alias passes the startup information along to the
original program.
The -s option can be used with SYS files to put a default "startup
pathname" in the alias's startup buffer. This name will be passed on
to the application being aliased. The fifth example above creates a
file called "basic" which is an alias for "/disk1/basic.system".
If you type "basic" without a parameter, Davex will run BASIC.SYSTEM,
and BASIC.SYSTEM will run "/disk2/tons.o.fun", because this was
specified with the -s option.
This alias can still accept a startup path. If you type
"basic /disk3/more.fun" BASIC.SYSTEM will run the program you
specified instead.
Note: It is advisable to use COMPLETE pathnames as startup
parameters to BASIC.SYSTEM. Here's why: BASIC.SYSTEM handles
the Prefix as you would expect ONLY if it refers to a subdirectory.
If the Prefix is set to a disk's top-level directory, BASIC.SYSTEM
will behave as if you are Prefixed TO THE DISK BASIC.SYSTEM IS
RUNNING FROM. This can be confusing. (Alternatively, you could
use a partial pathname AND use the -p option to set a particular
subdirectory prefix.)
When you sysalias a S16 application, the -s option tells the alias
to put the specified string in a "files to open" message in the Apple
IIgs Message Center, the same way the Finder does.
In the last example above, the S16 file AWGS is created. When you type
AWGS on the Davex command line, Davex launches the file
/awgs.program/appleworks.gs AND creates a "files" message containing
the path /ss/my.budget. Then AppleWorks GS automatically opens the
file /ss/my.budget, just like you clicked on that file's icon in the
Finder.
|
||||
|
||||
sysalias -- create an alias for a SYS or S16 file (EXTERNAL) [v1.3]
|
||||
|
||||
syntax: sysalias <existing_program> <alias_to_create> [-p prefix]
|
||||
[-s startpath]
|
||||
|
||||
ex: sysalias /disk/davex/davex.system /disk/dvx.system
|
||||
sysalias davex.dir/davex /disk/start.system
|
||||
sysalias /disk/awks/aplworks.system %aw
|
||||
sysalias /work/applewr/awd.system %awr -p /work/applewr
|
||||
sysalias /disk1/basic.system basic -s /disk1/tons.o.fun
|
||||
sysalias /awgs.program/appleworks.gs awgs -s /ss/my.budget
|
||||
|
||||
Creates a one-block program file (name = alias_to_create) which
|
||||
runs a given SYS or S16 file (name = existing_program). Wildcards are
|
||||
allowed. This allows program files to appear to be in more than one
|
||||
place at a time without taking up much extra disk space. (S16 files
|
||||
are useful only on the Apple IIgs.)
|
||||
|
||||
In most cases, you will want to specify a complete pathname for
|
||||
<existing_program>. If you specify a partial pathname, the
|
||||
one-block SYS or S16 file created may or may not be able to find the
|
||||
program it's looking for, depending on the prefix at run time.
|
||||
|
||||
If you use -p, the file created will set the prefix as specified before
|
||||
running its program file.
|
||||
|
||||
When you sysalias a SYS file that has a startup buffer, the alias will
|
||||
have one, too; the alias passes the startup information along to the
|
||||
original program.
|
||||
|
||||
The -s option can be used with SYS files to put a default "startup
|
||||
pathname" in the alias's startup buffer. This name will be passed on
|
||||
to the application being aliased. The fifth example above creates a
|
||||
file called "basic" which is an alias for "/disk1/basic.system".
|
||||
If you type "basic" without a parameter, Davex will run BASIC.SYSTEM,
|
||||
and BASIC.SYSTEM will run "/disk2/tons.o.fun", because this was
|
||||
specified with the -s option.
|
||||
|
||||
This alias can still accept a startup path. If you type
|
||||
"basic /disk3/more.fun" BASIC.SYSTEM will run the program you
|
||||
specified instead.
|
||||
|
||||
Note: It is advisable to use COMPLETE pathnames as startup
|
||||
parameters to BASIC.SYSTEM. Here's why: BASIC.SYSTEM handles
|
||||
the Prefix as you would expect ONLY if it refers to a subdirectory.
|
||||
If the Prefix is set to a disk's top-level directory, BASIC.SYSTEM
|
||||
will behave as if you are Prefixed TO THE DISK BASIC.SYSTEM IS
|
||||
RUNNING FROM. This can be confusing. (Alternatively, you could
|
||||
use a partial pathname AND use the -p option to set a particular
|
||||
subdirectory prefix.)
|
||||
|
||||
When you sysalias a S16 application, the -s option tells the alias
|
||||
to put the specified string in a "files to open" message in the Apple
|
||||
IIgs Message Center, the same way the Finder does.
|
||||
|
||||
In the last example above, the S16 file AWGS is created. When you type
|
||||
AWGS on the Davex command line, Davex launches the file
|
||||
/awgs.program/appleworks.gs AND creates a "files" message containing
|
||||
the path /ss/my.budget. Then AppleWorks GS automatically opens the
|
||||
file /ss/my.budget, just like you clicked on that file's icon in the
|
||||
Finder.
|
||||
|
|
|
|||
83
doc/help/TR
83
doc/help/TR
|
|
@ -1 +1,82 @@
|
|||
tr -- translate strings (EXTERNAL) [v1.2]
Written by Jeff Ding
syntax: tr <input pathname> [<output pathname>] -s<search string>
[-r<replace string>] [-f] [-d] [-w<margin>]
[-c<number>] [-h<number>]
ex: tr infile outfile -s^j
tr infile temp -s^m -r^m^j -fd
tr infile -s" " -r"" -m60
'Tr' looks for every occurrence of the <search string> in the input
file and replaces it with the <replace string>. The translated data
is saved to the output file. If the <output pathname> is not specified,
output goes to the screen. Wildcards are supported.
'Tr' works with any file type, but the input file is always treated as
a raw collection of bytes; no special processing is done for AWP files.
If you use 'tr' on an AWP file, you are not guaranteed to get a valid
AWP file as a result (and if the search and replace strings have
different lengths, you are guaranteed *not* to!).
The search and replace strings are specified in text. The text normally
has the hi-bits off. To turn the hi-bit of a character on, use the hi-bit
delimiter, default "~", before the character. To specify a control
character, use the control character delimiter, default "^", before the
character. To specify both, use both delimiters in succession; any order
works. Use "^?" to specify the delete key. Use "^>" to specify the
control character delimiter. Use "^=" to specify the hi-bit delimiter.
With these options, it is possible to specify any byte from 0 to 255.
Here are some examples:
"^j^m" - "ctrl-j ctrl-m" (case for control characters is ignored)
"~A~B~C" - "ABC" with hi-bits on.
"AbC" - "AbC" with hi-bits off.
"~^m^~m" - "ctrl-m ctrl-m" with hi-bits on.
"^>^=" - "^~"
Options are as follows:
output pathname: translated data is saved to this file. If not
specified, output goes to the screen. The output
file type will always be the same as the input file
type.
-s: search string. (REQUIRED) See above for description. This string
cannot be null. You must search for at least a 1 byte string. The
string can be at most 63 characters long AFTER control characters
and hi-bit characters are translated.
-r: replace string. See above for description. The string can be at
most 63 characters long AFTER control characters and hi-bit
characters are translated. Omitting this option is the same as
specifying the null string (matches of the search string are
replaced by nothing, the null string).
-f: force overwrite. Skips the "Okay to overwrite" question if the
output file already exists.
-d: delete original. Deletes the original file and renames the
output file to the original name. The output file is needed
as a temporary storage. Version 1.1 fixes a bug that caused
this option not to work.
-c <ascii number>: determines what character is used for the
control delimiter character. Use the ascii value
for the character.
-h <ascii number>: determines what character is used for the
hi-bit delimiter character. Use the ascii value
for the character.
-w <margin>: wrap margin. Affects output to the screen only. This
forces a carriage return when either the margin or a
space within 9 characters of the margin is reached.
Allowed values are 0 through 255. A 0 value has the same
effect as not using the option.
Version 1.2 fixes a bug when the search string was more than one
character long.
|
||||
|
||||
tr -- translate strings (EXTERNAL) [v1.2]
|
||||
Written by Jeff Ding
|
||||
|
||||
syntax: tr <input pathname> [<output pathname>] -s<search string>
|
||||
[-r<replace string>] [-f] [-d] [-w<margin>]
|
||||
[-c<number>] [-h<number>]
|
||||
|
||||
ex: tr infile outfile -s^j
|
||||
tr infile temp -s^m -r^m^j -fd
|
||||
tr infile -s" " -r"" -m60
|
||||
|
||||
'Tr' looks for every occurrence of the <search string> in the input
|
||||
file and replaces it with the <replace string>. The translated data
|
||||
is saved to the output file. If the <output pathname> is not specified,
|
||||
output goes to the screen. Wildcards are supported.
|
||||
|
||||
'Tr' works with any file type, but the input file is always treated as
|
||||
a raw collection of bytes; no special processing is done for AWP files.
|
||||
If you use 'tr' on an AWP file, you are not guaranteed to get a valid
|
||||
AWP file as a result (and if the search and replace strings have
|
||||
different lengths, you are guaranteed *not* to!).
|
||||
|
||||
The search and replace strings are specified in text. The text normally
|
||||
has the hi-bits off. To turn the hi-bit of a character on, use the hi-bit
|
||||
delimiter, default "~", before the character. To specify a control
|
||||
character, use the control character delimiter, default "^", before the
|
||||
character. To specify both, use both delimiters in succession; any order
|
||||
works. Use "^?" to specify the delete key. Use "^>" to specify the
|
||||
control character delimiter. Use "^=" to specify the hi-bit delimiter.
|
||||
With these options, it is possible to specify any byte from 0 to 255.
|
||||
|
||||
Here are some examples:
|
||||
|
||||
"^j^m" - "ctrl-j ctrl-m" (case for control characters is ignored)
|
||||
"~A~B~C" - "ABC" with hi-bits on.
|
||||
"AbC" - "AbC" with hi-bits off.
|
||||
"~^m^~m" - "ctrl-m ctrl-m" with hi-bits on.
|
||||
"^>^=" - "^~"
|
||||
|
||||
Options are as follows:
|
||||
|
||||
output pathname: translated data is saved to this file. If not
|
||||
specified, output goes to the screen. The output
|
||||
file type will always be the same as the input file
|
||||
type.
|
||||
|
||||
-s: search string. (REQUIRED) See above for description. This string
|
||||
cannot be null. You must search for at least a 1 byte string. The
|
||||
string can be at most 63 characters long AFTER control characters
|
||||
and hi-bit characters are translated.
|
||||
|
||||
-r: replace string. See above for description. The string can be at
|
||||
most 63 characters long AFTER control characters and hi-bit
|
||||
characters are translated. Omitting this option is the same as
|
||||
specifying the null string (matches of the search string are
|
||||
replaced by nothing, the null string).
|
||||
|
||||
-f: force overwrite. Skips the "Okay to overwrite" question if the
|
||||
output file already exists.
|
||||
|
||||
-d: delete original. Deletes the original file and renames the
|
||||
output file to the original name. The output file is needed
|
||||
as a temporary storage. Version 1.1 fixes a bug that caused
|
||||
this option not to work.
|
||||
|
||||
-c <ascii number>: determines what character is used for the
|
||||
control delimiter character. Use the ascii value
|
||||
for the character.
|
||||
|
||||
-h <ascii number>: determines what character is used for the
|
||||
hi-bit delimiter character. Use the ascii value
|
||||
for the character.
|
||||
|
||||
-w <margin>: wrap margin. Affects output to the screen only. This
|
||||
forces a carriage return when either the margin or a
|
||||
space within 9 characters of the margin is reached.
|
||||
Allowed values are 0 through 255. A 0 value has the same
|
||||
effect as not using the option.
|
||||
|
||||
Version 1.2 fixes a bug when the search string was more than one
|
||||
character long.
|
||||
|
|
|
|||
|
|
@ -1 +1,33 @@
|
|||
tail -- Display end of file (EXTERNAL) [v1.0]
Written by Jeff Ding
syntax: tail <pathname> [-l<number>] [-w<number>] [-d<ascii number>]
ex: tail long.file
tail read.me -l10
> & ; tail wide.file -w132
'Tail' displays the ending of a file without having to wait for the
beginning part to scroll by on the screen. This command is useful for
quickly displaying the ending of any file that is very long. Wildcards
are supported.
Options are as follows:
-l: number of lines to print. This defaults to 5 lines. You can
specify 'tail' to print any number of lines from 1 to 255 off
the end of a file. A 0 value has the same effect as not using
the option.
-w: wrap margin. Use this option to force the number of lines to
increment at either a specific margin or a space within 9 characters
of the margin. This option is good for files that use a carriage
return to specify paragraphs instead of lines. Allowed values are
0 through 255. A 0 value has the same effect as not using the
option. The default wrap margin is set to 79.
-d: delimiter for end of line. Enter the ascii value of the character
after the -d.
(see also: hdr)
|
||||
|
||||
tail -- Display end of file (EXTERNAL) [v1.0]
|
||||
Written by Jeff Ding
|
||||
|
||||
syntax: tail <pathname> [-l<number>] [-w<number>] [-d<ascii number>]
|
||||
|
||||
ex: tail long.file
|
||||
tail read.me -l10
|
||||
> & ; tail wide.file -w132
|
||||
|
||||
'Tail' displays the ending of a file without having to wait for the
|
||||
beginning part to scroll by on the screen. This command is useful for
|
||||
quickly displaying the ending of any file that is very long. Wildcards
|
||||
are supported.
|
||||
|
||||
Options are as follows:
|
||||
|
||||
-l: number of lines to print. This defaults to 5 lines. You can
|
||||
specify 'tail' to print any number of lines from 1 to 255 off
|
||||
the end of a file. A 0 value has the same effect as not using
|
||||
the option.
|
||||
|
||||
-w: wrap margin. Use this option to force the number of lines to
|
||||
increment at either a specific margin or a space within 9 characters
|
||||
of the margin. This option is good for files that use a carriage
|
||||
return to specify paragraphs instead of lines. Allowed values are
|
||||
0 through 255. A 0 value has the same effect as not using the
|
||||
option. The default wrap margin is set to 79.
|
||||
|
||||
-d: delimiter for end of line. Enter the ascii value of the character
|
||||
after the -d.
|
||||
|
||||
(see also: hdr)
|
||||
|
|
|
|||
12
doc/help/Top
12
doc/help/Top
|
|
@ -1 +1,11 @@
|
|||
top -- set prefix to parent volume
syntax: top
ex: top
'top' performs 0 or more 'up' commands until the prefix is a
volume name (or until the prefix is null).
(see also: prefix, up, over, origin)
|
||||
|
||||
top -- set prefix to parent volume
|
||||
|
||||
syntax: top
|
||||
|
||||
ex: top
|
||||
|
||||
'top' performs 0 or more 'up' commands until the prefix is a
|
||||
volume name (or until the prefix is null).
|
||||
|
||||
(see also: prefix, up, over, origin)
|
||||
|
|
|
|||
|
|
@ -1 +1,56 @@
|
|||
(Type "help xxx" for more information, where "xxx" is one of
the items listed below. For example, type "help cat" or "help ls"
for information on the catalog command.)
general info:
topics help/? shareware/$
pathnames/path cmdline version
working with volumes and directories:
cat/ls init create/mkdir vstore
online du eject/ej vrestore
doscat
miscellaneous:
boot mon dt deschw echo/e
cls/home rep err equal/= num
setdate date ram3 viewdhr viewhr
I/O redirection:
como/> exec/<
setting prefix (working directory):
prefix/cd up top origin/or over
finding and examining files and their attributes:
cat/ls what ffind find wc
info size modchk hdr tail
ptype
viewing contents of files:
pg/more type blist dump
strings expand tr
fiddling with files:
touch rename delete/rm tr
copy/cp move update split
lock unlock prot combine
setstart sysalias filetype expand
Davex environment:
ftype dev scan config
alias bye/quit brun index
Apple IIgs only:
conp gsbuff
printers:
pset iw2 spool wait
mx80 fp como/> cls/home
Use 'config' to find out what directory contains your help files.
There may be information there not listed here.
See Davex.Doc for discussion of general topics like wildcards
and slot/drive shorthand.
|
||||
|
||||
(Type "help xxx" for more information, where "xxx" is one of
|
||||
the items listed below. For example, type "help cat" or "help ls"
|
||||
for information on the catalog command.)
|
||||
|
||||
general info:
|
||||
topics help/? shareware/$
|
||||
pathnames/path cmdline version
|
||||
|
||||
working with volumes and directories:
|
||||
cat/ls init create/mkdir vstore
|
||||
online du eject/ej vrestore
|
||||
doscat
|
||||
|
||||
miscellaneous:
|
||||
boot mon dt deschw echo/e
|
||||
cls/home rep err equal/= num
|
||||
setdate date ram3 viewdhr viewhr
|
||||
|
||||
I/O redirection:
|
||||
como/> exec/<
|
||||
|
||||
setting prefix (working directory):
|
||||
prefix/cd up top origin/or over
|
||||
|
||||
finding and examining files and their attributes:
|
||||
cat/ls what ffind find wc
|
||||
info size modchk hdr tail
|
||||
ptype
|
||||
|
||||
viewing contents of files:
|
||||
pg/more type blist dump
|
||||
strings expand tr
|
||||
|
||||
fiddling with files:
|
||||
touch rename delete/rm tr
|
||||
copy/cp move update split
|
||||
lock unlock prot combine
|
||||
setstart sysalias filetype expand
|
||||
|
||||
Davex environment:
|
||||
ftype dev scan config
|
||||
alias bye/quit brun index
|
||||
|
||||
Apple IIgs only:
|
||||
conp gsbuff
|
||||
|
||||
printers:
|
||||
pset iw2 spool wait
|
||||
mx80 fp como/> cls/home
|
||||
|
||||
Use 'config' to find out what directory contains your help files.
|
||||
There may be information there not listed here.
|
||||
|
||||
See Davex.Doc for discussion of general topics like wildcards
|
||||
and slot/drive shorthand.
|
||||
|
|
|
|||
|
|
@ -1 +1,37 @@
|
|||
touch -- touch a file's last-mod date, backup bit, invisible bit, or
disable bit
syntax: touch <pathname> [-b y|n] [-d y|n] [-i y|n]
ex: touch myfile
touch =:bin -iy
touch ?:cda -dn
touch ? -bn
'touch' with no options sets a file's modification date/time to the
current date and time without actually modifying the file's contents.
Wildcards are allowed.
This is intended for use with recently-created files that, for some
reason, are not properly date- and time-stamped. (Some DOS 3.3-to-
ProDOS conversion programs, for example, stamp files with an invalid
date and time.)
The -b option lets you set or clear the "needs backup" bit on a
file. Use -by to set the bit or -bn to clear it. See also 'copy',
'update', 'cat', and 'ffind'.
The -i option lets you set or clear a file's "invisible" bit.
Invisible files don't show up in Davex catalog listings unless the
catalog command's -i option is used. The "invisible" bit has been
recently defined by Apple, and other programs may or may not pay
attention to the invisibility of a file.
The -d option lets you ENABLE or DISABLE certain types of Apple IIgs
files. A disabled file is not loaded automatically at boot time.
The filetypes that can be disabled are $B6 (permanent init file), $B7
(temporary init file), $B8 (new desk accessory), $B9 (classic desk
accessory), $BB (driver), $BC (generic load file), and $BD (GS/OS file
system translator). [Bit 15 of the auxiliary type for these filetypes
is the disable bit.]
|
||||
|
||||
touch -- touch a file's last-mod date, backup bit, invisible bit, or
|
||||
disable bit
|
||||
|
||||
syntax: touch <pathname> [-b y|n] [-d y|n] [-i y|n]
|
||||
|
||||
ex: touch myfile
|
||||
touch =:bin -iy
|
||||
touch ?:cda -dn
|
||||
touch ? -bn
|
||||
|
||||
'touch' with no options sets a file's modification date/time to the
|
||||
current date and time without actually modifying the file's contents.
|
||||
Wildcards are allowed.
|
||||
|
||||
This is intended for use with recently-created files that, for some
|
||||
reason, are not properly date- and time-stamped. (Some DOS 3.3-to-
|
||||
ProDOS conversion programs, for example, stamp files with an invalid
|
||||
date and time.)
|
||||
|
||||
The -b option lets you set or clear the "needs backup" bit on a
|
||||
file. Use -by to set the bit or -bn to clear it. See also 'copy',
|
||||
'update', 'cat', and 'ffind'.
|
||||
|
||||
The -i option lets you set or clear a file's "invisible" bit.
|
||||
Invisible files don't show up in Davex catalog listings unless the
|
||||
catalog command's -i option is used. The "invisible" bit has been
|
||||
recently defined by Apple, and other programs may or may not pay
|
||||
attention to the invisibility of a file.
|
||||
|
||||
The -d option lets you ENABLE or DISABLE certain types of Apple IIgs
|
||||
files. A disabled file is not loaded automatically at boot time.
|
||||
The filetypes that can be disabled are $B6 (permanent init file), $B7
|
||||
(temporary init file), $B8 (new desk accessory), $B9 (classic desk
|
||||
accessory), $BB (driver), $BC (generic load file), and $BD (GS/OS file
|
||||
system translator). [Bit 15 of the auxiliary type for these filetypes
|
||||
is the disable bit.]
|
||||
|
|
|
|||
|
|
@ -1 +1,31 @@
|
|||
type -- display plain text file or AppleWorks (AWP) file
syntax: type <pathname> [-h] [-f] [-u] [-l] [-p] [-t tab_string]
ex: type this
type ?:txt -h
como that;type this -l
Types contents of a file (any type, not just TXT). Wildcards are
allowed. -h generates a headergiving the date/time the file was last
modified. -f disables filtering of control characters; normally they
are filtered out.
-u and -l force alphabetic characters to display as uppercase or
lowercase, respectively.
-p begins a new page after the file is printed (useful when
redirecting to printer)
-t lets you specify a string to print in place of each TAB
character (Ctrl-I). You may want to make an alias for 'type' with
a tab string.
Note: many file types do not contain plain ASCII text. This command
knows how to interpret AWP files, but simply displays all other
files byte-for-byte. If you pg a SYS file, for example, you
will get a lot of garbage and a (probably) few readable
messages.
(see also: pg, como, strings, alias)
|
||||
|
||||
type -- display plain text file or AppleWorks (AWP) file
|
||||
|
||||
syntax: type <pathname> [-h] [-f] [-u] [-l] [-p] [-t tab_string]
|
||||
|
||||
ex: type this
|
||||
type ?:txt -h
|
||||
como that;type this -l
|
||||
|
||||
Types contents of a file (any type, not just TXT). Wildcards are
|
||||
allowed. -h generates a headergiving the date/time the file was last
|
||||
modified. -f disables filtering of control characters; normally they
|
||||
are filtered out.
|
||||
|
||||
-u and -l force alphabetic characters to display as uppercase or
|
||||
lowercase, respectively.
|
||||
|
||||
-p begins a new page after the file is printed (useful when
|
||||
redirecting to printer)
|
||||
|
||||
-t lets you specify a string to print in place of each TAB
|
||||
character (Ctrl-I). You may want to make an alias for 'type' with
|
||||
a tab string.
|
||||
|
||||
Note: many file types do not contain plain ASCII text. This command
|
||||
knows how to interpret AWP files, but simply displays all other
|
||||
files byte-for-byte. If you pg a SYS file, for example, you
|
||||
will get a lot of garbage and a (probably) few readable
|
||||
messages.
|
||||
|
||||
(see also: pg, como, strings, alias)
|
||||
|
|
|
|||
|
|
@ -1 +1,12 @@
|
|||
unlock -- allow read, write, rename, delete
syntax: unlock <pathname>
ex: unlock this
unlock =:txt
Allows read, write, rename, and delete for file. Wildcards
are allowed.
(see also: lock, prot)
|
||||
|
||||
unlock -- allow read, write, rename, delete
|
||||
|
||||
syntax: unlock <pathname>
|
||||
|
||||
ex: unlock this
|
||||
unlock =:txt
|
||||
|
||||
Allows read, write, rename, and delete for file. Wildcards
|
||||
are allowed.
|
||||
|
||||
(see also: lock, prot)
|
||||
|
|
|
|||
13
doc/help/Up
13
doc/help/Up
|
|
@ -1 +1,12 @@
|
|||
up -- change prefix to parent directory
syntax: up
ex: up
Removes one segment from the end of the prefix. If the
prefix is a volume directory, 'up' makes the prefix null.
If the prefix is already null, up has no effect.
(see also: over, prefix, origin, top)
|
||||
|
||||
up -- change prefix to parent directory
|
||||
|
||||
syntax: up
|
||||
|
||||
ex: up
|
||||
|
||||
Removes one segment from the end of the prefix. If the
|
||||
prefix is a volume directory, 'up' makes the prefix null.
|
||||
If the prefix is already null, up has no effect.
|
||||
|
||||
(see also: over, prefix, origin, top)
|
||||
|
|
|
|||
|
|
@ -1 +1,38 @@
|
|||
update -- replace outdated files
syntax: update <pathname> <pathname> [-f] [-b]
ex: update %help /otherdisk/davex/help -f
update /work /backup
update /that/? /there/?
'update' takes two pathnames (original path first, target
path second) and updates old files, reporting on its
progress as it goes. If the pathnames are DIRECTORIES,
update descends into them and updates corresponding files.
[Note: If one of the pathnames refers to a directory, the
other one should, too. A command like "update /disk1/dir1/?
/disk2/dir2" will result only in a series of "filetypes differ"
messages. So use a wildcard on both pathnames or don't use
one at all.]
For files, here's what happens. If the target file does not
exist, update asks for permission to create it. If the target
file does exist, three conditions are possible. If the
modification dates and times match exactly, you see "current"
and 'update' takes no further action on that pair of files.
If the target file is older, you see "outdated" and are asked
for permission to replace the old file. If the target file is
NEWER, you get a warning message and update takes no further
action on that pair of files.
-f (force) bypasses the "Okay to replace" question, just
like for the copy command. (In fact, update USES the copy
command.) -f also bypasses the "Okay to create new file"
questions.
-b clears the Backup bit on the source original files. See
"help copy" for more information.
|
||||
|
||||
update -- replace outdated files
|
||||
|
||||
syntax: update <pathname> <pathname> [-f] [-b]
|
||||
|
||||
ex: update %help /otherdisk/davex/help -f
|
||||
update /work /backup
|
||||
update /that/? /there/?
|
||||
|
||||
'update' takes two pathnames (original path first, target
|
||||
path second) and updates old files, reporting on its
|
||||
progress as it goes. If the pathnames are DIRECTORIES,
|
||||
update descends into them and updates corresponding files.
|
||||
|
||||
[Note: If one of the pathnames refers to a directory, the
|
||||
other one should, too. A command like "update /disk1/dir1/?
|
||||
/disk2/dir2" will result only in a series of "filetypes differ"
|
||||
messages. So use a wildcard on both pathnames or don't use
|
||||
one at all.]
|
||||
|
||||
For files, here's what happens. If the target file does not
|
||||
exist, update asks for permission to create it. If the target
|
||||
file does exist, three conditions are possible. If the
|
||||
modification dates and times match exactly, you see "current"
|
||||
and 'update' takes no further action on that pair of files.
|
||||
If the target file is older, you see "outdated" and are asked
|
||||
for permission to replace the old file. If the target file is
|
||||
NEWER, you get a warning message and update takes no further
|
||||
action on that pair of files.
|
||||
|
||||
-f (force) bypasses the "Okay to replace" question, just
|
||||
like for the copy command. (In fact, update USES the copy
|
||||
command.) -f also bypasses the "Okay to create new file"
|
||||
questions.
|
||||
|
||||
-b clears the Backup bit on the source original files. See
|
||||
"help copy" for more information.
|
||||
|
||||
|
|
|
|||
|
|
@ -1 +1,33 @@
|
|||
vrestore -- restore a ProDOS volume from a file (EXTERNAL) [v1.1]
syntax: vrestore <pathname> <device number> [-f]
ex: vrestore /my.disk/image.of.ram .32
vrestore .61/ram5.image .52 -f
'vrestore' reconstructs a ProDOS volume from a file. The file
must have been created earlier with 'vstore'. The reconstructed
volume completely replaces any information on the destination
device.
The -f option forces 'vrestore' to destroy any existing data on
the destination disk without asking. If you don't use -f, it
asks for permission first.
'vstore' and 'vrestore' are especially useful with RAM disks
that have no battery backup. If the stored image was too big
to fit on one disk, 'vrestore' will prompt you to insert the
next disk in the same drive as the first one.
'vrestore' v1.1 assumes that the destination device has the
same number of blocks as the original volume (the one the image
was created from). [A future version of 'vrestore' may allow
the destination device to be larger, provided the number of
bitmap blocks is the same. One bitmap block is needed for
every 4096 blocks.] Note: v1.1 actually doesn't even check the
number of blocks on the destination device. You can restore
to a bigger device if you want to, but the extra blocks will not
be available for file storage.
(see also: vstore)
|
||||
|
||||
vrestore -- restore a ProDOS volume from a file (EXTERNAL) [v1.1]
|
||||
|
||||
syntax: vrestore <pathname> <device number> [-f]
|
||||
|
||||
ex: vrestore /my.disk/image.of.ram .32
|
||||
vrestore .61/ram5.image .52 -f
|
||||
|
||||
'vrestore' reconstructs a ProDOS volume from a file. The file
|
||||
must have been created earlier with 'vstore'. The reconstructed
|
||||
volume completely replaces any information on the destination
|
||||
device.
|
||||
|
||||
The -f option forces 'vrestore' to destroy any existing data on
|
||||
the destination disk without asking. If you don't use -f, it
|
||||
asks for permission first.
|
||||
|
||||
'vstore' and 'vrestore' are especially useful with RAM disks
|
||||
that have no battery backup. If the stored image was too big
|
||||
to fit on one disk, 'vrestore' will prompt you to insert the
|
||||
next disk in the same drive as the first one.
|
||||
|
||||
'vrestore' v1.1 assumes that the destination device has the
|
||||
same number of blocks as the original volume (the one the image
|
||||
was created from). [A future version of 'vrestore' may allow
|
||||
the destination device to be larger, provided the number of
|
||||
bitmap blocks is the same. One bitmap block is needed for
|
||||
every 4096 blocks.] Note: v1.1 actually doesn't even check the
|
||||
number of blocks on the destination device. You can restore
|
||||
to a bigger device if you want to, but the extra blocks will not
|
||||
be available for file storage.
|
||||
|
||||
(see also: vstore)
|
||||
|
|
|
|||
|
|
@ -1 +1,41 @@
|
|||
vstore -- store a ProDOS volume into a file (EXTERNAL) [v1.1]
syntax: vstore <volume name> <pathname>
ex: vstore /ram /my.disk/image.of.ram
vstore /ram5 .61/ram5.image
'vstore' stores an image of a ProDOS volume into a file (or
several files on different disks). 'vrestore' is used to
restore the volume from the stored image. 'vstore' and
'vrestore' are especially useful with RAM disks that don't
have a battery backup.
'vstore' will prompt you to insert another disk whenever
one is full. This means you can store a large RAM disk
(or even a hard disk) on a number of smaller disks.
'vstore' and 'vrestore' are not intended to replace your
normal backup procedures. You should still keep normal
copies of your files somewhere, in case the large device
you are storing becomes unavailable. For example, a stored
image of your 1024K RAM disk will not be useful if you have
to send in your RAM board for repair--but normal copies of
the files would be useful.
Note that a file created by 'vstore' is normally "sparse,"
so that its physical length is less than its logical length.
(This is because 'vstore' leaves gaps in the file corresponding
to unused blocks on the volume being stored.) However, many
file-copy commands (including Davex's copy command at present)
don't preserve the sparseness when you copy a file. The
resulting files may be much larger than the originals, so you
will probably not want to copy files created by 'vstore'.
(Copying *disks* containing sparse files is no problem, though.)
The 'what' command recognizes files created by 'vstore' and
displays some useful information about them. The files are
now stored with filetype $E0 and auxiliary type $8004.
(see also: vrestore, what)
|
||||
|
||||
vstore -- store a ProDOS volume into a file (EXTERNAL) [v1.1]
|
||||
|
||||
syntax: vstore <volume name> <pathname>
|
||||
|
||||
ex: vstore /ram /my.disk/image.of.ram
|
||||
vstore /ram5 .61/ram5.image
|
||||
|
||||
'vstore' stores an image of a ProDOS volume into a file (or
|
||||
several files on different disks). 'vrestore' is used to
|
||||
restore the volume from the stored image. 'vstore' and
|
||||
'vrestore' are especially useful with RAM disks that don't
|
||||
have a battery backup.
|
||||
|
||||
'vstore' will prompt you to insert another disk whenever
|
||||
one is full. This means you can store a large RAM disk
|
||||
(or even a hard disk) on a number of smaller disks.
|
||||
|
||||
'vstore' and 'vrestore' are not intended to replace your
|
||||
normal backup procedures. You should still keep normal
|
||||
copies of your files somewhere, in case the large device
|
||||
you are storing becomes unavailable. For example, a stored
|
||||
image of your 1024K RAM disk will not be useful if you have
|
||||
to send in your RAM board for repair--but normal copies of
|
||||
the files would be useful.
|
||||
|
||||
Note that a file created by 'vstore' is normally "sparse,"
|
||||
so that its physical length is less than its logical length.
|
||||
(This is because 'vstore' leaves gaps in the file corresponding
|
||||
to unused blocks on the volume being stored.) However, many
|
||||
file-copy commands (including Davex's copy command at present)
|
||||
don't preserve the sparseness when you copy a file. The
|
||||
resulting files may be much larger than the originals, so you
|
||||
will probably not want to copy files created by 'vstore'.
|
||||
(Copying *disks* containing sparse files is no problem, though.)
|
||||
|
||||
The 'what' command recognizes files created by 'vstore' and
|
||||
displays some useful information about them. The files are
|
||||
now stored with filetype $E0 and auxiliary type $8004.
|
||||
|
||||
(see also: vrestore, what)
|
||||
|
|
|
|||
|
|
@ -1 +1,14 @@
|
|||
version -- print Davex version information
syntax: version
ex: version
The 'version' command reprints the header you normally see
when you enter Davex. (Depending on the 'config -q' setting,
you may not see the header when you enter.)
The version number and serial number on your copy of Davex
are displayed. This header also appears when you press
Ctrl-RESET (*not* Apple-Ctrl-RESET).
|
||||
|
||||
version -- print Davex version information
|
||||
|
||||
syntax: version
|
||||
|
||||
ex: version
|
||||
|
||||
The 'version' command reprints the header you normally see
|
||||
when you enter Davex. (Depending on the 'config -q' setting,
|
||||
you may not see the header when you enter.)
|
||||
|
||||
The version number and serial number on your copy of Davex
|
||||
are displayed. This header also appears when you press
|
||||
Ctrl-RESET (*not* Apple-Ctrl-RESET).
|
||||
|
|
|
|||
|
|
@ -1 +1,36 @@
|
|||
viewdhr -- view a double hi-res picture (EXTERNAL) [v1.1] Written by Jeff Ding
syntax: viewdhr <pathname> [-f] [-r]
ex: viewdhr /picture.disk/pic.1
viewdhr /picture.disk/pic.1 -f
viewdhr /picture.disk/pic=
'viewdhr' displays a double hi-res picture on the screen without leaving
the Davex command shell. Wildcards are accepted in the pathname.Once the
picture is displayed, any key will exit. Ctrl-C will abort wildcard
expansions. 'viewdhr' will not work on a II+ or 64k //e because they do
not have the auxiliary memory needed to display double hi-res pictures.
This program will work on a //c, //e compatible with an extended 80 column
card, and the //gs.
In order for 'viewdhr' to work you have to uninstall the ram driver in
slot 3 drive 2. To do that you have to use the 'ram3' external command.
The following options are available:
-f: force load -- This option will force the program to load the
picture regardless of the status of the ram drive. Use this
option with caution as it will destroy any files that might
be stored in that memory
-r: reverse pages -- This option will load the picture in reversed
format. Normally the first half of the file is loaded into the
auxiliary memory and the second half into the main memory. Using
this option will switch the main and auxiliary pages in memory.
'viewdhr' makes sure the filetype is BIN or FOT and the auxtype is set
to $2000. It then loads the file and displays it on the screen. It
will not load the picture if the length is less than $2001 bytes.
(see also: ram3)
|
||||
|
||||
viewdhr -- view a double hi-res picture (EXTERNAL) [v1.1] Written by Jeff Ding
|
||||
|
||||
syntax: viewdhr <pathname> [-f] [-r]
|
||||
|
||||
ex: viewdhr /picture.disk/pic.1
|
||||
viewdhr /picture.disk/pic.1 -f
|
||||
viewdhr /picture.disk/pic=
|
||||
|
||||
'viewdhr' displays a double hi-res picture on the screen without leaving
|
||||
the Davex command shell. Wildcards are accepted in the pathname.Once the
|
||||
picture is displayed, any key will exit. Ctrl-C will abort wildcard
|
||||
expansions. 'viewdhr' will not work on a II+ or 64k //e because they do
|
||||
not have the auxiliary memory needed to display double hi-res pictures.
|
||||
This program will work on a //c, //e compatible with an extended 80 column
|
||||
card, and the //gs.
|
||||
|
||||
In order for 'viewdhr' to work you have to uninstall the ram driver in
|
||||
slot 3 drive 2. To do that you have to use the 'ram3' external command.
|
||||
The following options are available:
|
||||
|
||||
-f: force load -- This option will force the program to load the
|
||||
picture regardless of the status of the ram drive. Use this
|
||||
option with caution as it will destroy any files that might
|
||||
be stored in that memory
|
||||
|
||||
-r: reverse pages -- This option will load the picture in reversed
|
||||
format. Normally the first half of the file is loaded into the
|
||||
auxiliary memory and the second half into the main memory. Using
|
||||
this option will switch the main and auxiliary pages in memory.
|
||||
|
||||
'viewdhr' makes sure the filetype is BIN or FOT and the auxtype is set
|
||||
to $2000. It then loads the file and displays it on the screen. It
|
||||
will not load the picture if the length is less than $2001 bytes.
|
||||
|
||||
(see also: ram3)
|
||||
|
|
|
|||
|
|
@ -1 +1,17 @@
|
|||
viewhr -- view a hi-res picture (EXTERNAL) [v1.1] Written by Jeff Ding
syntax: viewhr <pathname>
ex: viewhr /picture.disk/pic.1
viewhr /picture.disk/pic=
'viewhr' displays a hi-res picture on the screen without leaving
the Davex command shell. Wildcards are accepted in the pathname.
Once the picture is displayed, any key will exit. Ctrl-C will
abort wildcard expansions.
'viewhr' makes sure the filetype is BIN or FOT and the auxtype is set
to $2000 or $4000. It then loads $2000 bytes of the file and displays
it on the screen. It is possible to view double-hires pictures but
you will only see half of the picture.
|
||||
|
||||
viewhr -- view a hi-res picture (EXTERNAL) [v1.1] Written by Jeff Ding
|
||||
|
||||
syntax: viewhr <pathname>
|
||||
|
||||
ex: viewhr /picture.disk/pic.1
|
||||
viewhr /picture.disk/pic=
|
||||
|
||||
'viewhr' displays a hi-res picture on the screen without leaving
|
||||
the Davex command shell. Wildcards are accepted in the pathname.
|
||||
Once the picture is displayed, any key will exit. Ctrl-C will
|
||||
abort wildcard expansions.
|
||||
|
||||
'viewhr' makes sure the filetype is BIN or FOT and the auxtype is set
|
||||
to $2000 or $4000. It then loads $2000 bytes of the file and displays
|
||||
it on the screen. It is possible to view double-hires pictures but
|
||||
you will only see half of the picture.
|
||||
|
|
|
|||
48
doc/help/WC
48
doc/help/WC
|
|
@ -1 +1,47 @@
|
|||
wc -- character/word/line count program (EXTERNAL) [v2.0]
Written by Jeff Ding
syntax: wc <pathname1..5> [-c] [-w] [-l] [-t] [-d<number>] [-e<number>]
[-m<number>]
ex: wc text.file1 text.file2 text.file3
wc apple.txt -lw -m60
wc read.me -d138
'Wc' with no options prints the number of characters, words, and lines in
the given file. The file type is not checked so any file of any type can
be given on the command line. Up to five file names can be given on the
command line at any one time. AppleWorks word processor files are
supported. The standard delimiter between two words is a space. The
standard end of line delimiter is a carriage return.
If more than one file is given on the command line, 'wc' version 2.0 will
print the grand total of characters, words, and lines. If wildcards are
used, the grand total will be printed after every file matching the
wildcard starting with the second file. Printing of the grand total is
also subject to the -c,-w, and -l options.
Options are as follows:
-c: print character count.
-w: print word count.
-l: print line count.
-t: print grand totals only.
-d: delimiter for end of line. Enter the ascii value of the character
after the -d.
-e: delimiter between words. Enter the ascii value of the character
after the -e.
-m: wrap margin. Use this option to force the number of lines to
increment at either a specific margin or a space within 9 characters
of the margin. This option is good for files that use a carriage
return to specify paragraphs instead of lines. Allowed values are
0 through 255. A 0 value has the same effect as not using the
option.
Note: You can mix the -c, -w, -l options in different combinations.
The hi-bit of each character in the file is ignored.
|
||||
|
||||
wc -- character/word/line count program (EXTERNAL) [v2.0]
|
||||
Written by Jeff Ding
|
||||
|
||||
syntax: wc <pathname1..5> [-c] [-w] [-l] [-t] [-d<number>] [-e<number>]
|
||||
[-m<number>]
|
||||
|
||||
ex: wc text.file1 text.file2 text.file3
|
||||
wc apple.txt -lw -m60
|
||||
wc read.me -d138
|
||||
|
||||
'Wc' with no options prints the number of characters, words, and lines in
|
||||
the given file. The file type is not checked so any file of any type can
|
||||
be given on the command line. Up to five file names can be given on the
|
||||
command line at any one time. AppleWorks word processor files are
|
||||
supported. The standard delimiter between two words is a space. The
|
||||
standard end of line delimiter is a carriage return.
|
||||
|
||||
If more than one file is given on the command line, 'wc' version 2.0 will
|
||||
print the grand total of characters, words, and lines. If wildcards are
|
||||
used, the grand total will be printed after every file matching the
|
||||
wildcard starting with the second file. Printing of the grand total is
|
||||
also subject to the -c,-w, and -l options.
|
||||
|
||||
Options are as follows:
|
||||
|
||||
-c: print character count.
|
||||
-w: print word count.
|
||||
-l: print line count.
|
||||
|
||||
-t: print grand totals only.
|
||||
|
||||
-d: delimiter for end of line. Enter the ascii value of the character
|
||||
after the -d.
|
||||
|
||||
-e: delimiter between words. Enter the ascii value of the character
|
||||
after the -e.
|
||||
|
||||
-m: wrap margin. Use this option to force the number of lines to
|
||||
increment at either a specific margin or a space within 9 characters
|
||||
of the margin. This option is good for files that use a carriage
|
||||
return to specify paragraphs instead of lines. Allowed values are
|
||||
0 through 255. A 0 value has the same effect as not using the
|
||||
option.
|
||||
|
||||
Note: You can mix the -c, -w, -l options in different combinations.
|
||||
The hi-bit of each character in the file is ignored.
|
||||
|
|
|
|||
|
|
@ -1 +1,14 @@
|
|||
wait -- wait for spooled files to finish printing
syntax: wait
ex: wait;ej;park
'wait' simply sits there and does nothing until files
spooled with the 'spool' command are done printing. Press
any key to abort the wait and return to the command prompt.
(The example assumes that 'park' is available as a SYS or
S16 file or external Davex command; it would presumably park
the heads on your hard drive.)
|
||||
|
||||
wait -- wait for spooled files to finish printing
|
||||
|
||||
syntax: wait
|
||||
|
||||
ex: wait;ej;park
|
||||
|
||||
'wait' simply sits there and does nothing until files
|
||||
spooled with the 'spool' command are done printing. Press
|
||||
any key to abort the wait and return to the command prompt.
|
||||
|
||||
(The example assumes that 'park' is available as a SYS or
|
||||
S16 file or external Davex command; it would presumably park
|
||||
the heads on your hard drive.)
|
||||
|
|
|
|||
|
|
@ -1 +1,70 @@
|
|||
what -- determine what a file is (EXTERNAL) [v2.1]
syntax: what <pathname> [-m] [-c] [-x] [-l] [-s] [-b]
[-a] [-n]
ex: what thatfile
what %=:bin -a
what =:src -n
what .62 -amc
'what' examines a file's type, auxiliary type, and first
512 bytes and prints whatever interesting information it
can about the file.
Wildcards are allowed. Output is, at minimum, the file's
type and name. For many filetypes, additional information
appears.
Options:
-n: no blank lines (prevents 'what' from printing a blank
line before each file's information)
-a: print All information (modification date/time, creation
date/time, auxiliary type, length in bytes, length in
blocks, storage type)
-m: modification date and time
-c: creation date and time
-x: auxiliary type (load address for BIN files, total blocks
for a volume, etc.--meaning depends on filetype)
-l: length in bytes
-s: storage type (seedling, sapling, tree, Pascal area,
subdirectory, or volume)
-b: length in blocks
Note: 'what foo -a' is the same as 'what foo -mcsxlb'. Also, you
can print ALL BUT certain pieces of information by
specifying -a AND the options to omit. For example,
'what foo -ac' prints all information EXCEPT the creation
date/time.
For BIN or $2E files that are external Davex commands, version
information, a one-line summary, and the command's execution address
are displayed.
SYS files created by the 'sysalias' command are identified, and
the pathname of the aliased application is displayed. If
there is a startup buffer, its size is displayed.
SYS files -not- created by 'sysalias' are identified as ProDOS 8
applications. If there is a startup buffer, its length and
default contents will be displayed (for example, BASIC.SYSTEM
normally has a 65-byte startup buffer containing "startup").
BAS files are identified as Applesoft BASIC programs. 'what'
computes the correct Aux-type for the file and prints a warning
message if the file has a different Aux-type. (Use 'filetype'
with -x to correct the problem.) [Some DOS 3.3-to-ProDOS
conversion programs (including Apple's CONVERT utility) always
give BAS files an Aux-type of $0801, which is typically correct.
But if the DOS program had been saved from an address other than
$801, nastiness will result when you try to load or run the
converted program under ProDOS.]
Apple IIgs TOL files (TOOLnnn) are identified as specific system
tools by the last 3 digits of their names.
For all GS/OS Object Module Format files (types $B1 through
$BE), the OMF Version number is displayed. Version 1 is the
first version and will work under all versions of ProDOS 16 and
GS/OS.
|
||||
|
||||
what -- determine what a file is (EXTERNAL) [v2.1]
|
||||
|
||||
syntax: what <pathname> [-m] [-c] [-x] [-l] [-s] [-b]
|
||||
[-a] [-n]
|
||||
|
||||
ex: what thatfile
|
||||
what %=:bin -a
|
||||
what =:src -n
|
||||
what .62 -amc
|
||||
|
||||
'what' examines a file's type, auxiliary type, and first
|
||||
512 bytes and prints whatever interesting information it
|
||||
can about the file.
|
||||
|
||||
Wildcards are allowed. Output is, at minimum, the file's
|
||||
type and name. For many filetypes, additional information
|
||||
appears.
|
||||
|
||||
Options:
|
||||
-n: no blank lines (prevents 'what' from printing a blank
|
||||
line before each file's information)
|
||||
-a: print All information (modification date/time, creation
|
||||
date/time, auxiliary type, length in bytes, length in
|
||||
blocks, storage type)
|
||||
-m: modification date and time
|
||||
-c: creation date and time
|
||||
-x: auxiliary type (load address for BIN files, total blocks
|
||||
for a volume, etc.--meaning depends on filetype)
|
||||
-l: length in bytes
|
||||
-s: storage type (seedling, sapling, tree, Pascal area,
|
||||
subdirectory, or volume)
|
||||
-b: length in blocks
|
||||
|
||||
Note: 'what foo -a' is the same as 'what foo -mcsxlb'. Also, you
|
||||
can print ALL BUT certain pieces of information by
|
||||
specifying -a AND the options to omit. For example,
|
||||
'what foo -ac' prints all information EXCEPT the creation
|
||||
date/time.
|
||||
|
||||
For BIN or $2E files that are external Davex commands, version
|
||||
information, a one-line summary, and the command's execution address
|
||||
are displayed.
|
||||
|
||||
SYS files created by the 'sysalias' command are identified, and
|
||||
the pathname of the aliased application is displayed. If
|
||||
there is a startup buffer, its size is displayed.
|
||||
|
||||
SYS files -not- created by 'sysalias' are identified as ProDOS 8
|
||||
applications. If there is a startup buffer, its length and
|
||||
default contents will be displayed (for example, BASIC.SYSTEM
|
||||
normally has a 65-byte startup buffer containing "startup").
|
||||
|
||||
BAS files are identified as Applesoft BASIC programs. 'what'
|
||||
computes the correct Aux-type for the file and prints a warning
|
||||
message if the file has a different Aux-type. (Use 'filetype'
|
||||
with -x to correct the problem.) [Some DOS 3.3-to-ProDOS
|
||||
conversion programs (including Apple's CONVERT utility) always
|
||||
give BAS files an Aux-type of $0801, which is typically correct.
|
||||
But if the DOS program had been saved from an address other than
|
||||
$801, nastiness will result when you try to load or run the
|
||||
converted program under ProDOS.]
|
||||
|
||||
Apple IIgs TOL files (TOOLnnn) are identified as specific system
|
||||
tools by the last 3 digits of their names.
|
||||
|
||||
For all GS/OS Object Module Format files (types $B1 through
|
||||
$BE), the OMF Version number is displayed. Version 1 is the
|
||||
first version and will work under all versions of ProDOS 16 and
|
||||
GS/OS.
|
||||
|
|
|
|||
|
|
@ -1 +1,36 @@
|
|||
como -- redirect command output to file or printer
syntax: como <pathname>
ex: como listing;type =:txt -h
como &;cat -t
como 2;type davex.doc
For commands on the same line only, redirects output that would
normally appear on the screen. If the specified file exists,
output will be appended to it. If it does not exist, it will be
created as a TXT file.
Output can be redirected to a device by slot number, as in the
third example.
'&' (or '0') represents the printer slot set by 'config'.
Even while spooled files are printing, you can redirect output
to a slot. (Not to the SAME slot 'spool' is printing to.)
Note: If no pathname is specified, output redirection is
cancelled; output returns to the screen. (The same thing happens
automatically after the whole command line is processed, so this
feature is rarely needed.)
A standard alias "print" is provided; it stands for "como &;", so
you can do things like
print help (same as "como &;help")
print;pg foo (same as "como &;;pg foo"
[extra ";" doesn't matter])
(see also: exec, config)
|
||||
|
||||
como -- redirect command output to file or printer
|
||||
|
||||
syntax: como <pathname>
|
||||
|
||||
ex: como listing;type =:txt -h
|
||||
como &;cat -t
|
||||
como 2;type davex.doc
|
||||
|
||||
For commands on the same line only, redirects output that would
|
||||
normally appear on the screen. If the specified file exists,
|
||||
output will be appended to it. If it does not exist, it will be
|
||||
created as a TXT file.
|
||||
|
||||
Output can be redirected to a device by slot number, as in the
|
||||
third example.
|
||||
|
||||
'&' (or '0') represents the printer slot set by 'config'.
|
||||
|
||||
Even while spooled files are printing, you can redirect output
|
||||
to a slot. (Not to the SAME slot 'spool' is printing to.)
|
||||
|
||||
Note: If no pathname is specified, output redirection is
|
||||
cancelled; output returns to the screen. (The same thing happens
|
||||
automatically after the whole command line is processed, so this
|
||||
feature is rarely needed.)
|
||||
|
||||
A standard alias "print" is provided; it stands for "como &;", so
|
||||
you can do things like
|
||||
|
||||
print help (same as "como &;help")
|
||||
|
||||
print;pg foo (same as "como &;;pg foo"
|
||||
[extra ";" doesn't matter])
|
||||
|
||||
(see also: exec, config)
|
||||
|
|
|
|||
Loading…
Reference in New Issue