@DATABASE "DOpusV4.guide"
@(C) "Copyright 1994-2000 GPSoftware, Copyright 2000-2001 Directory Opus 4 Research Project"
@AUTHOR "Christoph Gutjahr, Jonathan Potter"
@$VER: DOpus4Manual_English 1.2 (21.06.01)

@SMARTWRAP

@NODE Main "Directory Opus Manual"
@{LINDENT 1}

@{b}Directory Opus 4.16 Manual @{ub}@{PAR}

Written by Christoph Gutjahr and Jonathan Potter@{PAR}

Copyright 2000-2001 Directory Opus 4 Research Project@{PAR}
Copyright 1994-2000 GPSoftware@{PAR}

@{LINDENT 4}

@{" Introduction                 " link intro}@{PAR}
@{" Copyright Information        " link copyright}@{PAR}
@{" System Requirements          " link reqments}@{PAR}
@{" Installation                 " link installation}@{PAR}

@{" Directory Opus Walk-through  " link DOWT}@{PAR}
@{" Requesters & Viewers         " link Req&View}@{PAR}
@{" Directory Opus Configuration " link Config}@{PAR}
@{" Tech Guide                   " link tech}@{PAR}

@{" History                      " link history} @{fg highlight}<- Upgrading users: Read this!@{fg text}@{PAR}
@{" Frequently Asked Questions   " link faq}@{PAR}

@{" Contact / Support            " link contact}@{PAR}
@{LINDENT 1}


@{fg highlight}Note:@{fg text}@{PAR}

This manual makes heavy use of Amigaguide features that were introduced with
AmigaOS 3.1. It won't display correctly on earlier versions of the operating system
(lots of strange characters on the screen, ugly text formatting).@{PAR}

@ENDNODE
@NODE intro "Introduction"
@{LINDENT 1}

@{b}Introduction@{ub}@{PAR}

Welcome to the Directory Opus 4 Manual!@{PAR}

DirectoryOpus 4 (or 'Diropus', or 'DOpus') is a legendary file manager for Amiga Computers. It
features two directory windows, a very intuitive graphical user interface (including Drag'n
drop functionality) and is probably one of the most configurable programs you'll ever come
across.@{PAR}

It was developed by Jonathan Potter, the first (commercial) version was released in 1990.
Development continued until 1994 (up to version number 4.12), when Jonathan joined GPSoftware
as a partner, due to disputes with his former distributor about the non-payment of outstanding
royalties.@{PAR}

Together, they rewrote the program from scratch, turning it into a complete Workbench
replacement. That 'new' DirOpus (called DirOpus5, later versions are entitled 'Magellan' or
'Magellan 2') is still available for the Amiga from GPSoftware and most Amiga dealers, but the
decline of the Amiga market has forced the development of the Amiga version to be put on
indefinite hold.@{PAR}

Jon Potter and Greg Perry of GPSoftware are still developing Directory Opus. Currently a
Windows 95/98/NT version is nearing completion. This builds on the concepts of DOpus4 and
DOpus5 and introduces a number of new features and design elements for the PC market.@{PAR}

The 'old' DirOpus4 was released on several magazine coverdisks, but it retained its copyrighted
status until 1999. At that time, GPSoftware decided that the program had lost all its commercial
value, and they released the source codes under the GNU Public License.@{PAR}

At that point, Jacek Rzeuski took over the development of DirOpus. New versions of the program
can always be found on Aminet or at the @{" homepage " link contact} of the Directory Opus Research Project.@{PAR}

This manual was spread with coverdisk versions of Directory Opus 4. It's now the official
manual for Directory Opus 4, as the original printed manual is far more difficult to
distribute :)@{PAR}

@ENDNODE
@NODE copyright "Copyright information"
@{LINDENT 1}

@{b}Copyright Information@{ub}@{PAR}

Directory Opus 4 is Copyright (c) 1990-2000 by Jonathan Potter.@{PAR}

Directory Opus 4.13 and later versions modified by Jacek Rzeuski@{PAR}

This program is free software; you can redistribute it and/or
modify it under the terms of the GNU General Public License
as published by the Free Software Foundation; either version 2
of the License, or (at your option) any later version.@{PAR}

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.@{PAR}

All users of Directory Opus 4 (including versions distributed
under the GPL) are entitled to upgrade to the latest version of
Directory Opus version 5 at a reduced price. Please see
http://www.gpsoft.com.au for more information.@{PAR}

@{FG highlight}Copyright Notice@{FG text}@{PAR}

Note: Opus, Directory Opus,  DOpus, Opus File Manager, OpusPC, PCOpus are copyrights and
trademarks of GPSoftware and associated companies and may not be used except under
licence.@{PAR}

@ENDNODE
@NODE reqments "Directory Opus 4 System Requirements"
@{LINDENT 1}

@{b}Minimum System requirements@{ub}@{PAR}

To get Directory Opus 4 running you should have an Amiga computer with
at least AmigaOS 3.0. This computer should be equipped with a 68020
processor (or any later model of the 68xxx CPU series). DirOpus needs at
least 0.5 megabyte of memory.@{PAR}

@{FG Highlight}Recommended Third Party AddOns@{FG text}@{PAR}

Additional functionality can be achieved by installing the third party
libraries described below.@{PAR}
@{LINDENT 4}

@{i}PopupMenu.library: @{ui}@{PAR}

This will enable the popup menu that appears by clicking on the
@{" Disk Name " link 1.5.2} field with the right mouse button. This library is
Freeware and can be found on Aminet (util/libs/pmuser.lha).@{PAR}

@{i}XADMaster.library: @{ui}@{PAR}

This is a depacker system that is used to handle various types of file archives from
within DOpus. With this library system installed, you can @{" browse through archives " link 1.11} as
if it were normal directories. This library is Shareware and can be found on Aminet
(util/arc/xadmaster.lha). It is also included with OS 3.9 (OS 3.9 users: Please read
the @{" FAQ " link faq} entry regarding XADmaster.library!!). See also: @{" FORCEOPENXAD " link 1.3.1} tooltype.@{PAR}

@{i}XFDMaster.library: @{ui}@{PAR}

This is a decruncher system that decompresses crunched files on
the fly. DirOpus utilizes this library to load such crunched files
(i.e. into the text viewer). This library is Freeware and can be
found on Aminet (util/pack/xfdmaster.lha). See also: @{" FORCEOPENXFD " link 1.3.1}
tooltype and @{" -x " link 1.3.2} argument.@{PAR}

@{i}SysInfo.library: @{ui}@{PAR}

DirOpus can use this library for CPU usage estimation (instead of internal
meter). This might result in a more accurate value. Note that the library requires
Executive or SysMon to work. If none of them is running DOpus falls back to
internal meter. SysInfo.library support must be turned on with the @{" USESYSINFO " link 1.3.1} tooltype.@{PAR}

@ENDNODE
@NODE installation "Installation"
@{LINDENT 1}

@{b}Installing Directory Opus@{ub}@{PAR}

To install DirectoryOpus, just copy its directory to any place on your harddisk.@{PAR}

The program doesn't require any additional libraries to work, but there are several
recommended third party Add-Ons that will increase DOpus' functionality. Have a look at
the @{" Requirements " link reqments} section for more information.@{PAR}

Beginning with version 4.16, Directory Opus does not need an assign anymore.
If you are upgrading from earlier versions of the program, check your
"User-Startup" file located in S: and remove the following line:@{PAR}
@{LINDENT 4}

ASSIGN DOPUS: <path to your old version of DOpus>@{PAR}
@{LINDENT 1}

(where "<path to...>" would be something like "SYS:Tools/Dopus").@{PAR}

@{FG highlight}Further notes regarding installation@{FG text}@{PAR}

If you're upgrading from a very old version (3.x or earlier) or you used to
have your DirOpus files spread around your harddisk, please make sure that
the following files do not exist in your system directories (you may encounter
various problems otherwise):@{PAR}
@{LINDENT 4}

DopusRT:           C:@{PAR}
ConfigOpus#?       C:@{PAR}
DOpus_#?           C:@{PAR}
Diskcopy.info      C:@{PAR}
Format.info        C:@{PAR}
Install.info       C:@{PAR}
dopus.library      LIBS:@{PAR}
DirectoryOpus.#?   S:@{PAR}
DO_Deutsch.#?      S:@{PAR}
ConfigOpus.#?      S:@{PAR}
CO_Deutsch.#?      S:@{PAR}
DM_#?_Deutsch.str  S:@{PAR}
@{LINDENT 1}

@ENDNODE
@NODE DOWT "A Directory Opus Walk Through"
@{LINDENT 1}

@{b}Chapter 1 - A Directory Opus Walk Through@{ub}@{PAR}

This section describes the installation of the program and how to start
it. And it gives you an overview of the components of Directory Opus
and their usage.@{PAR}
@{LINDENT 4}

@{" What Is Directory Opus?              " link 1.1}@{PAR}
@{" Files and Directories                " link 1.2}@{PAR}

@{" Running Directory Opus               " link 1.3}@{PAR}
@{" Introduction to Using Directory Opus " link 1.4}@{PAR}

@{" Directory Windows                    " link 1.5}@{PAR}
@{" Custom Buttons                       " link 1.6}@{PAR}
@{" The Tiny Buttons                     " link 1.7}@{PAR}
@{" The Tiny Bottom Right Buttons        " link 1.8}@{PAR}
@{" Default Menus                        " link 1.9}@{PAR}

@{" Drag'n Drop                          " link 1.10}@{PAR}
@{" Handling archives                    " link 1.11}@{PAR}

@ENDNODE
@NODE 1.1 "DOWT/What is Directory Opus ?"
@{LINDENT 1}

@{b}1.1 - What Is Directory Opus?@{ub}@{PAR}

The theory behind Directory Opus is quite simple. On the screen there
are two windows. These are called Directory Windows. You can read a
directory into each of these from any device accessible by the Amiga.@{PAR}

You select files and/or directories in either of these windows, then
manipulate them almost any way you like. Selected entries can be copied
to the opposite window, deleted or renamed; text files can be read,
picture files can be viewed, and sound files can be heard.@{PAR}

Directory Opus offers much more than these "bare-bones" features, and you will
learn more throughout this guide.@{PAR}

@ENDNODE
@NODE 1.2 "DOWT/Files and Directories"
@{LINDENT 1}

@{b}1.2 - Files and Directories@{ub}@{PAR}

The Amiga's DOS (Disk Operating System) deals with two kinds of data
arrangement: files and directories.@{PAR}

Each file and directory must be given a unique name; within a directory
you cannot have two files, two directories, or a file and a directory
with the same name as each other.@{PAR}

@{FG Highlight}Files@{FG text}@{PAR}

Any data you record on a disk is stored in a file. Files contain
information, which may be from a database, from a word processor,
from a paint program, or the entire contents of a program.@{PAR}

The size of a file is expressed in bytes, each byte being
equivalent to one character. Storing the string "Hello" in a file
would use five bytes, as the word "Hello" is five characters long.@{PAR}

Whether a file can be displayed, executed, deleted, edited or
considered as a script file depends upon attributes that are
explained in the @{" Protection " link 2.1} Requester section.@{PAR}

All files have a datestamp which shows what the system date and
time were the last time the file was written to.@{PAR}

Files may also have a comment of up to 79 characters attached
to them. @{PAR}

@{FG Highlight}Directories@{FG text}@{PAR}

To store information in a logical manner, disks are generally
organised into directories, which are often referred to as
as drawers. If you picture a disk as a filing cabinet, with your
programs, database files and pictures as the actual files, than
directories are the drawers of the filing cabinet. Some of these
drawers have further drawers inside them, called sub-directories,
which themselves contain drawers, and so on, indefinitely.@{PAR}

The directory or sub-directory containing any given sub-directory
is known as its parent directory.@{PAR}

The highest level of organisation is the Root Directory. If the
directory is a filing cabinet, then the root directory is the room
it stands in.@{PAR}

The route you take along a directory tree to reach a file is
called path. As you proceed along the path, each branch of the
tree is separated from the next by a / character. For example,
the path of Archives is expressed as Work:Downloads/Archives.@{PAR}

To refer to Picture.ARC, you use what is called pathname. This
consists of a file's path, followed by the name of the file,
Picture.ARC's pathname would be:@{PAR}
@{LINDENT 3}

Work:Downloads/Archives/Picture.ARC@{PAR}
@{LINDENT 1}

The number of files and sub-directories any given directory can
contain is limited only by the amount of space on the disk.@{PAR}

@ENDNODE
@NODE 1.3 "DOWT/Running Directory Opus"
@{LINDENT 1}

@{b}1.3 - Running Directory Opus@{ub}@{PAR}

There are three common ways of running Directory Opus.@{PAR}
@{LINDENT 4}

@{" Manually from Workbench             " link 1.3.1}@{PAR}
@{" Manually from CLI                   " link 1.3.2}@{PAR}
@{" Automatically from the User-Startup " link 1.3.3}@{PAR}

@ENDNODE
@NODE 1.3.1 "DOWT/Running Directory Opus"
@{LINDENT 1}

@{b}1.3.1 - Starting From Workbench@{ub}@{PAR}

The easiest way to run Directory Opus is from the Workbench. Double
click on the Directory Opus icon on the Workbench screen and a few
seconds later the Directory Opus screen will appear.@{PAR}

You may also specify a directory that should be read into DOpus' left directory
lister at startup, overriding the configuration settings. Just select the directory
you want to display in DOpus, hold "Shift" and double-click on DOpus' icon.@{PAR}

If you've got the @{" XAD libraries " link reqments} installed, you may even specify an archive
that DOpus should display in its left directory lister. Again, just select the
archive file, hold "Shift" and double-click DOpus' icon.@{PAR}

@{FG Highlight}ToolTypes@{FG text}@{PAR}

If started from Workbench, DirOpus understands the following Tooltypes
(have a look at your Amiga documentation, if you do not understand the
concept of tooltypes):@{PAR}
@{LINDENT 4}

@{i}ICONSTART=1 @{ui}@{PAR}

Tells Directory Opus to start up iconified, which means that
the program will open only a small window on the Workbench
screen, instead of its own custom screen, and will sit
unobtrusively in the background until needed.@{PAR}

@{i}BUTTONSTART=1 @{ui}@{PAR}

Tells Directory Opus to start up @{" Button Iconified " link 1.9.1.Button_Iconified}. This is
a special variation of iconification: Only the Button Banks
will be shown on the Workbench screen. If both ICONSTART=1
and BUTTONSTART=1 are specified, Directory Opus will start up
Button Iconified.@{PAR}

@{i}CHECK=0 @{ui}@{PAR}

Directory Opus can be run several times at once. Normally
the program will check at Startup, if another copy is already
running. In case Directory Opus is already running, you will
be asked, if you want to run another copy, bring the already
running DirOpus to front or cancel the whole process. With
this ToolType, you can deactivate this check. Just set CHECK=0.@{PAR}

@{i}CONFIGFILE=<path to configfile> @{ui}@{PAR}

Tells Directory Opus where to load the configuration file
from. For instance, CONFIGFILE=DH1:stuff/directoryopus.cfg
would load (and subsequently save) the configuration file
from DH1:stuff/directoryopus.cfg. By default, DirOpus will
look in DOpus:S/ or S: for its configuration settings.@{PAR}

@{i}FORCEOPENXAD @{ui}@{PAR}

This will force DirOpus to open the XADMaster library at
startup (this library is used for handling archives). Normally
Directory Opus opens that library only when needed, and only if
it is opened by another program already.@{PAR}

@{i}FORCEOPENXFD @{ui}@{PAR}

This will force DirOpus to open the XFDMaster library at
startup (this library is used for reading crunched files into
the text reader or for printing them). Normally Directory
Opus opens that library only when needed, and only if it is
opened by another program already.@{PAR}

@{i}USESYSINFO @{ui}@{PAR}

This enables @{" sysinfo.library " link reqments} support.@{PAR}

@ENDNODE
@NODE 1.3.2 "DOWT/Running Directory Opus"
@{LINDENT 1}

@{b}1.3.2 - Starting From a CLI@{ub}@{PAR}

To run Directory Opus from the CLI enter:@{PAR}
@{LINDENT 4}

CD <path of DOpus' directory>@{PAR}
DirectoryOpus@{PAR}
@{LINDENT 1}

The first line switches to Directory Opus' directory, the second line start DirOpus.@{PAR}

You may also specify a directory that should be read into DOpus' left directory
lister at startup, overriding the configuration settings. Here's an example (assuming
DOpus can be found in "SYS:Tools/DirOpus"):@{PAR}
@{LINDENT 4}

CD SYS:Tools/DirOpus/@{PAR}
DirectoryOpus Work:download/@{PAR}
@{LINDENT 1}

If you've got the @{" XAD libraries " link reqments} installed, you may even specify an archive
that DOpus should display in its left directory lister:@{PAR}
@{LINDENT 4}

CD SYS:Tools/DirOpus/@{PAR}
DirectoryOpus Work:download/archive.lha@{PAR}
@{LINDENT 1}

@{FG Highlight}Arguments@{FG text}@{PAR}

DirOpus understands several arguments when it is started from the CLI
(NOTE: These arguments are case sensitive!):@{PAR}
@{LINDENT 4}

@{i}-i @{ui}@{PAR}

Tells Directory Opus to start up iconified, which means
that the program will open only a small window on the
Workbench screen, instead of its own custom screen, and
will sit unobtrusively in the background until needed.@{PAR}

@{i}-b @{ui}@{PAR}

Tells Directory Opus to start up @{" Button Iconified " link 1.9.1.Button_Iconified}.
This is a special variation of iconification: Only the
Button Banks will be shown on the Workbench screen. If
both -i and -b are specified, Directory Opus will start
up Button Iconified.@{PAR}

@{i}-g @{ui}@{PAR}

Directory Opus can be run several times at once. Normally
the program will check at Startup, if another copy is
already running. In case Directory Opus is already
running, you will be asked, if you want to run another
copy, bring the already running DirOpus to front or cancel
the whole process. Specifying this argument will
deactivate this check.@{PAR}

@{i}-c @{ui}@{PAR}

Tells Directory Opus where to load the configuration file
from. For instance, -cDH1:stuff/directoryopus.cfg would
load (and subsequently save) the configuration file from
DH1:stuff/directoryopus.cfg. By default, it will look in
DOpus:S/ and S:@{PAR}

@{i}-X @{ui}@{PAR}

This will force DirOpus to open the XADMaster library at
startup (this library is used for handling archives). Normally
Directory Opus opens that library only when needed, and only if
it is opened by another program already.@{PAR}

@{i}-x @{ui}@{PAR}

This will force DirOpus to open the XFDMaster library at
startup (this library is used for reading crunched files
into the text reader or for printing them). Normally
Directory Opus opens that library only when needed, and
only if it is opened by another program already.@{PAR}

@ENDNODE
@NODE 1.3.3 "DOWT/Running Directory Opus"
@{LINDENT 1}

@{b}1.3.3 - Automatic Startup in the User-Startup@{ub}@{PAR}

The User-Startup is a script file that is automatically executed when
you first turn on the computer. It can contain instructions to do many
different things, including running Directory Opus.@{PAR}

To modify your User-Startup you need a text
editor such as Commodore's Ed or MEmax. A highly recommended commercial
text editor is CygnusEd Professional, by ASDG-Inc. This is the text
editor with which Directory Opus was written, and is a very powerful
tool.@{PAR}

Run your text editor and load your User-Startup into it. The
User-Startup resides in the S: directory of your boot disk. Pick a
convenient place to put the new instruction (you can really put it
anywhere) and add the following lines:@{PAR}
@{LINDENT 4}

;BEGIN DirOpus@{PAR}
CD SYS:Tools/DirOpus@{PAR}
DirectoryOpus -i@{PAR}
;END DirOpus@{PAR}
@{LINDENT 1}

This assumes you have installed DirectoryOpus in a directory called
"SYS:Tools/DirOpus/". Of course you need to use the actual directory path.@{PAR}

The -i at the end of the instruction tells Directory Opus to start up
iconified, which means that the program will open only a small window
on the Workbench screen, instead of its own custom screen, and will sit
unobtrusively in the background until needed. If you do not want
Directory Opus to start up iconified, simply remove the -i.@{PAR}

Have a look at the @{" Running DirOpus from CLI " link 1.3.2} section for more
arguments that can be added to the instruction.@{PAR}

The more technically inclined may notice that there is no RUN on the
instruction line. This is because Directory Opus detaches itself,
freeing up the CLI and allowing it to continue with the User-Startup
(and ultimately closing).@{PAR}

Make sure you save the User-Startup once you have modified it. If your
changes make sense, Directory Opus will be run automatically when you
boot up.@{PAR}

@ENDNODE
@NODE 1.4 "DOWT/Intro to Opus"
@{LINDENT 1}

@{b}1.4 - Introduction to Using Directory Opus@{ub}@{PAR}

This section gives you a short tour of Directory Opus. It describes
Directory Opus in its default configuration. The various
@{" configuration " link Config} options are described later.@{PAR}

@{FG Highlight}Aborting@{FG text}@{PAR}

Before using the program, it is important to know how to abort an
action. Most commands can be aborted once they have begun, and
this can be useful if you accidentally start deleting the contents
of your hard drive.@{PAR}

To abort, press the left and right mouse buttons simultaneously.
This will only take effect if the Directory Opus screen is active
(i.e., at the front of the display).@{PAR}

Do not be alarmed if the action does not abort immediately; some
commands such as copy have to finish the file they are working on
before aborting.@{PAR}

@{FG Highlight}Directory Opus Components@{FG text}@{PAR}

Let's start with a brief description of the main components of
the Directory Opus Display.@{PAR}
@{LINDENT 4}

@{" Title Bar         " link 1.4.1}@{PAR}
@{" Clock/Memory Bar  " link 1.4.2}@{PAR}
@{" Directory Windows " link 1.4.3}@{PAR}
@{" Custom Buttons    " link 1.4.4}@{PAR}
@{" Drive Buttons     " link 1.4.5}@{PAR}
@{" Custom Menus      " link 1.4.6}@{PAR}
@{" Tiny Buttons      " link 1.4.7}@{PAR}

@ENDNODE
@NODE 1.4.1 "DOWT/Intro to DOpus/DOpus Components"
@{LINDENT 1}

@{b}1.4.1 - Title Bar@{ub}@{PAR}

The Title Bar is at the very top of the Directory Opus display. It is
used to display various status or error messages. If you are unsure
what Directory Opus is doing, it is a good idea to look in the title
bar for a hint. The title bar is also used to reposition the Directory
Opus window.@{PAR}

@ENDNODE
@NODE 1.4.2 "DOWT/Intro to DOpus/DOpus Components"
@{LINDENT 1}

@{b}1.4.2 - Clock/Memory Bar@{ub}@{PAR}

The Clock/Memory Bar is at the bottom of the Directory Opus display. It
displays current memory and time information.@{PAR}

@ENDNODE
@NODE 1.4.3 "DOWT/Intro to DOpus/DOpus Components"
@{LINDENT 1}

@{b}1.4.3 - Directory Windows@{ub}@{PAR}

A directory window allows you to display the files and sub-directories
contained in a directory. You can select (and deselect) files and
sub-directories. Directory Opus has two directory windows. More
information about Directory Windows is available in the section
@{" Directory Windows " link 1.5}.@{PAR}

@ENDNODE
@NODE 1.4.4 "DOWT/Intro to DOpus/DOpus Components"
@{LINDENT 1}

@{b}1.4.4 - Custom Buttons@{ub}@{PAR}

The Custom buttons perform actions which usually trigger an operation
of the selected files in the active directory window. More information
about Custom Buttons is available in the section @{" Custom Buttons " link 1.6}.@{PAR}

@ENDNODE
@NODE 1.4.5 "DOWT/Intro to DOpus/DOpus Components"
@{LINDENT 1}

@{b}1.4.5 - Drive Buttons@{ub}@{PAR}

The Drive buttons read the contents of a specific directory and display
them in the currently active directory window.@{PAR}

@ENDNODE
@NODE 1.4.6 "DOWT/Intro to DOpus/DOpus Components"
@{LINDENT 1}

@{b}1.4.6 - Custom Menus@{ub}@{PAR}

@{" Custom menus " link 1.9}, like @{" Custom buttons " link 1.4.4}, perform actions.@{PAR}

@{FG Highlight}NOTE:@{FG text}@{PAR}

Many parts of the DirectoryOpus Interface use the Right Mouse button
for alternative operations. As with DPaint, the mouse pointer must be
positioned on the title bar when the Right Mouse button is clicked for
the Menu Titles to appear.@{PAR}

@ENDNODE
@NODE 1.4.7 "DOWT/Intro to DOpus/DOpus Components"
@{LINDENT 1}

@{b}1.4.7 - Tiny Buttons@{ub}@{PAR}

Four Tiny buttons are positioned between the two directory windows, and
six Tiny buttons are placed on the @{" Clock/Memory Bar " link 1.4.2}. More information
about Tiny Buttons is available in the sections @{" Tiny Buttons " link 1.7} and
@{" The Tiny Bottom Right Buttons " link 1.8}.@{PAR}

@ENDNODE
@NODE 1.5 "DOWT/Intro to DOpus/Dir Windows"
@{LINDENT 1}

@{b}1.5 - Directory Windows@{ub}@{PAR}

There are two Directory windows. Only one window is active at a time.
Because some actions, such as copy, work with selected files in the
active Directory Window and use the inactive Directory Window as the
destination, the active window is referred to as the Source Window and
the inactive window is referred to as the Destination Window.@{PAR}

@{FG Highlight}Selecting the Active Directory Window@{FG text}@{PAR}

Clicking anywhere in a window with either mouse button will
activate that window. Unless you are extremely precise in your
placement of the pointer, however, clicking with the left mouse
button to activate a window may lead to selecting an
unwanted entry. This is when using the right mouse button can be
useful, as selecting entries is a left mouse button command, but
clicking with the right mouse button will never have that effect.@{PAR}

Pressing the space bar or the TAB key activates the inactive
directory window. This allows you to toggle between the active and
inactive windows.@{PAR}

@{FG Highlight}Directory Window components:@{FG text}@{PAR}
@{LINDENT 4}

@{" Directory Field                  " link 1.5.1}@{PAR}
@{" Disk Name                        " link 1.5.2}@{PAR}
@{" Window Area                      " link 1.5.3}@{PAR}
@{" Window View Sliders              " link 1.5.4}@{PAR}
@{" Next and Previous Buffer buttons " link 1.5.5}@{PAR}

@ENDNODE
@NODE 1.5.1 "DOWT/Intro DOpus/Dir Windows"
@{LINDENT 1}

@{b}1.5.1 - Directory Field@{ub}@{PAR}

Many DirectoryOpus commands require that you read a directory into the
active Directory Window. To read any directory, enter the name into the
Directory Field.@{PAR}

When you click in a directory field it will be activated and a cursor
will appear. Pressing the Return key will activate the Directory Field
for the Active Directory Window too. Once the Field is activated, enter
the mane of the directory you want.@{PAR}

There are several @{" editing features " link edfeat} you can use.@{PAR}

Once your have entered the pathname you wish to read, press return. You
will see the directory window activated (if it is not already active),
and the contents of the directory will be shown.@{PAR}

@ENDNODE
@NODE 1.5.2 "DOWT/Intro DOpus/Dir Windows"
@{LINDENT 1}

@{b}1.5.2 - Disk Name@{ub}@{PAR}

The Disk Name area of the Directory Window shows the Disk or Volume
Name for the currently displayed Directory. This area also displays the
amount of free space on the directory's volume.@{PAR}

Double clicking on a window's Disk Name field with the left mouse
button will bring up a requester showing all parent directories of the
displayed directory.@{PAR}

Performing a @{" Click-M-Click " link glos} operation (Click-Move-Click) with the left
mouse button (first click on the Disk Name of the active directory
window then on the Disk Name of the inactive window) will cause DirOpus
to copy the active window into the inactive one.@{PAR}

Performing a Click-M-Click operation with the right mouse button will
swap the two directory windows.@{PAR}

@{FG highlight}The PopUp Menu@{FG text}@{PAR}

Clicking on the Disk Name with the right mouse button (and holding that
button) will bring up a popup menu that lets you select the sort method
easily, without starting the configuration program first.@{PAR}

This menu offers a list of items which the window list can be sorted
on. A checkmark indicates the current sort item. The following sort
items are available:@{PAR}
@{LINDENT 4}

- File name@{PAR}
- File size@{PAR}
- Protection bits@{PAR}
- Creation date@{PAR}
- File comment@{PAR}
- File type@{PAR}
@{LINDENT 1}

By selecting the item 'Reverse order' you can specify that the list
should be sorted in reverse order. For instance instead of A coming
before B, B would come before A. A checkmark indicates if Reverse order
is activated at the moment.@{PAR}

The last menu item,'K/M/G mode', corresponds to the configuration
setting @{" Show entries as K/M/G " link 3.17.7.displayed}.@{PAR}

@{FG Highlight}NOTE:@{FG text}@{PAR}

The popup menu described above is only available if you have installed
the optional 'popupmenu.library' correctly. See @{" Requirements " link reqments} for
further details.@{PAR}

@ENDNODE
@NODE 1.5.3 "DOWT/Intro DOpus/Dir Windows"
@{LINDENT 1}

@{b}1.5.3 - Window Area@{ub}@{PAR}

The Window Area of the Directory Window displays the directory's files
and sub-directories.@{PAR}
@{LINDENT 4}

@{" Selecting Files              " link 1.5.3.selecting}@{PAR}
@{" Entering Sub-Directories     " link 1.5.3.entering}@{PAR}
@{" Moving to a Parent Directory " link 1.5.3.moving}@{PAR}

@ENDNODE
@NODE 1.5.3.selecting "DOWT/Intro DOpus/Dir Windows"
@{LINDENT 1}

@{b}Selecting Files@{ub}@{PAR}

To select an entry, file or sub-directory, click on it with the left
mouse button. If you hold down the left mouse button and move the mouse
up or down, all entries that the pointer passes over will be
highlighted. This is called drag-selecting.@{PAR}

Clicking on an entry which is already selected will deselect it. If you
drag-select when you click on an already selected entry, other already
selected entries that are passed over will be deselected.@{PAR}

@ENDNODE
@NODE 1.5.3.entering "DOWT/Intro DOpus/Dir Windows"
@{LINDENT 1}

@{b}Entering Sub-Directories@{ub}@{PAR}

Many directories that you read in will contain sub-directories. Instead
of having to type in the name of a sub-directory, you only need to
double-click on it. This will load the sub-directory into the same
Directory Window.@{PAR}

Opening the sub-directory in the other directory window allows you to
copy files between the sub-directory and its parent. To do this, you
perform a @{" Click-M-Click " link glos} operation (Click Move Click) with the left mouse button.
Click-M-Click means to click first on a sub-directory entry then to
move the mouse pointer to the other (inactive) window and click again.
This can be tricky because the two clicks must occur within the Amiga
Configured Double-Click Time (see Amiga Input Preferences).@{PAR}

An alternative method to Click-M-Click (which requires less mouse
pointer gymnastics), is called @{" Click-Drag-Release " link glos}:
Click and hold on an unselected sub-directory entry. Then, without releasing the
left mouse button, press and release the right mouse button. Still holding the left mouse
button, move the mouse pointer to the inactive window. As you move the
mouse pointer, a copy of the selected sub-directory will follow the
mouse. When you position the mouse pointer over the inactive window,
release the mouse button; the sub-directory will be read into the
inactive window, which now will become the active Directory Window.@{PAR}

A final alternative (also called @{" Click-Drag-Release " link glos}), is
to click and hold on an unselected sub-directory entry. Then, without
releasing the left mouse button, move the pointer to the unselected
Directory Window. The trick to this method is to move the mouse
pointer horizontally without moving up or down (this is for the sure
handed mouse gymnast). Should you inadvertently move the mouse pointer
over an entry above or below the selected sub-directory, that entry
will follow the mouse pointer over to the inactive window and will be
read when you release the mouse pointer.@{PAR}

@{FG highlight}Note:@{FG text}@{PAR}

The @{" Click-Drag-Release " link glos} methods are only available if the
appropriate @{" config setting " link 3.17.5} is activated!@{PAR}

@ENDNODE
@NODE 1.5.3.moving "DOWT/Intro DOpus/Dir Windows"
@{LINDENT 1}

@{b}Moving to a Parent Directory@{ub}@{PAR}

If the directory displayed in a Directory Window is a sub-directory,
you may wish to return to its Parent Directory. You could return to the
Parent directory by editing the Directory Field text directly, but the
procedure is cumbersome and error-prone; there are better ways.@{PAR}

The default configuration includes a Custom Button which returns you to
the @{" Parent " link 1.6.Parent} Directory.@{PAR}

Each Directory Window contains a hidden Parent button on the outer edge
of the window area which will move you to a Parent Directory. On the
left Directory Window, it is the white border on the on the far left.
On the right Directory window, it is the black border on the far right.
When you click the left mouse button on a hidden Parent button,
Directory Opus will display the directory's parent, if it has one. When
you click the right mouse button on the hidden Parent button, Directory
Opus will display the root directory.@{PAR}

Double clicking on a window's @{" Disk Name " link 1.5.2} field with the left
left mouse button will bring up a requester showing all parent
directories of the displayed directory.@{PAR}

@ENDNODE
@NODE 1.5.4 "DOWT/Intro DOpus/Dir Windows"
@{LINDENT 1}

@{b}1.5.4 - Window View Sliders@{ub}@{PAR}

Once a directory had been read in, it is displayed in the directory
window. There is limited space in the window so the entire directory
contents may not be visible at once. A pair of Sliders extends your
view of the window. In the center of the two directory windows are two
vertical Window Sliders. You can slide these up and down thus scroll
though the contents of the directory.@{PAR}

To slide the vertical window view sliders, press the left mouse button
on the black bar and, while holding down the mouse button, move the
mouse up and down.@{PAR}

Click above or below the solid bar for the slider to move one page in
that direction.@{PAR}

At the bottom of the two vertical Window View Sliders are arrow
buttons. These will move the slider on their line in the direction of
the arrow when clicked on.@{PAR}

Click and hold the left mouse button on one of the arrow buttons for
the directory to continuously scroll through the window.@{PAR}

Press either the up or down cursor keys to move one line in that
direction. These too will continuously scroll when held down.@{PAR}

Press the up or down cursor keys in conjunction with either SHIFT key
to move a page in that direction.@{PAR}

Press the cursor key in conjunction with the CTRL key to jump to the
top or bottom of the directory listing.@{PAR}

To scroll quickly to the first entry starting with a particular letter,
press that letter. The directory will scroll as close as it can get
to the first entry, file or directory, starting with that letter.@{PAR}

Press a letter in conjunction with either SHIFT key to scroll only to
the first file beginning with that letter.@{PAR}

Regardless of if entire directory fits in vertically, it will
definitely not fit in horizontally. There is more information available
for entries than just the filename. Also displayed is the size in
bytes, the @{" protection " link 2.1} bits assigned to that entry, the date that
entry was last written to the disk, and any @{" comment " link 1.6.Comment} that may be
assigned to that entry.@{PAR}

Horizontal Window View Sliders can be seen at the bottom of the
directory windows, with arrows at the inner ends. These work like the
Vertical Window Views Sliders, including the keyboard equivalents.@{PAR}

You can also scroll up and down, and left and right, by holding the
right mouse button and moving the mouse.@{PAR}

The Directory Windows are usually tha same size. If you want to see
more information than is displayed in the windows you can stretch the
divider between them left or right to resize them.@{PAR}

There is a hidden size bar between the two vertical Window View
Sliders. When you click and hold this button, the size bar will appear.
While holding he mouse button, move the mouse left or right. When you
have the window as you want it, release the mouse button.@{PAR}

There are three shortcut keys for resizing the Directory Windows:@{PAR}
@{LINDENT 4}

- Slides the Window View Sliders to the far left@{PAR}

\\ Slides them to the far right.@{PAR}

= Recentres the Window View Sliders@{PAR}

@ENDNODE
@NODE 1.5.5 "DOWT/Intro DOpus/Dir Windows"
@{LINDENT 1}

@{b}1.5.5 - Next and Previous Buffer Buttons@{ub}@{PAR}

Directory Opus maintains up to 100 directory buffers for each directory
window.@{PAR}

To move back and forth through the buffers, click on either the
Previous Buffer button or the Next Buffer button. The Buffer will be
displayed without re-reading the drive. The keyboard equivalent
alternative is to press the ALT key in conjunction with the left or
right cursor key.@{PAR}

To activate the directory field, press the Return key.@{PAR}

To re-read the directory, press the Return key twice.@{PAR}

@ENDNODE
@NODE 1.6 "DOWT/Intro to DOpus/Custom Buttons"
@{LINDENT 1}

@{b}1.6 - Custom Buttons@{ub}@{PAR}

There are default Custom buttons, all of which have left mouse button
commands. Some of the buttons are also configured to perform Right
Mouse button commands.@{PAR}

The Custom buttons with right mouse button commands are indicated by a
"dog-ear" in the upper right corner of the button. The All Custom
button demonstrates the dog-ear.@{PAR}

@{FG Highlight}IMPORTANT:@{FG text}@{PAR}

Many of the Custom buttons perform actions on the selected files in the
current directory window. Before clicking on a Custom button, verify
that the intended directory window is active. Novice Directory Opus
users can be confused when they have clicked on a Custom button in an
inactive window, and it does nothing. Of course you should verify that
the selected files and directories within the directory window are the
ones you wish acted on.@{PAR}
@{LINDENT 4}

@{" All    " link 1.6.All}            @{" MakeDir    " link 1.6.MakeDir}           @{" Icon Info " link 1.6.Icon_Info}@{PAR}
@{" Toggle " link 1.6.Toggle}            @{" Assign     " link 1.6.Assign}           @{" Add Icon  " link 1.6.Add_Icon}@{PAR}
@{" None   " link 1.6.None}            @{" Check_Fit  " link 1.6.Check_Fit}           @{" Arc Ext   " link 1.6.Arc_Ext}@{PAR}
@{" Parent " link 1.6.Parent}            @{" GetSizes   " link 1.6.GetSizes}           @{" Encrypt   " link 1.6.Encrypt}@{PAR}
@{" Root   " link 1.6.Root}            @{" ClearSizes " link 1.6.ClearSizes}           @{" Read      " link 1.6.Read}@{PAR}
@{" Copy   " link 1.6.Copy}            @{" Hunt       " link 1.6.Hunt}           @{" ANSI Read " link 1.6.ANSI_Read}@{PAR}
@{" CopyAs " link 1.6.CopyAs}            @{" Search     " link 1.6.Search}           @{" Hex Read  " link 1.6.Hex_Read}@{PAR}
@{" Move   " link 1.6.Move}            @{" Run        " link 1.6.Run}           @{" Show      " link 1.6.Show}@{PAR}
@{" MoveAs " link 1.6.MoveAs}            @{" Execute    " link 1.6.Execute}           @{" Play      " link 1.6.Play}@{PAR}
@{" Rename " link 1.6.Rename}            @{" Comment    " link 1.6.Comment}           @{" Loop Play " link 1.6.Loop_Play}@{PAR}
@{" Clone  " link 1.6.Clone}            @{" Datestamp  " link 1.6.Datestamp}           @{" Edit      " link 1.6.Edit}@{PAR}
@{" Delete " link 1.6.Delete}            @{" Protect    " link 1.6.Protect}           @{" New File  " link 1.6.New_File}@{PAR}
@{" Print  " link 1.6.Print}@{PAR}
@{LINDENT 1}

The number of custom buttons in Directory Opus is limited only by@{PAR}
available memory. The @{" Commands " link Commands} chapter explains more about the@{PAR}
buttons, and the @{" Command Editor " link 3.6} section explains how to configure@{PAR}
them.@{PAR}

@ENDNODE
@NODE 1.6.All "DOWT/Intro to DOpus/Custom Buttons"
@{LINDENT 1}

@{b}All@{ub}@{PAR}

The All button selects all entries in the currently active directory
window.@{PAR}

@ENDNODE
@NODE 1.6.Toggle "DOWT/Intro to DOpus/Custom Buttons"
@{LINDENT 1}

@{b}Toggle@{ub}@{PAR}

Selecting Toggle with the right mouse button will Toggle or reverse the
state of all entries. This causes selected entries to be deselected
and deselected entries to be selected.@{PAR}

@ENDNODE
@NODE 1.6.None "DOWT/Intro to DOpus/Custom Buttons"
@{LINDENT 1}

@{b}None@{ub}@{PAR}

The None button deselects all entries in the currently active directory
window.@{PAR}

@ENDNODE
@NODE 1.6.Parent "DOWT/Intro to DOpus/Custom Buttons"
@{LINDENT 1}

@{b}Parent@{ub}@{PAR}

The @{" Parent " link Parent} button reads the parent directory of the directory open
in the active directory window. If the parent directory is contained
in the window's @{" Buffer List " link 1.7.B}, it will be displayed without re-reading
the directory.@{PAR}

When the current directory is an @{" assignment " link 1.6.Assign}, for example C:, the
assignment will be expanded, and then the parent command will move to
the parent directory of the assigned directory.@{PAR}

@ENDNODE
@NODE 1.6.Root "DOWT/Intro to DOpus/Custom Buttons"
@{LINDENT 1}

@{b}Root@{ub}@{PAR}

The @{" Root " link Root} button reads the root directory of the active directory
window. As with the @{" Parent " link 1.6.Parent} command, the buffer list will be
searched before the parent directory is re-read.@{PAR}

When the current directory is a sub-directory to an @{" assigned " link 1.6.Assign} directory,
the Root command will display the assigned directory. When
the current directory is an assigned directory, the Root command will
display the root drive of the assigned directory.@{PAR}

@ENDNODE
@NODE 1.6.Copy "DOWT/Intro to DOpus/Custom Buttons"
@{LINDENT 1}

@{b}Copy@{ub}@{PAR}

The @{" Copy " link Copy} button copies the selected file to the destination
(inactive) directory. If any directories are selected to copy, the
sub-directory @{" Filter " link 1.8.F} will be used to determine which files will
be copied.@{PAR}

@ENDNODE
@NODE 1.6.CopyAs "DOWT/Intro to DOpus/Custom Buttons"
@{LINDENT 1}

@{b}CopyAs@{ub}@{PAR}

The @{" CopyAs " link CopyAs} command is similar to @{" Copy " link 1.6.Copy} except that the antries
are copied to the destination directory using new names that you
specify. @{" Wildcards " link WldCrdPat} can be used here.@{PAR}

@ENDNODE
@NODE 1.6.Move "DOWT/Intro to DOpus/Custom Buttons"
@{LINDENT 1}

@{b}Move@{ub}@{PAR}

This command will move all selected entries from the source directory
to the destination directory. The entry will no longer exist in its
original place. If any directories are selected to move, the sub-
directory @{" Filter " link 1.8.F} will be used to determine which files will be
moved.@{PAR}

Be careful with this command. Directory Opus will @{" delete " link 1.6.Delete} the file
if you are moving it to a different device.@{PAR}

@ENDNODE
@NODE 1.6.MoveAs "DOWT/Intro to DOpus/Custom Buttons"
@{LINDENT 1}

@{b}MoveAs@{ub}@{PAR}

@{" MoveAs " link MoveAs} is similar to the @{" Move " link 1.6.Move} command except that it allowes you
to give each entry a new name before it is moved.@{PAR}

@ENDNODE
@NODE 1.6.Rename "DOWT/Intro to DOpus/Custom Buttons"
@{LINDENT 1}

@{b}Rename@{ub}@{PAR}

@{" Rename " link Rename} allows you to give new names to all selected entries in the
active directory window. A requester will appear for each entry in
turn, asking for the new name. The initial rename requester has two
string fields instead of one. You will usually just edit the name in
the lower of the two fields to the new name.@{PAR}

A limited type of @{" wildcard " link WldCrdPat} rename is possible. Entering an * in the
bottom field allows you to add prefixes or suffixes. For instance,
entering *.pic will add a .pic suffix to all selected entries. Entering
A* will add an A prefix. Only one * may be used in this process.@{PAR}

You cannot give a file a name that contains an *.@{PAR}

If you enter a * in the top as well as the bottom field, you can
replace sections of the name. For example, entering *.pic in the top
Field and *.iff in the bottom Field will replace the .pic suffix in
that entry that has one with a .iff suffix. If an entry does not have
a .pic suffix, it will be left untouched. The * may also be embedded. 
For instance, renaming FOO*BAZ as GEE*WIZ would rename FOOBARBAZ as
GEEBARWIZ. Again, only one * may be used in each of the string Fields.@{PAR}

@ENDNODE
@NODE 1.6.Clone "DOWT/Intro to DOpus/Custom Buttons"
@{LINDENT 1}

@{b}Clone@{ub}@{PAR}

@{" Clone " link Clone} allows you to make a copy of selected entries in the same
directory, but with different names. A requester will appear for each
entry, asking for the new name.@{PAR}

@ENDNODE
@NODE 1.6.Delete "DOWT/Intro to DOpus/Custom Buttons"
@{LINDENT 1}

@{b}Delete@{ub}@{PAR}

@{" Delete " link Delete} will remove all selected entries in the active directory
window.@{PAR}

Be careful with this, as it is easy to wipe out valuable data if you
are careless. Directory Opus's default configuration brings up a
requester before deleting. Nevertheless, you should always double
check the selected files before clicking this button.@{PAR}

The Delete button can also be used to remove assigns: Just display the device list
(press the right mouse button over the @{" tiny S button " link 1.7.s} in the center of DirOpus'
window), select the assign(s) you want to remove and press Delete.

@ENDNODE
@NODE 1.6.Print "DOWT/Intro to DOpus/Custom Buttons"
@{LINDENT 1}

@{b}Print@{ub}@{PAR}

The @{" Print " link Print} button brings up a requester which allows you full control
of Print formatting. For more information, see the
@{" Print File Requester " link 2.6}.@{PAR}

The Print command automatically decrunches text crunched with various
packing methods. It utilizes the XFDmaster library for that purpose.
Please refer to the @{" Requirements " link reqments} section for further information).@{PAR}

@ENDNODE
@NODE 1.6.Makedir "DOWT/Intro to DOpus/Custom Buttons"
@{LINDENT 1}

@{b}Makedir@{ub}@{PAR}

Makedir allows you to create a new sub-directory in the active
directory window; its name is limited to 30 characters. A configuration
option, @{" Create Icons With Directories " link 3.17.6}, can be used to create an icon
at the same time. The name of the directory is limited to 25 characters
if Create Icons With Directories is enabled.@{PAR}

@ENDNODE
@NODE 1.6.Assign "DOWT/Intro to DOpus/Custom Buttons"
@{LINDENT 1}

@{b}Assign@{ub}@{PAR}

@{" Assign " link Assign} allows you to create an AmigaDOS assignment to the directory
in the active window. The Assign Command gives more examples.@{PAR}

@ENDNODE
@NODE 1.6.Check_Fit "DOWT/Intro to DOpus/Custom Buttons"
@{LINDENT 1}

@{b}Check Fit@{ub}@{PAR}

The @{" Check Fit " link CheckFit} button tests whether the selected file will fit on the
destination drive. The Screen title bar will display the number of
bytes needed, the available space, and the percentage of the files
which will fit on the destination drive.@{PAR}

@{fg highlight}Important Note!@{fg text}@{PAR}

This command is heavily outdated. It only knowns about FFS partitions with
512 Bytes per block. It will fail (in other words: report wrong results) on any
partition that does not match these specs exactly. Avoid this command if you're
not sure that all of your partitions are FFS, 512 Bytes/block!@{PAR}

@ENDNODE
@NODE 1.6.GetSizes "DOWT/Intro to DOpus/Custom Buttons"
@{LINDENT 1}

@{b}GetSizes@{ub}@{PAR}

The @{" GetSizes " link GetSizes} button causes any selected sub-directories to be
scanned. The scanning process calculates the total size, in bytes, of
all files contained in the sub-directory. Once scanned, the sub-
directory will be displayed.@{PAR}

If a sub-directory has been previously scanned, it will not be re-
scanned when you select the GetSizes button. See @{" Clear Sizes " link 1.6.ClearSizes} for
more information.@{PAR}

The GetSizes button also displays in the status bar the number of
files, directories and bytes that have been selected out of the total
number of files, directories and bytes. If there is enough space for
the total selected bytes on the disk in the destination directory
window, all selected files would fit on the destination disk if they
were copied and a Y will be displayed after the count. If they won't
fit, an N will be displayed.@{PAR}

If you select an operation which causes a sub-directory to be scanned
(e.g. @{" COPY " link 1.6.Copy}, @{" PROTECT " link 1.6.Protect}, @{" HUNT " link 1.6.Hunt}, etc.), the size will be displayed as
though you had performed a GetSizes.@{PAR}

@ENDNODE
@NODE 1.6.ClearSizes "DOWT/Intro to DOpus/Custom Buttons"
@{LINDENT 1}

@{b}ClearSizes@{ub}@{PAR}

The @{" ClearSizes " link ClearSizes} button will clear the sizes for selected
directories, but not for selected files.@{PAR}

If a sub-directory has been scanned already, pressing the @{" Get Sizes " link 1.6.GetSizes} button
will not work. It is possible that a previously scanned
directory's size is no longer accurate; any application, including
Directory Opus, might have changed the contents of the sub-directory
since it was last scanned. To re-scan a sub-directory, the size must be
cleared with the ClearSizes button.@{PAR}

@ENDNODE
@NODE 1.6.Hunt "DOWT/Intro to DOpus/Custom Buttons"
@{LINDENT 1}

@{b}Hunt@{ub}@{PAR}

The Hunt button allows you to search all selected sub-directories for a
specified file or files. A requester appears asking for the pattern to
hunt for. You can use full pattern matching for this search.@{PAR}

If a file matching the pattern is found, you are asked if you wish to
enter the directory containing it, or to continue the search. If you
select to enter the directory, the directory will be read and then all
matching entries will be highlighted.@{PAR}

You can also select entire devices to hunt, using the @{" DEVICE LIST " link GetDevices} command.@{PAR}

If any directories are selected to hunt, the sub-directory @{" Filter " link 1.8.F} will be used to determine which files will be searched.@{PAR}

@ENDNODE
@NODE 1.6.Search "DOWT/Intro to DOpus/Custom Buttons"
@{LINDENT 1}

@{b}Search@{ub}@{PAR}

The @{" Search " link Search} button allows you to search the contents of all selected
files, and the files within selected directories, for a specified
string. A requester appears asking for the string pattern to look for.
Again, full pattern matching is supported.@{PAR}

If a file containing the string is found, you are asked if you wish to
read that file, or continue the search. If you select to read the
file, it will be loaded into the text viewer, and a search will
automatically be initiated for the string you want.@{PAR}

You can also select entire devices to search, using the @{" DEVICE LIST " link GetDevices} command.@{PAR}

If any directories are selected to search, the sub-directory @{" Filter " link 1.8.F} will be used to determine which files will be searched.@{PAR}

@{fg highlight}Searching for ASCII codes@{fg text}@{PAR}

The search string may also contain ASCII codes. Just type the decimal ASCII value, preceeded
by a backslash (i.e. "\\65" would be the same as "a"). ASCII values may be mixed with normal
text. If you enter several ASCII codes (or mix ASCII codes and normal text) make sure that each
ASCII value is followed by a space. Use "\\\\" to search for a backslash, this way DOpus
knows that the following text is not an ASCII code.@{PAR}

Even hexadecimal ASCII codes are supported: Use the "$" sign to inform DOpus that you want to
search for hexadecimal ASCII codes. Mixing hex. ASCII and normal text is not possible..@{PAR}

Here are some examples:@{PAR}
@{LINDENT 4}

- "\\65"                  (the letter "a")@{PAR}
- "ag\\65 in"             (is the same as "again")@{PAR}
- "\\65 \\71 \\65 \\73 n"    (is the same as "again")@{PAR}
- "$0D0A"                (search for Windows-like EOL coding)@{PAR}
- "\\\\"                   (search for a backslash)@{PAR}
- "$$"                   (search for "$")@{PAR}
@{LINDENT 1}

@ENDNODE
@NODE 1.6.Run "DOWT/Intro to DOpus/Custom Buttons"
@{LINDENT 1}

@{b}Run@{ub}@{PAR}

The Run button allows you to run each selected file in turn, providing
that file is executable. It is similar to double-clicking on the file's
icon, or running it from the CLI. A requester will appear asking for
any arguments, should it require any.@{PAR}

@ENDNODE
@NODE 1.6.Execute "DOWT/Intro to DOpus/Custom Buttons"
@{LINDENT 1}

@{b}Execute@{ub}@{PAR}

The @{" Execute " link Execute} button will "execute" files as script files. This has
the same effect as running that script file via IconX (refer to
AmigaDOS manual), or executing it from the CLI.@{PAR}

@ENDNODE
@NODE 1.6.Comment "DOWT/Intro to DOpus/Custom Buttons"
@{LINDENT 1}

@{b}Comment@{ub}@{PAR}

The @{" Comment " link Comment} button allows you to add comments to all selected
entries, or to edit existing comments. The maximum length of a comment
is 79 characters. If any directories are selected to comment, the sub-
directory @{" Filter " link 1.8.F} will be used to determine which files will be
commented.@{PAR}

You will be prompted for a comment for each selected entry. If you wish
to attach the same comment to all entries, you should select the All
button within the requester.@{PAR}

@ENDNODE
@NODE 1.6.Datestamp "DOWT/Intro to DOpus/Custom Buttons"
@{LINDENT 1}

@{b}Datestamp@{ub}@{PAR}

The Datestamp button allows you to change the datestamp of the selected
files and directories in the active directory window to what ever date
you want. When you select directories, you are asked whether you wish
the files within them to have their datestamps modified also.@{PAR}

If any directories are selected to datestamp, the sub-directory
@{" Filter " link 1.8.F} will be used to determine which files will be datestamped.@{PAR}

For each entry, you are presented with a requester. If you wish the
file to have its datestamp set to the current date and time, simply
press return. Otherwise, enter the date and time you want.@{PAR}

To set the datestamp of all selected entries you should select the All
button from the datestamp requester.@{PAR}

Choose Okay or press return to set the datestamp one file at a time.@{PAR}

@ENDNODE
@NODE 1.6.Protect "DOWT/Intro to DOpus/Custom Buttons"
@{LINDENT 1}

@{b}Protect@{ub}@{PAR}

The @{" Protect " link Protect} button allows you to modify the protection bits of the
selected files and directories in the active directory window. When
you select directories, you are asked whether you also wish the files
within them to be protected. For each entry, you are presented with a
requester displaying the protection bits currently set for that entry.
This is described in greater detail in @{" Protection Requester " link 2.1}.@{PAR}

If any directories are selected to protect, the sub-directory @{" Filter " link 1.8.F} will
be used to determine which files will be protected.@{PAR}

@ENDNODE
@NODE 1.6.Icon_Info "DOWT/Intro to DOpus/Custom Buttons"
@{LINDENT 1}

@{b}Icon Info@{ub}@{PAR}

The @{" Icon Info " link IconInfo} Info button brings up the Directory Opus info
Requester for each of the selected files.@{PAR}

@ENDNODE
@NODE 1.6.Add_Icon "DOWT/Intro to DOpus/Custom Buttons"
@{LINDENT 1}

@{b}Add Icon@{ub}@{PAR}

@{" AddIcon " link AddIcon} allows you to add icons to all selected entries in the
active directory window. Directory Opus will automatically sense what
type of file it is and add the appropriate icon (drawer, tool or
project). Default icons are used unless you have specified the name of
your own icons within the @{" configuration " link 3.19.5}.@{PAR}

@ENDNODE
@NODE 1.6.Arc_Ext "DOWT/Intro to DOpus/Custom Buttons"
@{LINDENT 1}

@{b}Arc Ext@{ub}@{PAR}

This button allows you to extract files from an Archive File. Directory
Opus comes configured for ARC, ZOO, LHARC and files. When you click on
this button, the files are extracted from the selected archive files
and copied into the destination window.@{PAR}

Another way to extract archives is using the @{" XAD library system " link reqments}.
Please check @{" chapter 1.11 " link 1.11} for more information.@{PAR}

@{FG Highlight}NOTE:@{FG text}@{PAR}

Directory Opus' distribution disks do not include the actual archive
programs ARC, ZOO and LHA. Because they are Shareware, we are not
allowed to distribute them. They are available free on most bulletin
boards and you should ensure the ones you require are installed in one
of the directories in the command path used by the CLI.@{PAR}

@ENDNODE
@NODE 1.6.Encrypt "DOWT/Intro to DOpus/Custom Buttons"
@{LINDENT 1}

@{b}Encrypt@{ub}@{PAR}

Have you ever had files that you wanted to encrypt so that only people
who knew the password could understand them? This command allows you to
do just that. It will encrypt all selected files, using the password
that you enter, with a complex algorithm that most people will find
impossible to work out. The resulting files are not written over the
originals, but are instead written to the destination directory. They
will be the same size as the original files, so you can ensure you have
enough room in the destination directory.@{PAR}

To decrypt a previously encrypted file, you should enter the same
password preceded by a minus sign. For example, to decrypt files you
encrypted with the password FOO, select the file, choose the encrypt
command and enter -FOO as the password.@{PAR}

@ENDNODE
@NODE 1.6.Read "DOWT/Intro to DOpus/Custom Buttons"
@{LINDENT 1}

@{b}Read@{ub}@{PAR}

The @{" Read " link Read} button allows you to read selected files. The name of the
file is displayed at the bottom of the screen. You can use the sliders 
and cursor keys to move though the file. Buttons along the bottom move
up and down the page, move to the top and bottom, allow you to search
for text, and print the file. Pressing the right mouse button or the Q
key quits the text viewer.@{PAR}

For more information, see the chapter @{" Text Viewer " link 2.7}.@{PAR}

@ENDNODE
@NODE 1.6.ANSI_Read "DOWT/Intro to DOpus/Custom Buttons"
@{LINDENT 1}

@{b}ANSI Read@{ub}@{PAR}

The @{" ANSI Read " link ANSIRead} button brings up the same Reader as @{" Read " link 1.6.Read} except that
it handles the special ANSI control sequences.@{PAR}

@ENDNODE
@NODE 1.6.Hex_Read "DOWT/Intro to DOpus/Custom Buttons"
@{LINDENT 1}

@{b}Hex Read@{ub}@{PAR}

The Hex Read button will read the selected files in the same way as
@{" READ " link 1.6.Read}, except in hexadecimal format. This allows you to view binary
files and other files containing non-text characters.@{PAR}

@ENDNODE
@NODE 1.6.Show "DOWT/Intro to DOpus/Custom Buttons"
@{LINDENT 1}

@{b}Show@{ub}@{PAR}

The @{" Show " link Show} button is very versatile indeed. It will display IFF
ILBM pictures and brushes, animations, Workbench icons and fonts.@{PAR}

If the file is an IFF ILBM, it will be displayed using information from
the file. Directory Opus will show most pictures and brushes, including
overscan, extra halfbrite (EHB), HAM (4096 colour) pictures, Dynamic
HiRes pictures created by MacroPaint (from Lake Forest Logic), and AGA
8 bit pictures.@{PAR}

The following keys can be used when viewing a picture or animation:@{PAR}
@{LINDENT 4}


Tab               - Cycle Colours@{PAR}

Cursor Keys       - Scroll@{PAR}

Mouse Pointer     - Scroll@{PAR}

Shift Cursor Keys - Scroll by Page@{PAR}

Ctrl Cursor Keys  - Scroll to End@{PAR}

.                 - Mouse pointer On/Off@{PAR}

[                 - display in 4 bit format@{PAR}

]                 - display in 8 bit format@{PAR}

Esc or RMB        - Abort@{PAR}

Q or LMB          - Next@{PAR}

Space, Help or P  - Help and Print Requester@{PAR}
@{LINDENT 1}


These keys can be used when viewing an Animation:@{PAR}
@{LINDENT 4}


S        - Starts and Stops@{PAR}

N        - Next Frame@{PAR}

-        - Slow Down@{PAR}

=        - Speed Up@{PAR}

\        - Original Speed@{PAR}

F1 - F10 - Various Speeds (F1=Fastest)@{PAR}
@{LINDENT 1}


The show routine will also display icons. If a file has a .info suffix
is assumed to be an icon. If the icon has an alternative image, you can
press return to toggle between the two.@{PAR}

To display a font, you need to enter the actual font drawer, and select
the Size file (that is, the file 8, 12, 19, etc.), NOT the .font file.@{PAR}

@ENDNODE
@NODE 1.6.Play "DOWT/Intro to DOpus/Custom Buttons"
@{LINDENT 1}

@{b}Play@{ub}@{PAR}

The @{" Play " link Play} button plays the selected files as sound files. If the file
is an 8SVX format IFF sampled sound (of the type generated by
AudioMaster, for instance), the speed and other information from within
the file will be used. This button will play any file, though, and if
the file is not 8SVX, it will assume a speed of 10000 samples/second.@{PAR}

Using the inovamusic.library, the Play button also plays Star/Sound/
Noise/ProTracker, Med, OctaMed, Octalizer, and Med with MIDI modules.@{PAR}

Each file is played once only. To abort a sound while it is playing,
press the left and right mouse buttons together.@{PAR}

@ENDNODE
@NODE 1.6.Loop_Play "DOWT/Intro to DOpus/Custom Buttons"
@{LINDENT 1}

@{b}Loop Play@{ub}@{PAR}

If you select this button with the right mouse button, the sounds are
played continuously (looped). To advance to the next sound, you must
press the left mouse button. See @{" Play " link 1.6.Play} for more information.@{PAR}

@ENDNODE
@NODE 1.6.Edit "DOWT/Intro to DOpus/Custom Buttons"
@{LINDENT 1}

@{b}Edit@{ub}@{PAR}

The Edit button allows you to edit any selected files, using the text
editor (or word processor) specified in the @{" configuration " link 3.4}.@{PAR}

By default, it is configured to use Commodore's c:ED program. You will
probably want to alter this configuration to use an editor of your own
choosing.@{PAR}

@ENDNODE
@NODE 1.6.New_File "DOWT/Intro to DOpus/Custom Buttons"
@{LINDENT 1}

@{b}New File@{ub}@{PAR}

The New File lets you create a new file with the text editor specified in the
@{" configuration " link 3.4}.@{PAR}

If you select this button with the right mouse button, you will be
asked for a filename to create a new file.@{PAR}

@ENDNODE
@NODE 1.7 "DOWT/The Tiny Buttons"
@{LINDENT 1}

@{b}1.7 - The Tiny Buttons@{ub}@{PAR}

The Directory Opus screen has several buttons that are not
configurable; they activate the most necessary and useful commands and
are included so that these commands are always available, whatever your
configurations may be. If you had mistakenly configured Directory Opus
so that no button or menu called the configuration program, you would
never be able to run the configuration program to change this!@{PAR}

These buttons are called the Tiny Buttons, as they are much smaller
than the configurable buttons on the screen. Four of them are arranged
in the square approximately at the center of the screen, six others are
found in the bottom right-hand corner of the screen. They all have one-
character titles.@{PAR}
@{LINDENT 4}

@{" B " link 1.7.B} Buffer List@{PAR}
@{" R " link 1.7.R} Reselect@{PAR}
@{" S " link 1.7.S} Select@{PAR}
@{" A " link 1.7.A} ARexx@{PAR}

@ENDNODE
@NODE 1.7.B "DOWT/The Tiny Buttons"
@{LINDENT 1}

@{b}B - Buffer list@{ub}@{PAR}

This activate the buffer list command. This command displays a list of
all the directories contained in Directory Opus' internal buffers. You
may then double-click on one of the displayed buffers so as to jump to
that buffer immediately, rather than clicking the arrow to cycle
through the buffers one by one.@{PAR}

Pressing the right mouse button over the Buffer List button will
activate the @{" Clear Buffers " link ClearBuffers} command which clears from memory the
contents of all buffer except the two that are currently displayed.@{PAR}

@ENDNODE
@NODE 1.7.R "DOWT/The Tiny Buttons"
@{LINDENT 1}

@{b}R - Reselect@{ub}@{PAR}

This activates the reselect command. This command will reselect all
entries that were selected before the last operation was initiated.
The entries are reselected only if they still exist, and regardless of
whether the buffer containing them is currently displayed.@{PAR}

Pressing the right mouse button over the R - Reselect button performs
the @{" Rescan " link Rescan} command on the active directory window.@{PAR}

@ENDNODE
@NODE 1.7.S "DOWT/The Tiny Buttons"
@{LINDENT 1}

@{b}S - Select@{ub}@{PAR}

This button activates the @{" select " link Select} command. This allows you to select
files and directories in the active directory window using wildcards.
All standard wildcards are supported (*,? etc..) as well as the
AmigaDOS wildcards ? and #?.@{PAR}

Pressing the right mouse button over the File Select Requester Button
will activate the @{" Get Devices " link GetDevices} command. This command produces a list
of all devices, volumes and logically @{" assigned " link 1.6.Assign} directories that
exist in the system.@{PAR}

@ENDNODE
@NODE 1.7.A "DOWT/The Tiny Buttons"
@{LINDENT 1}

@{b}A - ARexx@{ub}@{PAR}

This activate the ARexx command, which allows you to launch an ARexx
script or execute an ARexx command from within Directory Opus.@{PAR}

Pressing the right mouse button over this button will activate the
@{" dirtree " link DirTree} command (the Directory Tree command). This command scans
all sub-directories in the currently displayed directory, and produces
a tree structure.@{PAR}

@ENDNODE
@NODE 1.8 "DOWT/The Tiny Bottom Right Buttons"
@{LINDENT 1}

@{b}1.8 - The Tiny Bottom Right Buttons@{ub}@{PAR}

These buttons are optional; if you don't want them you can make them
disappear by deselecting the Bottom-Right Tiny buttons flag at the
Config/Screen/General configuration screen.@{PAR}
@{LINDENT 4}

@{" ? " link 1.8.?} Help@{PAR}
@{" E " link 1.8.E} Errror Help@{PAR}
@{" F " link 1.8.F} Sub-Directory Filter@{PAR}
@{" C " link 1.8.C} Configure@{PAR}
@{" I " link 1.8.I} Inconify@{PAR}
@{" Q " link 1.8.Q} Quit@{PAR}

@ENDNODE
@NODE 1.8.? "DOWT/The Tiny Bottom Right Buttons"
@{LINDENT 1}

@{b}? - Help@{ub}@{PAR}

This button activates the @{" help " link Help_a} command. Provided a help files has
been loaded, selecting any button or menu after enabling the help mode
should result in the appearance of some helpful text.@{PAR}

@{FG Highlight}NOTE:@{FG text}@{PAR}

The highlighted question mark indicates the help mode is active.@{PAR}

@ENDNODE
@NODE 1.8.E "DOWT/The Tiny Bottom Right Buttons"
@{LINDENT 1}

@{b}E - Errror Help@{ub}@{PAR}

This activates the @{" ErrorHelp " link ErrorHelp} command, which gives you more
information about DOS error codes than is generally available.@{PAR}

@ENDNODE
@NODE 1.8.F "DOWT/The Tiny Bottom Right Buttons"
@{LINDENT 1}

@{b}F - Sub-Directory Filter@{ub}

This button activate the sub-directory Filter. When you click on this
button, a requester will ask you to enter a file filter. The filter can
contain a file specification containing @{" wildcard " link WldCrdPat} characters. When
you click Okay or press return, the requester will disappear and the F
button will be highlighted. This indicates the filter is activated.@{PAR}

When the filter is activated, any command which processes the files in
selected sub-directories will only act on files which match the filter
pattern. These commands are:@{PAR}
@{LINDENT 4}

@{" Copy   " link 1.6.Copy}          @{" Search    " link 1.6.Search}@{PAR}
@{" CopyAs " link 1.6.CopyAs}          @{" Protect   " link 1.6.Protect}@{PAR}
@{" Move   " link 1.6.Move}          @{" DateStamp " link 1.6.DateStamp}@{PAR}
@{" MoveAs " link 1.6.MoveAs}          @{" Comment   " link 1.6.Comment}@{PAR}
@{" Hunt   " link 1.6.Hunt}@{PAR}
@{LINDENT 1}

If the F button is highlighted, you can turn off the filter by clicking@{PAR}
on it again. It will become un-highlighted.@{PAR}

@ENDNODE
@NODE 1.8.C "DOWT/The Tiny Bottom Right Buttons"
@{LINDENT 1}

@{b}C - Configure@{ub}@{PAR}

This activates the configure command, and will either load into memory
or invoke the @{" configuration " link Config} program.@{PAR}

@ENDNODE
@NODE 1.8.I "DOWT/The Tiny Bottom Right Buttons"
@{LINDENT 1}

@{b}I - Inconify@{ub}@{PAR}

This button activate the @{" iconify " link Iconify} command. It closes the Directory
Opus screen, de-allocates as much memory as possible, and them opens a
small window on the Workbench screen.@{PAR}

This allows you to have Directory Opus constantly available, while
using the minimum amount of memory possible.@{PAR}

For more information, see @{" Iconify " link 1.9.1.Iconify}.@{PAR}

@ENDNODE
@NODE 1.8.Q "DOWT/The Tiny Bottom Right Buttons"
@{LINDENT 1}

@{b}Q - Quit@{ub}@{PAR}

This activates the quit command, which allows you to exit Directory
Opus (providing there is not a print operation under way). If the
configuration has been modified and not saved, you are asked if you
wish to save it first.@{PAR}

@ENDNODE
@NODE 1.9 "DOWT/Default Menus"
@{LINDENT 1}

@{b}1.9 - Default Menus@{ub}@{PAR}

This section gives a brief description of the Default Menus. All the
menus can be changed, but they are configured initially for certain
command.@{PAR}
@{LINDENT 4}


Project Menu                 Function Menu@{PAR}

@{" Current Dir      " link 1.9.1.Current_Dir}           @{" Disk Copy " link 1.9.2.Disk_Copy}@{PAR}
@{" Help             " link 1.9.1.Help}           @{" Format    " link 1.9.2.Format}@{PAR}
@{" Error Help       " link 1.9.1.Error_Help}           @{" Install   " link 1.9.2.Install}@{PAR}
@{" Configure        " link 1.9.1.Configure}           @{" Relabel   " link 1.9.2.Relabel}@{PAR}
@{" About            " link 1.9.1.About}           @{" Print Dir " link 1.9.2.Print_Dir}@{PAR}
@{" Version          " link 1.9.1.Version}           @{" Disk info " link 1.9.2.Disk_Info}@{PAR}
@{" Iconify          " link 1.9.1.Iconify}           @{" LHA Add   " link 1.9.2.LHA_Add}@{PAR}
@{" Button Iconify   " link 1.9.1.Button_Iconified}           @{" Arc Add   " link 1.9.2.LHA_Add}@{PAR}
@{" Quit             " link 1.9.1.Quit}           @{" Zoo Add   " link 1.9.2.LHA_Add}@{PAR}
@{LINDENT 1}


Directory Opus has 100 user-definable menus. The @{" Commands " link Commands} chapter
explains more about the menus, and the @{" Command Editor " link 3.6} section
explains how to configure them.@{PAR}

@ENDNODE
@NODE 1.9.1.Current_Dir "DOWT/Default Menus/Project Menu"
@{LINDENT 1}

@{b}Project/Current dir@{ub}@{PAR}

This command allows you to set the current working directory for
Directory Opus. The current directory is the directory loaded when you
activate either directory field, delete the existing pathname (if there
is one), and press return on a blank string.@{PAR}

A requester will appear containing the pathname of the active directory
window. If this is acceptable as the new current directory, press
return. Otherwise, edit it to read as you wish.@{PAR}

@ENDNODE
@NODE 1.9.1.Help "DOWT/Default Menus/Project Menu"
@{LINDENT 1}

@{b}Project/Help!@{ub}@{PAR}

Providing a help file has been loaded in, selecting any button/menu
after enabling help mode with this menu should result in the appearance
of some helpful text.@{PAR}

Help can be read from any file, the default is S:DirectoryOpus.HLP. The
file name can be changed with the @{" Helpfile configuration " link Modify} option.@{PAR}

@ENDNODE
@NODE 1.9.1.Error_Help "DOWT/Default Menus/Project Menu"
@{LINDENT 1}

@{b}Project/Error Help@{ub}@{PAR}

Error help gives you information about DOS error codes. When you select
this option, you are asked for which DOS error code number you want
help. Examples of DOS error codes are 123, 205 and 225. You are then
presented with a description of that error, and information pertaining
to the possible cause and cure of the error.@{PAR}

Error help is also stored in the help file; if the help file has not
been loaded, error help will not be available. See the @{" help " link 1.8.?} section
for more information.@{PAR}

@ENDNODE
@NODE 1.9.1.Configure "DOWT/Default Menus/Project Menu"
@{LINDENT 1}

@{b}Project/Configure@{ub}@{PAR}

Directory Opus uses a separate program to modify the configuration.
This saves about 127K of memory, as the configuration program need only
be in memory when it is being used.@{PAR}

If you do have plenty of memory, Directory Opus can be configured to
load the configuration program on start-up. In this case, it is run
from memory each time the configure command is invoked, rather than
loaded from the disk. This can be much faster, especially if you have
a floppy-based system.@{PAR}

See @{" ConfigOpus " link Config} section for more detailed information.@{PAR}

@ENDNODE
@NODE 1.9.1.About "DOWT/Default Menus/Project Menu"
@{LINDENT 1}

@{b}Project/About@{ub}@{PAR}

This command displays some information about the program. @{PAR}

@ENDNODE
@NODE 1.9.1.Version "DOWT/Default Menus/Project Menu"
@{LINDENT 1}

@{b}Project/Version@{ub}@{PAR}

This menu displays the current version of Kickstart, Workbench and
Directory Opus. This information will be necessary when getting
Technical Support.@{PAR}

@ENDNODE
@NODE 1.9.1.Iconify "DOWT/Default Menus/Project Menu"
@{LINDENT 1}

@{b}Project/Iconify@{ub}@{PAR}

This command closes the Directory Opus window and screen, deallocates
as much memory as possible, and then opens a small window on the
Workbench screen. This is known as iconifying, and allows you to have
Directory Opus constantly available, while using the least amount of
memory.@{PAR}

The iconified window may contain a clock, or may not be visible at all,
depending on how you have set the Iconified type @{" configuration " link 3.19.2} option.@{PAR}

To determine the initial position of the iconified window (especially
if you plan to start up Directory Opus in the iconified state), you
should iconify Directory Opus, and position the window as you would
like it to appear. That done, re-enter Directory Opus, and save the
@{" configuration " link 3.3 30}.@{PAR}

When iconified, you can drop Workbench Icons on the Directory Opus
window. This will have the same effect as if you displayed the file in
a Directory Opus window and double-click on it. For Example, if you
drop a picture on the window, it will show it.@{PAR}

To re-enter Directory Opus, click the left mouse button in the
iconified window, then press the right mouse button. If you wish to
quit Directory Opus without going back into it, click the close button
at the top left of the iconified window.@{PAR}

Note that if you have the configuration option Iconify Type set to
Hidden, the only way to re-enter Directory Opus is with the hotkeys.
These default to CTRL-SHIFT-ALT (the CTRL key, the left SHIFT key and
the left ALT key simultaneously), although this may be changed in the
@{" configuration " link 3.19.4}.@{PAR}

@ENDNODE
@NODE 1.9.1.Button_Iconified "DOWT/Default Menus/Project Menu"
@{LINDENT 1}

@{b}Project/Button Iconify@{ub}@{PAR}

This causes a special variation for Directory Opus iconification.
Normally iconification is set up by the ConfigOpus/System/Clocks
screen, but with this command you can iconify Directory Opus into a
bank of buttons on Workbench.@{PAR}

In this mode Directory Opus allows you to do almost all, if not all it
normally does. For instance, if you select the Copy button a requester
will open asking you to select something to copy followed by another asking
where to copy it. You can also use the bank of buttons as an AppWindow:
To show a picture, you would simply @{" drag'n drop " link 1.10} the icon of
the picture onto the show button.@{PAR}

The slider to the right of the button bank allows you choose which
button bank is shown.@{PAR}

To uniconify back to Directory Opus, press the Uniconify button above
the slider to the right of the bank, or select the Close button of the
window. The close button will ask you if you wish to quit Directory
Opus or to uniconify it.@{PAR}

@ENDNODE
@NODE 1.9.1.Quit "DOWT/Default Menus/Project Menu"
@{LINDENT 1}

@{b}Project/Quit@{ub}@{PAR}

This command will exit Directory Opus (providing there is not a print
operation happening at the time). If the configuration has been
modified and not saved, you are asked if you want to save it first.@{PAR}

@ENDNODE
@NODE 1.9.2.Disk_Copy "DOWT/Default Menus/Function Menu"
@{LINDENT 1}

@{b}Function/Disk Copy@{ub}@{PAR}

This command brings up a requester which allows you to make an exact
copy of one disk on another. For more information, see the @{" DiskCopy " link 2.2} Requester
or the @{" DiskCopy " link DiskCopy} command.@{PAR}

@ENDNODE
@NODE 1.9.2.Format "DOWT/Default Menus/Function Menu"
@{LINDENT 1}

@{b}Function/Format@{ub}@{PAR}

This allows you to @{" format " link Format} a new disk. All new disks
need to be formatted before the computer can write files to them.@{PAR}

For more information, see the @{" Format " link 2.3} Requester.@{PAR}

@ENDNODE
@NODE 1.9.2.Install "DOWT/Default Menus/Function Menu"
@{LINDENT 1}

@{b}Function/Install@{ub}@{PAR}

This command brings up a requester that allows you to make a disk
bootable. To be bootable, disks must have special information written
in their first sector. For more information, see the @{" Install " link 2.4} Requester.@{PAR}

@ENDNODE
@NODE 1.9.2.Relabel "DOWT/Default Menus/Function Menu"
@{LINDENT 1}

@{b}Function/Relabel@{ub}@{PAR}

This command allows you to change the name (label) of the disk that is
open in the active directory window.@{PAR}

@ENDNODE
@NODE 1.9.2.Print_Dir "DOWT/Default Menus/Function Menu"
@{LINDENT 1}

@{b}Function/Print Dir@{ub}@{PAR}

This command allows you to print the directory in the active directory
window. You are able to choose the information you want to print (file
sizes, protection bits, dates and comments).@{PAR}

This command is not started as a separate process, unlike the @{" print " link 1.6.print} command.
For more information, see the @{" Print Dir " link 2.5} Requester.@{PAR}

@ENDNODE
@NODE 1.9.2.Disk_Info "DOWT/Default Menus/Function Menu"
@{LINDENT 1}

@{b}Function/Disk info@{ub}@{PAR}

This command displays some information about the disk the active
directory resides on, including space used, space free, datestamp and
number of errors on the disk.@{PAR}

@ENDNODE
@NODE 1.9.2.LHA_Add "DOWT/Default Menus/Function Menu"
@{LINDENT 1}

@{b}Function/LHA Add, Arc Add, Zoo Add@{ub}@{PAR}

These commands allows you to create and add files to archives, using
the popular archives ARC, ZOO and LHA or LHARC (and up to three others;
see the @{" Comands " link Commands} section for more information).@{PAR}

To add files to an archive, select the files you wish to add, and
select this command. You will be asked for the name of the archive to
create or add to. You should have the destination directory open in
the inactive window.@{PAR}

@ENDNODE
@NODE 1.10 "DOWT/Drag'n Drop"
@{LINDENT 1}

@{b}1.10 - Drag'n Drop@{ub}@{PAR}

DirOpus supports @{" Drag'n Drop " link glos}. You may drag Workbench icons and drop them over one of
DirOpus' directory windows, over its button banks or over its AppIcon.@{PAR}

@{fg highlight}Drag'n Drop when DirOpus is opening its window on Workbench's screen@{fg text}@{PAR}

You can @{" configure " link 3.18.6} DirOpus to open its window on Workbench screen,
instead of its own screen. This will give you the possibility to drop Workbench icons over
various parts of DirOpus' window:@{PAR}
@{LINDENT 4}

@{i}Droping a volume or drawer icon over one of the directory windows @{ui}@{PAR}

This will activate the directory window and read the appropriate drawer or volume into the directory window.@{PAR}

@{i}Droping a file's icon over one of the directory windows @{ui}@{PAR}

This will copy the file to the directory currently listed in the appropriate directory window.@{PAR}

@{i}Droping a file's icon over one of the custom buttons @{ui}@{PAR}

This will invoke the current button with the droped file as an argument. I.e., you
could drop a picture's icon over the "Show" button to view it, or a textfile's icon over
the "Edit" button to edit it. Droping a file's icon over the "Hunt" button would not make
much sense though..@{PAR}
@{LINDENT 1}

@{fg highlight}Drag'n Drop when DirOpus is iconified to an AppIcon@{fg text}@{PAR}

You can @{" configure " link 3.19.2} DirOpus to display an AppIcon on the Workbench
screen when it is in iconified state. You can drag'n drop files to that AppIcon and
they will be treated as if they were doubleclicked in a directory window (i.e. a picture
will be shown or a sample will get played).@{PAR}

@{fg highlight}Drag'n Drop when DirOpus is Buttoniconified@{fg text}@{PAR}

DirOpus can be @{" ButtonIconified " link 1.9.1.Button_Iconified}. In this case it will display its button
banks on the Workbench screen as long as it is in iconified state. You can drag'n drop files
to those button banks. Results will be the same as if DirOpus would be running on Workbench
screen (see above).@{PAR}

@{fg highlight}Drag'n Drop in ConfigOpus@{fg text}@{PAR}

Whenever @{" ConfigOpus " link config} (the Directory Opus configuration utility) opens a
@{" Command Editor " link 3.6} window, you can drag'n drop Workbench icons over that window and
ConfigOpus will add a @{" Workbench command entry " link 3.6.1.Command_type.Workbench}.@{PAR}

In some rare cases (i.e. if ConfigOpus is unable to allocate enough free pens on the Workbench
screen) the configuration window will be opened on a new screen. ConfigOpus will then put
an AppIcon on the Workbench screen as soon as you enter the Command Editor. This AppIcon looks
like a normal icon, but it does not do anything when you double-click on it. However, if you
drop an icon over it, ConfigOpus will add a @{" Workbench command entry " link 3.6.1.Command_type.Workbench}.@{PAR}

@ENDNODE
@NODE 1.11 "DOWT/Handling archives"
@{LINDENT 1}

@{b}1.11 - Handling archives with Directory Opus@{ub}@{PAR}

A file (or disk) archive is a group of files concatenated to one single file, usually crunched
afterwards to reduce filesize. Archives are very handy for transfering files through
networks or bulletin board systems. Most files you will come across these days are distributed
in archive format. Most common archive formats are "LhA", "LZX", "ZIP" and "GZIP"
(to name but a few).@{PAR}

To deal with file archives (i.e. examine their contents, extract them (or parts of them)), you
would normally have to use a seperate dearchiving tool for each archive type you come across,
learn its commandline syntax or configure your software to make use of it. Additionally, if
you just need one single file from an archive (or just want to have a quick look at the
archive's contents) you would always have to extract the whole archive.@{PAR}

But if you've got the @{" XAD library system " link reqments} installed, Directory Opus is able
to handle more than 60 archive formats internally. You can browse through archives as if it were
normal directories! You can enter subdirectories within an archive, extract one or more files
(simply by selecting them and hitting the "Copy" button) or access files (i.e. load them into
the text reader) without extracting them!@{PAR}
@{LINDENT 4}


@{" Preparing Dopus for handling archives " link 1.11.prepare}@{PAR}
@{" Browsing Archives like directories    " link 1.11.browse}@{PAR}
@{" Extracting Archives                   " link 1.11.extract}@{PAR}
@{" Additional possibilities              " link 1.11.add}@{PAR}
@{LINDENT 1}


@{fg highlight}Note:@{fg text}@{PAR}

The implementation of XAD library support is not finished yet. Read the chapters above to
see what works already and what is not implemented yet. More features will be added in
future versions.@{PAR}

@{fg highlight}Note:@{fg text}@{PAR}

"Disk" archives (i.e. "DMS" or "ADF" archives) are not supported at all at the moment. You
still have to use external tools to deal with them.@{PAR}

@ENDNODE
@NODE 1.11.prepare "DOWT/Archives/Preparing DOpus"
@{LINDENT 1}

@{b}How to prepare DOpus for handling Archives@{ub}@{PAR}

Install the @{" XAD library system " link reqments}. Make sure you have the @{" FORCEOPENXAD " link 1.3.1} tooltype
set. Start Directory Opus by doubleclicking its icon on the Workbench screen
(or use the @{" -X " link 1.3.2} commandline switch if you're starting DOpus from the CLI).@{PAR}

Now you have to modify your existing filetypes. Go to the Configuration program, enter the
@{" filetype " link 3.9.1} section and delete the "double-click action" of all your archive
filetypes. If this action is undefined, DOpus will start @{" browsing an archive " link 1.11.browse} if you
doubleclick it.@{PAR}

@ENDNODE
@NODE 1.11.browse "DOWT/Archives/Browsing Archives"
@{LINDENT 1}

@{b}Browsing archives@{ub}@{PAR}

Make sure you have followed every step in the @{" how to prepare DOpus.. " link 1.11.prepare} chapter
before continuing!@{PAR}

To "enter" an archive, simply double-click it.@{PAR}

Now you're "inside" the archive. You can enter sub-directories by double-clicking them. You can
select or deselect files and directories as usual.@{PAR}

Additionally, you can use the following buttons:@{PAR}
@{LINDENT 4}


@{i}Parent @{ui}@{PAR}

This will display the parent directory. If the archive's root directory is displayed
when clicking the "Parent" button, you'll leave the archive (the directory containing
the archive will be displayed again).@{PAR}

@{i}Root @{ui}@{PAR}

This will display the archive's "root" directory. Clicking the "Root" button while the
archive's root directory is displayed already will leave the archive.@{PAR}

@{i}Copy, CopyAs @{ui}@{PAR}

These buttons will extract the selected files from the archive.@{PAR}

NOTE: You can't ADD files to an archive using these buttons. The XAD library system
does not support modifying archives (The Move(As) command does not work for the same
reason). You'll still need to use external tools for creating archives, or adding files
to archives.@{PAR}

@{i}Getsizes, Hunt @{ui}@{PAR}

These buttons will work the same way as with normal directories. In other words: you can
"Hunt" files inside an archive or even calculate directory sizes without extracting it!@{PAR}

@{i}Show, Read, HexRead, AnsiRead, IconInfo @{ui}@{PAR}

Use these buttons to display files in DOpus internal viewers.@{PAR}
@{LINDENT 1}


@{fg highlight}Note:@{fg text}@{PAR}

The implementation of XAD library support is not finished yet. Doubleclicking files will
not work at the moment, and all Buttons not mentioned here won't have any effect at the
moment or will bring up an error message.@{PAR}

@ENDNODE

@NODE 1.11.extract
@{LINDENT 1}

@{b}Extracting archives@{ub}@{PAR}

Not implemented yet. You still have to use external tools for that purpose. Note that you
can extract parts of an archive already, see @{" browsing archives " link 1.11.browse}.@{PAR}

@ENDNODE
@NODE 1.11.add
@{LINDENT 1}

@{b}Additional possibilities@{ub}@{PAR}

Not implemented yet. Future versions may enable you to delete all your archive filetypes (as
DOpus will be able to handle everything internally) or at least use only one Archive filetype
for all kinds of archives.@{PAR}

@ENDNODE
@NODE Req&View "Req&View"
@{LINDENT 1}

@{b}Chapter 2 - Requesters & Viewers@{ub}@{PAR}

This chapter presents the more complicated requesters and viewers. Each
of these is associated with Directory Opus Commands which are activated
by Custom Buttons and Menus.@{PAR}
@{LINDENT 4}

@{" Protection Requester " link 2.1}@{PAR}
@{" Disk Copy Requester  " link 2.2}@{PAR}
@{" Format Requester     " link 2.3}@{PAR}
@{" Install Requester    " link 2.4}@{PAR}
@{" Print Dir Requester  " link 2.5}@{PAR}
@{" Print Requester      " link 2.6}@{PAR}
@{" Text Viewer          " link 2.7}@{PAR}
@{" Hex Viewer           " link 2.8}@{PAR}

@ENDNODE
@NODE 2.1 "Req&View/Protection Requester"
@{LINDENT 1}

@{b}2.1 Protection Requester@{ub}@{PAR}

The Protection Requester allows you to change a file's or sub-
directory's protection bits.@{PAR}

The protection bits are a group of flags that are stored with the file,
that determine the characteristics of the file. These flags are given
one character names. The protection bits currently in use are:@{PAR}
@{LINDENT 4}

@{" H " link 2.1.bits} Hidden@{PAR}
@{" S " link 2.1.bits} Script@{PAR}
@{" P " link 2.1.bits} Pure@{PAR}
@{" A " link 2.1.bits} Archived@{PAR}
@{" R " link 2.1.bits} Readable@{PAR}
@{" W " link 2.1.bits} Writeable@{PAR}
@{" E " link 2.1.bits} Executable@{PAR}
@{" D " link 2.1.bits} Deleteable@{PAR}
@{LINDENT 1}

While AmigaDOS and other programs do not fully support all of these
bits, DirectoryOpus gives you access to all documented protection bits.
As AmigaDOS is enhanced, some bits, such as Writeable, will become more
useful. If you have additional questions about the usage of the bits,
refer to your Amiga Documentation.@{PAR}

There is a button for each protection bit along the left edge of the
requester. Clicking on each of these will toggle a checkmark on and
off within the button. When the checkmark is on, it means that the bit
will be set when you click the Okay button.@{PAR}

In the middle of the requester are four buttons which manipulate
multiple protection bits at a time. These buttons do not cause any
action to take place within the selected files, they simply change the
state of the protection bit buttons.@{PAR}
@{LINDENT 4}

@{" All bits " link 2.1.buttons}@{PAR}
@{" None     " link 2.1.buttons}@{PAR}
@{" Toggle   " link 2.1.buttons}@{PAR}
@{" Revert   " link 2.1.buttons}@{PAR}
@{LINDENT 1}

On the right side of the requester are three groups of protection bits:
@{" Old " link 2.1.buttons}, @{" New " link 2.1.buttons}, and @{" Mask " link 2.1.buttons}. Each group contains a protection bit
letter or a '-' (dash) for each bit. The letter indicates that the
associated protection bit is set, a dash indicates that it is clear.@{PAR}

Along the bottom of the requester are three buttons:@{PAR}
@{LINDENT 4}

@{i}Okay @{ui}@{PAR}

Causes the current file (shown in the screen title bar) to be set
set as indicated in the protection bit buttons (and possibly
filtered according to the Mask Group).@{PAR}

@{i}All @{ui}@{PAR}

Causes all selected files to be set, without additional prompting,
as indicated in the protection bit buttons (and possibly filtered
according to the @{" Mask " link 2.1.buttons} Group).@{PAR}

@{i}Cancel @{ui}@{PAR}

Aborts the Protection command.@{PAR}

@ENDNODE
@NODE 2.1.BITS "Req&View/Protection Requester"
@{LINDENT 1}

@{i}H - Hidden @{ui}@{PAR}

If this flag is set, the file is not normally displayed. This
allows you to mark certain files as "invisible", to avoid
cluttering your directories. The file can still be accessed
normally, and not all programs implement this flag.@{PAR}

@{i}S - Script @{ui}@{PAR}

A script file is a file containing a list of AmigaDOS commands
to execute; it is like a simple computer program. This flag
indicates that the file in question is a script file. A script
file is sometimes called a batch file.@{PAR}

@{i}P - Pure @{ui}@{PAR}

If a program file is flagged as pure, it can be made to remain in
memory, even when not in use, This can save a great deal of time,
especially if the program is used a lot, as it does not have to
be loaded from disk each time.@{PAR}

@{i}A - Archive @{ui}@{PAR}

This flag indicted that the file has not been changed. If this
file is ever written to, the A flag will be turned off. This can
be used in a hard disk backup program, to record which files have
been backed-up, and need not be backed-up again.@{PAR}

@{i}R - Readable @{ui}@{PAR}

If this flag is set, the file can be accessed.@{PAR}

@{i}W - Writeable @{ui}@{PAR}

If this flag is set, the file can be written to (ie, more
information can be stored in it than is already there).@{PAR}

@{i}E - Executable @{ui}@{PAR}

If a program file does not have this flag set, it can not be run.@{PAR}

@{i}D - Deleteable @{ui}@{PAR}

If this flag is not set, the file can not be deleted.@{PAR}

@ENDNODE
@NODE 2.1.BUTTONS "Req&View/Protection Requester"
@{LINDENT 1}

@{i}All bits @{ui}@{PAR}

Sets all protection bit buttons.@{PAR}

@{i}None @{ui}@{PAR}

Causes all protection bit buttons to be cleared.@{PAR}

@{i}Toggle @{ui}@{PAR}

Sets all clear protection bit buttons, and clears all set
protection bit buttons.@{PAR}

@{i}Revert @{ui}@{PAR}

Restores the protection bit buttons to the settings they had when
you entered this requester.@{PAR}

@{i}Old @{ui}@{PAR}

The Old group indicates the original bits when you entered the
requester.@{PAR}

@{i}New @{ui}@{PAR}

The New indicates the current status of the protection bit
buttons. Whenever you click the protection bit button, it will
be reflected in the New group.@{PAR}

@{i}Mask @{ui}@{PAR}

Unlike the previously described Old and New groups, the Mask group
bits can be changed by clicking on the associated letter or dash.
The Mask group allows you to specify protection bits which should
not be modified, regardless of the protection bit buttons. 
When the Letter is shown, the bit will not be modified. The dash
means that you need to set the bit according to the setting of
the protection bit button. This is most useful when changing
files within a sub-directory or using the All button. For
example: you want to set the Archive bit in all files contained
in a sub-directory, but you don't want to affect any of the other
protection bits. Set the Archive Protection button on the left
side of the requester and set all the Archive bits in the Mask
group except A. This will preserve all the file's bits with the
exception of the Archive bit, which will be set.@{PAR}

There are keyboard shortcuts available to (un)set bits in the "Mask" group: Just
press "Shift" and the first letter of the bits' name (i.e. "Shift+A").@{PAR}

@ENDNODE
@NODE 2.2 "Req&View/Disk Copy Requester"
@{LINDENT 1}

@{b}2.2 Disk Copy Requester@{ub}@{PAR}

This command allows you to make an exact copy of one disk on another.
When this command is invoked, a requester with several buttons appears.@{PAR}
@{LINDENT 4}

@{i}FROM @{ui}@{PAR}

This list contains the possible disk drives that may be used as
the source. When you click on one, it becomes the selected drive.@{PAR}

@{i}TO @{ui}@{PAR}

This list contains the possible destination drives which are
compatible with the selected source drive. The source disk
drive is always available as a destination to allow you to make
single drive copies. This only makes sense with removable media
such as floppy drives as it would accomplish nothing to copy a
hard drive to itself.@{PAR}

@{i}Verify @{ui}@{PAR}

This button allows you to turn off the integrity verification
when writing data to the destination drive. Although it is faster,
you probably won't want to do this.@{PAR}

@{i}Bump Name @{ui}@{PAR}

This button allows you to change the volume name using the same
naming convention as WorkBench's DiskCopy. (See AmigaDOS
documentation for details.)@{PAR}
@{LINDENT 1}


Disk Copy will not copy any protected software, or non-AmigaDOS format disks.@{PAR}

Selecting the DiskCopy button will start the copy. The Exit button will
abort without attempting a DiskCopy.@{PAR}

@ENDNODE
@NODE 2.3 "Req&View/Format Requester"
@{LINDENT 1}

@{b}2.3 Format Requester@{ub}@{PAR}

This allows you to format a new disk. All new disks need to be
formatted before the computer can write to them.@{PAR}

When this is selected, a requester with several buttons appears. On the
left side is a list containing the devices which can be formatted using
this operation.@{PAR}

Warning! This option will destroy existing data on a disk. Be sure you
want to erase the data before you click Format or Quick Format buttons.@{PAR}

The list on the left side of the requester contains the devices which
you can format. The selected device is highlighted. Be sure the device
you intend to format is the one that is highlighted!@{PAR}
@{LINDENT 4}

@{" Name               " link 2.3.name}@{PAR}
@{" Fast File System   " link 2.3.name}@{PAR}
@{" International Mode " link 2.3.name}@{PAR}
@{" Directory Caching  " link 2.3.name}@{PAR}
@{" Put Trashcan       " link 2.3.name}@{PAR}
@{" Verify             " link 2.3.name}@{PAR}
@{" Format             " link 2.3.name}@{PAR}
@{" Quick Format       " link 2.3.name}@{PAR}
@{LINDENT 1}

The Exit button will abort without attempting a Format.@{PAR}

@ENDNODE
@NODE 2.3.name "Req&View/Format Requester"
@{LINDENT 1}

@{i}Name @{ui}@{PAR}

This field allows you to give the drive to be formatted a volume
name.@{PAR}

@{i}Fast File System @{ui}@{PAR}

This allows you to format a device using the Fast File System
option of AmigaDOS. You should consult AmigaDOS documentation
for more detail.@{PAR}

@{i}International Mode @{ui}@{PAR}

This allows file and directory names to include accented
characters.@{PAR}

@{i}Directory Caching @{ui}@{PAR}

Directory caching mode will decrease the storage space on your
disk but the directory reading speed will be much greater.@{PAR}

NOTE:@{PAR}

Do not use this option when formatting anything else then floppy disks!
It was never meant to be used on hard disks, it is more a nuisance than
a benefit on such devices.@{PAR}

@{i}Put Trashcan @{ui}@{PAR}

This button allows you to put a trashcan in the root directory
of the newly formatted device.@{PAR}

@{i}Verify @{ui}@{PAR}

This button allows you to disable the format verification. As with
@{" Disk Copy " link 2.2}, the process is faster with Verify turned off, but
you won't be made aware of any errors, so it's better to leave
Verify turned on unless you completely trust your disks (you
really shouldn't).@{PAR}

@{i}Format @{ui}@{PAR}

This button begins the formating process. Be very careful you
have selected the correct device. Once a Format begins, it can be
aborted, but data will be lost!@{PAR}

@{i}Quick Format @{ui}@{PAR}

When this button is selected, the disk will just be initialised
(wiped). This provides an extremely fast way to erase an old
disk. This will not work on new disks however, only on disks that
have previously been formatted.@{PAR}

@ENDNODE
@NODE 2.4 "Req&View/Install Requester"
@{LINDENT 1}

@{b}2.4 Install Requester@{ub}@{PAR}

This command allows you to make a disk bootable. To be bootable, disks
must have special information written on their first sector.@{PAR}

The list on the left side of the requester contains the possible
devices on which you can install a boot sector. Select the device you
want to install on.@{PAR}

When you select a device (or insert a new disk in the device) Directory
Opus will examine the boot sector and inform you of the disk's current
status. It does this automatically when you first bring up the Install
Requester. It will tell you one of the following:@{PAR}
@{LINDENT 4}

@{" No Disk Present            " link 2.4.no}@{PAR}
@{" Normal 1.3 OFS bootblock   " link 2.4.no}@{PAR}
@{" Normal 2.0+ FFS bootblock  " link 2.4.no}@{PAR}
@{" Non-Standard bootblock     " link 2.4.no}@{PAR}
@{" Disk is not bootable       " link 2.4.no}@{PAR}
@{" Bootblock info unavailable " link 2.4.no}@{PAR}
@{LINDENT 1}

On the right side, you can see a checkbox labeled Fast File System. This allows you
to install a fast file system bootblock@{PAR}

There are three buttons at the bottom of the requester:@{PAR}
@{LINDENT 4}

@{i}Install @{ui}@{PAR}

This button installs the boot sector on the Disk.@{PAR}

@{i}No Boot @{ui}@{PAR}

This button removes the boot sector from the Disk. This will keep
the disk from being bootable. However, you can always re-install
the boot sector by clicking the Install button.@{PAR}

@{i}Exit @{ui}@{PAR}

This button will abort without attempting an Install.@{PAR}

@ENDNODE
@NODE 2.4.no "Req&View/Install Requester"
@{LINDENT 1}

@{i}No Disk Present @{ui}@{PAR}

This simply means that you haven't inserted a disk in the drive
yet. When you do so, it will update this status message.@{PAR}

@{i}Normal 1.3 OFS bootblock @{ui}@{PAR}

This means the disk was installed with the old file system used
before version 2.0 of AmigaDOS.@{PAR}

@{i}Normal 2.0+ FFS bootblock @{ui}@{PAR}

This means that the disk was installed with the new file system
used for 2.0 and later versions of AmigaDOS.@{PAR}

@{i}Non-Standard bootblock @{ui}@{PAR}

This means that the disk is corrupt or is formatted for another
type of system. It may contain a virus and it would be a good
idea to run a virus checker program to make sure.@{PAR}

@{i}Disk is not bootable @{ui}@{PAR}

The disk does not contain a bootblock and is therefore not bootable.@{PAR}

@{i}Bootblock info unavailable @{ui}@{PAR}

This message appears if there is a bootblock in the disk, but the filesystem
is unable to read it properly (i.e. due to a corrupted disk).@{PAR}

@ENDNODE
@NODE 2.5 "Req&View/Print Dir Requester"
@{LINDENT 1}

@{b}2.5 Print Dir Requester@{ub}@{PAR}

This command allows you to print the directory in the active directory
window. If no files are selected, all files listed in the window will
be printed. However, if some files are selected, only those entries
will be printed.@{PAR}

You can select the information you want to print: file sizes,
protection bits, dates, comments, and file types. Directory Opus can
only print the selected information when it is being displayed in the
Directory Window.@{PAR}
@{LINDENT 4}

@{i}Output to... @{ui}@{PAR}

By default, the output will be sent to the printer. However, you
can redirect the output to a file of your choosing.@{PAR}
@{LINDENT 4}

@{i}Printer @{ui}@{PAR}

This option directs output to the printer.@{PAR}

@{i}File @{ui}@{PAR}

When this option is enabled, output is directed to the file
indicated in the accompanying field.@{PAR}

Click on the magnifying glass next to the File field to use a file
requester to find the file name; otherwise type the name directly into
the File field.@{PAR}

@{i}Print @{ui}@{PAR}

When you click this button, Directory Opus will begin printing the
information. It is not started as a separate process, so you
might have to wait while Directory Opus completes printing the
information.@{PAR}

@{i}Exit @{ui}@{PAR}

This button will abort without attempting to print.@{PAR}

@ENDNODE
@NODE 2.6 "Req&View/Print Requester"
@{LINDENT 1}

@{b}2.6 Print Requester@{ub}@{PAR}

This Requester gives you full print formatting control for text files.@{PAR}

@{FG highlight}Note:@{FG text}@{PAR}

Not All printers are created equal. Some printers will ignore
some of these configuration options.@{PAR}

@{FG highlight}Note:@{FG text}@{PAR}

These configuration options work in accordance with the Amiga
Printer Preferences. The Amiga Preferences may override these
preferences or simply make the output look silly. For example, you
cannot use these options to display more lines on a page than is
specified in Amiga Preferences.@{PAR}

There are several configuration items in the print requester:@{PAR}
@{LINDENT 4}

@{" Top margin       " link 2.6.no}@{PAR}
@{" Bottom Margin    " link 2.6.no}@{PAR}
@{" Left margin      " link 2.6.no}@{PAR}
@{" Right Margin     " link 2.6.no}@{PAR}
@{" Tab Size         " link 2.6.no}@{PAR}
@{" Print pitch      " link 2.6.no}@{PAR}
@{" Quality          " link 2.6.no}@{PAR}
@{" Eject Final Page " link 2.6.no}@{PAR}
@{" configuration... " link 2.6.no}@{PAR}
@{" Title            " link 2.6.no}@{PAR}
@{" Date             " link 2.6.no}@{PAR}
@{" Page no.         " link 2.6.no}@{PAR}
@{" Text style       " link 2.6.no}@{PAR}
@{" Output to...     " link 2.6.no}@{PAR}

@{" Print " link 2.6.no}@{PAR}
@{LINDENT 1}

The Exit button will abort without attempting an Install.@{PAR}

This command will print all selected files, one at a time.
If you select only one file to print, the print routine will be
started up as a separate process, allowing you to continue
working with Directory Opus. To cancel this type of print,
simply select the print command again. A requester will appear
asking if you want to continue with the print or halt it. This
requester will also appear if you attempt to quit Directory Opus
while a print operation is in place, as you cannot quit until the
print has finished.@{PAR}

Even if you abort a print, the printer may not actually stop
for some time. This is because most printers have buffers, some
quite large ones, which store data for printing and will need to
empty themselves before the printout will stop.@{PAR}

The Print command automatically decrunches text crunched with various
packing methods. It utilizes the XFDmaster library for that purpose.
Please refer to the @{" Requirements " link reqments} section for
further information).@{PAR}

@ENDNODE
@NODE 2.6.no  "Req&View/Print Requester"
@{LINDENT 1}

@{i}Top margin @{ui}@{PAR}

This field contains the Line Number where text should start.
A Top Margin of 1 starts on the first line and does not have any
blank lines.@{PAR}

@{i}Bottom Margin @{ui}@{PAR}

This field contains the number of printed lines on each page.
The Top Margin Lines are not included in this value. For Example,
a Top Margin of 5, and a Bottom Margin of 60 the last line will
be printed on Line 65.@{PAR}

@{i}Left margin @{ui}@{PAR}

This field contains the number of characters to skip before
printing each line.@{PAR}

@{i}Right Margin @{ui}@{PAR}

This field contains the number of printed characters allowed on
each line. The Left Margin characters are not included in this
value. For example, a Left Margin of 5 and Right Margin of 70
will result in the last printable character in the column 75.@{PAR}

@{i}Tab Size @{ui}@{PAR}

This field contains the Number of spaces to which a tab charcter
is equivalent. Directory Opus converts tabs to spaces and will
insert the appropriate number of spaces to create columns based on
Tab Size. For example, a Tab Size of 8 specifies Tab positions of
8, 16, 32, 40, 48, 56, and 64.@{PAR}

@{i}Print pitch @{ui}@{PAR}

This button cycles between Pica, Elite, and Fine. These values
specify the size of letters to print. Your printer will determine
the exact dimensions of these values.@{PAR}

@{i}Quality @{ui}@{PAR}

This button cycles between Letter, and Draft. Some printers can
be toggled between letter and Draft quality printing.@{PAR}

@{i}Eject Final Page @{ui}@{PAR}

A check in this button enables a final Form Feed character after
printing the last page.@{PAR}

@{i}Configuration... @{ui}@{PAR}

This button cycles between Header and Footer. The 'Title', 'Date'
and 'Page no.'buttons (described below) can be used with
creating a Header or Footer line for each page in the print out.
When the configuration button is Header, these buttons affect the
Header line; otherwise, they affect the Footer line. By default,
Directory Opus will not create a Header or a Footer line.@{PAR}

@{i}Title @{ui}@{PAR}

When the checkmark next to Title is on, a title will be generated
By default, the filename will be the title. However, you can
override this by putting text in the Title field. You can have
different titles in the header and footer lines.@{PAR}

@{i}Date @{ui}@{PAR}

When the checkmark next to Date is on, the current date will be
printed. Usually this is enabled for either the header line or
the footer line, but not for both.@{PAR}

@{i}Page no. @{ui}@{PAR}

When the checkmark next to Page no is on, the page number will
printed. Usually this is enabled for either the header
line or the footer line, but not for both.@{PAR}

@{i}Text style @{ui}@{PAR}

This button allows you to modify the appearance of all the
printed text except the headers and footers. (some printers do
not support all of these styles.) Clicking on the Text Style
Cycle button allows you to choose from the following options:
Normal, Bold, Italics, Unlined (Under Lined), DblStrik (Double
Strike), and Shadow.@{PAR}

@{i}Output to... @{ui}@{PAR}

By default, the output will be sent to the printer.
However, you can redirect the output to a file of your choosing.@{PAR}

@{i}Printer @{ui}@{PAR}

This option directs output to the printer.@{PAR}

@{i}File @{ui}@{PAR}

When this option is enabled, output is directed to the file
indicated in the accompanying field.@{PAR}

Click on the magnifying glass next to the File field to use
a file requester to find the file name; otherwise type the name
directly into the File field. If you leave the field empty, the
output will go to the printer.@{PAR}

@{i}Print @{ui}@{PAR}

When yo click this button, Directory Opus will begin
printing the information.@{PAR}

@ENDNODE
@NODE 2.7 "Req&View/Text Viewer"
@{LINDENT 1}

@{b}2.7 Text Viewer@{ub}@{PAR}

The name of the field is displayed at the bottom of the screen, giving
the current position within the file to both in lines and as a
percentage, and also the total number of lines in the file.@{PAR}

Press the left mouse button to turn scrolling on or off. The direction
and speed of the scroll are governed by the position of the mouse
pointer in the window. The mouse pointer will become invisible while
the text is scrolling. No scrolling occurs if you have the mouse in
the center of the window.@{PAR}

To scroll forward, move the mouse down until the text starts to scroll
(providing there is actually more than one page of text). The further
down you move the mouse, the faster the test will scroll. This
procedure is reversed for backwards scrolling.@{PAR}

The buttons in the bottom-right of the screen also allow you to move
around the file. Most buttons will repeat if held down for any length
of time. (Each button uses the corresponding letter as a shortcut key.)@{PAR}
@{LINDENT 4}


@{" up/down arrows " link 2.7.no} @{" U " link 2.7.no} @{" D " link 2.7.no} @{" T " link 2.7.no} @{" B " link 2.7.no} @{" S " link 2.7.no} @{" P " link 2.7.no} @{" Q " link 2.7.no}@{PAR}
@{LINDENT 1}


The current line and percentage values (in the middle of the bottom
bar) act as hidden buttons: click on them and a requester will allow
you to specify a new value. It will jump to the new location. The
shortcut key for this function is J.@{PAR}

If you have selected more than one file, the next one will be read when
you exit. To exit without reading the next file, press the right mouse
button (or hit the ESCAPE key).@{PAR}

The text viewer automatically decrunches text crunched with various
packing methods. It utilizes the XFDmaster library for that purpose.
Please refer to the @{" Requirements " link reqments} section for
further information).@{PAR}

By default, the text viewer opens its window on a new screen instead of DirOpus'
screen. This can be changed in the @{" configuration " link 3.19.9.text}.@{PAR}

@ENDNODE
@NODE 2.7.no "Req&View/Text Viewer"
@{LINDENT 1}

@{i}up/down arrows @{ui}@{PAR}

Move up and down a line at a time. you may also use the up and
down cursor keys.@{PAR}

@{i}U @{ui}@{PAR}

Moves up a page at a time. You may also use BACKSPACE or the up
Cursor key with shift.@{PAR}

@{i}D @{ui}@{PAR}

Moves down a page at a time. You may also use SPACE or the down
Cursor key with shift.@{PAR}

@{i}T @{ui}@{PAR}

Moves to the top of the file. You may also use the up Cursor key
with control.@{PAR}

@{i}B @{ui}@{PAR}

Moves to the bottom of the file. You may also use the down Cursor
key with control.@{PAR}

@{i}S @{ui}@{PAR}

Searches for a string. You may also use / as a shortcut key. You
can issue full patternmatching in this search. Searching for ASCII codes
is also possible, have a look at the @{" Search button " link 1.6.search} description
for more information.@{PAR}

If a string is found that matches your search string, the
appropriate line will be highlighted. Hit N to search for the next match.@{PAR}

@{i}P @{ui}@{PAR}

Prints the current file. Hitting C Prints only the current page. This has no button
equivalent.@{PAR}

@{i}Q @{ui}@{PAR}

(additional keyboard shortcuts are X or Esc) leaves the text viewer. You can also use
the right mouse button to exit.@{PAR}

@ENDNODE
@NODE 2.8 "Req&View/Hex Viewer"
@{LINDENT 1}

@{b}2.8 Hex Viewer@{ub}@{PAR}

The Hex Viewer will read files in the same way as the @{" Text Viewer " link 2.7},
except in hexadecimal format. This allows you to view binary files and
other files containing non-textual characters. The file is displayed in
the following manner:@{PAR}

The first value is the offset, displayed in hex. This is the number of
bytes you are into the file. The next four values are each a four-byte
longword, with the actual ASCII representation at the end. Any non-text
characters are shown as a . character.@{PAR}

@ENDNODE
@NODE Config "ConfigOpus"
@{LINDENT 1}

@{b}Chapter 3 - ConfigOpus@{ub}@{PAR}

ConfigOpus is the Directory Opus Configuration Utility. This section
describes how to customise DirOpus to your needs, using the powerful
ConfigOpus utility.@{PAR}
@{LINDENT 4}

@{" Introduction      " link 3.1}              @{" Fileclass Manager " link 3.11}@{PAR}
@{" Main Screen       " link 3.2}              @{" Fileclass Editor  " link 3.12}@{PAR}
@{" Configure Menus   " link 3.3}              @{" Hotkeys Manager   " link 3.13}@{PAR}
@{" Buttons Manager   " link 3.4}              @{" Hotkeys Editor    " link 3.14}@{PAR}
@{" Buttons Editor    " link 3.5}              @{" Menus Manager     " link 3.15}@{PAR}
@{" Command Editor    " link 3.6}              @{" Menus Editor      " link 3.16}@{PAR}
@{" Drives Manager    " link 3.7}              @{" Operation         " link 3.17}@{PAR}
@{" Drives Editor     " link 3.8}              @{" Screen            " link 3.18}@{PAR}
@{" Filetypes Manager " link 3.9}              @{" System            " link 3.19}@{PAR}
@{" Filetypes Editor  " link 3.10}

@ENDNODE
@NODE 3.1 "ConfigOpus Introduction"
@{LINDENT 1}

@{b}3.1 - Introduction@{ub}@{PAR}

The Opus Configuration utility is a powerful and easy-to-use instrument
for customising Directory Opus precisely to your tastes. Do you want to
use an interlace screen ?  Eight or sixteen colours ? Lots of buttons ?
Fancy buttons?  Directories sorted by date, in reverse order ?  Instant
access to various assignments ?  With ConfigOpus, these are but a few
of the myriad choices you can make.@{PAR}

Sophisticated though it is, the ConfigOpus utility is quick and easy to
use. This section is intended as a complete set of instructions for
users new to Directory Opus, and as a convenient reference for
experienced users.@{PAR}

Directory Opus uses a separate program to modify the configuration.
This saves approximately 130K of memory, as the configuration program
need only be in memory when it is being used. Not only that, but the
configuration program can be run independently of Directory Opus, if
you are really short on memory.@{PAR}

If you do have plenty of memory, however, Directory Opus can be
configured to load the configuration program on start-up. In this case,
it is run form memory each time the Configure program is invoked,
rather than loaded form disk. That can be much faster, especially if
you have a floppy based system.@{PAR}

From within Directory Opus, you can start up ConfigOpus by clicking on
the small C button on the lower right or selecting the "Configure" item
from the Project Menu.@{PAR}

From outside Directory Opus, you can start ConfigOpus by itself either
by double-clicking on the ConfigOpus icon or starting it from a CLI.@{PAR}

@ENDNODE
@NODE 3.2 "ConfigOpus Main Screen"
@{LINDENT 1}

@{b}3.2 - ConfigOpus Main Screen@{ub}@{PAR}

On the ConfigOpus screen there are several items of interest. At the
top of the screen you will see Screen Depth button and the Screen Title
Bar. The Screen Depth button allows the user to push the screen behind
the other screens opened.@{PAR}

You can press the Help key at any time to bring up help information. 
When you have questions about something on the screen, try here first.
If the Help button does not answer your question, then you can drag out
the manual.@{PAR}

@{FG highlight}NOTE:@{FG text}@{PAR}

The Help key does not work if a 'String Gadget' is active (i.e. if
ConfigOpus expects you to enter some text). In this case, deactivate
the String Gadget by clicking on an empty area in the window.@{PAR}

The Window Title Bar describes the current screen. It Doubles as the
Window Drag Bar, which allows you to drag the ConfigOpus window around.@{PAR}

The next set of buttons to look at are the subject buttons along the
left side of the screen. When you select one, the screen will change to
show that part of the ConfigOpus.@{PAR}
@{LINDENT 4}

@{" Buttons " link 3.4}@{PAR}

Configure the custom buttons, allowing you to launch internal
commands and external programs.@{PAR}

@{" Drives " link 3.7}@{PAR}

Configure the custom drive buttons.@{PAR}

@{" Filetypes " link 3.9}@{PAR}

Configure the file classes and actions necessary for file
recognition.@{PAR}

@{" Hotkeys " link 3.13}@{PAR}

Configure the global Hotkeys, allowing you to launch programs from
anywhere in the system while Directory Opus is active or
iconified.@{PAR}

@{" Menus " link 3.15}@{PAR}

Configure the custom menus, allowing you to launch internal
commands and external programs.@{PAR}

@{" Operations " link 3.17}@{PAR}

Flags and settings that affect the way Directory Opus behaves.@{PAR}

@{" Screen " link 3.18}@{PAR}

Modifies the characteristics and appearances of the Directory Opus
screen and graphic user interface.@{PAR}

@{" System " link 3.19}@{PAR}

Additional items that affect the way Directory Opus interacts with
the operating system.@{PAR}

@{i}Save @{ui}@{PAR}

Save the current configuration settings as the default settings
(this will be the setting that Directory Opus will start up with).@{PAR}

@{i}Okay and Cancel: @{ui}@{PAR}

These allow you to say either "OK, let's use these settings and go
back to Directory Opus", or "Oops! Forget all that, and let's get
out of here!"@{PAR}

@ENDNODE
@NODE 3.3 "Configure Menus"
@{LINDENT 1}

@{b}3.3 - ConfigOpus Configure Menus@{ub}@{PAR}

There are four menu items available on most screens in ConfigOpus that
allow the user to control the configuration data. You can revert to the
default configuration, load a configuration file or save the current
configuration. On the ConfigOpus screen, these menus will allow you to
affect all the configuration data. When you select the Open item, you
load all the configuration data from that file, replacing any changes
that you have made with this new data.@{PAR}

On the other screens in ConfigOpus, the Open menu will only override
the information specific to that screen. For instance, on the
@{" Custom Button " link 3.4} screen only the Custom Button banks will be loaded from
a configuration file. This allows you to load banks of buttons that you
have defined in advance, so as to control the NewTek Video Toaster, for
or some other application.@{PAR}
@{LINDENT 4}

@{i}Default @{ui}@{PAR}

Reset to the factory default configuration settings.@{PAR}

@{i}Open... @{ui}@{PAR}

Load configuration settings from a disk file. If you are on
@{" Custom Buttons " link 3.4}, @{" Drives " link 3.7}, @{" Filetypes " link 3.9}, @{" Hotkeys " link 3.13} or @{" Menus " link 3.15} this
will only load that part of the configuration file. As an
example, by using this, you can import Custom Button banks from
someone else's configuration file.@{PAR}

@{i}Save @{ui}@{PAR}

Save the current configuration settings as the default settings
This will be the setting that Directory Opus will start up with
up with.@{PAR}

@{i}Save As... @{ui}@{PAR}

Same as 'Save', but this allows you to specify a filename. This
allows you to save alternative configurations to the default.@{PAR}

@ENDNODE
@NODE 3.4 "Configuration: Buttons Manager"
@{LINDENT 1}

@{b}3.4 - Buttons Manager Screen@{ub}@{PAR}

There are 42 custom buttons, located at the bottom of the Directory
Opus screen. Each button can have a left and/or right mouse button
events, bringing the total number of customs buttons to 84.@{PAR}

The custom buttons are arranged in banks. There is only one bank of
these buttons by default, but the configuration program allows you add
add or delete as many banks as you want, which means that the number of
custom buttons is limited only by available memory and your
imagination.@{PAR}

The button configuration screen displays the current button bank, with
the left mouse button events at the top and the right mouse button
events at the bottom of the screen.@{PAR}

There are ten buttons across the bottom of the Buttons Manager screen
The Copy, Swap and Delete buttons stay selected if they have been
selected with the left mouse button. For instance, Copy button will
stay selected to remind you that you are now in copy button mode. When
you want to leave this mode, select Copy button again. The buttons
below that work in this fashion are Copy, Swap and Delete.@{PAR}
@{LINDENT 4}

@{" Next bank   " link 3.4.1.next_bank}             @{" Copy button " link 3.4.1.copy_button}@{PAR}
@{" Copy bank   " link 3.4.1.copy_bank}             @{" Swap button " link 3.4.1.swap_button}@{PAR}
@{" Swap bank   " link 3.4.1.swap_bank}             @{" Del. button " link 3.4.1.delete_button} (Delete button)@{PAR}
@{" Delete bank " link 3.4.1.delete_bank}@{PAR}
@{LINDENT 1}

The last two buttons on this screen (lower right corner) are the Okay
and Cancel buttons. These allow you to say, "OK, let's use all these
custom button changes and go back to ConfigOpus' main screen", or
"Oops! Forget all this, and let's just leave."@{PAR}

The Default or Open... menu items in the Configure menu allow you
import custom button banks from either the default configuration or a
configuration file from disk. These banks will be inserted at the end
of banks you have already defined.@{PAR}

The Button Rows menu allows you to configure the actual number of rows of custom
buttons that will be displayed at one time on the main Directory Opus
window. You can choose from zero (no buttons displayed), one, two,
three or six rows. This will also affect the drive bank height.@{PAR}

The Paint Mode menu provides an easy way of changing several button colours
without invoking the @{" button Editor " link 3.5} each time.@{PAR}

When you select it, a requester will appear, asking you for the fore- and
background color you want to use. If you click on OK, the Paint Mode will
be activated. You can now apply the selected colors to any button by simply
clicking on it.@{PAR}

To leave Paint Mode, just select it again. A checkmark in front of the menu item
indicates that Paint Mode is active at the moment.@{PAR}

To edit a custom button, make sure you are not in Copy, Swap or Delete
mode. Select the custom button, and you will be shown the custom
@{" button editor " link 3.5} screen.@{PAR}

@ENDNODE
@NODE 3.4.1.next_bank "Configuration: Buttons Manager/Next bank"
@{LINDENT 1}

@{b}Next bank@{ub}@{PAR}

With this button you can cycle through the button banks. If you select
this button with the left mouse button, it will create an empty bank at
the end of the bank list. This bank will then be shown.@{PAR}

If you press this button with the right mouse button, the new bank will
be inserted before the current bank, instead of at the end of the bank
list.@{PAR}

@ENDNODE
@NODE 3.4.1.copy_bank "Configuration: Buttons Manager/Copy bank"
@{LINDENT 1}

@{b}Copy bank@{ub}@{PAR}

Use this to copy the currently displayed bank. A requester will appear
asking you to enter the bank number to copy the current bank onto. If
the bank number you enter does not exist, a new bank will be created at
the end of the bank list. The current bank will be copied to there.@{PAR}

@ENDNODE
@NODE 3.4.1.swap_bank "Configuration: Buttons Manager/Swap bank"
@{LINDENT 1}

@{b}Swap bank@{ub}@{PAR}

Swap bank allows you to swap the contents of the currently displayed
bank with those of another. A requester will appear asking you to enter
the bank number to copy to. If the bank number you enter does not
exist, the swap operation will be aborted.@{PAR}

@ENDNODE
@NODE 3.4.1.delete_bank "Configuration: Buttons Manager/Delete bank"
@{LINDENT 1}

@{b}Delete bank@{ub}@{PAR}

After asking for confirmation, this button will delete the current
bank. If the current bank is also the only bank, you will be warned.@{PAR}

@ENDNODE
@NODE 3.4.1.copy_button "Configuration: Buttons Manager/Copy button"
@{LINDENT 1}

@{b}Copy button@{ub}@{PAR}

This button allows you to copy one custom button onto another. Select
the custom button to be copied, then select a custom button to copy it
onto. To abort the copy, turn off copy mode by selecting the Copy
button again or just select the custom button you are copying from
again.@{PAR}

When in Copy button mode, the @{" Next bank " link 3.4.1.next_bank} button is still usable and
allows you to copy and swap custom buttons between banks.@{PAR}

@ENDNODE
@NODE 3.4.1.swap_button "Configuration: Buttons Manager/Swap button"
@{LINDENT 1}

@{b}Swap button@{ub}@{PAR}

This permits you to swap two custom buttons. It works the same way as
the @{" Copy button " link 3.4.1.copy_button} except that it simply exchanges the two custom
buttons.@{PAR}

When in Swap button mode, the @{" Next bank " link 3.4.1.next_bank} button is still usable and
allows you to copy and swap custom buttons between banks.@{PAR}

@ENDNODE
@NODE 3.4.1.delete_button "Configuration: Buttons Manager/Delete button"
@{LINDENT 1}

@{b}Delete button@{ub}@{PAR}

After asking for confirmation, this will reset all the data associated
with a custom button.@{PAR}

@ENDNODE
@NODE 3.5 "Configuration: Buttons Editor"
@{LINDENT 1}

@{b}3.5 - Buttons Editor@{ub}@{PAR}

At the top of the Custom Button Edit screen you can see what the
current custom button looks like. The palettes on either side of the
example allow you to select the button's foreground and background
colours. The example button between the palettes show you what the real
button will look like.@{PAR}
@{LINDENT 4}


@{i}Name @{ui}@{PAR}

This field allows you to modify the name that appears on the
button, and is limited to 63 characters.@{PAR}

@{i}Shortcut key @{ui}@{PAR}

This is a display area for the keyboard equivalent for this custom
button. The Sample button allows you to modify the shortcut key
sequence.@{PAR}

@{i}Sample @{ui}@{PAR}

To modify the Shortcut key, select this button. Any keys, along
with any qualifiers you press will be inserted in the Shortcut key
field. To turn off Sample mode, select the Sample button again.@{PAR}

To clear the Shortcut key sequence simply select the Sample button
with the right mouse button.@{PAR}
@{LINDENT 1}


The bottom half of the Buttons Editor window shows the
@{" Command Editor " link 3.6}. Here you can define what command(s) should be
invoked by the button.@{PAR}

@ENDNODE
@NODE 3.6 "Configuration: Command Editor"
@{LINDENT 1}

@{b}3.6 - Command Editor@{ub}@{PAR}

A Command tells Directory Opus what to do when something happens, and
can be attached to @{" Custom Buttons " link 3.4}, @{" Filetype " link 3.9} Actions, @{" Hotkeys " link 3.13}
and @{" Menus " link 3.15}. Each of these has its own configuration screen with
unique aspects (e.g. the title and colours used on a Custom Button).@{PAR}

The unique aspects of the various editors are described in their own
sections, but they all have a common portion, referred to as the
Command Editor, which allows you to edit the Command.


@{FG highlight}The Command list@{FG text}@{PAR}

At the center of the Command editor is the Command List which
contains the commands associated with the button/menu item/hotkey
or filetype action. To the left of this list are four buttons that
allow you to modify the order and effectiveness of these commands.@{PAR}
@{LINDENT 4}

@{" New Entry " link 3.6.0.cl}@{PAR}
@{" Duplicate " link 3.6.0.cl}@{PAR}
@{" Swap      " link 3.6.0.cl}@{PAR}
@{" Delete    " link 3.6.0.cl}@{PAR}
@{LINDENT 1}

To edit a Command, simply click on it. The Command string will be
copied to the field below the list for you to edit it.@{PAR}

@{FG highlight}Edit Fields@{FG text}@{PAR}

Below the Command list is a group of editing tools. These tools
allow you to edit active Command entries. When you click on an
entry in the Command list it becomes active, or an empty one is
created when you select New entry.@{PAR}
@{LINDENT 4}

@{" Command Type " link 3.6.1.Command_Type}@{PAR}
@{" {} Button    " link 3.6.1.braces}@{PAR}
@{" Flags        " link 3.6.1.Flags}@{PAR}
@{" Fields       " link 3.6.1.Fields}@{PAR}
@{LINDENT 1}

@{FG highlight}Edit Menu@{FG text}@{PAR}

If you move the mouse to the top of the screen and press the right
mouse button, you will see that the main @{" Configure menu " link 3.3} has
been replaced by the Edit menu. The options in this menu operate
on the frequently displayed Command List. This includes the Flags
and fields.@{PAR}

All screens with a Command Editor contain the Edit Menu with Cut,
Copy and Paste commands. These allow you to swap command
definitions between @{" custom buttons " link 3.4}, @{" menus " link 3.15} and @{" Filetypes " link 3.9}.@{PAR}
@{LINDENT 4}

@{" Cut         " link 3.6.2}@{PAR}
@{" Copy        " link 3.6.2}@{PAR}
@{" Paste       " link 3.6.2}@{PAR}
@{" Erase       " link 3.6.2}@{PAR}
@{" Clear Clips " link 3.6.2}@{PAR}

@ENDNODE
@NODE 3.6.0.cl "Configuration: Command Editor/Command List"
@{LINDENT 1}

@{b}New entry@{ub}@{PAR}

Adds a new Command to the list.@{PAR}

@{b}Duplicate@{ub}@{PAR}

To duplicate an existing Command, select the Command and select the
Duplicate button. The duplicated Command will be added to the end of
the Command list.@{PAR}

@{b}Swap@{ub}@{PAR}

To exchange the position of two Commands, select the first, then select
the Swap button. With the Swap button active, select the second Command
to swap. To cancel the swap operation, select the Swap button again.@{PAR}

@{b}Delete@{ub}@{PAR}

To delete a Command from the list, select the Command and select the
Delete button.@{PAR}

@ENDNODE
@NODE 3.6.1.Command_Type "Configuration: Command Editor/Edit fields/Command type"
@{LINDENT 1}

@{b}Command Type@{ub}@{PAR}

The cycle button on the left below the Command List allows you to
specify which kind of Command is used. When you click on this button,
it will cycle through the following Command types:@{PAR}
@{LINDENT 4}

@{" Command    " link 3.6.1.Command_type.Command}@{PAR}
@{" AmigaDOS   " link 3.6.1.Command_type.Executable}@{PAR}
@{" Workbench  " link 3.6.1.Command_type.Workbench}@{PAR}
@{" Batch      " link 3.6.1.Command_type.Batch}@{PAR}
@{" ARexx      " link 3.6.1.Command_type.ARexx}@{PAR}
@{LINDENT 1}

When you click on the magnifying-glass button just to the right of the
Command Type button, a requester appears allowing you to pick an
appropriate entry for the selected Command type. Each of the
descriptions indicates the kind of requester which will appear.@{PAR}

@ENDNODE
@NODE 3.6.1.Command_type.Command "Configuration: Command Editor/Edit Fields/Command type/Command"
@{LINDENT 1}

@{b}Command@{ub}@{PAR}

These are internal Commands, built into Directory Opus. Many of these
Commands can take parameters from buttons and menus as well as from
ARexx. Internal Commands are documented in the @{" Commands " link commands} section.@{PAR}

The magnifying-glass button brings up a list of internal commands.@{PAR}

@ENDNODE
@NODE 3.6.1.Command_type.Executable "Configuration: Command Editor/Edit Fields/Command type/AmigaDOS"
@{LINDENT 1}

@{b}AmigaDOS@{ub}@{PAR}

This is for executable programs that will get launched as if you were running
them manually from the CLI. Thus, with an output window enabled, they can
receive keyboard input from the user and display output on the screen.@{PAR}

The magnifying-glass button brings up a file requester.@{PAR}

@ENDNODE
@NODE 3.6.1.Command_type.Workbench "Configuration: Command Editor/Edit fields/Command type/Workbench"
@{LINDENT 1}

@{b}Workbench@{ub}@{PAR}

Workbench programs are also executable programs. They are launched,
however, as if you were double-clicking on their icons from Workbench.
This can be an advantage, as many programs do not take arguments, or do
not work at all if run from the CLI.@{PAR}

If the Workbench program given is a tool (i.e. an executable program),
Directory Opus will look for its icon file to determine the necessary
stack size to give to the program. If the icon cannot be located, the
stack size defined in the button, menu or filetype will be used.@{PAR}

If the Workbench program given is a project (a non-executable file
created by another program), Directory Opus will look for its icon file
to find its Default Tool, the actual program needed to load the file.
If the icon cannot be found, or a Default Tool can not be loaded
successfully, Directory Opus will not launch the file. The project's
icon is also used to determine stack size.@{PAR}

Workbench programs can also take arguments from Directory Opus using
the @{" {f} " link SimArgFun 7} and similar sequences. This can be very useful indeed.
DeluxePaint, for instance, does not accept arguments if run from the
CLI; you would be unable, therefore, to select a picture file for
DeluxePaint to load from Directory Opus if you were running DPaint as
an @{" AmigaDOS " link 3.6.1.Command_type.Executable} executable.@{PAR}

If, however, you have the command defined as:@{PAR}
@{LINDENT 4}

DPaint {f}@{PAR}
@{LINDENT 1}

and have the Command type set to Workbench, DeluxePaint will be run as
a Workbench program. From the Workbench, DeluxePaint will accept
arguments, so the first file you selected would be loaded into DPaint
automatically.@{PAR}

The magnifying-glass button brings up a file requester.@{PAR}

You can @{" drag'n drop " link 1.10} Workbench icons over the Command Editor window and
ConfigOpus will add a Workbench Command entry.

@ENDNODE
@NODE 3.6.1.Command_type.Batch "Configuration: Command Editor/Edit fields/Command type/Batch"
@{LINDENT 1}

@{b}Batch@{ub}@{PAR}

Batch files, also called script files, are files that you might run
with the @{" Execute Command " link Execute}, or with the execute command from the CLI.
Selecting a Command type as Batch will cause the file to be executed as
a script file.@{PAR}

The magnifying-glass button brings up a file requester. This file
requester is initially set to S: because this is where batch files come
from by default.@{PAR}

@ENDNODE
@NODE 3.6.1.Command_type.ARexx "Configuration: Command Editor/Edit Fields/Command type/ARexx"
@{LINDENT 1}

@{b}ARexx@{ub}@{PAR}

This type indicates that the Command is an ARexx script. The script
will only be launched if ARexx is active in the system. Note that the
address of the ARexx port will be set automatically, you do not need to
use the ARexx ADDRESS command to address the command to Directory Opus.@{PAR}

The magnifying-glass button brings up a file requester. This file
requester is initially set to Rexx: because this is the place ARexx
files come from by default.@{PAR}

@ENDNODE
@NODE 3.6.1.braces "Configuration: Command Editor/Edit fields/{} Button"
@{LINDENT 1}

@{b}{} button@{ub}@{PAR}

This button is located next to the Command Edit Field. This button
brings up a list of the @{" argument functions " link SimArgFun} and
the @{" requester functions " link ReqFun}. This is a very powerful feature
of Directory Opus.@{PAR}

Command strings can contain many different command sequences to do
different things with files and directories. For documentation on
these, and more information on commands in general, consult the
@{" commands " link commands} section.@{PAR}

@ENDNODE
@NODE 3.6.1.Flags "Configuration: Command Editor/Edit fields/Flags"
@{LINDENT 1}

@{b}Flags...@{ub}@{PAR}

Below the Command list is the Flags list. This is a list of all the
flags available for custom Commands. These flags apply to all Commands
in the Command list. The flags are:@{PAR}
@{LINDENT 4}

@{" Auto Iconify            " link 3.6.1.ai }             @{" Output Window         " link 3.6.1.ow }@{PAR}
@{" CD source               " link 3.6.1.cs }             @{" Output to File        " link 3.6.1.otf }@{PAR}
@{" CD destination          " link 3.6.1.cd }             @{" Recursive Directories " link 3.6.1.rd }@{PAR}
@{" Directory OPus to front " link 3.6.1.dotf}             @{" Reload each file      " link 3.6.1.ref }@{PAR}
@{" Do all files            " link 3.6.1.daf }             @{" Rescan destination    " link 3.6.1.rdest }@{PAR}
@{" Include Dopus-Startup   " link 3.6.1.ids }             @{" Rescan source         " link 3.6.1.rs }@{PAR}
@{" Include Shell-Startup   " link 3.6.1.iss }             @{" Run asynchronously    " link 3.6.1.ra }@{PAR}
@{" No Filename Quote       " link 3.6.1.nfq }             @{" Workbench to front    " link 3.6.1.wtf }@{PAR}

@ENDNODE
@NODE 3.6.1.ai "Configuration: Command Editor/Edit Fields/Flags"
@{LINDENT 1}

@{b}Auto iconify@{ub}@{PAR}

Causes Directory Opus to enter iconified mode when the Commands are
launched. This could be useful in low-memory situations. It only works
with @{" Run Asynchronously " link 3.6.1.ra} enabled.@{PAR}

@ENDNODE
@NODE 3.6.1.cs "Configuration: Command Editor/Edit Fields/Flags"
@{LINDENT 1}

@{b}CD source@{ub}@{PAR}

If this is turned on, the current directory of the custom Command will
be set to the current source directory (active directory window).@{PAR}

@ENDNODE
@NODE 3.6.1.cd "Configuration: Command Editor/Edit Fields/Flags"
@{LINDENT 1}

@{b}CD destination@{ub}@{PAR}

This has a similar effect to @{" CD source " link 3.6.1.cs}, except that the
current directory of the custom Command will be set to the current
destination directory (inactive directory window).@{PAR}

@ENDNODE
@NODE 3.6.1.dotf "Configuration: Command Editor/Edit Fields/Flags"
@{LINDENT 1}

@{b}Directory Opus to front@{ub}@{PAR}

Causes the Directory Opus screen to be brought to the front when the
Commands have terminated. It is used in conjunction with
@{" Workbench To Front " link 3.6.1.wtf}. If enabled in conjunction with
@{" Run Asynchronously " link 3.6.1.ra} and @{" Output Window " link 3.6.1.ow}, this flag will have slightly
slightly different effect. In that case, the output window will be
opened on the Workbench screen as normal, but the Workbench screen will
not be brought to the front.@{PAR}

@ENDNODE
@NODE 3.6.1.daf "Configuration: Command Editor/Edit Fields/Flags"
@{LINDENT 1}

@{b}Do all files@{ub}@{PAR}

This causes the Commands to act on each selected entry in turn, instead
of just the first entry. This is used for commands that do not support
multiple filenames on the command line, where @{" {F} " link SimArgFun 14} to send all
selected entries would not work.@{PAR}

@ENDNODE
@NODE 3.6.1.ids "Configuration: Command Editor/Edit Fields/Flags"
@{LINDENT 1}

@{b}Include DOpus-Startup@{ub}@{PAR}

Makes Directory Opus execute a file called S:DOpus-Startup before any
external Commands are actually executed. This is used in the same way
as the @{" Shell-Startup " link 3.6.1.iss} file, but is distinct from the Shell-Startup
file, and therefore allows you to put into it any Directory Opus
specific commands.@{PAR}

@ENDNODE
@NODE 3.6.1.iss "Configuration: Command Editor/Edit Fields/Flags"
@{LINDENT 1}

@{b}Include Shell-Startup@{ub}@{PAR}

If this option is enabled, then Directory Opus will execute the
standard S:Shell-Startup file before any external Commands are actually
executed. This allows you to have all your path lists, resident
commands, etc. available to custom Commands.@{PAR}

@ENDNODE
@NODE 3.6.1.nfq "Configuration: Command Editor/Edit Fields/Flags"
@{LINDENT 1}

@{b}No filename quote@{ub}@{PAR}

This option enables Directory Opus to operate correctly with some older
or poorly written software. Normally, whenever Directory Opus sends a 
filename to a custom Command with the @{" {f} " link SimArgFun 7}, @{" {o} " link SimArgFun 35}, etc. flags, the
filename is enclosed in quotation marks. This allows you to use
filenames containing spaces with external programs. However, some
software does not interpret the quotation marks correctly. If you find
this is the case with any program, simply select the No filename quote flag.@{PAR}

@ENDNODE
@NODE 3.6.1.ow "Configuration: Command Editor/Edit Fields/Flags"
@{LINDENT 1}

@{b}Output window@{ub}@{PAR}

Opens a window for output from these Commands. The window will open on
the Directory Opus screen, unless the @{" Workbench to front " link 3.6.1.wtf} option
or the @{" Run asynchronously " link 3.6.1.ra} option is enabled. In this case, it will
open on the Workbench screen, and the Workbench screen will be brought
to the front automatically. This window is opened using the handle
specified in the @{" System/AmigaDOS " link 3.19.1} section of the configuration.@{PAR}

@ENDNODE
@NODE 3.6.1.otf "Configuration: Command Editor/Edit Fields/Flags"
@{LINDENT 1}

@{b}Output to file@{ub}@{PAR}

Redirects all output from the Commands to a temporary file in T:
directory, which is then red via the @{" text viewer " link 2.7}. This
allows you to read the output of a program thoroughly, and even to
print it. Note that if you are sending output to a file, the Command
cannot receive input from the keyboard.@{PAR}

@ENDNODE
@NODE 3.6.1.rd "Configuration: Command Editor/Edit Fields/Flags"
@{LINDENT 1}

@{b}Recursive directories@{ub}@{PAR}

Allows the Command access to files within sub-directories. Normally,
whenever a @{" {f} " link SimArgFun 7} or @{" {F} " link SimArgFun 13} or similar sequence would result in the
name of a directory being included in the same way as a file. In other
words, the Command would not act recursively on all files within the
directory.@{PAR}

If this option is enabled, the names of all files within that
directory, and within sub-directories within the directory, and so on,
are included in the program's parameters. This allows the Command to
act on all files in the directory and not just on the directory itself.@{PAR}

@ENDNODE
@NODE 3.6.1.ref "Configuration: Command Editor/Edit Fields/Flags"
@{LINDENT 1}

@{b}Reload each file@{ub}@{PAR}

Causes Directory Opus to rescan a file after it has been acted upon by
a Command, and updates the size, datestamp, comment and
@{" protection bits " link 2.1 10} of the file. You can therefore reflect changes in
size, for instance, made by a text editor to a file.@{PAR}

@ENDNODE
@NODE 3.6.1.rdest "Configuration: Command Editor/Edit Fields/Flags"
@{LINDENT 1}

@{b}Rescan destination@{ub}@{PAR}

This flag makes Directory Opus reload the destination directory
(inactive directory window) when the Command terminates. This, and
@{" Reload each file " link 3.6.1.ref}, allows Directory Opus to display correctly any
changes made to either directory window by external programs, such as archivers.@{PAR}

@ENDNODE
@NODE 3.6.1.rs "Configuration: Command Editor/Edit Fields/Flags"
@{LINDENT 1}

@{b}Rescan source@{ub}@{PAR}

Makes Directory Opus reload the source directory (active directory
window) when the Command terminates.@{PAR}

@ENDNODE
@NODE 3.6.1.ra "Configuration: Command Editor/Edit Fields/Flags"
@{LINDENT 1}

@{b}Run asynchronously@{ub}@{PAR}

Indicates that the Commands are to be launched as a new process, and
Directory Opus is not to wait for it to return. If this is the case,
and an output window is specified, the output window opens on the
Workbench screen.@{PAR}

@ENDNODE
@NODE 3.6.1.wtf "Configuration: Command Editor/Edit Fields/Flags"
@{LINDENT 1}

@{b}Workbench to front@{ub}@{PAR}

Causes the Workbench screen to be brought to the front.@{PAR}

@ENDNODE
@NODE 3.6.1.Fields "Configuration: Command Editor/Edit Fields/"
@{LINDENT 1}

@{b}Fields@{ub}@{PAR}

Three fields at the lower right allow you to specify stack size,
priority and output window close delay.@{PAR}
@{LINDENT 4}

@{" Stack Size  " link 3.6.1.fields.stack}@{PAR}
@{" Priority    " link 3.6.1.fields.priority}@{PAR}
@{" Close delay " link 3.6.1.fields.close}@{PAR}

@ENDNODE
@NODE 3.6.1.fields.stack  "Configuration: Command Editor/Edit Fields/Fields"
@{LINDENT 1}

@{b}Stack Size@{ub}@{PAR}

The stack size is the size (in bytes) that external programs will use a
stack space. The default and minimum is 4000 bytes. The documentation
of the program you are running should advise you of the best stack size
to use.@{PAR}

@ENDNODE
@NODE 3.6.1.fields.priority "Configuration: Command Editor/Edit Fields/Fields"
@{LINDENT 1}

@{b}Priority@{ub}@{PAR}

The priority field allows you to determine the priority at which the
programs will run. The default is 0. You should not normally use
anything lower then -10 or higher than 10, except for certain programs
(the documentation of the program may advise you of appropriate priorities).@{PAR}

@ENDNODE
@NODE 3.6.1.fields.close  "Configuration: Command Editor/Edit Fields/Fields"
@{LINDENT 1}

@{b}Close delay@{ub}@{PAR}

This field is the number of seconds after the Commands have finished
before the output window closes (if one is specified). The default is
2, which means that the output window will close two seconds after the
Commands have terminated. If you set the close delay to 0, the output
window will close immediately. If you set it to -1, it will wait for
you to press the left mouse button before closing.@{PAR}

@ENDNODE
@NODE 3.6.2 "Configuration: Command Editor/Edit Menu"
@{LINDENT 1}

@{b}Cut@{ub}@{PAR}

Copies the settings of this Command List to the clipboard then erases
them, resetting all fields to their default settings.@{PAR}

@{b}Copy@{ub}@{PAR}

Copies the settings of this Command List to the clipboard, but will
leave the values untouched.@{PAR}

@{b}Paste...@{ub}@{PAR}

Displays a list of all Command Clips in the clipboard (if there are any
present). If you select an entry from this list, it will be pasted into
the current Command, replacing any information that was there already.@{PAR}

@{b}Erase@{ub}@{PAR}

Resets all fields to their settings, erasing the Command List. The
Command will not be copied to the clipboard.@{PAR}

@{b}Clear Clips@{ub}@{PAR}

This will remove all Command Clips from memory aswell as delete the file
T:configopus.clip (which is used to store the clips if you exit ConfigOpus,
i.e. to test some changes). This will cause all previously clipped commands
to be cleared.@{PAR}

@ENDNODE
@NODE 3.7 "Configuration: Drives Manager"
@{LINDENT 1}

@{b}3.7 - Drives Manager@{ub}@{PAR}

The Drives button configuration screen allows you to configure the
drive buttons. These buttons give you quick and easy access to a device
or directory. There are 30 drive buttons, arranged in five banks with
six buttons in each. The Drives configuration screen displays all 30
drive buttons at the top.@{PAR}

There are ten buttons across the bottom of the screen. Some of these
buttons stay selected when selected with the left mouse button. For
instance, Copy bank will stay selected, reminding you that you are now
in copy bank mode. To leave this mode, select Copy bank again The
buttons that work in this fashion are: Copy bank, Swap bank, Delete
bank, Sort bank, Copy drive, Swap drive and Delete drive.@{PAR}
@{LINDENT 4}

@{" Get drives  " link 3.7.Get_drives}          @{" Copy drive    " link 3.7.Copy_drive}@{PAR}
@{" Copy bank   " link 3.7.Copy_bank}          @{" Swap drive    " link 3.7.Swap_drive}@{PAR}
@{" Swap bank   " link 3.7.Swap_bank}          @{" Delete drive  " link 3.7.Delete_drive}@{PAR}
@{" Delete bank " link 3.7.Delete_bank}@{PAR}
@{" Sort bank   " link 3.7.Sort_bank}@{PAR}
@{LINDENT 1}

The last two buttons on this screen (lower right corner) are the Okay
and Cancel buttons. These allow you to say "OK, let's use all these
drive buttons changes and go back to ConfigOpus' main screen", or
"Oops! Forget all this, and let's just leave".@{PAR}

The Default or Open... menu items in the Configure menu allow you to
import drive buttons from either the default configuration or a configuration
file from disk.@{PAR}

The Paint Mode menu provides an easy way of changing several button colours
without invoking the @{" drives editor " link 3.8} each time.@{PAR}

When you select it, a requester will appear, asking you for the fore- and
background color you want to use. If you click on OK, the Paint Mode will
be activated. You can now apply the selected colors to any button by simply
clicking on it.@{PAR}

To leave Paint Mode, just select it again. A checkmark in front of the menu item
indicates that Paint Mode is active at the moment.@{PAR}

To edit a drive button, make sure you are not in Copy, Swap, Delete or
Sort mode. Select the custom button, and you will be shown the
@{" drives editor " link 3.8} screen.@{PAR}


@ENDNODE
@NODE 3.7.Get_drives "Configuration: Drives Manager/Get drives"
@{LINDENT 1}

@{b}Get drives@{ub}@{PAR}

Causes the drive buttons to be assigned to the names of all the devices
and assigned directories (the first 30) present in your system. You
would normally only do this when performing a major reconfiguration.@{PAR}

@ENDNODE
@NODE 3.7.Copy_bank "Configuration: Drives Manager/Copy bank"
@{LINDENT 1}

@{b}Copy bank@{ub}@{PAR}

Copies one drive bank onto another. Select any drive button in the
bank to copy, and then any drive button in the destination bank.@{PAR}

@ENDNODE
@NODE 3.7.Swap_bank "Configuration: Drives Manager/Swap bank"
@{LINDENT 1}

@{b}Swap bank@{ub}@{PAR}

Allows you to exchange the contents of the two banks. This works the
same way as the @{" Copy bank " link 3.7.Copy_Bank} button.@{PAR}

@ENDNODE
@NODE 3.7.Delete_bank "Configuration: Drives Manager/Delete bank"
@{LINDENT 1}

@{b}Delete bank@{ub}@{PAR}

Erases the contents of a drive bank. If a drive bank has no buttons
defined in it, it will not be displayed on the main Directory Opus
screen (ie, Directory Opus skips over unused drive banks). In fact,
if you delete all the banks, the drive banks will not even be shown
on the main Directory Opus screen. This allows the main
@{" custom buttons " link 3.4} to be wider.@{PAR}

@ENDNODE
@NODE 3.7.Sort_bank "Configuration: Drives Manager/Sort bank"
@{LINDENT 1}

@{b}Sort bank@{ub}@{PAR}

Alphabetically sorts the contents of a drive bank. Select any drive
button in a bank and that bank will be sorted.@{PAR}

@ENDNODE
@NODE 3.7.Copy_drive "Configuration: Drives Manager/Copy drive"
@{LINDENT 1}

@{b}Copy drive@{ub}@{PAR}

Copies one drive button onto another. Select the drive button to be
copied, then select a drive button to copy it onto. You can abort the
copy by turning off copy mode, selecting Copy drive again, or selecting
the drive button to copy from a second time.@{PAR}

@ENDNODE
@NODE 3.7.Swap_drive "Configuration: Drives Manager/Swap drive"
@{LINDENT 1}

@{b}Swap drive@{ub}@{PAR}

Swaps two drive buttons. This works the same way as the @{" Copy drive " link 3.7.Copy_Drive} button
except that it exchanges the two drive buttons.@{PAR}

@ENDNODE
@NODE 3.7.Delete_drive "Configuration: Drives Manager/Delete drive"
@{LINDENT 1}

@{b}Delete drive@{ub}@{PAR}

After asking for confirmation, resets all the data associated with the
drive button.@{PAR}

@ENDNODE
@NODE 3.8 "Configuration: Drives Editor"
@{LINDENT 1}

@{b}3.8 - Drives Editor@{ub}@{PAR}

When you select a drive button from one of the banks, the Drives Editor
will appear or be updated with that drive button's information. The
drives editor will be displayed directly below the drive banks.@{PAR}

In the middle of the screen is an example of what the current drive
button will look like. The palettes on either side of the example allow
you to select the foreground and background colours of
the button.@{PAR}
@{LINDENT 4}


@{i}Name @{ui}@{PAR}

This field allows you to modify the name that appears on the drive
button. The Name field is limited to fifteen characters.@{PAR}

@{i}Path @{ui}@{PAR}

This is the actual AmigaDOS path that is read in whenever this
drive button is selected. The Path field is limited to 256
characters.@{PAR}

@{i}Shortcut Key @{ui}@{PAR}

This is a display area for the keyboard equivalent for this drive
button.@{PAR}

@{i}Sample @{ui}@{PAR}

To modify the Shortcut key, select the Sample button. While the
Sample button is selected, any keys, along with any qualifiers,
you press will be inserted in the Shortcut key field. To turn off
Sample mode simply select the Sample button again.@{PAR}

To remove the shortcut key simply select the Sample button with
the right mouse button.@{PAR}
@{LINDENT 1}


The bottom half of the Drives Editor window shows the
@{" Command Editor " link 3.6}. Here you can define what command(s) should be
invoked by the button.@{PAR}

@ENDNODE
@NODE 3.9 "Configuration: Filetypes Manager"
@{LINDENT 1}

@{b}3.9 - Filetypes Manager@{ub}@{PAR}

A file is simply stored data. Files can contain executable programs,
IFF pictures, Icons for Workbench, or a multitude of other kinds of
data. Most (but not all) files have an identifiable structure.
Directory Opus's FileTypes system is designed to examine a file's
structure and identify the kind (or Type) of data it contains. You can
configure Directory Opus to understand an unlimited number of
Filetypes.@{PAR}

Filetypes are a versatile feature of Directory Opus. Using filetypes,
you can configure Directory Opus to play animations when they are 
double-clicked, to load a database program when you attempt to "Read"
a database file, or to uncompress an archived file when you
@{" Click-M-Click " link glos} on it.@{PAR}

This is the essence of the Filetypes: when you do something to a file,
Directory Opus can figure out what kind of file it is and take the
appropriate action for that type of data.@{PAR}

There are two sections to the Filetypes configuration:@{PAR}
@{LINDENT 4}

@{" Filetypes " link 3.9.1}@{PAR}

There is a list of Filetypes which is searched when an action
occurs. If the file being processed matches a FileType, you can
configure Directory Opus to perform a specific action.@{PAR}

@{" File Classes " link 3.11}@{PAR}

There is a DataBase of File Class definitions. Each describes the
process of matching a particular kind of File. Directory Opus
comes with more File Classes than you will probably use. You can
select from this list when you are creating a new Filetype entry.
You don't have to be an expert or know anything about the internal
structure of the file to do this.@{PAR}

The @{" File Class Manager " link 3.11} allows you to edit existing File
Classes, or define new ones. (This can be somewhat more
complicated.)@{PAR}

@ENDNODE
@NODE 3.9.1 "Configuration: Filetypes Manager/Filetypes"
@{LINDENT 1}

@{b}Filetypes@{ub}@{PAR}

The Filetypes configuration screen displays the list of filetypes that
Directory Opus recognises. By default,it recognises LHA archives, ARC
archives, ZOO archive, and Workbench icons.@{PAR}

There are five buttons across the bottom of the screen. Some of these
buttons when selected with the left mouse button stay selected. For
instance Delete will stay selected indicating that you are now in
delete mode. To leave this mode simply select Delete again. Both the
Delete and Swap buttons work in this fashion.@{PAR}

The buttons available are:@{PAR}
@{LINDENT 4}


@{i}New @{ui}@{PAR}

This allows you to create a new filetype entry based on a 
predefined File Class. When you select this button a requester
appears containing currently defined classes. To create a new
entry for one of these File Classes simply select it and you will
be brought to the @{" filetype action editor " link 3.10}.@{PAR}

@{i}Swap @{ui}@{PAR}

This button allows you to exchange the positions of two Filetypes
in the list. This can be very useful or even necessary. In the
case of having two filetypes defined in which one is a sub-set of
the other, e.g., 24 bit ILBM pictures versus regular IFF ILBM
picture filetype. Otherwise, pictures (in this case) will be
matched with the regular IFF ILBM picture filetype and will never
have a chance to match with the sub-set 24 bit ILBM picture filetype.@{PAR}

To actually perform a swap, click on the Swap button to enter that
mode. Click on the first filetype, then on the second. Those two
filetypes will exchange places in the list. To exit swap mode
simply press Swap a second time.@{PAR}

@{i}Delete @{ui}@{PAR}

In this mode you can select filetypes to remove from the list.
Click on the Delete button, then click on the entries you wish to
delete. If you accidentally delete an entry, click on the Cancel
button.@{PAR}

@{i}Okay and Cancel @{ui}@{PAR}

These buttons allow you to say "OK, let's use all these filetypes
changes and of back to ConfigOpus' main screen", or "Oops! Forget
all this and let's just leave".@{PAR}
@{LINDENT 1}


To edit a filetype, make sure you are not in Swap or Delete mode. Then
simply select it. You will then be taken to the @{" Filetype Editor " link 3.10} screen.@{PAR}

There is an additional menu on this screen which controls File Classes.
Please refer to the section on @{" File Class Manager " link 3.11} for information
about this menu.@{PAR}

@ENDNODE
@NODE 3.10 "Configuration: Filetypes Editor"
@{LINDENT 1}

@{b}3.10 - Filetypes Editor@{ub}@{PAR}

This editor allows you to define the actions taken on a matching
Filetype. In the @{" Command Editor " link 3.6} section, you learned to configure an
action when a custom button is selected. Essentially, you say: "When
I do this to this particular Filetype - Do that." The primary
difference is that a custom button can only be activated by being
clicked on; the commands available for editing Filetypes can be
activated in several ways.@{PAR}
@{LINDENT 4}


@{" Events... " link 3.10.events}@{PAR}

This is where you select the filetype-event you want to configure.@{PAR}

@{i}Name @{ui}@{PAR}

Below the list of Events associated with this filetype is a field
describing this particular Event. For instance you could have the Read
Event say something like "Reading file...". This message will appear in
Directory Opus' Title Bar when the Event is being performed.@{PAR}

@{i}Edit Class: @{ui}@{PAR}

The button to the far right of the list allows you to modify this
filetype's class definition. We will talk about editing File
Classes in the @{" File Class " link 3.11} section.@{PAR}
@{LINDENT 1}


The remaining parts of this requester are described in the
@{" Command Editor " link 3.6} section.@{PAR}

@ENDNODE
@NODE 3.10.events "Configuration: Filetypes Editor"
@{LINDENT 1}

@{b}Events...@{ub}@{PAR}

At the top of the Filetypes Editor is a list of Event types, which are
instructions you may choose to give Directory Opus regarding Filetypes.
Each of the Events is associated to either a mouse action or a
Directory Opus command, so each entry on the list is tagged either
@{" Action " link 3.10.1} or @{" Command " link 3.10.2}. An asterisk * indicates that this entry already
has an Event Command List defined for it. Clicking on an entry in the
list highlights it to show that it is the Command List currently being
edited. The current Command List is displayed in the editing list in
the middle of the screen. The The small field immediately above it
describes the Event.@{PAR}

While each of these Event types can be defined to do something, usually
only a few are actually defined. It certainly is not necessary to
define all Events for a Filetype.@{PAR}

When one of these Events is activated, Directory Opus does the
following:@{PAR}

It first searches the Filetypes list, starting with the first entry,
and checks whether it matches the entry's File Class.@{PAR}

If it matches, it looks to see if the corresponding Event is defined
from this Editor. If it is defined, it performs the Command List.@{PAR}

If it does not match the File Class, or if it matches and does not have
a Command List defined, it continues to search the Filetypes List. It
is possible for it to match a subsequent entry that does have a Command
List defined.@{PAR}

@ENDNODE
@NODE 3.10.1 "Configuration: Filetypes Editor/Events"
@{LINDENT 1}

@{b}Mouse Action Events@{ub}@{PAR}

Mouse Events occur when you either Double-click on a file or perform a
Click-m-click.@{PAR}
@{LINDENT 4}

@{i}Double-click @{ui}@{PAR}

This occurs when you double click on a file. A popular use of this
is to examine a file (e.g. show it if it is a picture or play it
if it is a sound). The actual double click speed is defined by the
operating system's preference program.@{PAR}

@{i}@{" Click-M-Click " link glos} @{ui}@{PAR}

This Event occurs when a file is clicked on then the mouse is
moved to the other window and clicked. One popular use of this
Event is for archive extracting. Another way this Event can happen
is by using @{" Click-Drag-Release " link glos}. With this you literally drag a
file into the window and drop it there.@{PAR}

@ENDNODE
@NODE 3.10.2 "Configuration: Filetypes Editor/Events"
@{LINDENT 1}

@{b}Command Events@{ub}@{PAR}

Command Events are called when a file is acted upon by a Directory Opus
command. For example, when a @{" Read " link 1.6.Read} Command is performed on a file,
Directory Opus will search for a @{" Filetype " link 3.9} which matches the file
and has a Read Event defined. You could, however, have Read do
something special for an archive ( i.e. list the contents of the
archive). Likewise if you have a music score you could define the
@{" Play " link 1.6.Play} (or @{" LoopPlay " link 1.6.Loop_Play}) to call up your player for that music score.@{PAR}

Each of the following Command Events is associated with a corresponding
Directory Opus command. This allows you to redefine the specific action
taken for a particular filetype. By convention you should use a command
Event for something similar to its normal use, but there is nothing to
stop you from giving a command Event a label that is totally irrelevant
to its use. It's up to you to keep the context of the command (i.e. a
Read would be confusing if it did a Disk Format).@{PAR}

The following list describes the normal usages. You can decide what you
want it to mean for any given filetype.@{PAR}
@{LINDENT 4}

@{" AnsiRead " link AnsiRead}  Fancy text viewer@{PAR}
@{" HexRead  " link HexRead}  Binary or Hexadecimal file viewer@{PAR}
@{" LoopPlay " link LoopPlay}  Normally associated with playing sounds in loops@{PAR}
@{" Play     " link Play}  Playing sounds@{PAR}
@{" Read     " link Read}  Simple text viewer or viewer contents of archives@{PAR}
@{" Show     " link Show}  Picture viewer@{PAR}
@{LINDENT 1}

@{FG highlight}User Events:@{FG text}@{PAR}

The terms @{" User1, User2, User3, and User4 " link User1} may seem cryptic, but
they are here to give you flexibility. Each of the preceding
commands has an implied usage, but you may have an application
which doesn't really mean any of these. In that case, you can
decide that one of these User Events means "Perform this special
operation".@{PAR}

Directory Opus' default configuration employs User1 for extracting
from archives.@{PAR}

@ENDNODE
@NODE 3.11 "Configuration: File Class Manager"
@{LINDENT 1}

@{b}3.11 - File Class Manager@{ub}@{PAR}

File Class management is handled by a menu accessible from the Filetype
manager screen that offers management tools and storage options:@{PAR}
@{LINDENT 4}


@{i}New @{ui}@{PAR}

Selecting this menu option allows you to create a new File class
definition.@{PAR}

@{i}Edit @{ui}@{PAR}

This will open a requester showing you all the currently defined
File Classes. To pick one to edit, simply select it. You will then
be brought to the @{" File Class editor " link 3.12}. To abort press cancel.@{PAR}

Once you have made a filetype entry based on a
@{" File Class definition " link 3.12.1.fcid} then you must use the Edit Class button
on the filetype editor screen.@{PAR}

When you make a Filetype, it uses a copy of the File Class in the
actual filetype entry. This had several important results. Once a
Filetype is made, you can edit its File Class definition without
changing the original definition. The Edit Class button on the
filetype editor allows you to so this. Selecting Edit from the
Classes Menu allows you to edit the original File Class
Definition. This will not automatically update any Filetypes which
used the original definition. You can even delete the original
File Class without affecting a filetype which used it.@{PAR}

@{i}Duplicate @{ui}@{PAR}

This allows you to create a new File Class based on an already
defined File Class.@{PAR}

@{i}Delete @{ui}@{PAR}

This will bring up a requester allowing you to select a File Class
to clear from memory. Simply select the File Class to delete and
respond Yes to the confirming requester. Press Cancel to abort
deleting.@{PAR}

@{i}Open @{ui}@{PAR}

With this you can import File Class definitions from a file.@{PAR}

@{i}Save @{ui}@{PAR}

Save the current File Classes to their default place on disk.@{PAR}

@{i}Save As... @{ui}@{PAR}

Save the current File Class to a specific file on disk.@{PAR}

@{i}Clear @{ui}@{PAR}

Clear all File Classes definitions from memory.@{PAR}


@ENDNODE
@NODE 3.12 "Configuration: File Class Editor"
@{LINDENT 1}

@{b}3.12 - File Class Editor@{ub}@{PAR}
@{LINDENT 4}

@{" File Class Editor            " link 3.12.0}@{PAR}
@{" File Class Editor Example    " link 3.12.0.example}@{PAR}
@{" File Class Editor Components " link 3.12.1}@{PAR}
@{" Editing                      " link 3.12.2}@{PAR}
@{" File Class Edit Commands     " link 3.12.3}@{PAR}
@{" Testing Directives           " link 3.12.4}@{PAR}
@{" Movement Directives          " link 3.12.5}@{PAR}

@ENDNODE
@NODE 3.12.0 "Configuration: File Class Editor"
@{LINDENT 1}

@{b}File Class Editor@{ub}@{PAR}

Selecting @{" New " link 3.11}, @{" Edit " link 3.11}, or @{" Duplicate " link 3.11} from the Fileclass manager
menus or clicking Edit class button on the @{" Filetypes Editor " link 3.10} brings
up the File Class Editor.@{PAR}

This screen is the most complex section of ConfigOpus. It even looks
scary, but don't worry, it is rather simply once you get to know it.
it. The best way to describe this screen is to start at the top and go
down form there.@{PAR}
@{LINDENT 4}

@{" File viewer " link 3.12.0.file}@{PAR}
@{" Decimal/Hex " link 3.12.0.dec}@{PAR}
@{" An example  " link 3.12.0.example}@{PAR}

@ENDNODE
@NODE 3.12.0.file "Configuration: File Class Editor"
@{LINDENT 1}

@{b}File viewer@{ub}@{PAR}

The field viewer at the top of the screen is simply a file viewer. To
view a file, type its name into the field or click on the magnifying-
glass to bring up a file requester. The file selected will appear below
the field. It will be displayed in Hex/ASCII format similar to the
@{" HexRead " link HexRead} command in Directory Opus itself.@{PAR}

You may wonder why we have a file viewer on this screen. We have found
that when creating a new File Class definition it is useful to have a
way to look at files, since you are trying to describe to Directory
Opus a way of identifying files.@{PAR}

@ENDNODE
@NODE 3.12.0.dec "Configuration: File Class Editor"
@{LINDENT 1}

@{b}Decimal/Hex@{ub}@{PAR}

To the right of the file viewer is a button that cycles from Decimal to
Hex. This button tells ConfigOpus in what format to display the
Position and Offset information in the two read-only fields below the
cycle button.@{PAR}

@ENDNODE
@NODE 3.12.0.example "Configuration: File Class Editor"
@{LINDENT 1}

@{b}An Example@{ub}@{PAR}

The simplest way to show how this all works is with an example. Select
the field "C:ED" (by either typing into the field or using the
magnifying-glass file requester).@{PAR}

The format of the data in the file viewer is as follows: The first
column is the address into the file we are looking at. The next four
columns are 16 bytes of data from the file in hexadecimal format. The
last column is simply those 16 bytes in ASCII format. Where there is a
byte that '00' or null we display it in ASCII as a period.@{PAR}

Position your mouse pointer over the 'F3' characters and press the left
mouse button. A cursor will appear on 'F3' and the position field
(read-only) will be filled in with '000000003'. This means that the
cursor is positioned on the 4th byte in the file (remember: byte
locations are zero relative, that is, first byte is at location zero).
If you click the cycle button above the position read-only field and
change it to Hex then the position will be filled in with '$000000003'
which is hexadecimal for three. You can move the cursor around in the
file with either the mouse pointer (simply select another place in the
file) or the cursor keys.@{PAR}

Now double click on the 'F3' characters. This time the characters
change colour. They are now the position from which offsets are
computed. Move the cursor by pressing the down key a few times and you
will notice the offset read-only field contains the offset from the
double-click position.@{PAR}

@ENDNODE
@NODE 3.12.1 "Configuration: File Class Editor"
@{LINDENT 1}

@{b}File Class Editor Components@{ub}@{PAR}

Now we go off to the real power house of Directory Opus.@{PAR}
@{LINDENT 4}

@{" File Class                           " link 3.12.1.fc}@{PAR}
@{" Class ID                             " link 3.12.1.cid}@{PAR}
@{" File Class identification definition " link 3.12.1.fcid}@{PAR}

@ENDNODE
@NODE 3.12.1.fc "Configuration: File Class Editor/Components"
@{LINDENT 1}

@{b}File Class@{ub}@{PAR}

The field below the file viewer is for the name of the File Class. This
is for the name of the File Class.@{PAR}

@ENDNODE
@NODE 3.12.1.cid "Configuration: File Class Editor/Components"
@{LINDENT 1}

@{b}Class ID@{ub}@{PAR}

The Class ID will appear beside the Filetype in the Filetype manager
screen and is a shorthand way for Directory Opus to write the name for
the file class.@{PAR}

@ENDNODE
@NODE 3.12.1.fcid "Configuration: File Class Editor/Components"
@{LINDENT 1}

@{b}File Class identification definition@{ub}@{PAR}

Underneath the File Class and Class ID fields is the File Class
identification definition. This is a series of actions that Directory
Opus will perform in order to identify a file class. The action may be
as simple as matching a filename to a pattern or as complex as
scanning an IFF form looking for data in a specific IFF chunk. @{PAR}

Below the list is a magnifying-glass, a read-only field and an argument
field. These are used for @{" editing " link 3.12.2} the File Class identification
definition.@{PAR}
@{LINDENT 4}

@{i}New entry @{ui}@{PAR}

Creates a new entry in the File Class definition script.@{PAR}

@{i}Duplicate @{ui}@{PAR}

Duplicates the current File Class definition script line. The copied
line is inserted after the current line.@{PAR}

@{i}Swap @{ui}@{PAR}

Lets you swap the position of the two File Class definition script lines.@{PAR}

@{i}Delete @{ui}@{PAR}

Will let you delete the current line.@{PAR}

@ENDNODE
@NODE 3.12.2 "Configuration: File Class Editor"
@{LINDENT 1}

@{b}Editing@{ub}@{PAR}

To edit a line simply click on it, and the read-only and argument
fields will be filled in. To change the command in the read-only field,
click on the magnifying-glass button and a list of other commands will
be displayed. Select the one you want or press Cancel to abort.@{PAR}

The general structure of the File Class definition script is that there
is a clause or a sequence of clauses that describe what should be
considered a matching file for a given filetype. There are only two
directives that delimit clauses: @{" And " link 3.12.3} and @{" Or " link 3.12.3}. They are used to tell
the system what to do if a clause fails or succeeds.@{PAR}

When all the clauses are finished and the result is true then the file
is of the right type.@{PAR}

We would suggest looking at the predefined File Classes to get an idea
of the type of thing you can do with this system.@{PAR}

@ENDNODE
@NODE 3.12.3 "Configuration: File Class Editor"
@{LINDENT 1}

@{b}File Class Edit Commands@{ub}@{PAR}
@{LINDENT 4}

@{i}And @{ui}@{PAR}

If the preceding clause succeeds, then also do this clause, otherwise
skip to the next clause. If the preceding clause executed did not
succeed, then execution stops and the file does not match.@{PAR}

@{i}Or @{ui}@{PAR}

If the preceding clause fails then do this clause, otherwise skip to
the next clause.

@ENDNODE
@NODE 3.12.4 "Configuration: File Class Editor"
@{LINDENT 1}

@{b}Testing directives@{ub}@{PAR}
@{LINDENT 4}

@{" Match        " link 3.12.4.Match}  Match text or $hex.@{PAR}
@{" MatchI       " link 3.12.4.MatchI}  Match text (case insensitive)@{PAR}
@{" MatchBits    " link 3.12.4.MatchBits}  MatchBits HSPARWED@{PAR}
@{" MatchComment " link 3.12.4.MatchComment}  MatchComment text@{PAR}
@{" MatchDate    " link 3.12.4.MatchDate}  MatchDate dates@{PAR}
@{" MatchName    " link 3.12.4.MatchName}  MatchName filename@{PAR}
@{" MatchSize    " link 3.12.4.MatchSize}  MatchSize > or < or = integer@{PAR}

@ENDNODE
@NODE 3.12.4.Match "Configuration: File Class Editor/Testing Directives"
@{LINDENT 1}

@{b}Match: Match text or $hex.@{ub}@{PAR}

This states that a sequence of bytes starting at the current file
offset must match the given pattern. To match a single unknown
character when text is given, use the ? character. To match a single
unknown byte when $hex is given use two of them (??). You can also use
\\xxx syntax in text to specify ASCII characters by their decimal
number. A \\009 would be a tab character, a \\114 would be the lower
case r.@{PAR}
@{LINDENT 4}


Example:@{PAR}

Match $000003F3          (executables start with these bytes)@{PAR}
Match FORM????ILBM       (the way a IFF ILBM picture starts)@{PAR}
Match Hey\\009Overthere   ("Hey" then a tab then "Overthere")@{PAR}
@{LINDENT 1}


Note:@{PAR}

The "Match" and @{" MatchI " link 3.12.4.MatchI} testing directives will
move the "file position index". Directory Opus normally examines a file beginning
at position zero. But once a "Match" instruction was executed, further
@{" testing directives " link 3.12.4} will start examing the file directly behind
the bytes that were used in the previous instruction!@{PAR}
@{LINDENT 4}


Example:@{PAR}

If you want to check for a file that starts with either@{PAR}
"DirOpus" or "DOpus", the following would NOT work:@{PAR}

Match DirOpus@{PAR}
Or@{PAR}
Match DOpus@{PAR}

You would have to do it like this instead:@{PAR}

Match DirOpus@{PAR}
Or@{PAR}
MoveTo 0@{PAR}
Match DOpus@{PAR}

@ENDNODE
@NODE 3.12.4.MatchI "Configuration: File Class Editor/Testing Directives"
@{LINDENT 1}

@{b}MatchI: Match text (case insensitive).@{ub}@{PAR}

This works exactly like the @{" Match " link 3.12.4.Match} testing directive, but
it is @{b}not@{ub} case-sensitive (whereas "Match" is).@{PAR}
@{LINDENT 4}


Example:@{PAR}

MatchI \@database (AGuide files usually start with "\@DATABASE" or "\@database")@{PAR}
MatchI <html>    (HTML files should start with "<HTML>" or "<html>")@{PAR}

@ENDNODE
@NODE 3.12.4.MatchBits "Configuration: File Class Editor/Testing Directives"
@{LINDENT 1}

@{b}MatchBits HSPARWED@{ub}@{PAR}

This tests the file's @{" protection bits " link 2.1 10}. To see if a bit is set, put a
+ before the character. To see if the bit is unset use the -.@{PAR}
@{LINDENT 4}


Example:@{PAR}

MatchBits +RW     - read write must be on, others don't matter@{PAR}
MatchBits -E      - executable must be off, others don't matter@{PAR}
MatchBits +RW -E  - read, write must be on and no executable@{PAR}

@ENDNODE
@NODE 3.12.4.MatchComment "Configuration: File Class Editor/Testing Directives"
@{LINDENT 1}

@{b}MatchComment text@{ub}@{PAR}

Simply compare the text given against the comment of the file. Any
valid AmigaDOS @{" wildcard pattern " link WldCrdPat} is useable here.@{PAR}
@{LINDENT 4}


Example:@{PAR}

MatchComment Silly_Picture (file with silly_picture as a comment)
MatchComment #?vikki#? (any file with vikki in its comment)

@ENDNODE
@NODE 3.12.4.MatchDate "Configuration: File Class Editor/Testing Directives"
@{LINDENT 1}

@{b}MatchDate dates@{ub}@{PAR}

Test the date of the file against a date. For information about date
strings or ranges see the @{" Select " link Select} command.@{PAR}
@{LINDENT 4}


Example:@{PAR}

MatchDate 08-Sept-92@{PAR}
MatchDate < 10-Jan-92@{PAR}

@ENDNODE
@NODE 3.12.4.MatchName "Configuration: File Class Editor/Testing Directives"
@{LINDENT 1}

@{b}MatchName filename@{ub}@{PAR}

The filename must match the character pattern given. Any valid AmigaDOS
@{" wildcard " link WldCrdPat} pattern is useable here.@{PAR}
@{LINDENT 4}


Example:@{PAR}

MatchName #?.ilbm@{PAR}
MatchName *.lzh@{PAR}

@ENDNODE
@NODE 3.12.4.MatchSize "Configuration: File Class Editor/Testing Directives"
@{LINDENT 1}

@{b}MatchSize > or < or = integer@{ub}@{PAR}

Test the size of the file against a value.@{PAR}
@{LINDENT 4}


Example:@{PAR}

MatchSize > 1000@{PAR}

@ENDNODE
@NODE 3.12.5 "Configuration: File Class Editor"
@{LINDENT 1}

@{b}Movement directives@{ub}@{PAR}

A failure of any Movement directives causes the clause to fail.@{PAR}
@{LINDENT 4}

@{" MoveTo     " link 3.12.5.MoveTo}  MoveTo ByteLocation@{PAR}
@{" Move       " link 3.12.5.Move}  Move ByteOffset@{PAR}
@{" SearchFor  " link 3.12.5.SearchFor}  Search For text or $hex@{PAR}

@{" An Example " link 3.12.5.Example}@{PAR}

@ENDNODE
@NODE 3.12.5.MoveTo "Configuration: File Class Editor/Movement Directives"
@{LINDENT 1}

@{b}MoveTo - MoveTo ByteLocation@{ub}@{PAR}

Move to a specific byte offset from the beginning of the file.
Initially you are always at the beginning of the file, but you may have
been moved in a previous clause, so you might want to put a MoveTo at
the beginning of a clause in order to know exactly where you are.@{PAR}
@{LINDENT 4}


Example:@{PAR}

MoveTo 0 (back to beginning of the file)@{PAR}
MoveTo 100 (move to the 101st byte of the file)@{PAR}

@ENDNODE
@NODE 3.12.5.Move "Configuration: File Class Editor/Movement Directives"
@{LINDENT 1}

@{b}Move - Move ByteOffset@{ub}@{PAR}

Move to a byte relative to the current file offset.@{PAR}
@{LINDENT 4}


Example:@{PAR}

Move 16 (move sixteen bytes forward into the file)@{PAR}
Move -4 (move back four bytes from where we are)@{PAR}

@ENDNODE
@NODE 3.12.5.SearchFor "Configuration: File Class Editor/Movement Directives"
@{LINDENT 1}

@{b}SearchFor - Search For text or $hex@{ub}@{PAR}

Search (starting at the current file offset) for a certain byte pattern
that matches the given pattern. See the @{" Match " link 3.12.4.Match} command
for valid options fro this directive. If the match occurs, then the
current file position will be the first character matched.@{PAR}
@{LINDENT 4}


Example:@{PAR}

SearchFor CMAP (look for the 'CMAP', position on the 'C')@{PAR}
SearchFor M.K. (search for 'M.K.", position on the 'M')@{PAR}

@ENDNODE
@NODE 3.12.5.Example "Configuration: File Class Editor/Movement Directives"
@{LINDENT 1}

@{b}An Example@{ub}@{PAR}

One example of usage is the file class 24bit picture.@{PAR}
@{LINDENT 4}


Match FORM????ILBM (file must start with these characters) @{PAR}
And (if the previous cause is true then do the following)@{PAR}
SearchFor BMHD (then search for the BMHD chunk ID)@{PAR}
Move 16 (move sixteen bytes into the file)@{PAR}
Match $18 (this must be 24 (or $18 in hex) to be a 24bit picture.)@{PAR}

@ENDNODE
@NODE 3.13 "Configuration: Hotkeys Manager"
@{LINDENT 1}

@{b}Hotkeys Manager@{ub}@{PAR}

Directory Opus can have an unlimited number of Hotkeys defined. Hotkeys
are systematic global key definitions. These keys are available from
every application you run, as long as Directory Opus is running or
@{" iconified " link 1.9.1.Iconify}. If Directory Opus is busy doing something else (i.e.
copying files, etc.) then the key's operation will start up as soon as
Directory Opus has finished. Hotkeys are implemented via Commodities
and are controllable via the Commodities Exchange program (see your
Amiga manual).@{PAR}

There are six buttons across the bottom of the screen. Some of these
buttons stay selected when selected with the left mouse button. For
instance, Delete will stay selected to remind your that you are now in
delete mode. To leave this mode, select Delete again. The buttons that
work in this fashion are Duplicate, Swap and Delete.@{PAR}
@{LINDENT 4}


@{i}New Hotkey @{ui}@{PAR}

Takes you to the @{" Hotkey editor " link 3.14} so your can define a new Hotkey.@{PAR}

@{i}Duplicate @{ui}@{PAR}

Duplicates a Hotkey. You can abort the copy by simply turning off
duplication mode selecting Duplicate again.@{PAR}

@{i}Swap @{ui}@{PAR}

Allows you to swap the order of the two Hotkeys. Remember that the
first Hotkey is seen first, so if you have two Hotkey entries
defined to the same key sequence, only the first one will be seen.
To get out of swap mode, select Swap again.@{PAR}

@{i}Delete @{ui}@{PAR}

After asking for confirmation, deletes Hotkeys. To get out of
delete mode, select Delete again.@{PAR}

@{i}Okay and Cancel: @{ui}@{PAR}

These allow you to say either "OK, let's use these settings and go
back to Directory Opus", or "Oops! Forget all that, and let's get
out of here!"@{PAR}
@{LINDENT 1}


The Default or Open... menu items in the Configure menu allow you to
import Hotkeys from either the default configuration or a configuration
file from disk.@{PAR}

To edit a Hotkey, make sure that you are not in Duplicate, Swap or
Delete mode, them simply select it. You will then be taken to the
@{" Hotkey editor " link 3.14} screen.@{PAR}

@ENDNODE
@NODE 3.14 "Configuration: Hotkeys Editor"
@{LINDENT 1}

@{b}3.12 - Hotkeys Editor@{ub}@{PAR}
@{LINDENT 4}


@{i}Name @{ui}@{PAR}

This field is simply a name for the Hotkey and can contain
anything. Directory Opus only uses this as a label so that you
will know what the Hotkey does.@{PAR}

@{i}Hotkey @{ui}@{PAR}

Hotkey is a display area for the Hotkey sequence. It shows the
defined Hotkey or is empty if one has not been defined.@{PAR}

@{i}Sample @{ui}@{PAR}

To modify the Hotkey, select this button. While the Sample button
is selected, any keys, along with any qualifiers you press will be
inserted in the Hotkey field. To turn off Sample mode, select the
Sample button again.@{PAR}

To clear the Hotkey sequence simply select the Sample button with
the right mouse button.@{PAR}
@{LINDENT 1}


The remaining parts of this section is described in the
@{" Command Editor " link 3.6} section.@{PAR}

@ENDNODE
@NODE 3.15 "Configuration: Menus Manager"
@{LINDENT 1}

@{b}3.15 Menus Manager@{ub}@{PAR}

This section allows you to configure the menus. There are 100 custom
menu items, arranged as five menus of twenty items each. The Menu
Configuration screen displays the five menus, with the menu titles at
the top.@{PAR}

All the menu items in each menu strip are not displayed at once because
space is limited on the screen, only a certain number are visible at a
time. To move through the menu items, use the slider at the right of
the screen.@{PAR}

There are ten buttons across the bottom of the screen. Some of these
buttons stay selected when selected with the left mouse button. For
instance, Delete Item will stay selected to remind you that you are now
in Delete Item mode. To leave this mode, select Delete Item again. All
buttons except Okay and Cancel work in this fashion.@{PAR}
@{LINDENT 4}

@{" Copy menu   " link 3.15.Copy_menu}          @{" Insert item " link 3.15.Insert_item}@{PAR}
@{" Swap menu   " link 3.15.Swap_menu}          @{" Copy item   " link 3.15.Copy_item}@{PAR}
@{" Delete menu " link 3.15.Delete_menu}          @{" Swap item   " link 3.15.Swap_item}@{PAR}
@{" Sort menu   " link 3.15.Sort_menu}          @{" Delete item " link 3.15.Delete_item}@{PAR}
@{LINDENT 1}

The last two buttons on this screen (lower right corner) are the Okay
and Cancel buttons. These allow you to say, "OK, let's use all these
custom menus changes and go back to ConfigOpus' main screen," or "Oops!
Forget all this and let's just leave."@{PAR}

The Default or Open... menu items in the Configure menu allow you to
import menus from either the default configuration or a configuration
file from disk.@{PAR}

The Paint Mode menu provides an easy way of changing several menu item colours
without invoking the @{" item editor " link 3.16} each time.@{PAR}

When you select it, a requester will appear, asking you for the fore- and
background color you want to use. If you click on OK, the Paint Mode will
be activated. You can now apply the selected colors to any displayed menu item by simply
clicking on it.@{PAR}

To leave Paint Mode, just select it again. A checkmark in front of the menu item
indicates that Paint Mode is active at the moment.@{PAR}

To edit a menu item, make sure you are not in Copy menu, Swap menu,
Delete menu, Sort menu, Insert item, Copy item, Swap item or Delete
item mode. Then simply select it, and you will be taken to the menu
@{" item editor " link 3.16} screen.@{PAR}

@ENDNODE
@NODE 3.15.Copy_menu "Configuration: Menus Manager"
@{LINDENT 1}

@{b}Copy menu@{ub}@{PAR}

Copies the contents of one menu to another. When you have selected this
option, select a menu item in the actual menu you wish to copy, and
then a menu item in the menu you want to copy the first menu to.@{PAR}

@ENDNODE
@NODE 3.15.Swap_menu "Configuration: Menus Manager"
@{LINDENT 1}

@{b}Swap menu@{ub}@{PAR}

Swaps the contents of two menus. It works in the same way as the
@{" Copy menu " link 3.15.Copy_menu} command, except that the contents of the second
menu are exchanged and not replaced.@{PAR}

@ENDNODE
@NODE 3.15.Delete_menu "Configuration: Menus Manager"
@{LINDENT 1}

@{b}Delete menu@{ub}@{PAR}

Removes all commands from one of the five menus. Select a menu item
in the appropriate menu and a requester will appear to verify the
operation. If you select Okay, the contents of the menu will be
deleted.@{PAR}

@ENDNODE
@NODE 3.15.Sort_menu "Configuration: Menus Manager"
@{LINDENT 1}

@{b}Sort menu@{ub}@{PAR}

Sorts the contents of each selected menu alphabetically by name.@{PAR}

@ENDNODE
@NODE 3.15.Insert_item "Configuration: Menus Manager"
@{LINDENT 1}

@{b}Insert item@{ub}@{PAR}

Allows you to insert a new item between two existing items. Select the
item in front of which you want the new item to be inserted.@{PAR}

@ENDNODE
@NODE 3.15.Copy_item "Configuration: Menus Manager"
@{LINDENT 1}

@{b}Copy item@{ub}@{PAR}

Allows you to copy one menu item to another. When you have selected
this option, select the menu item to copy, and then the menu item to
copy it to.@{PAR}

@ENDNODE
@NODE 3.15.Swap_item "Configuration: Menus Manager"
@{LINDENT 1}

@{b}Swap item@{ub}@{PAR}

Allows you to swap two menu items. It works in the same way as the
@{" Copy item " link 3.15.Copy_item} command, except that the second item is
exchanged and not replaced.@{PAR}

@ENDNODE
@NODE 3.15.Delete_item "Configuration: Menus Manager"
@{LINDENT 1}

@{b}Delete item@{ub}@{PAR}

Deletes menu items. Select the menu item you wish to delete. All menu
items below it will be moved up to fill the empty space.@{PAR}

@ENDNODE
@NODE 3.16 "Configuration: Menus Editor"
@{LINDENT 1}

@{b}3.16 - Menus Editor@{ub}@{PAR}

At the top of the menu item edit screen is an example of what the
current menu item looks like. The palettes on either side of the
example allow you to select the Foreground and Background colours of
the menu item.
@{LINDENT 4}


@{i}Name @{ui}@{PAR}

This field allows you to modify the name that appears on the menu
item, and is limited to 63 characters.@{PAR}

@{i}Shortcut key @{ui}@{PAR}

Shortcut key is a display area for the Shortcut key sequence. The
Shortcut key gives the keyboard equivalent for this menu item. The
Sample button allows you to modify the shortcut key sequence.@{PAR}

@{i}Sample @{ui}@{PAR}

To modify the Shortcut key, select this button. Any keys, along
with any qualifiers you press will be inserted in the Shortcut key
field. To turn off Sample mode, select the Sample button again.@{PAR}

To clear the Shortcut key sequence simply select the Sample button
with the right mouse button.@{PAR}
@{LINDENT 1}


The remaining part of this requester is described in the
@{" Command Editor " link 3.6} section.@{PAR}

@ENDNODE
@NODE 3.17 "Configuration: Operation"
@{LINDENT 1}

@{b}3.17 - Operation@{ub}@{PAR}

The Operations Configuration Screen gives you complete control over the
way each of the listed operations is performed. You can cover any
contingency by specifying precisely how you want each operation to be
carried out in any situation that might arise. When you select one of
the buttons to the left of the screen, requesters will appear asking
you how to proceed.@{PAR}
@{LINDENT 4}


@{" Copy " link 3.17.1}@{PAR}

This button allows you to check the amount of space available for
copying files and directories, and to set the archive bits once
the copying is finished. You are able to choose which parts of the
file information need to be copied. You are also given options to
consider if the file being copied already exists in the
destination.@{PAR}

@{" Date format " link 3.17.2}@{PAR}

With this button you may choose between the Amiga system's default
or three other formats for displaying the date.@{PAR}

@{" Delete " link 3.17.3}@{PAR}

Without the reminders that this button summons, you might lose
some very valuable information.@{PAR}

@{" Error check " link 3.17.4}@{PAR}

You may choose either DOS requesters or the more comprehensive
Directory Opus error requesters when you select this button.@{PAR}

@{" General " link 3.17.5}@{PAR}

This button displays miscellaneous flags.@{PAR}

@{" Icons " link 3.17.6}@{PAR}

With this button you may decide whether to create a drawer icon,
whether each file's icon undergoes every change that befalls its
file, and whether an icon is selected automatically with its file.@{PAR}

@{" List Format " link 3.17.7}@{PAR}

The screen summoned by this button gives you control of the format
of the lists in both screens.@{PAR}

@{" Update" link 3.17.8}@{PAR}

This button offers various features.@{PAR}

@{i}Okay and Cancel: @{ui}@{PAR}

These allow you to say either "OK, let's use these settings and go
back to Directory Opus", or "Oops! Forget all that, and let's get
out of here!"@{PAR}

@ENDNODE
@NODE 3.17.1 "Configuration: Operation/Copy"
@{LINDENT 1}

@{b}Copy@{ub}@{PAR}

@{i}Check destination's free space before starting @{ui}@{PAR}

----------@{PAR}

Important Note!@{PAR}

This option is heavily outdated. It only knowns about FFS partitions with
512 Bytes per block. It will fail (in other words: report wrong results) on any
partition that does not match these specs exactly. Always disable this option unless
you're sure that all of your partitions are FFS, 512 Bytes/block!@{PAR}

----------@{PAR}

This causes Directory Opus to check that the destination directory
has enough free space in it before attempting to copy selected
files and/or directories. If Directory Opus doesn't think that all
selected entries will fit in the destination directory, it will
alert you with a requester, and give you the option of abandoning
the copy process. If any selected directories do not have sizes
displayed for them, Directory Opus will ask you if you wish it to
perform a byte count on these directories before seeing whether or
not they will fit.@{PAR}

@{i}Set archive bit of source after finishing @{ui}@{PAR}

After Directory Opus copies a file, the original file will get its
archive bit set to true. This means that the file had been
archived.@{PAR}

@{i}Also copy source's... @{ui}@{PAR}

These flags tell Directory Opus that when it copies a file, it
must also copy these parts of the file information as well. You
can have all, none, or any combination of the following selected:@{PAR}
@{LINDENT 4}

 - Datestamp@{PAR}

 - @{" Protection bits " link 2.1 10}@{PAR}

 - Comment@{PAR}
@{LINDENT 1}

@{i}What to do when a file already exists... @{ui}@{PAR}

These flags tell Directory Opus what to do if a file that is being
copied already exists in the destination. Only one of these may be
selected. You have four options:@{PAR}
@{LINDENT 4}

@{i}Always replace files @{ui}@{PAR}

Replaces the original file regardless.@{PAR}

@{i}Never replace files @{ui}@{PAR}

Will never replace the original file.@{PAR}

@{i}Replace only older files @{ui}@{PAR}

Replace the original file only is the file to be copied has a
more recent last modification date.@{PAR}

@{i}Ask before replacing @{ui}@{PAR}

Asks the user what to do if the file already exists.@{PAR}

@ENDNODE
@NODE 3.17.2 "Configuration: Operation/Date Format"
@{LINDENT 1}

@{b}Date Format@{ub}@{PAR}

@{i}Date Format... @{ui}@{PAR}

This tells Directory Opus how to format dates. The Amiga's
operating system uses the first (DD-MMM-YY) by default, but you
may choose whichever one you prefer:@{PAR}
@{LINDENT 4}

- DD-MMM-YY (22-Sep-92)@{PAR}

- YY-MM-DD(92-09-22)@{PAR}

- MM-DD-YY(09-22-92)@{PAR}

- DD-MM-YY(22-09-92)@{PAR}
@{LINDENT 1}

@{i}Name substitution (Today, Tomorrow, etc) @{ui}@{PAR}

Causes words like Today, Tomorrow or Tuesday to be substituted
for a date, if appropriate.@{PAR}

@{i}12 hour clock @{ui}@{PAR}

This allows you to choose whether the clock format used by
Directory Opus be displayed in 12 hour or 24 hour format.@{PAR}

@ENDNODE
@NODE 3.17.3 "Configuration: Operation/Delete"
@{LINDENT 1}

@{b}Delete@{ub}@{PAR}

@{i}Ask before commencing delete @{ui}@{PAR}

Tells Directory Opus to check with you before actually starting
to delete. This is a rather useful everyday option because it's
always better to be safe than sorry.@{PAR}

@{i}Ask before deleting files @{ui}@{PAR}

Tells Directory Opus to ask for confirmation before deleting
each file.@{PAR}

@{i}Ask before deleting non-empty directories @{ui}@{PAR}

Tells Directory Opus to ask for confirmation before deleting
directories that have items in them.@{PAR}

@{i}Ignore the delete protection bit @{ui}@{PAR}

When deleting, this sets the Delete protection bit on all files
that do not have it set. This means that the files protected
against deletion will be deleted anyway.@{PAR}

@ENDNODE
@NODE 3.17.4 "Configuration: Operation/Error Check"
@{LINDENT 1}

@{b}Error Check@{ub}@{PAR}

@{i}Enable DOS requesters @{ui}@{PAR}

Disables AmigaDOS requesters that would appear on the Directory
Opus screen (disk is write protected, etc.). Instead, you will
only see an error message appear in Directory Opus' status bar.@{PAR}

@{i}Enable Opus error requesters @{ui}@{PAR}

Causes Directory Opus to open its own error requester when an
error is encountered. This requester contains more information
than the standard AmigaDOS requester.@{PAR}

@ENDNODE
@NODE 3.17.5 "Configuration: Operation/General"
@{LINDENT 1}

@{b}General@{ub}@{PAR}

@{i}Click-M-Click drag @{ui}@{PAR}

This enables @{" Click-Drag-Release " link glos}. If disabled, only
@{" Click-M-Click " link glos} is available.@{PAR}

@{i}Display info @{ui}@{PAR}

Makes Directory Opus behave as it did in version 1, by displaying
a file's @{" protection bits " link 2.1 10}, datestamp and comment in the status
bar. Directory Opus now displays these in the directory windows,
and keeps a count of selected files, etc. in the status bar
instead. If you prefer the old-style display, turn Display info
on. All file information will be displayed in the status bar as
you select entries, as well as in the directory windows. With this
turned on, you can use the @{" GetSizes " link GetSizes} Command to view the count
of selected entries.@{PAR}

@{i}File double-click @{ui}@{PAR}

Directory Opus will interrogate a file that is double-clicked on
with the left mouse button, and will perform the default action
for that Filetype.@{PAR}

You may define your own Filetypes, and specify what action is to
be performed on them. However, there are also several hard-coded
Filetypes. These are IFF ILBM pictures and brushes, icons, fonts,
IFF 8SVX sounds, and Amiga executable programs.@{PAR}

If a file does not match any of the user-defined Filetypes, it is
checked to see if is one of the hard-coded types. In that case,
the default action for these Filetypes is performed. If a file
does not match any Filetypes, user-defined or otherwise, it is
treated as a text file, and loaded into the @{" text viewer " link 2.7}. If any
ANSI control sequences are detected, these will be displayed
correctly. If the file contains any non-text characters, it will
be read in hexadecimal format.@{PAR}

@{i}Window slider activate @{ui}@{PAR}

Causes a directory window to become active whenever its sliders or
arrow buttons are selected. If this option is not enabled,
selecting the sliders or arrow buttons of a directory will not
cause it to become active.@{PAR}

@ENDNODE
@NODE 3.17.6 "Configuration: Operation/Icons"
@{LINDENT 1}

@{b}Icons@{ub}@{PAR}

@{i}Create icons with directories @{ui}@{PAR}

Creates a drawer icon whenever you create a directory with the
@{" MakeDir " link 1.6.Makedir} Command.@{PAR}

@{i}Perform all actions on icons as well @{ui}@{PAR}

Whatever happens to a file will happen to that file's icon as
well. For instance, if you delete the file DATA, DATA.info (if it
exists) will be deleted too. If you rename the file FROG to PIG,
then FROG.info (if it exists) will be renamed as PIG.info
automatically.@{PAR}

@{i}Select icons automatically @{ui}@{PAR}

Has similar results to "Perform all actions on icons as well",
except that whenever you select a file, its associated .info file
(if it exists) is also selected.@{PAR}

@ENDNODE
@NODE 3.17.7 "Configuration: Operation/List Format"
@{LINDENT 1}

@{b}List Format@{ub}@{PAR}
@{LINDENT 4}

@{" Format of the list in the  " link 3.17.7.format}@{PAR}
@{" Available display items... " link 3.17.7.available}@{PAR}
@{" Displayed lengths          " link 3.17.7.displayed}@{PAR}
@{" Selected display items...  " link 3.17.7.selected}@{PAR}
@{" Entry Separation           " link 3.17.7.entry}@{PAR}

@ENDNODE
@NODE 3.17.7.format "Configuration: Operation/List Format"
@{LINDENT 1}

@{b}Format of the list in the@{ub}@{PAR}

This cycle button specifies which directory window you are modifying.
This allows you to have different list formats in each window, but it
does require you to specify the format for each window. If you change
the format (using the buttons described below), and you want it to be
the same for both windows, don't forget to click on this button and
make the corresponding changes to the other window. The options
available are:@{PAR}
@{LINDENT 4}

- Left window@{PAR}

- Right window@{PAR}

@ENDNODE
@NODE 3.17.7.available "Configuration: Operation/List Format"
@{LINDENT 1}

@{b}Available display items...@{ub}@{PAR}

This list allows you to add display items to the Selected display
items... list by clicking on them. An item can only be added once, so
if you click on an item that is already in the list, nothing will
happen. The available display items are:@{PAR}
@{LINDENT 4}

- File name@{PAR}

- File size@{PAR}

- @{" Protection bits " link 2.1 10}@{PAR}

- Creation date@{PAR}

- File comment@{PAR}

- File type@{PAR}

@ENDNODE
@NODE 3.17.7.displayed "Configuration: Operation/List Format"
@{LINDENT 1}

@{b}Displayed lengths@{ub}@{PAR}

The fields allow you to adjust the width of some of these items. The
adjustable lengths are:@{PAR}
@{LINDENT 4}

- File name (max. 64 characters)@{PAR}

- File comment (max. 80 characters)@{PAR}

- File type (max. 40 characters)@{PAR}

@{LINDENT 1}

@{i}Show entries as K/M/G @{ui}@{PAR}

This checkbox lets you decide if you want to have filesizes displayed in bytes
(i.e. "338566") or Kilo/Mega/Gigabytes (i.e. "330K"). The latter needs four chars
less (saving valuable space) and is probably more readable. This setting can be
changed in the @{" PopUp menu " link 1.5.2} too.@{PAR}

@ENDNODE
@NODE 3.17.7.selected "Configuration: Operation/List Format"
@{LINDENT 1}

@{b}Selected display items...@{ub}@{PAR}

When you select an item from the list of Available display items... it
appears here. This allows you to specify exactly what to display. When
you select an item in this list, it places a check mark next to it.
This indicates which item to sort the window list on. Clicking on a
checked item unchecks it. If no items are checked then the directory
window will not be sorted.@{PAR}

The sort item can also be changed 'on the fly' from within DirOpus'
main program. Have a look at the @{" Dir Windows " link 1.5.2} section for further
information.@{PAR}
@{LINDENT 4}


@{i}Reset @{ui}@{PAR}

This button causes the list to reset to the factory default
settings.@{PAR}

@{i}Clear @{ui}@{PAR}

Clicking on this button with the left mouse button clears all
entries, allowing you to start all over again.
Clicking on this button with the right mouse button just clears
the last entry in the list, allowing you to correct a mistake.@{PAR}

@ENDNODE


@NODE 3.17.7.entry "Configuration: Operation/List Format"
@{LINDENT 1}

@{b}Entry Separation@{ub}@{PAR}

@{i}The Cycle Button @{ui}@{PAR}

The cycle button allows you to specify how directories and files
are sorted.@{PAR}
@{LINDENT 4}

- Directories first@{PAR}

- Files first@{PAR}

- Mix files/directories@{PAR}
@{LINDENT 1}

@{i}Reverse Sorting @{ui}@{PAR}

This specifies that the list should be sorted in reverse order.
For instance instead of A coming before B, B would come before A.@{PAR}

The sort method can also be changed 'on the fly' from within
DirOpus' main program. Have a look at the @{" Dir Windows " link 1.5.2} section
for further information.@{PAR}

@ENDNODE
@NODE 3.17.8 "Configuration: Operation/Update"
@{LINDENT 1}

@{b}Update@{ub}@{PAR}

@{i}Operation progress indicator @{ui}@{PAR}

Makes Directory Opus open a progress indicator window when it is
processing files. This window will show you how much percent of the
files are processed already.@{PAR}

@{i}Current file progress indicator (Copy) @{ui}@{PAR}

Adds more information to the above progress indicator window. Now
you will also be informed about the progress on the current file.
This additional information will only be shown during Copy or Move
operations.@{PAR}

@{i}Left-justify filename in status bar @{ui}@{PAR}

Left-justifies filenames in the status bar rather than centering
them as usual.@{PAR}

@{i}Scroll directory window to follow operation @{ui}@{PAR}

Causes the directory windows to scroll, ensuring the visibility
of the current entry being acted upon in an operation. The display
is returned to its original position when the operation is
complete.@{PAR}

@{i}Update free disk space @{ui}@{PAR}

Causes the free space display in the disk name display at the top
of the active directory window to be updated whenever a file is
copied to or deleted from the directory. Otherwise, the directory
is only updated at the end of a complete operation.@{PAR}

@{i}Directory refresh using StartNotify @{ui}@{PAR}

Sets up automatic notification of the currently visible
directories. If the directories are modified outside Directory
Opus (i.e. by another program), Directory Opus will automatically
re-read the directory to reflect the changes.@{PAR}

@{i}Redraw more than a quarter of a page @{ui}@{PAR}

Causes Directory Opus to redraw the window if you move more than
a quarter of a page in either direction. This flag can greatly
speed up movement through directories. Ordinarily, if you use the
sliders to move a directory less than a complete page in either
direction, the directory window will scroll one file at a time.
It is only if you move a complete page or more at once that the
window will actually be redrawn. Although not as pleasing
aesthetically, redrawing is considerably faster, especially in
high-resolution modes.@{PAR}

@{i}Update listview slider while scanning @{ui}@{PAR}

Turns updating the sliders while scanning a directory's content
on or off. Turning it off may result in a slight speedup,
especially for directories containing an extremely big amount of
files.@{PAR}

@ENDNODE
@NODE 3.18 "Configuration: Screen"
@{LINDENT 1}

@{b}Screen@{ub}@{PAR}

The Screen configuration screen allows you to modify the appearance
of the screen to suit you needs and preferences. Requesters
concerning the screen's features will appear when you click on one of
the buttons at the left side of the screen.@{PAR}
@{LINDENT 4}


@{" Arrows " link 3.18.1}@{PAR}

Allows you to specify where the arrows on the sliders used by
Directory Opus will appear.@{PAR}

@{" Colours " link 3.18.2}@{PAR}

Allows you to modify the pen colours of almost all the components
of the Directory Opus screen.@{PAR}

@{" Fonts " link 3.18.3}@{PAR}

Allows you to specify the fonts used in different parts of
Directory Opus.@{PAR}

@{" General " link 3.18.4}@{PAR}

Allows you to specify various options for the screen's appearance.@{PAR}

@{" Palette " link 3.18.5}@{PAR}

Allows you to set the colours of the Directory Opus screen.@{PAR}

@{" Screen mode " link 3.18.6}@{PAR}

Allows you to specify the mode, size and depth of the Directory
Opus screen.@{PAR}

@{" Sliders " link 3.18.7}@{PAR}

Lets you select the position of the @{" Window View Sliders " link 1.5.4} for
each of the directory windows.@{PAR}

@{i}Okay and Cancel: @{ui}@{PAR}

These allow you to say either "OK, let's use these Screen settings
and go back to Directory Opus", or "Oops! Forget all that, and
let's get out of here!"@{PAR}

@ENDNODE
@NODE 3.18.1 "Configuration: Screen/Arrows"
@{LINDENT 1}

@{b}Arrows@{ub}@{PAR}

This screen allows you to specify where the arrows on the sliders used
by Directory Opus will appear. There are three choices for each of the
three slider types. You can also adjust the size of the arrows.@{PAR}

The easiest way to learn how to use this is just to play with it.
Select the slider type by clicking on it, or cycle through the types by
clicking on the cycle button. The selected slider type will be
highlighted.@{PAR}
@{LINDENT 4}


@{i}Adjust size @{ui}@{PAR}

These buttons allow to adjust the width of the arrows in the
selected slider type. You can make these huge if you want.@{PAR}

@ENDNODE
@NODE 3.18.2 "Configuration: Screen/Colours"
@{LINDENT 1}

@{b}Colours@{ub}@{PAR}

This requester allows you to modify the pen colours of almost all the
components of the Directory Opus screen. The number of colours to
choose from are specified in @{" Screen/Screen mode " link 3.18.6} and the colour
palette is specified in @{" Screen/Palette " link 3.18.5}.@{PAR}

A mock-up of the Directory Opus screen is shown, to allow you to see
the results of your colour changes. To select the item you want to
modify, either click on it in the example box, or click the cycle
button at the top of the screen to advance to the next item.@{PAR}

To modify the colours of an item, use the Foreground and Background
palette boxes.@{PAR}

@ENDNODE
@NODE 3.18.3 "Configuration: Screen/Fonts"
@{LINDENT 1}

@{b}Fonts@{ub}@{PAR}

The Screen/Fonts requester allows you to specify the fonts used in
different parts of Directory Opus. When this option is selected for the
very first time, there will be a delay while Directory Opus looks to
see which fonts exist in the system.@{PAR}

There are three lists available at the top of the window:@{PAR}
@{LINDENT 4}
 

@{i}Display item... @{ui}@{PAR}

The items for which you may configure a font are displayed in this
list. Clicking on an item displays the currently selected font and
size in the Font and Size lists. You can then use these lists to
select the desired values for the display item.@{PAR}

@{i}Font... @{ui}@{PAR}

This list contains the list of available fonts. The selected font
for the Display item is highlighted. Click on a font name to
change the selected font.@{PAR}

@{i}Size... @{ui}@{PAR}

This list contains the sizes available for the currently selected
font. The selected size is highlighted. Click on a font size to
change the selected size.@{PAR}
@{LINDENT 1}


An example of the currently selected font and size will be displayed
below these lists.@{PAR}

Some Display items accept non-proportional fonts, and others only
accept 8-point fonts. The list of available fonts will change to filter
out unacceptable fonts.@{PAR}

@ENDNODE


@NODE 3.18.4 "Configuration: Screen/General"
@{LINDENT 1}

@{b}General@{ub}@{PAR}

This requester allows you to specify various options for the screen's
appearance.@{PAR}
@{LINDENT 4}


@{i}Bottom-right tiny buttons @{ui}@{PAR}

Makes the tiny buttons in the lower right of the Directory
Opus' screen visible.@{PAR}

@{i}Button banks sliders @{ui}@{PAR}

Makes sliders appear beside the drive and custom button
banks. These make it easier to scroll through the banks.@{PAR}

@{i}Custom screen window borders @{ui}@{PAR}

Turns on the new style guide compliant look. If Directory Opus
is using its own screen, the window will have style guide
compliant window borders.@{PAR}

@{i}Display status text in title bar @{ui}@{PAR}

Removes the dedicated status bar and instead displays status
text using the OS function SetWindowTitles().@{PAR}

@{i}Draggable requesters @{ui}@{PAR}

All requesters will have a window title bar allowing you to
move it.@{PAR}

@{i}Indicate button has RMB command @{ui}@{PAR}

All buttons with Right Mouse button command will have a
dog-eared upper right corner.@{PAR}

@{i}New-look sliders @{ui}@{PAR}

The sliders adopt the new style of operating system 2.0. Note that their
color is not configurable if this option is turned on.@{PAR}

@ENDNODE
@NODE 3.18.5 "Configuration: Screen/Palette"
@{LINDENT 1}

@{b}Palette@{ub}@{PAR}

The Screen/Palette requester allows you to set the colours of the
Directory Opus screen. A palette box is displayed, allowing you to
select the colours to modify. You can change the colour by using the
sliders to adjust the red, green and blue components. You can also
enter colour values directly, using the string fields.@{PAR}
@{LINDENT 4}


@{i}Presets... @{ui}@{PAR}

There are also several preset colour palettes available, which
you can select just by clicking. The Reset entry will return
the colours to the values they had when you entered this section
(an Undo feature, basically). The Directory Opus default entry
sets the default Directory Opus palette. The Workbench default
entry has the default Workbench colours. The Workbench current
entry is the colours currently set on the Workbench screen.
The other presets are different settings which you can
experiment with at your own leisure.@{PAR}

@ENDNODE
@NODE 3.18.6 "Configuration: Screen/Screen mode"
@{LINDENT 1}

@{b}Screen mode@{ub}@{PAR}

The Screen/Screen Mode requester allows you to specify the mode, size
and depth of the Directory Opus screen.@{PAR}
@{LINDENT 4}


@{i}Display mode... @{ui}@{PAR}

Contains a list of the available Display modes. The modes
available will vary depending upon the monitors currently active
in your system. The characteristics of the selected Display mode
are shown at the bottom of the screen.@{PAR}

There are two special items on the list: @{" Workbench:Use   " link 3.18.6.display.wu} and
@{" Workbench:Clone " link 3.18.6.display.wc}@{PAR}

@{i}Width @{ui}@{PAR}

This field allows you to specify the screen width.@{PAR}

When the Use Default button contains a check, the Width field
cannot be changed. It will, however, display the default value to
be used. When you click on this button, it will allow you to
change the value in the Width field.@{PAR}

When you are using Workbench:Clone, the Use default button
cannot be deselected.@{PAR}

@{i}Height @{ui}@{PAR}

This field allows you to specify the screen Height.@{PAR}

The Use Default button works the same way as with the Width
gadget.@{PAR}

@{i}Colours @{ui}@{PAR}

Depending upon the selected screen mode, the number of colours
will vary from four to sixteen. There are screen modes with a
maximum of less than sixteen. If this is the case, your
selection will be limited.@{PAR}

@{i}Half-height screen @{ui}@{PAR}

This causes the Directory Opus screen to open at half its normal
height, and to be positioned halfway down the display.
With an interlaced screen, this would give you a screen the size
of a normal (non-interlaced) screen, with the screen behind it
still partially visible. Turning on the Half-height screen
option will not modify the system's screen height setting. Note that
this option will not work with certain Graphic cards (i.e. BlizzardVision
or CybervisionPPC).@{PAR}

@ENDNODE
@NODE 3.18.6.display.wu "Configuration: Screen/Screen Mode/Display Mode"
@{LINDENT 1}

@{b}Workbench:Use@{ub}@{PAR}

Causes Directory Opus to open a window on the Workbench screen, and not
to open a custom screen. The width and height of this window are
editable, but the number of colours is fixed at the current Workbench
depth.@{PAR}

@ENDNODE
@NODE 3.18.6.display.wc "Configuration: Screen/Screen Mode/Display Mode"
@{LINDENT 1}

@{b}Workbench:Clone@{ub}@{PAR}

Causes Directory Opus to open a screen in the same mode and exactly the
same size as the Workbench screen. The size of this screen is not
editable, but you may modify the number of colours.@{PAR}

@ENDNODE
@NODE 3.18.7 "Configuration: Screen/Sliders"
@{LINDENT 1}

@{b}Sliders@{ub}@{PAR}

Lets you select the position of the @{" Window View Sliders " link 1.5.4} for each of
the directory windows.@{PAR}

@ENDNODE
@NODE 3.19 "Configuration: System"
@{LINDENT 1}

@{b}System@{ub}@{PAR}

The System configuration screen lets you tell Directory Opus how to run
several operations.@{PAR}
@{LINDENT 4}


@{" AmigaDOS " link 3.19.1}@{PAR}

Allows you to specify how Directory Opus starts up AmigaDOS
programs.@{PAR}

@{" Clocks " link 3.19.2}@{PAR}@{PAR}

Allows you to specify how Directory Opus displays Clock
information.@{PAR}

@{" Directories " link 3.19.3}@{PAR}

Allows you to set various options for Directory operations.@{PAR}

@{" Hotkey " link 3.19.4}@{PAR}

Allows you to specify the Hotkey to activate Directory Opus.@{PAR}

@{" Icons " link 3.19.5}@{PAR}

Allows you to specify the Icons which will be created with the
@{" AddIcon " link 1.6.Add_Icon} command.@{PAR}

@{" Modules " link 3.19.6}@{PAR}

Allows you to specify preloaded external modules.@{PAR}

@{" Show pattern " link 3.19.7}@{PAR}

Allows you to specify files to be shown or excluded form the
directory lists.@{PAR}

@{" Startup " link 3.19.8}@{PAR}

Allows you to specify various startup options.@{PAR}

@{" View & Play " link 3.19.9}@{PAR}

Allows you to configure options for Directory Opus' viewers.@{PAR}

@{i}Okay and Cancel: @{ui}@{PAR}

These allow you to say either "OK, let's use these settings and
go back to Directory Opus", or "Oops! Forget all that, and let's
get out of here!"@{PAR}

@ENDNODE
@NODE 3.19.1 "Configuration: System/AmigaDOS"
@{LINDENT 1}

@{b}AmigaDOS@{ub}@{PAR}

This requester allows you to specify how Directory Opus starts up
AmigaDOS programs.@{PAR}
@{LINDENT 4}


@{i}Shell @{ui}@{PAR}

This field is the AmigaDOS command used to launch programs
that have output windows. It defaults to @{" NewCLI " link NewCli}. If you
wish to use a shell, you could change the default to NewShell.
If you wish to use a WShell, you could change it to NewWsh. The
magnifying-glass button to the left of this field opens a
requester to help you locate the command you wish to use.@{PAR}

@{i}Console @{ui}@{PAR}

This is the console under which all output windows are opened.
It is also used to open a CLI by the @{" NewCLI " link NewCli} command, and by the
@{" Run " link 1.6.Run} command when no files are selected. The console allows you
to specify the size, position and title of the output window. It
follows the standard AmigaDOS format, namely:@{PAR}
@{LINDENT 7}

DEVICE:LeftEdge/TopEdge/Width/Height/Title/Options@{PAR}

DEVICE: This is the device you are using. It is normally CON:@{PAR}

LeftEdge: The left edge of the window (x coordinate, in pixels).@{PAR}

TopEdge:The top edge of the window (y coordinate, in pixels).@{PAR}

Width:The width of the window is pixels.@{PAR}

Height: The height of the window in pixels.@{PAR}

Title:The title of the window.@{PAR}

Options:Some devices allow you to specify optional
parameters (i.e. /Close). The valid parameters
vary, so consult the device's documentation for
details.@{PAR}
@{LINDENT 4}

An example is:@{PAR}
@{LINDENT 7}

CON:20/10/600/180/Directory Opus Output/Close@{PAR}
@{LINDENT 4}

@{i}Start-Up Script @{ui}@{PAR}

This is an AmigaDOS script that will be performed before
Directory Opus launches any programs.@{PAR}

@{i}Priority @{ui}@{PAR}

Main priority allows you to specify the priority at which
Directory Opus itself runs. The default priority is 0, which
means that it peacefully coexists with everything else. Setting
the priority higher means that while Directory Opus will not be
slowed down much by other tasks, the performance of other tasks
will suffer. It is suggested that you set the priority no higher
than 10.@{PAR}

@ENDNODE
@NODE 3.19.2 "Configuration: System/Clocks"
@{LINDENT 1}

@{b}Clocks@{ub}@{PAR}

This Requester allows you to specify how Directory Opus displays Clock
information.@{PAR}
@{LINDENT 4}


@{i}Clock/Memory bar... @{ui}@{PAR}

These flags tell Directory Opus how to format the clock bar at the
bottom of its screen. You can include any combination of these
items, but in some fonts you may not be able to see to all the
items selected because their space may be limited.@{PAR}
@{LINDENT 7}

@{" Memory monitor " link 3.19.2.Clock.Memory}          @{" Date " link 3.19.2.Clock.Date}@{PAR}
@{" CPU monitor    " link 3.19.2.Clock.CPU}          @{" Time " link 3.19.2.Clock.Time}@{PAR}
@{LINDENT 4}

@{i}Show free space as... @{ui}@{PAR}

There are two groups of buttons with this title. One applies to
the Clock/memory bar, and the other applies to the iconified
window. They allow you to specify how the Memory Monitor, when
enabled, will display memory.@{PAR}
@{LINDENT 7}

@{" Bytes free          " link 3.19.2.show.bytes}@{PAR}
@{" Kilo/Megabytes free " link 3.19.2.show.kilo}@{PAR}
@{LINDENT 4}

@{i}Text format... @{ui}@{PAR}

There are two groups of buttons with this title. One applies to
the Clock/Memory bar, and the other applies to the inconified
window. They allow you to specify how the titles for the Memory
Monitor, when enabled, will be displayed. See your AmigaDOS
documentation for an explanation of Fast and Chip Memory.@{PAR}

The choices are:@{PAR}
@{LINDENT 7}

- CHIP: and FAST:@{PAR}

- C: and F:@{PAR}
@{LINDENT 4}

@{i}When inconified @{ui}@{PAR}

These buttons allow you to specify how Directory Opus should act
when Iconified. In addition to the methods described, you can
always uniconify Directory Opus by pressing the Uniconify key
sequence defined in @{" System/Hotkey " link 3.19.4}.@{PAR}
@{LINDENT 7}

@{" Window     " link 3.19.2.icon.window}@{PAR}
@{" No Window  " link 3.19.2.icon.no}@{PAR}
@{" An AppIcon " link 3.19.2.icon.an}@{PAR}

@ENDNODE
@NODE 3.19.2.Clock.Memory "Configuration: System/Clocks/Memory Bar"
@{LINDENT 1}

@{b}Memory monitor@{ub}@{PAR}

Displays the amount of Chip Memory, Fast Memory and the Total Memory
in the clock bar.@{PAR}

@ENDNODE
@NODE 3.19.2.Clock.CPU "Configuration: System/Clocks/Memory Bar"
@{LINDENT 1}

@{b}CPU monitor@{ub}@{PAR}

Displays the percentage of CPU time that is being use. 100% indicates
that there is not any idle time and that at least one process is
attempting to run continuously.@{PAR}

@ENDNODE
@NODE 3.19.2.Clock.Date "Configuration: System/Clocks/Memory Bar"
@{LINDENT 1}

@{b}Date@{ub}@{PAR}

Displays the current date in the clock bar. The Date Format is
specified in @{" Operation/Date format " link 3.17.2}.@{PAR}

@ENDNODE
@NODE 3.19.2.Clock.Time "Configuration: System/Clocks/Memory Bar"
@{LINDENT 1}

@{b}Time@{ub}@{PAR}

Displays the current time in the clock bar.@{PAR}

@ENDNODE
@NODE 3.19.2.show.bytes "Configuration: System/Clocks/Show free space as"
@{LINDENT 1}

@{b}Bytes free@{ub}@{PAR}

Displays all digits (this can be hard to read with large values).@{PAR}

@ENDNODE
@NODE 3.19.2.show.kilo "Configuration: System/Clocks/Show free space as"
@{LINDENT 1}

@{b}Kilo/Megabytes free@{ub}@{PAR}

Displays value in either kilobytes or megabytes as applicable.@{PAR}

@ENDNODE
@NODE 3.19.2.icon.window "Configuration: System/Clocks/When Iconified"
@{LINDENT 1}

@{b}Window@{ub}@{PAR}

Directory Opus will iconify to a small window on Workbench. If this
window is enabled, its last position is saved when you save the
Configuration file.@{PAR}

To un-iconify the window, simply activate it by clicking on it with
the left mouse button and then press the right mouse button.@{PAR}

The following flags allow you to specify what is displayed in the
window.@{PAR}
@{LINDENT 4}

- Memory monitor@{PAR}

- CPU monitor@{PAR}

- Date@{PAR}

- Time@{PAR}

@ENDNODE
@NODE 3.19.2.icon.no "Configuration: System/Clocks/When Iconified"
@{LINDENT 1}

@{b}No Window@{ub}@{PAR}

Directory Opus will close its window. To uniconify DirOpus, press the
Uniconify key sequence defined in @{" System/Hotkey " link 3.19.4}.@{PAR}

@ENDNODE
@NODE 3.19.2.icon.an "Configuration: System/Clocks/When Iconified"
@{LINDENT 1}

@{b}An AppIcon@{ub}@{PAR}

Directory Opus will open an icon on WorkBench. Simply double-click on
the icon to uniconify it. You can also @{" Drag'n Drop " link 1.10} Workbench icons to
this Appicon.@{PAR}

Starting with v4.16, DOpus will use its own icon ("PROGDIR:DirectoryOpus.info") as
an AppIcon.@{PAR}

@ENDNODE
@NODE 3.19.3 "Configuration: System/Directories"
@{LINDENT 1}

@{b}Directories@{ub}@{PAR}

This requester allows you to set various options for Directory
operations.@{PAR}
@{LINDENT 4}

@{" Directory caches...   " link 3.19.3.Dir_cach}@{PAR}
@{" Search buffers on...  " link 3.19.3.Srch_buf}@{PAR}
@{" Misc. Flags...        " link 3.19.3.Misc}@{PAR}
@{" Show free space as... " link 3.19.3.show}@{PAR}

@ENDNODE
@NODE 3.19.3.Dir_cach "Configuration: System/Directories/Directory caches"
@{LINDENT 1}

@{b}Directory caches...@{ub}@{PAR}
@{LINDENT 4}


@{i}Buffers per window @{ui}@{PAR}

Allows you to specify the number of buffers to be allocated to
each directory window. You can have any value from one to 255.@{PAR}

@{i}Always move to empty buffer @{ui}@{PAR}

Causes Directory Opus to use an empty buffer (if possible)
whenever a new directory is read. A new directory is read
whenever you enter a path in the directory fields, double-click
or @{" Click-M-Click " link glos} on a directory name, or select a drive
button.@{PAR}

@{i}Re-read changed or incomplete buffers @{ui}@{PAR}

When a buffered directory is shown, this will make Directory
Opus check the directory on disk to see if it has changed. If
it has, this will cause a re-read of the directory. Also, if
the original reading of a directory was interrupted it will be
re-read in.@{PAR}

@ENDNODE
@NODE 3.19.3.Srch_buf "Configuration: System/Directories/Search buffers on..."
@{LINDENT 1}

@{b}Search buffers on...@{ub}@{PAR}
@{LINDENT 4}


@{i}Parent/Root operation @{ui}@{PAR}

This option causes the directory buffers to be searched for the
parent or root directory of the current directory, whenever the
@{" Parent " link 1.6.Parent} or @{" Root " link 1.6.Root} Commands are chosen. If the parent or root
directory exists in a buffer (i.e. it has already been read), the
buffered directory is retrieved from memory. This can save a lot
of needless disk access.@{PAR}

@{i}Double-click/Click-m-click directory read @{ui}@{PAR}

When a directory is selected via Double-Click or @{" Click-M-click " link glos} this
will cause Directory Opus to search the buffered directories first.@{PAR}

@ENDNODE
@NODE 3.19.3.Misc "Configuration: System/Directories/Misc flags"
@{LINDENT 1}

@{b}Misc. flags...@{ub}@{PAR}
@{LINDENT 4}


@{i}Auto diskchange @{ui}@{PAR}

Causes Directory Opus to sense disk changes in any drive. If you
have the root directory open in either of the directory windows
when you change the disk, then the new disk will be read
automatically. This allows you to scan through different disks
without having to follow the usual selection procedure.@{PAR}

@{i}Auto disk load @{ui}@{PAR}

This option works in a similar fashion to Auto diskchange,
except that it detects any disk being inserted, not just those
disks currently displayed. If you insert a disk in a floppy
drive with this option turned on, you will be asked whether you
wish to read the disk into the left or the right window.@{PAR}

@{i}Expand pathnames @{ui}@{PAR}

This flag will cause all paths to be expanded to their full
pathnames. For example, if this flag was enabled and you entered
S: in the directory field, the name might be expanded to
Workbench:S/. It will also do this when you select a drive
button. For instance, if you selected a drive button marked DF0:,
the actual name of the disk be inserted in the directory field.@{PAR}

You should note that as the Expand pathnames flag causes the
actual volume name of disks to be used, the system (and you) may
get confused when using two disks with the same name. As a rule,
you should avoid using identically-named disks at the same time.@{PAR}

@{i}Use ExAll() @{ui}@{PAR}

If selected, Directory Opus will use the ExAll() command to read
directories, rather than the old Examine()/ExNext() combination.
ExAll() can be slightly faster than the old method.@{PAR}

NOTE:@{PAR}

It is recommended that you always leave this function enabled. ExAll()
appeared in OS3.0 and as any new thing it required some time to be
correctly handled by other filesystems than FFS. Anyway, any disk filesystem
should handle it properly by now. But there are some possible troublemakers.
Parnet has some problems for example, but not only with ExAll().@{PAR}

So disable ExAll() only to work with buggy filesystems and reenable it just
after finishing the work.@{PAR}

@ENDNODE
@NODE 3.19.3.show "Configuration: System/Directories/Show free space as..."
@{LINDENT 1}

@{b}Show free space as...@{ub}@{PAR}

These allow you to choose how to measure the free space that is
displayed alongside the disk name.@{PAR}
@{LINDENT 4}


@{i}Bytes free @{ui}@{PAR}

Displays the number of free bytes.@{PAR}

@{i}Kilo/Megabytes free @{ui}@{PAR}

Displays the amount of free space in either kilobytes or
megabytes (depending upon the size).@{PAR}

@{i}Blocks free @{ui}@{PAR}

Displays the number of blocks free (as will also be shown by
the AmigaDOS Info command).@{PAR}

@{i}Percentage of space free @{ui}@{PAR}

Displays the free space as a percentage of the total size.@{PAR}

@ENDNODE
@NODE 3.19.4 "Configuration: System/Hotkey"
@{LINDENT 1}

@{b}Hotkey@{ub}@{PAR}

This requester allows you to specify the Directory Opus activate
Hotkey. The Uniconify/activate Hotkey is really a combination of keys that you press to do
one of four things:@{PAR}

If Directory Opus is iconified, it will be uniconified.@{PAR}

If the Directory Opus screen is open, but at the back of the
display, it will be brought to the front.@{PAR}

If the screen has been pulled down using the screen drag bar,
it will be brought to the top.@{PAR}

If the screen is already at the front of the display, it will
be moved to the back.@{PAR}
@{LINDENT 4}


@{i}Sample @{ui}@{PAR}

To modify the Hotkey, select the Sample button at the right of the
Hotkey field. While the Sample button is selected, any key that
you press, along with any qualifiers, will be inserted in the
hotkey field. To turn off sample mode, select the Sample button
again.@{PAR}

To remove the Hotkey simply select the Sample button with the
right mouse button.@{PAR}

The default Hotkeys are CONTROL + LSHIFT + LALT, meaning that
pressing the control key, the left shift key and the left Alt
keys together will perform the action.@{PAR}

@{i}Use middle mouse button @{ui}@{PAR}

With this flag turned on Directory Opus will also use the middle
mouse button as well as the Hotkey defined above. This option
requires a three button mouse.@{PAR}

@ENDNODE
@NODE 3.19.5 "Configuration: System/Icons"
@{LINDENT 1}

@{b}Icons@{ub}@{PAR}

This Requester allows you to specify the Icons which will be created
with the @{" AddIcon " link 1.6.Add_Icon} Command.@{PAR}
@{LINDENT 4}


@{i}AddIcon's icons... @{ui}@{PAR}

This list includes three built-in icon types Drawer, Tool and
Project. In addition, each of the filetypes is included in this
list. This system allows you to specify your own icons to use with
the @{" AddIcon " link 1.6.Add_Icon} Command if you do not like the default icons.
Simply select the type of icon you want to change (e.g. drawer,
tool, etc.), and its current icon will appear in the lower right
corner. You may change the icon by modifying the field directly
below the list. The magnifying-glass button is provided to allow
you to find the icon you want easily.@{PAR}

@{i}Project's Default Tool... @{ui}@{PAR}

Allows you to modify the Default Tool of project icons added with
the @{" AddIcon " link 1.6.Add_Icon} Command. This only works with the built-in
project icon or the default Workbench project icon; not with
user-supplied icons. For example, you may set the Default Tool
to c:FullView. Then, whenever you double-click from Workbench
on an icon that you have added to a project, Full View will be
invoked.@{PAR}

@ENDNODE
@NODE 3.19.6 "Configuration: System/Modules"
@{LINDENT 1}

@{b}Modules@{ub}@{PAR}

An external module is a small program which Directory Opus runs to
perform infrequent operations. By making them external, they do not
have to be in memory at all times. If you are not concerned with their
memory usage and you don't want Directory Opus to load them each time
you use them, this requester allows you to specify which modules you
want to be preloaded. If you want a module to be preloaded, select it
and a checkmark will appear. Select it again if you do not want it
preloaded. Preloaded modules take less time to start up but use
additional RAM and will increase the time DOpus needs to start up.@{PAR}

@ENDNODE
@NODE 3.19.7 "Configuration: System/Show pattern"
@{LINDENT 1}

@{b}Show pattern@{ub}@{PAR}

This requester allows you to specify files to show or exclude from the
directory lists.@{PAR}
@{LINDENT 4}


@{i}Hide files with hidden bit set @{ui}@{PAR}

Tells Directory Opus to take notice of the H bit; any files that
have this protection bit set will not be displayed.@{PAR}

@{i}Show @{ui}@{PAR}

Allows a @{" wildcard pattern " link WldCrdPat} against which all files are
checked. If the file matches this pattern, it is displayed.@{PAR}

@{i}Hide @{ui}@{PAR}

Allows a @{" wildcard pattern " link WldCrdPat} against which all files are
checked. If the file matches this pattern, it is not displayed.@{PAR}

@ENDNODE
@NODE 3.19.8 "Configuration: System/Startup"
@{LINDENT 1}

@{b}Startup@{ub}@{PAR}

This requester allows you to specify various startup options.@{PAR}
@{LINDENT 4}


@{i}Directories to read on startup... @{ui}@{PAR}

These fields allows you to specify the path name of a directory
that is loaded automatically into the left or right window
whenever Directory Opus starts. The magnifying-glass button to
the left of these fields opens a directory requester to help
you locate the path you require.@{PAR}

You can specify the startup directory for both the left and the
right lister.@{PAR}

@{i}ARexx scripts to execute on... @{ui}@{PAR}

These allow you to specify the names of ARexx scripts that are
automatically run when Directory Opus starts (Startup), or when
it returns from an iconified state (Uniconify) or from the
ConfigOpus utility (Cfg return).@{PAR}

@ENDNODE
@NODE 3.19.9 "Configuration: System/View & Play"
@{LINDENT 1}

@{b}View & Play@{ub}@{PAR}

This requester allows you to configure options for Directory Opus'
viewers.@{PAR}
@{LINDENT 4}

@{" Picture/animation viewer (IFF ILBM/ANIM) " link 3.19.9.pic}@{PAR}
@{" Sound player (IFF 8SVX)...               " link 3.19.9.sound}@{PAR}
@{" Text viewer...                           " link 3.19.9.text}@{PAR}

@ENDNODE
@NODE 3.19.9.pic "Configuration: System/View & Play"
@{LINDENT 1}

@{b}Picture/animation viewer (IFF ILBM/ANIM)@{ub}@{PAR}
@{LINDENT 4}


@{i}Black background between pictures @{ui}@{PAR}

This flag causes a blank screen to be displayed while each picture
is loading. Otherwise, the Directory Opus screen will be displayed
in between each picture.@{PAR}

@{i}Start animation paused @{ui}@{PAR}

Makes animations come up paused. This is particularly useful when
an animation is simply a collection of pictures and not really an
animation.@{PAR}

@{i}8-bits per gun colour @{ui}@{PAR}

This tells Directory Opus to treat the colour information in IFF
ILBMs as having 8 bits per gun. Pictures that have 4 bits per gun,
pre-AGA, are shown a little dimmer than usual. This option is only
available when using AGA.@{PAR}

@{i}Pick best screen mode @{ui}@{PAR}

If this option is enabled, DOpus will ask the Operating System to choose
the screenmode best suitable for DOpus' text/picture viewers (in other words:
DOpus will use the BestModeId() function of AmigaOS). Otherwise, DOpus
will try choose a screenmode on its own.@{PAR}

@{i}Show delay @{ui}@{PAR}

Allows you to show pictures as a simple slideshow. If set to 0,
pictures will wait for you to press the left mouse button before
continuing. On other settings, the pictures will continue to
display one after the other for the specified time in seconds.@{PAR}

@{i}Fade delay @{ui}@{PAR}

Allows you to configure the speed at which pictures fade in and
out. If it is set to 0, there will be no fading at all. The
default is 2; the maximum is 10. The value indicates in 60ths
(50ths in PAL) of a second the time between each change in
colour.@{PAR}

@ENDNODE
@NODE 3.19.9.sound "Configuration: System/View & Play"
@{LINDENT 1}

@{b}Sound player (IFF 8SVX)...@{ub}@{PAR}
@{LINDENT 4}


@{i}Turn audio filter off for play @{ui}@{PAR}

Causes the high-pass audio filter to be turned off while each IFF
8SVX sound file is played. Note that on A1000s the audio filter
may not be software-selectable.@{PAR}

@{i}Loop on double-click @{ui}@{PAR}

Tells Directory Opus to behave as it did in version 3.4. In that
version, when you double clicked on sounds, they played in looped
fashion. Under 4.0 the sound is played only once.@{PAR}

@ENDNODE
@NODE 3.19.9.text "Configuration: System/View & Play"
@{LINDENT 1}

@{b}Text viewer...@{ub}@{PAR}
@{LINDENT 4}


@{i}Text viewer borders @{ui}@{PAR}

Tells the @{" Text viewer " link 2.7} to have a slider and fancier borders.
Note that with the fancier borders and sliders you may not be able
to read text files that are 80 characters wide if you use very
small screen resolutions (like Hires).@{PAR}

@{i}View in window @{ui}@{PAR}

Tells the Text viewer to open as a window on DirOpus' screen (or on the screen
DirOpus is using) instead of opening its own screen.@{PAR}

@{i}Tab size @{ui}@{PAR}

Allows you to specify the number of spaces to which a tab
character is equivalent in the @{" Read " link 1.6.Read} and @{" AnsiRead " link 1.6.ANSI_Read} commands.
The default is 8, which is also the ANSI standard.@{PAR}

@{i}Left X, Top Y, Width, Height @{ui}@{PAR}

If the Text viewer is told to open a window on DirOpus screen (see above), this will
determine the window's position and size. '0' in width or height equals maximum
distance in that direction. Negative values are subtracted from the maximum available
size. The window cannot be made smaller than 50 x 50.@{PAR}

@ENDNODE
@Node tech "Tech Guide"
@{LINDENT 1}

@{b}Chapter 4 - Tech Guide@{ub}@{PAR}

This section of the manual contains technical information, reference
tables and parameter listings you need for using/configuring your
Directory Opus.@{PAR}
@{LINDENT 4}

@{" Command Reference              " link Commands}@{PAR}
@{" Simple Argument Functions      " link SimArgFun}@{PAR}
@{" Requester Functions            " link ReqFun}@{PAR}
@{" Wild Card Patterns             " link WldCrdPat}@{PAR}
@{" Shortcut Keys                  " link Shortcut}@{PAR}
@{" Editing Features               " link edfeat}@{PAR}
@{" How We Start External Programs " link StaExtPrg}@{PAR}
@{" Glossary                       " link Glos}@{PAR}

@ENDNODE
@NODE Commands "Tech Guide/Commands"
@{LINDENT 1}

@{" Command Reference Information " link ComRefInf}@{PAR}
@{LINDENT 4}

@{" About            " link About}  @{" FinishSection    " link FinishSection}  @{" Protect          " link Protect}@{PAR}
@{" AddCustEntry     " link AddCustEntry}  @{" Format           " link Format}  @{" Query            " link Query}@{PAR}
@{" AddCustHandler   " link AddCustHandler}  @{" FormatBG         " link FormatBG}  @{" Quit             " link Quit}@{PAR}
@{" AddFile          " link AddFile}  @{" GetAll           " link GetAll}  @{" Read             " link Read}@{PAR}
@{" AddIcon          " link AddIcon}  @{" GetDevices       " link GetDevices}  @{" Redraw           " link Redraw}@{PAR}
@{" Alarm            " link Alarm}  @{" GetDirs          " link GetDirs}  @{" Relabel          " link Relabel}@{PAR}
@{" All              " link All}  @{" GetEntry         " link GetEntry}  @{" Remember         " link Remember}@{PAR}
@{" AnsiRead         " link AnsiRead}  @{" GetFileType      " link GetFileType}  @{" RemoveEntry      " link RemoveEntry}@{PAR}
@{" ARexx            " link ARexx}  @{" GetFiles         " link GetFiles}  @{" RemoveFile       " link RemoveFile}@{PAR}
@{" Assign           " link Assign}  @{" GetNextSelected  " link GetNextSelected}  @{" Rename           " link Rename}@{PAR}
@{" Beep             " link Beep}  @{" GetSelectedAll   " link GetSelectedAll}  @{" Request          " link Request}@{PAR}
@{" BufferList       " link BufferList}  @{" GetSelectedDirs  " link GetSelectedDirs}  @{" Rescan           " link Rescan}@{PAR}
@{" Busy             " link Busy}  @{" GetSelectedFiles " link GetSelectedFiles}  @{" Reselect         " link Reselect}@{PAR}
@{" ButtonIconify    " link ButtonIconify}  @{" GetSizes         " link GetSizes}  @{" Restore          " link Restore}@{PAR}
@{" CD               " link CD}  @{" GetString        " link GetString}  @{" Root             " link Root}@{PAR}
@{" CheckAbort       " link CheckAbort}  @{" Help             " link Help_a}  @{" Run              " link Run}@{PAR}
@{" CheckFit         " link CheckFit}  @{" HexRead          " link HexRead}  @{" SaveConfig       " link SaveConfig}@{PAR}
@{" ClearBuffers     " link ClearBuffers}  @{" Hunt             " link Hunt}  @{" ScanDir          " link ScanDir}@{PAR}
@{" ClearSizes       " link ClearSizes}  @{" Iconify          " link Iconify}  @{" ScrollH          " link ScrollH}@{PAR}
@{" ClearWin         " link ClearWin}  @{" IconInfo         " link IconInfo}  @{" ScrollToShow     " link ScrollToShow}@{PAR}
@{" Clone            " link Clone}  @{" Install          " link Install}  @{" ScrollV          " link ScrollV}@{PAR}
@{" Comment          " link Comment}  @{" InstallBG        " link InstallBG}  @{" Search           " link Search}@{PAR}
@{" Configure        " link Configure}  @{" LastSaved        " link LastSaved}  @{" Select           " link Select}@{PAR}
@{" ContST           " link ContST}  @{" LoadConfig       " link LoadConfig}  @{" SelectEntry      " link SelectEntry}@{PAR}
@{" Copy             " link Copy}  @{" LoopPlay         " link LoopPlay}  @{" SelectFile       " link SelectFile}@{PAR}
@{" CopyAs           " link CopyAs}  @{" MakeDir          " link MakeDir}  @{" SetVar           " link SetVar}@{PAR}
@{" CopyWindow       " link CopyWindow}  @{" Modify           " link Modify}  @{" SetWinTitle      " link SetWinTitle}@{PAR}
@{" Datestamp        " link Datestamp}  @{" Move             " link Move}  @{" Show             " link Show}@{PAR}
@{" Defaults         " link Defaults}  @{" MoveAs           " link MoveAs}  @{" Smartread        " link SmartRead}@{PAR}
@{" Delete           " link Delete}  @{" NewCLI           " link NewCLI}  @{" Status           " link Status}@{PAR}
@{" DirTree          " link DirTree}  @{" Nextdrives       " link Nextdrives}  @{" StopST           " link StopST}@{PAR}
@{" DiskCopy         " link Diskcopy}  @{" None             " link None}  @{" SwapWindow       " link SwapWindow}@{PAR}
@{" DiskCopyBG       " link DiskCopyBG}  @{" Notify           " link Notify}  @{" Toggle           " link Toggle}@{PAR}
@{" DiskInfo         " link DiskInfo}  @{" Otherwindow      " link Otherwindow}  @{" TopText          " link TopText}@{PAR}
@{" DisplayDir       " link DisplayDir}  @{" Parent           " link Parent}  @{" Uniconify        " link Uniconify}@{PAR}
@{" DOpusToBack      " link DOpusToBack}  @{" ParentList       " link ParentList}  @{" User1, ...       " link User1}@{PAR}
@{" DOpusToFront     " link DOpusToFront}  @{" Patternmatch     " link Patternmatch}  @{" Verify           " link Verify}@{PAR}
@{" Encrypt          " link Encrypt}  @{" Play             " link Play}  @{" Version          " link Version}@{PAR}
@{" ErrorHelp        " link ErrorHelp}  @{" PlayST           " link PlayST}@{PAR}
@{" Execute          " link Execute}  @{" Print            " link Print}@{PAR}
@{" FileInfo         " link FileInfo}  @{" PrintDir         " link PrintDir}@{PAR}

@ENDNODE
@NODE ComRefInf "Tech Guide/Commands"
@{LINDENT 1}

@{b}Command Reference Information@{ub}@{PAR}

This section lists the Directory Opus commands in alphabetical order.
Let's begin with an example of an entry's layout, with its component
parts explained as they occur:@{PAR}
@{LINDENT 4}

command  argument  [argument2]@{PAR}
@{LINDENT 1}

This is the syntax of the command. Elements in square brackets are optional.@{PAR}
@{LINDENT 4}

@{" ARexx Only " link ComRefInf 8} / @{" Internal Only " link ComRefInf}@{PAR}
@{LINDENT 1}

If one of those buttons follows the syntax description of the command, it means that it is a
command that can only be used either from ARexx (the Amiga's inbuilt intercommunication
language) or for buttons (menus, hotkeys or filetypes).
Otherwise, a command can be used both in a button and as an ARexx command.@{PAR}

Below the syntax (or the "Arexx Only" button), the syntax elements are explained in turn.@{PAR}

If necessary, there will follow notes pertaining to the use of the
particular command.@{PAR}

@{FG highlight}Using DirOpus' commands from ARexx@{FG text}@{PAR}

All Directory Opus commands when called from ARexx respond with two
variables: RC (the error status code) and Result. RC will always be an
integer value indicating the severity of an error, 0 being no error.
Result will indicate success or failure of the command, usually
expressed as an integer value, or it may be data, such as the name of
a file.@{PAR}

@ENDNODE
@NODE About "Tech Guide/Commands"
@{LINDENT 1}

@{b}About@{ub}@{PAR}

This command displays copyright information and mailing addresses.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE AddCustEntry "Tech Guide/Commands"
@{LINDENT 1}

@{b}AddCustEntry  TEXT [USERDATA] [FGPEN] [BGPEN] [SELECTABLE] [SHOW] [BEFORE]@{ub}@{PAR}

@{" ARexx Only " link ComRefInf 8}@{PAR}


         TEXT  is the text for the entry, and may be up to 256@{PAR}
               characters long. The dimensions of the horizontal@{PAR}
               slider are adjusted automatically to the longest@{PAR}
               entry.@{PAR}

     USERDATA  user data for this entry. This is not displayed but@{PAR}
               can be retrieved, defaults to nothing.@{PAR}

        FGPEN  pen colour to display entry in or -1 for default@{PAR}
               file colour, defaults to -1.@{PAR}

        BGPEN  background colour of entry of -1 for default file@{PAR}
               background colour, defaults to -1.@{PAR}

   SELECTABLE  indicates if entry is selectable (0 = not selectable@{PAR}
               or 1 = selectable), defaults to 1.@{PAR}

         SHOW  boolean to update directory display (0 = do not@{PAR}
               update, 1 = update), defaults to 1.@{PAR}

       BEFORE  ordinal entry number before which to add this entry.@{PAR}
               A 0 adds the entry to the beginning of the list, -1@{PAR}
               adds at the end of the list, defaults to -1.@{PAR}


This is similar to the @{" AddFile " link AddFile} command, but allows for entries of
up to 256 characters. Entries added with this command are completely user-defined.@{PAR}

This command will fail if there are any normal entries already in
the active window, so you should always call @{" Clear Win " link ClearWin} before using it.
By default, entries are not sorted in any way; The most recent entry
will be shown as the last.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = 0 or 1 to indicate failure or success.@{PAR}

@ENDNODE
@NODE AddCustHandler "Tech Guide/Commands"
@{LINDENT 1}

@{b}AddCustHandler  PORTNAME [WIN]@{ub}@{PAR}

@{" ARexx Only " link ComRefInf 8}@{PAR}


   PORTNAME  name of handler's message port@{PAR}

        WIN  optional; window to add a custom handler to@{PAR}
             (-1 = current window, 0 = left or 1 = right)@{PAR}
             defaults to -1.@{PAR}


This command will attach an ARexx portname to the current
directory buffer. When you manipulate the buffer's entries, Directory
Opus will pass messages to the specified portname. This command is
only used with buffers created using @{" AddCustEntry " link AddCustEntry}. Currently the only
two actions supported are Double-Click and @{" Click-M-Click " link Glos}. As an
example, this system could be used to create a phonebook system or a
NetWork manager with Directory Opus.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = name of old handler's message port (if there was one)@{PAR}

@ENDNODE
@NODE AddFile "Tech Guide/Commands"
@{LINDENT 1}

@{b}AddFile  NAME  SIZE  TYPE  SECONDS  COMMENT  PROTECTION  RESERVED  SHOW@{ub}@{PAR}

@{" ARexx Only " link ComRefInf 8}@{PAR}


         NAME  name of entry@{PAR}

         SIZE  size in bytes of entry@{PAR}

         TYPE  type of entry (-1 = file or 1 = dir)@{PAR}

      SECONDS  datestamp of file, seconds from Jan 1, 1978 (date @{PAR}
               that AmigaDOS considers the beginning of time)@{PAR}

      COMMENT  file comment@{PAR}

   PROTECTION  protection bits in ASCII form. `RW' would mean@{PAR} 
               Readable and Writeable.@{PAR}

     RESERVED  reserved, must be 0 for now@{PAR}

         SHOW  update directory display, boolean@{PAR}


This command adds a file or directory entry to the active directory window.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = 0 or 1 to indicate failure or success.@{PAR}

@ENDNODE
@NODE AddIcon "Tech Guide/Commands"
@{LINDENT 1}

@{b}AddIcon  [NAME]@{ub}


   NAME  optional; name of file


This will add icons to all selected files and directories in the
active directory window. Directory Opus automatically senses what sort
of file it is (drawer, project, tool, etc.) and will add the
appropriate icon. Under OS2.0, however, we use the Workbench default
icons. You may specify your own icons in the ConfigOpus if the default
icons are not suitable. You may also specify the Default Tool to be
used for project icons. If the name is not given, it will use the
first available selected item in the current directory window.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE Alarm "Tech Guide/Commands"
@{LINDENT 1}

@{b}Alarm@{ub}@{PAR}

This command will sound an alarm on both or either of the sound
channels. You could use this command to warn people that they have
selected a dangerous command. For instance, you could modify the
@{" DELETE " link 1.6.delete} button to read:@{PAR}
@{LINDENT 4}

Command   Alarm@{PAR}
Command   Delete@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE All "Tech Guide/Commands"
@{LINDENT 1}

@{b}All@{ub}@{PAR}

This command selects all files and directories in the active
directory window.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE AnsiRead "Tech Guide/Commands"
@{LINDENT 1}

@{b}AnsiRead  [NAME]@{ub}@{PAR}


   NAME  optional; name of file@{PAR}


This command operates in exactly the same way as the @{" READ " link Read} command,
except that it displays ANSI control sequences (colours and
typestyles) properly, and also handles tab characters correctly. If
the name is not given it will use the first available selected item in
the current directory window.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE ARexx "Tech Guide/Commands"
@{LINDENT 1}

@{b}ARexx [COMMAND]@{ub}@{PAR}


 COMMAND  optional; command to execute@{PAR}


This allows you to launch an ARexx script or execute a
Directory Opus ARexx command from within Directory Opus. If the
command is not given a requester will open asking the user for one.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE Assign "Tech Guide/Commands"
@{LINDENT 1}

@{b}Assign [NAME]@{ub}@{PAR}


   NAME  optional; name to assign@{PAR}

This command allows you to assign a logical device name to the
currently active directory. The C: device is an example of a logical
device; it is not a physical disk itself, but is a directory that has
been assigned the name C:. For example, a simple name as Text: can be
assigned to a long and complicated pathname such as:@{PAR}
@{LINDENT 4}

DH0:Projects/Work/1989/April/Bits&Pieces/Text@{PAR}
@{LINDENT 1}

From then on, whenever you enter Text: into a directory field,
you will go straight to the directory at the end of the assigned path,
instead of having to go through all the sub-directories on the way.
You can use the assignment in any other program as well. Logical
device names always end with a colon.@{PAR}

"Assign" also allows you to cancel a previously assigned logical
device, or reassign a device to another directory. To do this, press
the right mouse button over the S (select) button to activate the
@{" GetDevices " link GetDevices} command. Select the assigned device(s) you wish to change,
and invoke the "Assign" command. A requester will appear, into which you
can type the new pathname to be assigned to each device selected. If you
enter a blank string, that logical device will be removed.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE Beep "Tech Guide/Commands"
@{LINDENT 1}

@{b}Beep@{ub}@{PAR}

This command will sound a beep on both or either of the sound
channels. You could use this command to signify that a command has
finished. For instance, you could modify the @{" Diskcopy " link 1.9.2.Disk_Copy} option to read:@{PAR}
@{LINDENT 4}

Command   DiskCopy@{PAR}
Command   Beep@{PAR}
@{LINDENT 1}

This command simply calls the system beep routine.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE BufferList "Tech Guide/Commands"
@{LINDENT 1}

@{b}BufferList  [WIN]@{ub}@{PAR}


   WIN  optional; window to scan the buffer list into@{PAR}
        (-1 = current window, 0 = left or 1 = right)@{PAR}
        defaults to -1.@{PAR}


This command displays a list of all the buffered directories. You
may then double-click on one of the displayed buffers to jump to that
buffer immediately, rather than clicking the arrows to cycle through
the buffers one by one.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE Busy "Tech Guide/Commands"
@{LINDENT 1}

@{b}Busy [ON|OFF]@{ub}@{PAR}

@{" ARexx Only " link ComRefInf 8}@{PAR}


   [ON|OFF]  optional; adjust the busy pointer,@{PAR}
             defaults to on.@{PAR}


This command turns on or off the busy pointer.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE ButtonIconify "Tech Guide/Commands"
@{LINDENT 1}

@{b}ButtonIconify  [ROWS]  [BANK]@{ub}@{PAR}


   ROWS  optional; number of button rows. This can be 1,2,3,@{PAR}
         or 6. Defaults to whatever Directory Opus is set to.@{PAR}

   BANK  optional; bank number to display initially,@{PAR}
         defaults to 1.@{PAR}


This causes Directory Opus to open a window on Workbench
containing the Custom Buttons. For more details see ButtonIconify
@{" menu item " link 1.9.1.Button_Iconified}.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE CD "Tech Guide/Commands"
@{LINDENT 1}

@{b}CD  [PATH]@{ub}@{PAR}


   PATH  optional; new current directory path. If a path is not@{PAR}
         given, a requester will open.@{PAR}


This command allows you to set the current working directory
for Directory Opus. This is the directory that is read if you press
return on an empty directory button.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE CheckAbort  "Tech Guide/Commands"
@{LINDENT 1}

@{b}CheckAbort@{ub}@{PAR}

@{" ARexx Only " link ComRefInf 8}@{PAR}

This command allows you to monitor, from an ARexx script, whether
the user has pressed the left and right mouse buttons together (to
abort). It also resets the Abort flag every time it is called. If you
plan to use the CheckAbort command, you should call CheckAbort at the
start of the script ( to reset the Abort flag), before actually using
it to check the abort status.@{PAR}


ARexx Results:@{PAR}@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = 0 if abort sequence has not been hit, 1 if it has.@{PAR}

@ENDNODE
@NODE CheckFit "Tech Guide/Commands"
@{LINDENT 1}

@{b}CheckFit  [WIN]@{ub}@{PAR}


   WIN  optional; window to a CheckFit on @{PAR}
        (-1 = current window, 0 = left or 1 = right)@{PAR}
        defaults to -1.@{PAR}


----------@{PAR}

@{fg highlight}Important Note!@{fg text}@{PAR}

This command is heavily outdated. It only knowns about FFS partitions with
512 Bytes per block. It will fail (in other words: report wrong results) on any
partition that does not match these specs exactly. Avoid this command if you're
not sure that all of your partitions are FFS, 512 Bytes/block!@{PAR}

----------@{PAR}

This works in the same way as @{" GetSizes " link GetSizes} does except that its
calculation is based on disk block sizes, and is therefore much more
accurate.@{PAR}

The disadvantage of CheckFit is that it needs to recalculate every
time the destination's block size changes. Therefore, even if all
source directories already have their sizes shown, CheckFit may need to
scan them all again. Operations like @{" Copy " link Copy}, etc., that generate
directory sizes, are not suitable for CheckFit, and so again CheckFit
will need to scan all selected directories.@{PAR}

CheckFit displays the total number of bytes needed and the number
of bytes free (i.e., block number multiplied by the block size), and
the percentage of files that will actually fit. If they will all fit,
it shows 100%, if only half of them will fit, it shows 50%.@{PAR}

The GetSizes command is retained as it can be used quickly to
provide a rough guide. CheckFit can completely replace the GetSizes
command if you don't mind it having to rescan directories when you
might not have expected it.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE ClearBuffers "Tech Guide/Commands"
@{LINDENT 1}

@{b}ClearBuffers@{ub}@{PAR}

This command will clear the contents of all the directory buffers
other than the two that are currently displayed. All unused memory
will be de-allocated. This is a good way to free memory quickly if you
have lots of used buffers and are running a bit low on memory.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE ClearSizes "Tech Guide/Commands"
@{LINDENT 1}

@{b}ClearSizes  [WIN]@{ub}@{PAR}


   WIN  optional; window to clear the sizes from @{PAR}
        (-1 = current window, 0 = left or 1 = right) @{PAR}
        defaults to -1.@{PAR}


If directory's size is already displayed, then the directory will
not be re-scanned when selected nor the @{" GetSizes " link GetSizes} command invoked. This
could mean that the directory size is inaccurate, especially if any
files have been created or deleted in it by another program. Selecting
one or more directories, and then selecting the ClearSizes command, 
will cause the directory sizes to disappear. You can then reselect the
directories, invoke the GetSizes command, and the directories will be 
re-scanned and their updated sizes displayed.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE ClearWin "Tech Guide/Commands"
@{LINDENT 1}

@{b}ClearWin  [WIN]@{ub}@{PAR}


   WIN  optional; window to clear@{PAR}
        (-1 = current window, 0 = left or 1 = right)@{PAR}
        defaults to -1.@{PAR}


This command will clear the contents of a directory window.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE Clone "Tech Guide/Commands"
@{LINDENT 1}

@{b}Clone  [NAME]  [NEW NAME]@{ub}@{PAR}


       NAME  optional; file name@{PAR}

   NEW NAME  optional; new file name@{PAR}


This command allows you to make a copy of selected entries in the
same directory, and rename them. A requester will appear for each
entry, asking for the new name.@{PAR}

This can also work with a specified file. If a new name is not
given then a requester will appear.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE Comment "Tech Guide/Commands"
@{LINDENT 1}

@{b}Comment  [NAME]  [COMMENT]@{ub}@{PAR}


      NAME  optional; file name@{PAR}

   COMMENT  optional; comment string@{PAR}


This command allows you to change the comment, or filenote, of the
selected files and directories in the active directory window. When
directories are selected, you are asked whether the files within them
are to have their comments modified also.@{PAR}

For each entry, you are presented with a requester containing its
current comment. To change the comment, edit it and press return. To
retain the comment, just press return.@{PAR}

To set the comment of all selected entries you should select the
"All" button from the comment requester; choosing Okay or pressing return
will set the comments one file at a time.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE Configure "Tech Guide/Commands"
@{LINDENT 1}

@{b}Configure@{ub}@{PAR}

Simply starts up the configuration program.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE ContST "Tech Guide/Commands"
@{LINDENT 1}

@{b}ContST@{ub}@{PAR}

If there is a song paused, then it starts playing again.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE Copy "Tech Guide/Commands"
@{LINDENT 1}

@{b}Copy  [NAME]  [DESTINATION]@{ub}@{PAR}


          NAME  optional; file name@{PAR}

   DESTINATION  optional; destination directory@{PAR}


This command copies all selected files and directories in the
active directory window to the inactive directory window, keeping the
same names. If a filename is given then only that file will be copied,
but you may also specify a destination directory.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE CopyAs "Tech Guide/Commands"
@{LINDENT 1}

@{b}CopyAs  [NAME]  [NEW NAME]@{ub}@{PAR}


       NAME  optional; file name@{PAR}

   NEW NAME  optional; new file name@{PAR}


This command copies all selected files and directories in the
active directory window to the inactive directory window, and allows
you to specify a new name for each file or directory. If a filename is
given, then only that file will be copied.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE CopyWindow "Tech Guide/Commands"
@{LINDENT 1}

@{b}CopyWindow  [WIN]@{ub}@{PAR}


   WIN  optional; window to copy from@{PAR}
        (-1 = current window, 0 = left or 1 = right)@{PAR}
        defaults to -1.@{PAR}


This will copy the contents of a specified window or the current
window into the other window.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE DateStamp "Tech Guide/Commands"
@{LINDENT 1}

@{b}DateStamp  [NAME]  [DATE]@{ub}@{PAR}


   NAME  optional; file name@{PAR}

   DATE  optional; date to set@{PAR}


This command allows you to change the datestamp of selected files
and directories in the active directory  window. When directories are
selected, you are asked whether you also wish the files within them to
have their datestamps modified.@{PAR}

For each entry, you are presented with a requester. If you wish
the file to have its datestamp set to current date and time, simply
press return. Otherwise, enter the desired date and time.@{PAR}

To set the datestamp of all selected entries you should select the
"All" button from the datestamp requester; choosing Okay will set the
datestamps a file at a time.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE Defaults "Tech Guide/Commands"
@{LINDENT 1}

@{b}Defaults@{ub}@{PAR}

This causes Directory Opus to reset to the hard-coded, default
configuration. If you have modified the configuration yourself, and
have not yet saved it using @{" SaveConfig " link SaveConfig}, you are asked if you wish 
to save it first.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE Delete "Tech Guide/Commands"
@{LINDENT 1}

@{b}Delete  [NAME]@{ub}@{PAR}


   NAME  optional; filename@{PAR}


This will delete all selected entries or just the specified file
in the active directory window. Be careful with this, as it is
easy to wipe out valuable data.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE DirTree "Tech Guide/Commands"
@{LINDENT 1}

@{b}DirTree  [WIN]@{ub}@{PAR}


   WIN  optional;  window to create a directory tree in@{PAR}
        (-1 = current window, 0 = left or 1 = right)@{PAR}
        defaults to -1.@{PAR}


This command will map out a directory tree in the active
directory window, or a specified window.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE DiskCopy "Tech Guide/Commands"
@{LINDENT 1}

@{b}DiskCopy  [SOURCE]  [DESTINATION]  [VERIFY]  [BUMP]@{ub}@{PAR}


        SOURCE  optional; source disk@{PAR}

   DESTINATION  optional; destination disk@{PAR}

        VERIFY  optional; diskcopy with verify on@{PAR}

          BUMP  optional; bump the revision of the disk name,@{PAR}
                as with Workbench@{PAR}


This command will diskcopy from source to destination, with Verify
turned on if the Verify keyword is specified. If no source or
destination are specified, the diskcopy requester is opened. If the
Bump keyword is given then Directory Opus will bump the revision (Copy
of DiskName) of the disk name as Workbench does.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE DiskCopyBG "Tech Guide/Commands"
@{LINDENT 1}

@{b}DiskCopyBG@{ub}@{PAR}

This is the same as @{" DiskCopy " link DiskCopy}, just that it operates
in background mode. This allows you to start up a diskcopy and still use
Directory Opus.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE DiskInfo "Tech Guide/Commands"
@{LINDENT 1}

@{b}DiskInfo  [PATH]@{ub}@{PAR}


   PATH  optional; path of a disk to get info about@{PAR}


This command displays some information about the disk the active
directory resides on, including space used and free, datestamp and
number of errors on the disk.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE DisplayDir "Tech Guide/Commands"
@{LINDENT 1}

@{b}DisplayDir  [WIN]@{ub}@{PAR}


   WIN  optional; window to refresh@{PAR}
        (-1 = current window, 0 = left or 1 = right)@{PAR}
        defaults to -1.@{PAR}


This command will update the display for the active directory
window or the specified window.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE DOpusToBack "Tech Guide/Commands"
@{LINDENT 1}

@{b}DOpusToBack@{ub}@{PAR}

Move the Directory Opus screen to the back.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE DOpusToFront "Tech Guide/Commands"
@{LINDENT 1}

@{b}DOpusToFront@{ub}@{PAR}

Move the Directory Opus screen to the front.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE Encrypt "Tech Guide/Commands"
@{LINDENT 1}

@{b}Encrypt  [NAME]  [PASSWORD]@{ub}@{PAR}


       NAME  optional; file name@{PAR}

   PASSWORD  optional; password to use@{PAR}


Have you ever had files that you wanted to encrypt so that only
people who knew the password could understand them?  This command
allows you to do just that. It will encrypt all selected files, using
a password that you enter, with a complex algorithm that most people
will find impossible to work out. The resulting files are not written
over the originals, but are instead written to the destination
directory. They will be the same size as the original files, so you
can ensure you have enough room in the destination directory.@{PAR}

To decrypt a previously encrypted file, you should enter the same
password preceded by a minus sign. For example, to decrypt files you
encrypted with the password FOO, select the files, choose the encrypt
command and enter -FOO as the password.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE ErrorHelp "Tech Guide/Commands"
@{LINDENT 1}

@{b}ErrorHelp  [CODE]@{ub}@{PAR}


   CODE  optional; error code@{PAR}


This command gives you more information about DOS error codes than
is generally available. When you select this option, you are asked for
the DOS error code you want help with. Examples of DOS error codes are
123, 205 and 225. You are then presented with a description of that
error and information pertaining to the possible cause and cure of the
error.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE Execute "Tech Guide/Commands"
@{LINDENT 1}

@{b}Execute  [FILENAME]@{ub}@{PAR}


   FILENAME  optional; name of a file to execute as a script file@{PAR}


This command will attempt to execute each selected file in turn or
to execute a specific file as a script file. This has the same effect
as if you had run the script file via IconX, or via the Execute command
from the CLI.@{PAR}

Note: This command will only try to execute files with the S @{" protection bit " link 2.1} set.@{PAR}

ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE FileInfo  "Tech Guide/Commands"
@{LINDENT 1}

@{b}FileInfo  NAME  [SEPARATOR]  [WIN]@{ub}@{PAR}

@{" ARexx Only " link ComRefInf 8}@{PAR}


        NAME  name of file to give info for (must be in the active or@{PAR}
              specified window)@{PAR}

   SEPARATOR  optional; character used to separate info@{PAR}

         WIN  optional; window to get file from@{PAR}
              (-1 = current window, 0 = left or 1 = right)@{PAR}
              defaults to -1.@{PAR}


This command returns information on the entry called name (which
must be in the active directory window (or the specified window)). The information returned is
separated by a separator (default separator is space), and consists of
the filename, the size in bytes, the size in block (not used yet), the
file type (less the 0 indicates a file, greater than 0 indicates a
directory), the selected status (boolean), the date (days), the date
(seconds), the comment and the protection bits.@{PAR}

The date is returned as a number of days since January 1st, 1978,
and as the number of seconds since midnight. The @{" protection " link Protect} bits are
returned in the format HSPARWED (with a - character where the bit is
not set).@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = information about the file@{PAR}

@ENDNODE
@NODE FinishSection "Tech Guide/Commands"
@{LINDENT 1}

@{b}FinishSection@{ub}@{PAR}

@{" Internal Only " link ComRefInf}@{PAR}

The FinishSection command forces any preceding programs
(AmigaDOS, Workbench, Script or ARexx) to executing before carrying on
to the next command. The next command need not be a Directory Opus
command; it is just more likely that it will be.@{PAR}

For instance, to add a @{" Beep " link Beep} to the end of the LHArc list
filetype command, you would change the command list to read:@{PAR}
@{LINDENT 4}

AmigaDOS  LHARc  v  {f}@{PAR}
Command   FinishSection@{PAR}
Command   Beep@{PAR}
@{LINDENT 1}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE Format "Tech Guide/Commands"
@{LINDENT 1}

@{b}Format  [DRIVE]  [VERIFY]  [QUICK]  [NOICONS]  [FFS]  [INTER]  [CACHE]@{ub}@{PAR}


     DRIVE  optional; drive to format@{PAR}

    VERIFY  optional; format with verify on@{PAR} 

     QUICK  optional; quick format@{PAR}

   NOICONS  optional; format with no icons@{PAR}

       FFS  optional; format fast file system@{PAR}

     INTER  optional; format in international mode@{PAR}

     CACHE  optional; format in directory caching mode.@{PAR}

                      NOTE: Do not use this option when formatting@{PAR}
                      anything else then floppy disks! It was never@{PAR}
                      meant to be used on hard disks, it is more a@{PAR}
                      nuisance than a benefit on such devices.@{PAR}


This allows you to format a new disk. All new disks need to be
formatted before the computer can write to them.@{PAR}

The Verify flag allows you to turn Verify on or off. If Verify is
turned off, the format process will be much faster, but you will not be
made aware of any errors that occur. If you don't completely trust
your disks, leave Verify on.@{PAR}

The FFS option in Format allows you to format a disk to use the
Fast Filing System of Kickstart 2.0. If you are running a Kickstart
less than 2.0, you will still be able to select this option to format a
disk. However, reading FFs-formatted disks is impossible without 2.0
or greater.@{PAR}

International mode allows file and directory names to include
accented characters. Directory caching mode will decrease the capacity
of your disk but the directory reading speed will be much greater.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE FormatBG "Tech Guide/Commands"
@{LINDENT 1}

@{b}FormatBG@{ub}@{PAR}

This is  same as @{" Format " link Format}, just that it operates in background mode.
This allows you to start up a disk format and still use Directory Opus.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE GetAll  "Tech Guide/Commands"
@{LINDENT 1}

@{b}GetAll  [SEPARATOR]  [WIN]@{ub}@{PAR}

@{" ARexx Only " link ComRefInf 8}@{PAR}


   SEPARATOR  optional; character used to separate names@{PAR}

         WIN  optional; window to get names from@{PAR}
              (-1 = current window, 0 = left or 1 = right)@{PAR}
              defaults to -1.@{PAR}


This command returns, in the RESULT variable, the names of all
entries in the active directory window (or the specified window). If
SEPARATOR is specified, the names are separated by a separator. The
default separator is a space. You should be prepared to handle a long
string.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = all the entries@{PAR}

@ENDNODE
@NODE GetDevices "Tech Guide/Commands"
@{LINDENT 1}

@{b}GetDevices  [WIN]@{ub}@{PAR}


   WIN  optional; window to put device list into@{PAR}
        (-1 = current window, 0 = left or 1 = right)@{PAR}
        defaults to -1.@{PAR}


This command displays a list of all devices, volumes and assigned
directories present in the system. You may then read in these devices
by double-clicking on them. You can also select entire devices for use
with the @{" Hunt " link Hunt} and @{" Search " link Search} commands.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE GetDirs  "Tech Guide/Commands"
@{LINDENT 1}

@{b}GetDirs  [SEPARATOR]  [WIN]@{ub}@{PAR}

@{" ARexx Only " link ComRefInf 8}@{PAR}


   SEPARATOR  optional; character used to separate directory names@{PAR}

         WIN  optional; window to get directory names from@{PAR}
              (-1 = current window, 0 = left or 1 = right)@{PAR}
              defaults to -1.@{PAR}


This command returns, in the RESULT variable, the names of all
directories in the active directory window (or the specified window). If
SEPARATOR is specified, the names are separated by a separator. The
default separator is a space. You should be prepared to handle a long
string.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = all the directory entries@{PAR}

@ENDNODE
@NODE GetEntry  "Tech Guide/Commands"
@{LINDENT 1}

@{b}GetEntry  NUM@{ub}@{PAR}

@{" ARexx Only " link ComRefInf 8}@{PAR}


   NUM  the entry number whose name is to be returned@{PAR}


Returns the file or directory name of entry number "num".@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = name of the specified entry@{PAR}

@ENDNODE
@NODE GetFileType  "Tech Guide/Commands"
@{LINDENT 1}

@{b}GetFileType  FILENAME  [TYPE]@{ub}@{PAR}

@{" ARexx Only " link ComRefInf 8}@{PAR}


   FILENAME  file whose filetype is to be returned@{PAR}
             Note: You must specify th full path to the file!@{PAR}

       TYPE  optional; form of filetype ID@{PAR}
             (0 = file class description or 1 = file class ID)@{PAR}
             defaults to 0@{PAR}


Returns the filetype (if recognised) of the specified file.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = filetype ID of the file if filetype is known@{PAR}

@ENDNODE
@NODE GetFiles "Tech Guide/Commands"
@{LINDENT 1}

@{b}GetFiles  [SEPARATOR]  [WIN]@{ub}@{PAR}

@{" ARexx Only " link ComRefInf 8}@{PAR}


   SEPARATOR  optional; character used to separate filenames@{PAR}

         WIN  optional; window to get filenames from@{PAR}
              (-1 = current window, 0 = left or 1 = right)@{PAR}
              defaults to -1.@{PAR}


This command returns, in the RESULT variable, the names of all
files in the active directory window (or the specified window). If
SEPARATOR is specified, the names are separated by a separator.
The default separator is a space. You should be prepared to handle
a long string.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = all the file entries@{PAR}

@ENDNODE
@NODE GetNextSelected  "Tech Guide/Commands"
@{LINDENT 1}

@{b}GetNextSelected  [WIN]@{ub}@{PAR}

@{" ARexx Only " link ComRefInf 8}@{PAR}


   WIN  optional; window to get next selected item from@{PAR}
        (-1 = current window, 0 = left or 1 = right)@{PAR}
        defaults to -1.@{PAR}


This command returns the name of the first selected entry (in the
Result variable) in the active directory window (or the specified window).
The entry is NOT deselected afterwards so if you don't deselect it
yourself, that is the only name you will ever get returned.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = name of the entry@{PAR}

@ENDNODE
@NODE GetSelectedAll  "Tech Guide/Commands"
@{LINDENT 1}

@{b}GetSelectedAll  [SEPARATOR]  [WIN]@{ub}@{PAR}

@{" ARexx Only " link ComRefInf 8}@{PAR}


   SEPARATOR  optional; character used to separate names@{PAR}

         WIN  optional; window to get names from@{PAR}
              (-1 = current window, 0 = left or 1 = right)@{PAR}
              defaults to -1.@{PAR}


This command returns, in the RESULT variable, the names of all
selected entries in the active directory window (or the specified window).
If SEPARATOR is specified, the names are separated by a separator. The default
separator is a space. You should be prepared to handle a long string.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = all the selected entries@{PAR}

@ENDNODE
@NODE GetSelectedDirs "Tech Guide/Commands"
@{LINDENT 1}

@{b}GetSelectedDirs  [SEPARATOR]  [WIN]@{ub}@{PAR}

@{" ARexx Only " link ComRefInf 8}@{PAR}@{PAR}


   SEPARATOR  optional; character used to separate directory names@{PAR}

         WIN  options; window to get selected directory names from@{PAR}
              (-1 = current window, 0=left or 1=right)@{PAR}
              defaults to -1.@{PAR}


This command returns, in the RESULT variable, the names of all
selected directories in the active directory window (or the specified window).
If SEPARATOR is specified, the names are separated by a separator. The default
separator is a space. You should be prepared to handle a long string. @{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = all the selected directory entries@{PAR}

@ENDNODE
@NODE GetSelectedFiles "Tech Guide/Commands"
@{LINDENT 1}

@{b}GetSelectedFiles  [SEPARATOR]  [WIN]@{ub}@{PAR}

@{" ARexx Only " link ComRefInf 8}@{PAR}@{PAR}


   SEPARATOR  optional; character used to separate selected filenames@{PAR}

         WIN  optional; window to get selected filenames from@{PAR}
              (-1=current window, 0=left or 1=right)@{PAR}
              defaults to -1.@{PAR}


This command returns, in the RESULT variable, the name of all
selected files in the active directory window (or the specified window). If
SEPARATOR is specified, the names are separated by a separator. The default
separator is a space. You should be prepared to handle a long string.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = all the selected file entries@{PAR}

@ENDNODE
@NODE GetSizes "Tech Guide/Commands"
@{LINDENT 1}

@{b}GetSizes  [WIN]@{ub}@{PAR}


   WIN  optional; window to work with.@{PAR}
        (-1 = current window, 0=left or 1=right)@{PAR}
        defaults to -1.@{PAR}


This will display in the status bar the same information that is
displayed when entries are selected (namely, the number of selected
files, directories and bytes, out of the total number of files,
directories and bytes), along with one additional piece of information.
If the selected entries occupy fewer bytes than the free space on the
disk in the opposite directory window, allowing all selected files to
fit on the destination disk were they to be copied, a Y will be
displayed after the count. Otherwise, an N will be displayed.@{PAR}

If any directories are selected when GetSizes is chosen, the
directories that do not already have a size displayed are scanned, and
the size of the directories are calculated and displayed.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE GetString "Tech Guide/Commands"
@{LINDENT 1}

@{b}GetString  [MESSAGE]@{ub}@{PAR}

@{" ARexx Only " link ComRefInf 8}@{PAR}


   MESSAGE  optional; text for requester@{PAR}


This command will open a requester for the user to enter text
into. If a message is given, that is used as the prompt for the
requester.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0 success, 1 cancel was pressed@{PAR}

@{" Result " link ComRefInf 24} = string entered by user@{PAR}

@ENDNODE
@NODE Help_a "Tech Guide/Commands"
@{LINDENT 1}

@{b}Help@{ub}@{PAR}

Provided a help file has been loaded in, selecting any button or
menu after enabling Help mode with this command should result in the
appearance of some helpful text. To turn  Help off, select this
command again.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE HexRead "Tech Guide/Commands"
@{LINDENT 1}

@{b}HexRead [NAME]@{ub}@{PAR}


   NAME  optional; name of file@{PAR}


This command will read the selected files in the same way as @{" READ " link Read},
but in hexadecimal format. This allows you to view binary and other
files containing non-text characters.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE Hunt "Tech Guide/Commands"
@{LINDENT 1}

@{b}Hunt  [NAME]  [PATTERN]@{ub}@{PAR}


      NAME  optional; name of directory to hunt@{PAR}

   PATTERN  optional; file pattern to hunt@{PAR}


This command allows you to search all selected directories (and
their sub-directories for a specified file or files. A requester
appears asking for the pattern to hunt for. You can use full pattern
matching for this search.@{PAR}

If a file matching the pattern is found, you are asked if you wish
to enter the directory containing it, or continue the search. If you
elect to enter the directory, the directory will be read and then all
matching entries will be highlighted.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE Iconify "Tech Guide/Commands"
@{LINDENT 1}

@{b}Iconify@{ub}@{PAR}

This command closes the Directory Opus window and screen, de-
allocates as much memory as possible, and then opens a small window on
the Workbench screen. This is known as iconifying, and allows you to
have Directory Opus constantly available while using the minimum amount
of memory.@{PAR}

To determine the initial position of the iconified window,
especially if you start up Directory Opus in the iconified state, you
should inconify Directory Opus, and position the window as you would
like it to appear. Then re-enter Directory Opus and save the
configuration using @{" SaveConfig " link SaveConfig}.@{PAR}

To re-enter Directory Opus, simply click the left mouse button in
the iconified window, then press the right mouse button. If you wish
to quit Directory Opus without going back into it, just click the Close
button at the far left of the iconified window.@{PAR}

If you have the configuration option Iconify Type set to hidden,
the only way to re-enter Directory Opus is with the hotkeys. These
default to CTRL-SHIFT-ALT (the CTRL key, the left SHIFT key and the
left ALT key held down simultaneously), although this may be changed
in the @{" configuration " link 3.19.4} using @{" Configure " link configure}.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE IconInfo "Tech Guide/Commands"
@{LINDENT 1}

@{b}IconInfo  [NAME]@{ub}@{PAR}


   NAME  optional; name of icon (or file with icon)@{PAR}


This command allows you to modify the characteristics of icons
such as Stack size, Default Tool and Tool Types. It operates in a
similar fashion to the Information option in the Icon menu of 
Workbench.@{PAR}

To use this command you may either select the info files
themselves or the actual files or directories the icons belong to.@{PAR}

A requester will appear when you run this command on a valid icon.
The actual appearance of the requester will vary depending on the type
of icon, but in all cases the actual icon imagery will be displayed.
You click on this image with the left mouse button to display the
alternative imagery (if it exists).@{PAR}

The Remap colours button will swap colours 1 and 2 of the icon
displayed. This can be useful to remap icons designed under OS1.3 for
usage under OS2.0, since OS2.0 swapped the light and dark colours
around.@{PAR}

The information displayed for each icon type is listed below.
Once you have made the desired changes to the icon, the Save button
will save the changes to disk. The Skip and Cancel buttons will exit
without modifying the icon on disk.@{PAR}
@{LINDENT 4}


@{i}Drawer icon: @{ui}@{PAR}

For a drawer icon you may edit the drawer's protection
bits, comment and tool types. The date of the last modification
of the drawer is also displayed.@{PAR}

@{i}Project icon: @{ui}@{PAR}

For a project icon you may edit the project's stack
size, default tool and tool types. Also displayed are the size of
the project in bytes and blocks, and the last modification date.@{PAR}

@{i}Tool icon: @{ui}@{PAR}

For a tool icon you may edit the tool's protection bits,
stack size, comment and tool types. Also displayed are the size
of the tool in bytes and blocks, and the last modification date.@{PAR}

@{i}Disk icon: @{ui}@{PAR}

For a disk icon you may edit the disk's Default Tool.
Displayed are the total number of blocks, and the number of blocks
used and free. The block size, creation date and disk status are
also displayed.@{PAR}

@{i}Trashcan icon: @{ui}@{PAR}

For a trashcan icon the only information available is
the last modification date.@{PAR}
@{LINDENT 1}


Protection bits (where appropriate) are modified in the same way
as with the @{" Protect " link Protect} command, except that the Hidden and Pure bits are
not accessible.@{PAR}

Tool types (where appropriate) are modified in the same way as
from Workbench. To edit an existing Tool type, simply select it, and
press return when you have modified it. To create a new Tool type,
select the New button. To delete an existing Tool type, select it and
then select the Delete button.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE Install "Tech Guide/Commands"
@{LINDENT 1}

@{b}Install  [DRIVE]  [FFS]  [NOBOOT]@{ub}@{PAR}


    DRIVE  optional; drive to install@{PAR}

      FFS  optional; install a FFS bootblock@{PAR}

   NOBOOT  optional; make disk non-bootable@{PAR}


This command allows you to make a disk bootable. All bootable
disks have special information written on the first sector of the disk.
Without this, the disk will not boot.@{PAR}


ARexx Results:@{PAR}@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE InstallBG "Tech Guide/Commands"
@{LINDENT 1}

@{b}InstallBG@{ub}@{PAR}

This is the same as @{" Install " link Install}, just that it operates in
background mode. This allows you to start up an install and still use Directory Opus.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE LastSaved "Tech Guide/Commands"
@{LINDENT 1}

@{b}LastSaved@{ub}@{PAR}

This command causes Directory Opus to read in the last saved
configuration file. If you have modified the configuration, and have
not yet saved it, you are asked for confirmation before this is done.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE LoadConfig "Tech Guide/Commands"
@{LINDENT 1}

@{b}LoadConfig  NAME@{ub}@{PAR}


   NAME  configuration file to load@{PAR}


Loads the specified configuration file.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = 0 means success, 1 means some sort of failure@{PAR}

@ENDNODE
@NODE LoopPlay "Tech Guide/Commands"
@{LINDENT 1}

@{b}LoopPlay  [NAME]@{ub}@{PAR}


   NAME  optional; name of file@{PAR}


Unlike the @{" Play " link Play} command, the LoopPlay command plays a sound 
file repeatedly, requiring a mouse button click to proceed to the
next one.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE MakeDir "Tech Guide/Commands"
@{LINDENT 1}

@{b}MakeDir  [NAME]@{ub}@{PAR}


   NAME  optional; name of directory@{PAR}


This command allows you to create a new sub-directory in the
active directory window.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE Modify "Tech Guide/Commands"
@{LINDENT 1}

@{b}Modify NAME VALUE@{ub}@{PAR}


    NAME  name of item to modify@{PAR}

   VALUE  new value@{PAR}


This command allows you to make quick changes in certain
configuration options from the buttons or menus, rather than going
through the configuration program.@{PAR}

The Modify command requires at least two parameters, the name of the
option to change, and the new value(s) for it. Most values are actually
a combination of flag bits; to determine the desired value, you simply
add the values of the flag bits together.@{PAR}

You can also add and subtract bits. To do this, specify each bit
(or combination of bits) that you wish to add or subtract, preceded by
the appropriate sign (+ for add and - for subtract).@{PAR}

The options you can change are:@{PAR}
@{LINDENT 4}


BankNumber  NUM@{PAR}

    Allows you to specify the bank being shown.@{PAR}


ButtonRows  ROWS@{PAR}

    Corresponds to Buttons/Button rows menu.@{PAR}


CopyFlags  FLAGS@{PAR}

    Corresponds to Operation/@{" Copy " link Copy}@{PAR}

     FLAGS...@{PAR}

          1 = Keep original datestamp@{PAR}

          2 = Keep original protection bits@{PAR}

          4 = Keep original comment@{PAR}

          8 = Set archive bit@{PAR}

         16 = Check destination free space.@{PAR}


DateFormat  FLAGS@{PAR}

    Corresponds to Operation/Date format@{PAR}

     FLAGS...@{PAR}

          1 = AmigaDOS format (DD-MMM-YY)@{PAR}

          2 = International format (YY-MM-DD)@{PAR}

          4 = USA format (MM-DD-YY)@{PAR}

          8 = English/Australian format (DD-MM-YY)@{PAR}

         16 = Name substitution (Today, Tomorrow, etc.)@{PAR}

         32 = 12 hour clock@{PAR}


DefaultTool  TOOLNAME@{PAR}

    The current Default Tool for project icons created with@{PAR}
    @{" AddIcon " link AddIcon}.@{PAR}


DeleteFlags  FLAGS@{PAR}

    Corresponds to Operation/@{" Delete " link Delete}@{PAR}

     FLAGS...@{PAR}

          1 = Ask before commencing delete@{PAR}

          2 = Ask before deleting files@{PAR}

          4 = Ask before deleting non-empty directories@{PAR}

          8 = Set delete protection bit@{PAR}


DirFlags  FLAGS@{PAR}

    Corresponds to System/Directories.@{PAR}

     FLAGS...@{PAR}

          1 = Always move to empty buffer@{PAR}

          2 = Use ExAll() to read directories@{PAR}

          4 = Auto diskchange@{PAR}

          8 = Auto disk load@{PAR}

         16 = Search buffers on Double-click@{PAR}

         32 = Re-read changed or incomplete buffers@{PAR}

         64 = Search buffers on Parent/Root operation@{PAR}

        128 = Expand pathnames@{PAR}


DisplayLength  WIN  TYPE  LENGTH@{PAR}

    Corresponds to Operation/List format's length fields. This@{PAR}
    sets the lengths of some of the directory list items.@{PAR}

        WIN  The window to act upon@{PAR}
             (-1 = current  window, 0=left or 1= right).@{PAR}

     TYPE...@{PAR}

          0 = Name@{PAR}

          1 = Comment@{PAR}

          2 = Filetype@{PAR}


ErrorFlags  FLAGS@{PAR}

    Corresponds to Operation/Error check@{PAR}

     FLAGS...@{PAR}

          1 = Enable DOS requesters@{PAR}

          2 = Enable error requester@{PAR}


FadeDelay  TIME@{PAR}

    Corresponds to Configuration: System/View & Play's fade delay.@{PAR}


Filter Adjust  [FILEPATTERN]@{PAR}

    The global filename filter. If filepattern is not given@{PAR}
    then global filter will be turned off.@{PAR}


Font  IDNUMBER  FONT  SIZE@{PAR}

    Corresponds to Screen/Fonts. This takes three values; the ID@{PAR}
    number of the font to change, the name of the new font, and the@{PAR}
    point size of the font.@{PAR}


     IDNUMBER...@{PAR}

          0 = General (8 point font)@{PAR}

          1 = Directory window font@{PAR}

          2 = Text viewer font@{PAR}

          3 = Buttons@{PAR}

          4 = Menus@{PAR}

          5 = Status bar@{PAR}

          6 = Disk names@{PAR}

          7 = Clock bar@{PAR}

          8 = Requesters@{PAR}

          9 = Path fields@{PAR}

         10 = Button iconify@{PAR}


GeneralFlags  FLAGS@{PAR}

    Corresponds to Operation/General@{PAR}

     FLAGS...@{PAR}

          2 = Display info@{PAR}

          8 = File double-click@{PAR}

         64 = Window slider activate@{PAR}

        128 = Click-m-click drag@{PAR}


HelpFile  PATHNAME@{PAR}

    Allows you to specify a help file to load when @{" Help " link 1.8.?} is@{PAR}
    pressed.@{PAR}


HidePattern PATTERN@{PAR}

    Corresponds to System/Show pattern's hide pattern@{PAR}


IconFlags  FLAGS@{PAR}

    Corresponds to Operation/Icons@{PAR}

     FLAGS...@{PAR}

          1 = Create icons with directories @{PAR}

          2 = Perform all actions on icons as well@{PAR}

          4 = Select icons automatically@{PAR}


IconifyFlags  FLAGS@{PAR}

    Corresponds to System/Clocks.@{PAR}

     FLAGS...@{PAR}

          1 = Memory monitor@{PAR}

          2 = CPU monitor@{PAR}

          4 = Date@{PAR}

          8 = Time @{PAR}

         16 = No window@{PAR}

         32 = Appicon@{PAR}

         64 = Memory in bytes@{PAR}

        128 = C: and F:@{PAR}

    Note that No window and AppIcon are mutually exclusive. If@{PAR}
    the two flags are specified together the results will be@{PAR}
    unpredictable.@{PAR}


ListFormat  WIN  ITEMS@{PAR}

    Corresponds to Operation/List format. The value for this@{PAR}
    is not a combination of flags, but instead a list of numbers@{PAR}
    representing items.@{PAR}

        WIN  The window to act upon@{PAR}
             (-1 = current window, 0=left or 1=right).@{PAR}

      ITEMS  Up to five numbers, which indicate what data is to be@{PAR} 
             displayed and in what order.@{PAR}

     ITEMS...@{PAR}

          0 = Name@{PAR}

          1 = Size@{PAR}

          2 = Protection@{PAR}

          3 = Datestamp@{PAR}

          4 = Comment@{PAR}

          5 = Filetype@{PAR}


OutputCmd  SHELLCOMMAND@{PAR}

    Corresponds to System/AmigaDOS/Shell command. This parameter does@{PAR}
    not work at the moment. Will be corrected in future versions.@{PAR}


OutputWindow  CONSOLEDEFINITION@{PAR}

    Corresponds to System/AmigaDOS/Output window. This parameter does@{PAR}
    not work at the moment. Will be corrected in future versions.@{PAR}


ReplaceFlags  FLAGS@{PAR}

    Corresponds to Operation/@{" Copy " link Copy}@{PAR}

     FLAGS...@{PAR}

          1 = Always replace files@{PAR}

          2 = Never replace files@{PAR}

          4 = Replace only older files@{PAR}

          8 = Ask before replacing@{PAR}


ScreenMode  MODE@{PAR}

    Corresponds to Screen/Screen mode.@{PAR}

     MODE values...@{PAR}

          1 = Open on Workbench's screen@{PAR}

          2 = Open a clone of Workbench's screen@{PAR}

    Mode ID's are also supported. Some common mode ID's@{PAR}
    are...@{PAR}

        32768 = High Res screen@{PAR}

        32772 = High Res Laced screen@{PAR}

        32800 = Super-High Res screen@{PAR}

        32804 = Super-high Res Laced screen@{PAR}

       233508 = Productivity screen@{PAR}

       233509 = Productivity Laced screen@{PAR}

       266240 = A2024 10 Hz screen@{PAR}

       299008 = A2024 15 Hz screen@{PAR}


ScrDepth  DEPTH@{PAR}

    Corresponds to Screen/Screen mode's depth. The depth can be@{PAR}
    2,3, or 4 bitplanes. That is the same as four, eight or sixteen@{PAR}
    colours.@{PAR}


ScreenFlags  FLAGS@{PAR}

    Corresponds to Screen/Screen mode.@{PAR}

     FLAGS...@{PAR}

          1 = Use default screen width@{PAR}

          2 = Use default screen height@{PAR}

          4 = Half-height screen@{PAR}


ScrClockFlags  FLAGS@{PAR}

    Corresponds to System/Clocks.@{PAR}

     FLAGS...@{PAR}

          1 = Memory monitor@{PAR}

          2 = CPU monitor@{PAR}

          4 = date@{PAR}

          8 = Time@{PAR}

         64 = Memory in bytes@{PAR}

        128 = C: and F:@{PAR}


ScrH  HEIGHT@{PAR}

    Corresponds to Screen/Screen mode's height.@{PAR}


ScrW  WIDTH@{PAR}

    Corresponds to Screen/Screen mode's width.@{PAR}


SeparateMethod  WIN  METHOD@{PAR}

    Corresponds to Operation/List format's cycle button.@{PAR}

        WIN  The window to act upon (-1 = current window, 0=left or@{PAR}
             1 = right).@{PAR}

     METHODS...@{PAR}

          0 = Mix files and directories@{PAR}

          1 = Display directories first@{PAR}

          2 = Display files first@{PAR}


ShowDelay  DELAY@{PAR}

    Corresponds to Configuration: System/View & Play's show delay.@{PAR}


ShowFreeFlags FLAGS@{PAR}

    Corresponds to System/Directory flags.@{PAR}

     FLAGS...@{PAR}

          1 = Bytes free@{PAR}

          2 = Kilo/Megabytes free@{PAR}

          4 = Blocks free@{PAR}

          8 = Percentage of space free@{PAR}

    These bits are mutually exclusive. If more than one is@{PAR}
    specified at a time the results will be unpredictable.@{PAR}


ShowPatBits  FLAGS@{PAR}

    Corresponds to System/Show pattern's hidden bit flag@{PAR}

     FLAGS...@{PAR}

          1 = Hide files with hidden bit set.@{PAR}


ShowPattern  PATTERN@{PAR}

    Corresponds to System/Show pattern's show pattern@{PAR}


SortFlags  FLAGS@{PAR}

    Corresponds to Operation/List format's sort flag@{PAR}

     FLAGS...@{PAR}

          1 = Reverse sort in left window@{PAR}

          2 = Reverse sort in right window@{PAR}


SortMethod  WIN  ITEM@{PAR}

    Corresponds to Operation/List format's checked sort item.@{PAR}

        WIN  The window to act upon (-1 = current window, 0=left or@{PAR}
             1 = right).@{PAR}

     ITEMS...@{PAR}

          0 = Name@{PAR}

          1 = Size@{PAR}

          2 = Protection@{PAR}

          3 = Datestamp@{PAR}

          4 = Comment@{PAR}

          5 = Filetype@{PAR}


UpdateFlags  FLAGS@{PAR}

    Corresponds to Operation/Update@{PAR}

     FLAGS...@{PAR}

          1 = Update free disk space@{PAR}

          2 = Scroll directory window to follow operations@{PAR}

          4 = Redraw more than a quarter of a page@{PAR}

          8 = Directory refresh using StartNotify()@{PAR}

         16 = Left-justify filename in status bar@{PAR}

         32 = Display progress indicator@{PAR}

         64 = Current file progress indicator@{PAR}

        128 = Update listview slider while scanning@{PAR}


ViewPlayFlags  FLAGS@{PAR}

    Corresponds to System/View & Play.@{PAR}

     FLAGS...@{PAR}

          1 = Black background between pictures@{PAR}

          2 = Turn audio filter off for 8SVX play@{PAR}

          4 = 8-bits per gun colour@{PAR}

          8 = LoopPlay 8SVX sound files on double-click@{PAR}

         16 = Text viewer borders@{PAR}

         32 = Start animations paused@{PAR}

         64 = Pick best screen-mode@{PAR}

        128 = View in Window@{PAR}


WindowSize  OFFSET@{PAR}

    Adjusts the placement of the center bar of Directory Opus's@{PAR}
    directory windows.@{PAR}
@{LINDENT 1}


Any Modify command that change display characteristics (screen
size, mode and depth, list format, etc) will not take effect until you
execute the @{" Redraw " link Redraw} command. For commands that only change directory
display characteristics, you use the @{" DisplayDir " link DisplayDir} command to update the
directory display. Some modifications (like date format, hide and show
pattern, etc.) will not take effect until the directory is actually re-
read (for instance, when the @{" Rescan " link Rescan} command is used). For example, 
you could have two buttons configured to switch between a High Res
screen with 8 colours, and a High Res Interlaced screen with 4 colours.
The definitions for these buttons might be:@{PAR}
@{LINDENT 4}

LACEON - Command Modify ScreenMode 32772@{PAR}
         Command Modify ScrDepth 2 @{PAR}
         Command Redraw@{PAR}

LACEOFF - Command Modify ScreenMode 32768@{PAR}
          Command Modify ScrDepth 3@{PAR}
          Command Redraw@{PAR}
@{LINDENT 1}

As another example, you might wish to change the left window to be
sorted by Date, but to leave the right window alone. For this, you
would have the command:@{PAR}
@{LINDENT 4}

Command Modify SortFlags 0 3@{PAR}
Command Rescan 0@{PAR}
@{LINDENT 1}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE Move "Tech Guide/Commands"
@{LINDENT 1}

@{b}Move  [NAME]  [DESTINATION]@{ub}@{PAR}


          NAME  optional; name of file@{PAR}

   DESTINATION  optional; destination path@{PAR}


This allows you to move all selected files and directories form
the active directory window to the inactive window. The file or 
directory will be copied to the destination, and the original will
be deleted.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE MoveAs "Tech Guide/Commands"
@{LINDENT 1}

@{b}MoveAs  [NAME]  [NEW NAME]@{ub}


       NAME  optional; name of file@{PAR}

   NEW NAME  optional; new file name@{PAR}


This command moves all selected files and directories from the
active directory window to the inactive window, and allows you to
specify a new name for each file or directory. The file or directory
will be copied to the destination under the new name, and the original
will be deleted.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE NewCLI "Tech Guide/Commands"
@{LINDENT 1}

@{b}NewCLI  [HANDLE]@{ub}@{PAR}


   HANDLE  optional; CLI console handle to use@{PAR}


This command opens a CLI from within Directory Opus, using the
output window defined in the configuration. The new CLI will be
separate from Directory Opus, so to end the CLI you must type EndCLI,
as usual.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE NextDrives "Tech Guide/Commands"
@{LINDENT 1}

@{b}NextDrives@{ub}@{PAR}

This command simply flips to the next bank of drive buttons.


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE None "Tech Guide/Commands"
@{LINDENT 1}

@{b}None@{ub}@{PAR}

This command deselects all files and directories in the active
directory window.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE notify "Tech Guide/Commands"
@{LINDENT 1}

@{b}Notify MESSAGE@{ub}@{PAR}


    MESSAGE  text to print in requester@{PAR}


Displays requester with given message text@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE OtherWindow "Tech Guide/Commands"
@{LINDENT 1}

@{b}OtherWindow@{ub}@{PAR}

This is the same as pressing the space bar, and activates the
inactive directory window.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE Parent "Tech Guide/Commands"
@{LINDENT 1}

@{b}Parent  [WIN]@{ub}@{PAR}


   WIN  optional; window to do a parent of@{PAR}
        (-1 = current window, 0=left or 1=right)@{PAR}
        defaults to -1.@{PAR}


This will read the parent directory of the directory open in the
active directory window (or the specified window).@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE ParentList "Tech Guide/Commands"
@{LINDENT 1}

@{b}ParentList  [WIN]@{ub}@{PAR}


   WIN  optional; window to display the parent list of@{PAR}
        (-1 = current window, 0=left or 1=right)@{PAR}
        defaults to -1.@{PAR}


This will display a list of parent directories for the directory
currently displayed in the active window (or the specified window).
That's just the same window that comes up when you double-click on
the @{" disk name field " link 1.5.2}.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE PatternMatch "Tech Guide/Commands"
@{LINDENT 1}

@{b}PatternMatch  PATTERN  STRING@{ub}@{PAR}

@{" ARexx Only " link ComRefInf 8}@{PAR}


   PATTERN  pattern string@{PAR}

    STRING  string to match to patten@{PAR}


This will return a boolean value to indicate whether the supplied
string matches the supplied pattern (which may include full wildcards).@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = 0 if string does not match, 1 if it does@{PAR}

@ENDNODE
@NODE Play "Tech Guide/Commands"
@{LINDENT 1}

@{b}Play  [NAME]@{ub}@{PAR}


   NAME  optional; name of file@{PAR}


This will attempt to play each selected file. If the file is an
8SVX format IFF sampled sound (of the type generated by AudioMaster,
for instance), the speed and other information from within the file
will be used. The Play routine plays both mono and stereo IFF 8SVX
files. When playing a file that is not IFF 8SVX, it will assume a
speed of 10000 samples/second.@{PAR}

This command also plays song modules. See @{" PlayST " link PlayST} for more
information.@{PAR}

Each file is played once only, unlike the @{" LoopPlay " link LoopPlay} command,
which plays each file continuously.@{PAR}

If the System/View/Play/Turn audio filter off for play option is
selected, the high-pass audio filter will be turned off while a sound
is playing.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE PlayST "Tech Guide/Commands"
@{LINDENT 1}

@{b}PlayST  [NAME]@{ub}@{PAR}


   NAME  optional; name of file@{PAR}


Play a song module. Directory Opus supports
Sound/Noise/ProTracker, Oktalizer and MED modules.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE Print "Tech Guide/Commands"
@{LINDENT 1}

@{b}Print  [NAME]@{ub}@{PAR}


   NAME  optional; name of file@{PAR}


The print routine is a full-featured text formatter. See @{" Print Requester " link 2.6} for
more information.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE PrintDir "Tech Guide/Commands"
@{LINDENT 1}

@{b}PrintDir  [WIN]@{ub}@{PAR}


   WIN  optional; window to scan the buffer list into@{PAR}
        (-1 = current window, 0=left or 1=right)@{PAR}
        defaults to -1.@{PAR}


This command allows you to print the directory in the active directory window
(or the specified window). You are able to choose the information you want to
print (file sizes, protection bits, dates and comments). This command
is not started as a separate process, unlike the @{" Print " link Print} command.
PrintDir also allows you to specify the output file to which the
directory is to be printed. This can be PRT: (i.e. your printer, the 
default) or a disk file.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE Protect "Tech Guide/Commands"
@{LINDENT 1}

@{b}Protect  [NAME]  [BITS]@{ub}@{PAR}


   NAME  optional; name of file@{PAR}

   BITS  optional; bits to set on given file@{PAR}


The Protect command now allows you to specify bit-masking. This
lets you mask some bits as untouchable. You can selectively add or
remove certain bits while leaving other bits in their original state.@{PAR}

See @{" Protection Requester " link 2.1} for more information.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE Query "Tech Guide/Commands"
@{LINDENT 1}

@{b}Query ITEM  [WIN]@{ub}@{PAR}

@{" ARexx Only " link ComRefInf 8}@{PAR}


   ITEM  configuration item to query@{PAR}

    WIN  optional; window argument that some items need@{PAR}
         (-1 = current window, 0=left or 1=right)@{PAR}
         defaults to -1.@{PAR}


Returns the current value of a specified configuration item.
These items are described in the @{" Modify " link Modify} command. Any item that can
be modified can be queried.@{PAR}

Several of the configuration items need an additional window
argument. These are ListFormat, DisplayLength, SortMethod and
SeparateMethod.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = current value of the specified item@{PAR}

@ENDNODE
@NODE Quit "Tech Guide/Commands"
@{LINDENT 1}

@{b}Quit  [FORCE]@{ub}@{PAR}


   FORCE  optional; do not ask user for confirmation.@{PAR}


This command will exit Directory Opus (providing there is not a
print operation happening at the time.)  If the configuration has been
modified and not saved, you are asked if you wish to save it first.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE Read "Tech Guide/Commands"
@{LINDENT 1}

@{b}Read  [NAME]@{ub}@{PAR}


   NAME  optional; name of file@{PAR}


This command allows you to read selected files. See @{" Text Viewer " link 2.7} for
more information.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE Redraw "Tech Guide/Commands"
@{LINDENT 1}

@{b}Redraw@{ub}@{PAR}

This command will completely redraw the Directory Opus screen.
The screen is closed, and then re-opened.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE Relabel "Tech Guide/Commands"
@{LINDENT 1}

@{b}Relabel  [DEVICE]   [NEWNAME]@{ub}@{PAR}


    DEVICE  optional; device to relabel@{PAR}

   NEWNAME  new name to give to selected device@{PAR}


This command allows you to change the name (label) of the disk
that is open in the active directory window.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE Remember "Tech Guide/Commands"
@{LINDENT 1}

@{b}Remember@{ub}@{PAR}

This command allows you to make temporary changes with the 
@{" Modify " link Modify} command, and then restore all the settings later.@{PAR}


ARexx Result:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE RemoveEntry "Tech Guide/Commands"
@{LINDENT 1}

@{b}RemoveEntry  NUMBER  SHOW@{ub}@{PAR}


   NUMBER  number of entry to remove@{PAR}

     SHOW  boolean, indicates whether to update display@{PAR}


Removes an entry by ordinal number.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = 0 entry was not found, 1 entry was found and removed@{PAR}

@ENDNODE
@NODE RemoveFile "Tech Guide/Commands"
@{LINDENT 1}

@{b}RemoveFile  NAME  SHOW@{ub}@{PAR}


   NAME  the file entry to remove@{PAR}

   SHOW  boolean indicates whether to update display@{PAR}


This command removes the specified entry form the active directory
window, and returns a boolean indicating whether the entry was found
and removed. Show is a boolean indicating whether you want the display
updated or not.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = 0 entry was not found, 1 entry was found and removed@{PAR}

@ENDNODE
@NODE Rename "Tech Guide/Commands"
@{LINDENT 1}

@{b}Rename  [NAME] [NEWNAME]@{ub}@{PAR}


      NAME  optional; name of file@{PAR}

   NEWNAME  optional; newname to give to selected file@{PAR}


This allows you to rename all selected files and directories. You
may use a * to specify a pattern. If no * is used, you are asked for a
new name for each individual file.@{PAR}

To add a prefix or a suffix (or both) to all selected entries, use
a * in the second string field. For example, to add HIRES as a prefix
and .pic as a suffix to all selected entries, enter HIRES*.pic.@{PAR}

To change a prefix or a suffix (or both) on all selected entries,
use a * in the top string field. For example, to change HIRES to
MEDRES as a prefix, and.pic to .iff as a suffix, enter HIRES*.pic in
the top string field, and MEDRES*.iff in the bottom string field.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE Request "Tech Guide/Commands"
@{LINDENT 1}

@{b}Request  MESSAGE@{ub}@{PAR}


   MESSAGE  text to print in the requester@{PAR}


Displays requester with given message text and two buttons
(Okay | Cancel). This one is just kept for compatability reasons. Use
the @{" Verify " link Verify} command instead.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = 0 cancel was selected, 1 okay was selected@{PAR}

@ENDNODE
@NODE Rescan "Tech Guide/Commands"
@{LINDENT 1}

@{b}Rescan  [WIN]@{ub}@{PAR}


   WIN  optional; window to rescan@{PAR}
        (-1 = current window, 0=left or 1=right)@{PAR}
        defaults to -1.@{PAR}


This causes the directory in the active window (or the specified window) to
be re-read. This has exactly the same effect as activating the directory
string field and pressing return, without modifying the directory name.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE Reselect "Tech Guide/Commands"
@{LINDENT 1}

@{b}Reselect@{ub}@{PAR}

This command will reselect all entries that were selected before
the last operation was initiated.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE Restore "Tech Guide/Commands"
@{LINDENT 1}

@{b}Restore@{ub}@{PAR}

This command is used to restore the previously @{" Remembered " link Remember} settings.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE Root "Tech Guide/Commands"
@{LINDENT 1}

@{b}Root  [WIN]@{ub}@{PAR}


   WIN  optional; window to scan the buffer list into@{PAR}
        (-1 = current window, 0=left or 1= right_@{PAR}
        defaults to -1.@{PAR}


This command reads the root directory of the active or specified
window.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE Run "Tech Guide/Commands"
@{LINDENT 1}

@{b}Run  [NAME]@{ub}@{PAR}


   NAME  optional; name of file@{PAR}


This command allows you to run each selected file in turn,
providing that file is executable. This will have much the same
effect as if you had double-clicked on the file's icon, or run it from
CLI. A requester will appear, asking for arguments (should program
require any).@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE SaveConfig "Tech Guide/Commands"
@{LINDENT 1}

@{b}SaveConfig  [FILENAME]@{ub}@{PAR}


   FILENAME  optional; configuration file to save to@{PAR}


This command saves the configuration to the file that it was read
from initially. See also @{" Configure " link Configure} and @{" LoadConfig " link LoadConfig}.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE ScanDir "Tech Guide/Commands"
@{LINDENT 1}

@{b}ScanDir  PATH  [WIN]@{ub}@{PAR}


   PATH  path to read@{PAR}

    WIN  optional; window to read directory into@{PAR}
         (-1 = current window, 0=left or 1=right)@{PAR}
         defaults to -1.@{PAR}


This command allows you to read a directory in much the same way
as the drive buttons. For example:@{PAR}
@{LINDENT 4}

Command ScanDir Dh0:work@{PAR}
@{LINDENT 1}

would read the DH0:Work directory into the current window.@{PAR}

One usage of this allows you to have an entire bank of buttons
devoted to "drive buttons". You could then set up a button on every
other bank that would, using the @{" Modify " link Modify} command, jump to that bank.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE ScrollH "Tech Guide/Commands"
@{LINDENT 1}

@{b}ScrollH  CHARS  [WIN]@{ub}@{PAR}


   CHARS  characters to scroll@{PAR}

     WIN  optional; window to scroll@{PAR}
          (-1 = current window, 0=left or 1=right)@{PAR}
          default to -1.@{PAR}


This will scroll the directory window horizontally by the
specified number of characters (either positive or negative).@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = new horizontal position@{PAR}

@ENDNODE
@NODE ScrollToShow "Tech Guide/Commands"
@{LINDENT 1}

@{b}ScrollToShow  ENTRY  [WIN]@{ub}@{PAR}


   ENTRY  entry to make visible. May be either a name or@{PAR}
          wildcard pattern, or the ordinal number of the desired@{PAR}
          entry.@{PAR}

     WIN  optional; window to scroll@{PAR}
          (-1 = current window, 0=left or 1=right)@{PAR}
          defaults to -1.@{PAR}


This command will try to scroll the specified entry into view.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = 0 if entry was not found, 1 if it was found@{PAR}

@ENDNODE
@NODE ScrollV "Tech Guide/Commands"
@{LINDENT 1}

@{b}ScrollV  LINES  [WIN]@{ub}@{PAR}


   LINES  lines to scroll@{PAR}

     WIN  optional; window to scroll@{PAR}
          (-1 = current window, 0=left or 1=right)@{PAR}
          defaults to -1.@{PAR}


This will scroll the directory window vertically by the specified
number of lines (either positive or negative).@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = new vertical position@{PAR}

@ENDNODE
@NODE Search "Tech Guide/Commands"
@{LINDENT 1}

@{b}Search  [NAME]  [PATTERN]  [UCNLC]  [WILD]  [BYWORD]@{ub}@{PAR}


      NAME  optional; name of file@{PAR}

   PATTERN  optional; text pattern to search for@{PAR}

     UCNLC  optional; uppercase characters does not equal lower@{PAR}
            case characters.@{PAR}

      WILD  optional; pattern contains wildcard characters@{PAR}

    BYWORD  optional; match only whole words@{PAR}


This command allows you to search all selected files for a
specified string, which may contain wildcards and @{" ASCII codes " link 1.6.search}.
If a match is found, you are told which file contains the string, and you
are given the option to enter the text viewer and read the file. If you
opt to do this, a search for the string is automatically initiated once
the file has been read by the text viewer.@{PAR}

If any directories are selected, all the files within those
directories are also searched.@{PAR}

The flags ucnlc, wild and byword are off by default.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE Select "Tech Guide/Commands"
@{LINDENT 1}

@{b}Select  [PATTERN]  [ONLYFILE|ONLYDIRS]  [NAME|DATE|PROTECTION]@{ub}@{PAR}


      PATTERN  optional; pattern to select by@{PAR}

    ONLYFILES  optional; select only files, defaults to both files@{PAR}
               and directories.@{PAR}

     ONLYDIRS  optional; select only directories@{PAR}

         NAME  optional; match on name, (default)@{PAR}

         DATE  optional; match on date@{PAR}

   PROTECTION  optional; match on protection bits@{PAR}


When used in name mode (default) this command allows you to select
files and directories in the active directory window using wildcards.
All standard @{" wildcards " link wldcrdpat} are supported.@{PAR}

When used in date mode you can select all files and directories
created or modified on a certain date only. Simply enter that date
(e.g. 28-Mar-90 would select all entries with datestamps set to any
time on the 28th of March, 1990). You can also use word like
Yesterday, Today, Tuesday, etc. If you can also specify a specific
time. Simply enter the time (in the format HH:MM:SS). If you enter a
time, however, the datestamp must match that time exactly for the
entry to be selected. If you enter a time but not a date it will
select files created today that match that time.@{PAR}

You can also select a range of dates. For instance, to select all
entries created or modified between the 18th of April, 1989 and the
22nd of September, 1991, you would enter:@{PAR}
@{LINDENT 4}

18-Apr-89 > 22-Sep-91@{PAR}
@{LINDENT 1}

The > character does not in this case signify "greater than"; it
simply indicates a range of dates. It must have at least one space on
either side of it.@{PAR}

To select all files from the beginning of time to, for instance,
the 3rd of January, 1990, you would enter:@{PAR}
@{LINDENT 4}

> 3-Jan-91
@{LINDENT 1}

To select all files from, for example, the 12th of July, 1983 to
the current date (today) you would enter:@{PAR}
@{LINDENT 4}

12-Jul-83 >@{PAR}
@{LINDENT 1}

You may also specify times when entering date ranges.@{PAR}

If used in protect bit mode you may specify protection bits that
are allowed to be set, and bits that are not. If a bit or group of
bits is allowed to be set, precede it with a + character. If a bit or
group of bits is not allowed to be set precede it with a - character.
The initial + character is assumed. For instance, to select all
readable and writeable files, you would simply enter:@{PAR}
@{LINDENT 4}

rw@{PAR}
@{LINDENT 1}

Or, you could enter:@{PAR}
@{LINDENT 4}

+rw@{PAR}
@{LINDENT 1}

Both these would have the same effect. To expand upon this, and
select all readable and writeable files, but not those that have the
hidden or archive bits set, you would enter:@{PAR}
@{LINDENT 4}

rw-ha@{PAR}
@{LINDENT 1}

Or, to select files that do not have the bits SPED set, you would
enter:@{PAR}
@{LINDENT 4}

-sped@{PAR}
@{LINDENT 1}

The Select command is additive; i.e. entries not matching the
given pattern are not deselected.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE SelectEntry "Tech Guide/Commands"
@{LINDENT 1}

@{b}SelectEntry  NUMBER  [STATE]  [SHOW]@{ub}@{PAR}


   NUMBER  ordinal number of entry to select@{PAR}

    STATE  optional; selection state@{PAR}
           (-1 = toggles, 0 = unselect and 1 = select)@{PAR}
           defaults to -1@{PAR}

     SHOW  optional; boolean indicating whether to update display@{PAR}


Selects an entry in the active window@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = previous select status of entry or -1 if it could not be found.@{PAR}

@ENDNODE
@NODE SelectFile "Tech Guide/Commands"
@{LINDENT 1}

@{b}SelectFile  NAME  [STATE]  [SHOW]@{ub}@{PAR}


    NAME  name of entry to select@{PAR}

   STATE  optional; selection state@{PAR}
          (-1 = toggles, 0 = unselect and 1 = select)@{PAR}
          defaults to -1@{PAR}

    SHOW  optional; boolean indicating whether to update display@{PAR}


This command will select the entry specified by the file name, as
if it had just been clicked on.@{PAR}


Arexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = previous select status of file or -1 if it cold not be found@{PAR}

@ENDNODE
@NODE SetVar "Tech Guide/Commands"
@{LINDENT 1}

@{b}SetVar  VARIABLE  CONTENT@{ub}@{PAR}


 VARIABLE  name of the internal variable@{PAR}

  CONTENT  content of the variable@{PAR}


This command lets you create internal variables and define their content. These variables
can later on be reffered with the {v} @{" argument function " link SimArgFun}. It's
difficult to explain, so here's an example:@{PAR}

Create a button called "Remember dir" and define its action like this:@{PAR}
@{LINDENT 4}

COMMAND:  SetVar RememberedDir {s}@{PAR}
@{LINDENT 1}

Create another button called "Restore dir" and define its action like this:@{PAR}
@{LINDENT 4}

COMMAND:  ScanDir {vRememberedDir}@{PAR}
@{LINDENT 1}

The first button will "remember" the directory displayed in the currently active directory
window: It will store its path in the internal variable "RememberedDir".@{PAR}

The second button will allow you to switch back to that directory at any time. It invokes the
@{" ScanDir " link ScanDir} command with the internal variable "RememberedDir" as an argument.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE SetWinTitle  "Tech Guide/Commands"
@{LINDENT 1}

@{b}SetWinTitle  TITLE  [WIN]@{ub}@{PAR}


   TITLE  title string to use@{PAR}

     WIN  optional; window to modify@{PAR}
          (-1 = current window, 0 = left or 1 = right)@{PAR}
          defaults to -1.@{PAR}


Sets title of active or specified window to given string.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE Show "Tech Guide/Commands"
@{LINDENT 1}

@{b}Show  [NAME]@{ub}@{PAR}


   NAME  optional; name of file@{PAR}


This command is very versatile indeed. It will display IFF ILBM
pictures and brushes, Workbench icons, and fonts.@{PAR}

See @{" Show button " link 1.6.show} for more informations.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE SmartRead "Tech Guide/Commands"
@{LINDENT 1}

@{b}SmartRead  [NAME]@{ub}@{PAR}


   NAME  optional; name of file@{PAR}


This command invokes the text viewer in the same way as the
@{" Read " link Read} command. However, it checks the file for binary characters, and
if any are found, the file is @{" HexRead " link HexRead} instead.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE Status "Tech Guide/Commands"
@{LINDENT 1}

@{b}Status  VALUE  [SET NEWVALUE]@{ub}@{PAR}

@{" ARexx Only " link ComRefInf 8}@{PAR}


          VALUE  indicates the type of status you want@{PAR}

   SET NEWVALUE  optional; set the status to the specified value@{PAR}


This command returns the value for the specified status command
(listed below). If the set keyword is specified, this command will set
the status to the specified value (if appropriate for that status
command). Most status values can be set.@{PAR}

Some status commands require a sub-number. An example of this is
status 4, which returns the total number of files in a specific
directory window. The directory window may be either 0 (for the left-
hand window), 1 (for the right-hand window) or -1 (for the active
window). The command would therefore be status 4 0 for the left-hand
window, and status 4 1 for the right-hand window.@{PAR}

Status values are as follows:@{PAR}
@{LINDENT 3}


 1 - Current directory@{PAR}

      This returns or sets the pathname of the current directory.@{PAR}

      Status 1 [SET PATH]@{PAR}


 2 - Version@{PAR}

      This returns the current version number (as a string).@{PAR}

      Status 2@{PAR}


 3 - Active window@{PAR}

      This returns or sets the active directory window@{PAR}
      (either 0 or 1).@{PAR}

      Status 3 [SET WIN]@{PAR}


 4 - Number of files@{PAR}

      This returns the total number of files in the directory@{PAR}
      window.@{PAR}

      Status 4 WIN@{PAR}


 5 - Number of dirs@{PAR}

      This returns the total number of entries in the directory@{PAR}
      window.@{PAR}

      Status 5 WIN@{PAR}


 6 - Number of entries@{PAR}

      This returns the total number of entries in the directory@{PAR}
      window.@{PAR}

      Status 6 WIN@{PAR}


 7 - Number of selected files@{PAR}

      This returns the total number of selected files in directory@{PAR}
      window.@{PAR}

      Status 7 WIN@{PAR}


 8 - Number of selected dirs@{PAR}

      This returns the total number of selected directories in the@{PAR}
      directory window.@{PAR}

      Status 8 WIN@{PAR}


 9 - Number of selected entries@{PAR}

      This returns the total number of selected entries in the@{PAR}
      directory window.@{PAR}

      Status 9 WIN@{PAR}


10 - Total bytes@{PAR}

      This returns the total number of bytes (sum of the lengths@{PAR}
      of all files) in the directory window.@{PAR}

      Status 10 WIN@{PAR}


11 - Total selected bytes@{PAR}

      This returns the total number of selected bytes (sum of the@{PAR}
      lengths of all selected files) in the directory window.@{PAR}

      Status 11 WIN@{PAR}


12 - Select pattern@{PAR}

      This returns or sets the current Select pattern (used in@{PAR}
      the @{" Select " link Select} command).@{PAR}

      Status 12 [TYPE] [SET PATTERN]@{PAR}

      TYPES...@{PAR}
         0 = Name, Default@{PAR}
         1 = Date@{PAR}
         2 = Bits@{PAR}


13 - Directory name@{PAR}

      This returns the name of the directory that is open in the@{PAR}
      specified window. Setting this to another pathname will read@{PAR}
      that directory.@{PAR}

      Status 13 WIN [SET PATH]@{PAR}


14 - Disk name@{PAR}

      This returns the name of the disk that is open in the@{PAR}
      directory window. This cannot be set (use the @{" Relabel " link Relabel}@{PAR}
      command to change the disk name).@{PAR}

      Status 14 WIN@{PAR}


15 - Disk free bytes@{PAR}

      This returns the number of bytes free on the disk open in@{PAR}
      the directory window.@{PAR}

      Status 15 WIN@{PAR}


16 - Disk total bytes@{PAR}

      This returns the total number of bytes (free+used) on the@{PAR}
      disk open in the directory window.@{PAR}

      Status 16 WIN@{PAR}


17 - Buffered directory name@{PAR}

      This returns the pathname of the directory that is stored in@{PAR}
      a specific directory buffer (from 0 to 255).@{PAR}

      Status 17 WIN BUF@{PAR}


18 - Buffered diskname@{PAR}

      This returns the diskname of the directory stored in a@{PAR}
      specific directory buffer (from 0 to 255).@{PAR}

      Status 18 WIN BUF@{PAR}


19 - Buffered disk free bytes@{PAR}

      This returns the free space on the disk whose directory is@{PAR}
      stored in a specific directory buffer (from 0 to 255). This@{PAR}
      data may no longer reflect the actual free space on that@{PAR}
      disk.@{PAR}

      Status 19 WIN BUF@{PAR}


20 - Buffered disk total bytes@{PAR}

      This returns the total number of bytes (free+used) on the disk@{PAR}
      whose directory is stored in a specific directory buffer@{PAR}
      (from 0 to 255).@{PAR}

      Status 20 WIN BUF@{PAR}


21 - Buffer displayed@{PAR}

      This returns the number of the buffer that is displayed in@{PAR}
      the directory window, a number from 0 to 255. If this is@{PAR}
      set to a specific buffer that buffer will be the one shown@{PAR}
      in the directory window.@{PAR}

      Status 21 WIN [SET BUF]@{PAR}


22 - (unused in Directory Opus 4.x)@{PAR}


23 - (unused in Directory Opus 4.x)@{PAR}


24 - Entries per page@{PAR}

      This returns the number of entries that can be displayed per@{PAR}
      page.@{PAR}

      Status 24@{PAR}


25 - Configuration changed@{PAR}

      This returns a boolean value to indicate whether the @{PAR}
      configuration has been changed since it was last saved.@{PAR}
      See also @{" Configure " link Configure} and @{" SaveConfig " link SaveConfig}@{PAR}

      Status 25 [SET STATE]@{PAR}


26 - Okay string@{PAR}

      This returns the name of the Okay string in requesters.@{PAR}
      This also allows you to select the text of the positive@{PAR}
      button for the @{" Verify " link Verify} and @{" GetString " link GetString} commands.@{PAR}

      Status 26 [SET STRING]@{PAR}


27 - Cancel string@{PAR}

      This returns the name of the Cancel string in requesters.@{PAR}
      This also allows you to select the text of the negative@{PAR}
      button for the @{" Verify " link Verify} and @{" GetString " link GetString} commands.@{PAR}

      Status 27 [SET STRING]@{PAR}


28 - Currently iconified@{PAR}

      This returns a value indicating whether Directory Opus is@{PAR}
      currently iconified and if so what type of iconification it@{PAR}
      is. This will return 0 if not iconified, 1 if iconified and@{PAR}
      2 if button iconified.@{PAR}

      Status 28@{PAR}


29 - (unused in Directory Opus 4.x)@{PAR}


30 - Top text justification@{PAR}

      This returns a value indicating how the text in the status@{PAR}
      bar is rendered.@{PAR}

      Status 30 [SET TYPE]@{PAR}

      TYPES...@{PAR}
         0 = left@{PAR}
         1 = right@{PAR}
         2 = center@{PAR}


31 - (unused in Directory Opus 4.x)@{PAR}


32 - (unused in Directory Opus 4.x)@{PAR}


33 - (unused in Directory Opus 4.x)@{PAR}


34 - (unused in Directory Opus 4.x)@{PAR}
@{LINDENT 1}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = depends on which status was requested)@{PAR}

@ENDNODE
@NODE StopST "Tech Guide/Commands"
@{LINDENT 1}

@{b}StopST@{ub}@{PAR}

Stops playing a song module started with either @{" Play " link Play} or @{" PlayST " link PlayST}.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE SwapWindow "Tech Guide/Commands"
@{LINDENT 1}

@{b}SwapWindow@{ub}@{PAR}

Swaps the contents of the two directory windows.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE Toggle "Tech Guide/Commands"
@{LINDENT 1}

@{b}Toggle@{ub}@{PAR}

This command reverses the state of all files and directories in
the active directory (i.e. all selected entries are deselected, and
vice versa).@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE TopText "Tech Guide/Commands"
@{LINDENT 1}

@{b}Toptext  TEXT@{ub}@{PAR}

@{" ARexx Only " link ComRefInf 8}@{PAR}


   TEXT  text string to display@{PAR}


Displays given string in the status bar.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE Uniconify  "Tech Guide/Commands"
@{LINDENT 1}

@{b}Uniconify@{ub}@{PAR}

Returns to main program from iconified state. See also @{" Iconify " link Iconify}.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24}  = undefined@{PAR}

@ENDNODE
@NODE User1 "Tech Guide/Commands"
@{LINDENT 1}

@{b}User1, User2, User3, User4@{ub}@{PAR}

These commands will invoke the four user definable commands
associated with your filetypes. In the default configuration the
command User1 is defined to extract files from archives.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE Verify "Tech Guide/Commands"
@{LINDENT 1}

@{b}Verify  [TEXT]@{ub}@{PAR}


   TEXT  optional; text to display in requester@{PAR}


Displays "Are you sure?" requester. If this is included in a
multi-command operation, Cancel will abort the rest of the commands.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = 0 is cancel, 1 is okay@{PAR}

@ENDNODE
@NODE Version "Tech Guide/Commands"
@{LINDENT 1}

@{b}Version@{ub}@{PAR}

This command displays version information about Directory Opus,
Kickstart, Workbench and your computer.@{PAR}


ARexx Results:@{PAR}

@{" RC " link ComRefInf 24} = 0@{PAR}

@{" Result " link ComRefInf 24} = undefined@{PAR}

@ENDNODE
@NODE SimArgFun "Tech Guide/Simple Argument Functions"
@{LINDENT 1}

@{b}Argument Functions@{ub}@{PAR}

These are the argument functions that can be used as arguments when calling
external programs.@{PAR}

You can use more complicated functions too, to bring up a requester, asking
the user to enter some text or to select a file. Have a look at
the @{" requester functions " link ReqFun} for further information.@{PAR}


{d}  Destination directory window's path@{PAR}

     This will insert the path of the destination directory window.@{PAR}


{f}  First selected entry (with Path)@{PAR}

     Insert the path and filenames of the first selected entry. The@{PAR}
     entry will then be deselected.@{PAR}


{F}  All selected entries (with paths)@{PAR}

     Insert the path and filenames of all selected entries. The@{PAR}
     entries will then be deselected.@{PAR}

     AmigaDOS has limited the length of the command line to 256@{PAR}
     characters. Therefore, if the length of a command line exceeds@{PAR}
     256 characters because of a {F} sequence (or for any reason),@{PAR}
     another command line will be created for the next lot of file@{PAR}
     entries until there are no more selected file entries.@{PAR}


{fu} First selected entry (with path, do not deselect)@{PAR}

     The same as {f} except that the entry is not deselected@{PAR}
     after it is used.@{PAR}

{Fu} All selected entries (with paths, do not deselect)@{PAR}

     The same as {F} except that the entries are not deselected@{PAR}
     after they are used.@{PAR}


{o}  First selected entry (name only)@{PAR}

     The same as {f} except that only the name of the first selected@{PAR}
     entry is used, without the pathname.@{PAR}


{O}  All selected entries (names only)@{PAR}

     The same as {F} except that only the names of the selected entries@{PAR}
     are used, without the pathname. @{PAR}


{ou} First selected entry (name only, do not deselect)@{PAR}

     The same as {o} except that the entry is not deselected after@{PAR}
     it is used.@{PAR}


{Ou} All selected entries (name only, do not deselect)@{PAR}

     The same as {O} except that the entries are not deselected after@{PAR}
     they are used.@{PAR}


{Q}  Query the value of something@{PAR}

     This will query the value of one of DirOpus internal flags and insert@{PAR}
     it. Currently only two values are supported:@{PAR}

        {Qp} - Insert the name of the ARexx port of this invocation of@{PAR}
               Directory Opus. Every Directory Opus running will have a@{PAR}
               unique ARexx port name.@{PAR}

        {Qs} - Insert the name of the public screen Directory Opus is@{PAR}
               using. This can either be something like "DOPUS.1" or@{PAR}
               "DOPUS.2" (the number indicating the invocation count) if@{PAR}
               DirOpus is using its own screen, or "Workbench" if DirOpus@{PAR}
               is running on Workbench's screen.@{PAR}


{s}  Source directory window's path@{PAR}

     This will insert the path of the source directory window.@{PAR}


{v}  Pre-defined variable@{PAR}

     This will insert the content of a variable that was previously defined@{PAR}
     with the @{" SetVar " link SetVar} command. I.e., if you defined a variable "MyVariable",@{PAR}
     you could refer to this variable like this: {vMyVariable}@{PAR}


@ENDNODE
@NODE ReqFun "Tech Guide/Requester Functions"
@{LINDENT 1}

@{b}Requester Functions@{ub}@{PAR}

The Title string is the title that will appear on the requester. You
can just omit the Title string, in which case a default title will be used.@{PAR}

The Default string (preceded by a colon) is the default string that is
to appear in the requester. This too can be omitted.@{PAR}
@{LINDENT 4}


{RdTitle:Default}   Directory requester@{PAR}

                    Default can be any valid pathname@{PAR}


{RfTitle:Default}   File requester@{PAR}

                    Default can be any valid pathname of filename@{PAR}


{RFTitle:Default}   Multi-select file requester@{PAR}

                    Default can be any valid pathname or filename@{PAR}


{RoTitle:Default}   Font requester@{PAR}

                    Default can be any font name. A point size@{PAR}
                    can be specified with a slash followed by a@{PAR}
                    number (ie. topaz/8)@{PAR}


{RsTitle:Default}   Requester that asks for some text@{PAR} 

                    Default can be any text.@{PAR}
@{LINDENT 1}


The Default string can contain bracketed letters. These tell Directory
Opus where to insert additional information into the requester. The
supported bracketed letters include...@{PAR}
@{LINDENT 4}


[o] inserts the last referred filename, only the filename@{PAR}

[f] inserts the last referred filename, both path and filename@{PAR}

[s] inserts the source directory window's path@{PAR}

[d] inserts the destination directory window's path@{PAR}
@{LINDENT 1}


For example, it would be possible to have your own custom rename button
with the following call function:@{PAR}
@{LINDENT 4}

c:rename [f] {RsEnter new filename:Foo.[o]}@{PAR}
@{LINDENT 1}

In this case a string requester would open with the title "Enter new
filename" and the default of the string field would be "Foo." followed
by the selected filename.@{PAR}

@ENDNODE
@NODE WldCrdPat "Tech Guide/Wild Card Patterns"
@{LINDENT 1}

@{b}Wild Card Patterns@{ub}@{PAR}

Directory Opus can use wild cards to make some tasks easier. Wild card
characters are expressions that tell Directory Opus to match (or not
match, in some cases) more than just one character. You may already
have encountered pattern matching in the discussion of the Rename
command.@{PAR}
@{LINDENT 4}


?  This token will match any single character, but does not@{PAR}
   include none. For example, FI?E would match FILE, FINE and@{PAR}
   FIRE but not FIE.@{PAR}

#  This character tells Directory Opus to match the following@{PAR}
   expression) or more times. For instance, FRE#D would match@{PAR}
   FRE, FRED, FREDD, FREDDD, etc. "#?" will match anything, just@{PAR}
   like "*" (see below).@{PAR}

() is in effect an or. (p1|p2|p3) will match on any one of the@{PAR}
   patterns p1, p2, and p3. For instance, (D*G|C*T) would match@{PAR}
   DOG, CAT, DIG, COT, etc. You may include as many patterns@{PAR}
   inside the parentheses as you like, separated by vertical bars@{PAR}
   (|).@{PAR}

|  Use this token within parentheses to separate different@{PAR}
   expressions you wish to match at the same time. For example,@{PAR}
   "(ab|cd)" will match any one of the items separated by "|"@{PAR}
   (here, "ab" and "cd").@{PAR}

%  Matches 0 characters. This is always (useful in an instance@{PAR}
   like "(foo/bar/%)"). Another example: "CA(M/%)P" will match@{PAR}
   CAMP and CAP.@{PAR}

*  Synonym for "#?", an asterisk will match any number of@{PAR}
   repetitions of any characters, including none. For instance,@{PAR}
   "F*" will match F, FR, FRE, FRED, FREDD, FREDDY, etc.@{PAR}

~  The tilde can be used to negate an expression. Anything that @{PAR}
   would normally match, now will not match. For example,@{PAR}
   "F~(ROFG)" will match FROM but not FROG, "~J*" will not match@{PAR}
   anything starting with J.@{PAR}

[] Brackets enclose a list of characters (a "character class")@{PAR}
   that match any of the characters in the class. "[abc]" tells@{PAR}
   Directory Opus to match either "a", "b", or "c" in this@{PAR}
   position.@{PAR}

~  A tilde at the beginning of a character class matches any@{PAR}
   characters that are not in the class. For example, "[~bc]"@{PAR}
   says "match any character except "b" or "c".@{PAR}

-  A hyphen indicates a character range (only within character@{PAR}
   classes). The expression "[a-z]" represents all the lower case@{PAR}
   letters from "a" to "z".@{PAR}

'  (apostrophe or single quote) Use this character to declare the@{PAR}
   following character to be a literal character, used as it @{PAR}
   stands instead of as a wildcard. This permits you to use the@{PAR}
   characters #, ?, |, %, (,), [,], *, ~ and even an apostrophe as@{PAR}
   themselves rather than as pattern-matching control characters.@{PAR}
   For instance, YEAR*'% will match YEAR1989%, YEAR1990% but not@{PAR}
   YEAR 1989 or YEAR1990 as would normally be the case, with % @{PAR}
   meaning match on nothing. Note that this means that you must@{PAR}
   use '' to match an apostrophe.@{PAR}
@{LINDENT 1}


Note:  "Expression" in the above table means either a single character
(i.e. "#?"), or an alternation (i.e. "#(ab|cd|ef)"), or a character
class (i.e. "#[a-zA-Z]").@{PAR}

@ENDNODE
@NODE ShortCut "Tech Guide/Key Shortcuts"
@{LINDENT 1}

@{b}Simple Shortcut Keys@{ub}@{PAR}

These are the shortcut keys for slieders, non-configurable gadgets and stuff like that.
They can not be redefined.@{PAR}
@{LINDENT 4}

@{FG highlight}Action                             Shortcut Key@{FG text}@{PAR}

Toggle Help Mode                   Help@{PAR}

Activate Directory Field           Return Key@{PAR}

Max Right Window                   -@{PAR}
Max Left Window                    /@{PAR}
Center Windows                     =@{PAR}

Change Active Window               Spacebar@{PAR}

Scroll Window Up One Line          Up Arrow@{PAR}
Scroll Window Down One Line        Down Arrow@{PAR}
Scroll Window Up One Page          Shift Up Arrow@{PAR}
Scroll Window Down One Page        Shift Down Arrow@{PAR}
Scroll Window to Top               Control Up Arrow@{PAR}
Scroll Window to Bottom            Control Down Arrow@{PAR}

Scroll Window Right One Column     Right Arrow@{PAR}
Scroll Window Left One Column      Left Arrow@{PAR}
Scroll Window Right One Page       Shift Right Arrow@{PAR}
Scroll Window Left One Page        Shift Left Arrow@{PAR}
Scroll Window to Far Right         Control Right Arrow@{PAR}
Scroll Window to Far Left          Control Left Arrow@{PAR}

Bufferlist (tiny B button)         LAMIGA-B@{PAR}
Reselect   (tiny R button)         LAMIGA-R@{PAR}
Select     (tiny S button)         LAMIGA-S@{PAR}
ARexx      (tiny A button)         LAMIGA-A@{PAR}

Scroll To First Entry Starting     'A' - 'Z'@{PAR}
With A Certain Letter (A-Z)@{PAR}

Scroll To First File Starting      Shift 'A' - Shift 'Z'@{PAR}
With A Certain Letter (A-Z)@{PAR}
@{LINDENT 1}


@{b}Short Keys@{ub}@{PAR}

These are the default shortcut keys. Each of these can be redefined
using the ConfigOpus utility.@{PAR}
@{LINDENT 4}

@{FG highlight}Command        Shortcut Key@{FG text}@{PAR}

Add Icon       Left Shift Ctrl     I@{PAR}
All            Ctrl                A@{PAR}
Arc Extract    Ctrl                E@{PAR}
Check fit      Ctrl                F@{PAR}
Clone          Ctrl                L@{PAR}
Comment        Left Shift Ctrl     C@{PAR}
Configure      Right Amiga         C@{PAR}
Copy           Ctrl                C@{PAR}
Date Stamp     Ctrl                D@{PAR}
Delete         Left Shift Ctrl     D@{PAR}
Edit           Left Shift Ctrl     E@{PAR}
Get Sizes      Ctrl                G@{PAR}
Hex Read       Crtl                H@{PAR}
Hunt           Left Shift Ctrl     H@{PAR}
Iconify        Right Amiga         I@{PAR}
Icon Info      Ctrl                I@{PAR}
Make Dir       Ctrl                M@{PAR}
Move           Left Shift Ctrl     M@{PAR}
None           Ctrl                N@{PAR}
Parent         Ctrl                P@{PAR}
Play           Ctrl                Y@{PAR}
Print          Left Shift ctrl     P@{PAR}
Protect        Ctrl                T@{PAR}
Quit           Right Amiga         Q@{PAR}
Read           Ctrl                R@{PAR}
Rename         Left Shift Ctrl     R@{PAR}
Root           Ctrl                O@{PAR}
Run            Ctrl                U@{PAR}
Search         Left Shift Ctrl     S@{PAR}
Show           Ctrl                S@{PAR}

@ENDNODE
@NODE edfeat "Editing Features"
@{LINDENT 1}

@{b}Editing Features@{ub}@{PAR}

The following editing features can used whenever DirOpus expects you to enter some
text (i.e. in a string requester, or when typing in a directory name at the
@{" directory field" link 1.5.1}.@{PAR}
@{LINDENT 4}


@{i}Cursor key: @{ui}@{PAR}

Moves the cursor one space in the direction of the arrow.@{PAR}

@{i}Cursor key + Shift: @{ui}@{PAR}

Moves the cursor to the beginning or end of the string.@{PAR}

@{i}Backspace: @{ui}@{PAR}

Deletes the character to the left of the cursor.@{PAR}

@{i}Backspace + Shift: @{ui}@{PAR}

Deletes all chars from the beginning of the string to the current cursorposition.@{PAR}

@{i}Delete: @{ui}@{PAR}

Deletes the character under the cursor.@{PAR}

@{i}Delete + Shift: @{ui}@{PAR}

Deletes all chars from the current cursor position to the end of the string.@{PAR}

@{i}Right Amiga + x key: @{ui}@{PAR}

This is known as Amiga-X; It erases the entire string.@{PAR}

@{i}Right Amiga + c key: @{ui}@{PAR}

This is known as the "Copy to Clipboard" action. It copies the string to the
clipboard. Note: This is only available under AmigaOS 3.5 or higher!@{PAR}

@{i}Right Amiga + v key: @{ui}@{PAR}

This is known as the "Paste from Clipboard" action. It pastes the contents of the
clipboard into the string gadget, starting at the cursor position.This is only
available under AmigaOS 3.5 or higher!@{PAR}

@{i}Right Amiga + q key: @{ui}@{PAR}

This is known as Amiga-Q;  It restores the contents of a field to the previous information.@{PAR}

@ENDNODE
@NODE StaExtPrg "Tutorials/Starting External Programs"
@{LINDENT 1}

@{b}How we start external programs@{ub}@{PAR}

Directory Opus uses the small (4k) AmigaDOS program 'DOpusRT' to help
it launch AmigaDOS, WorkBench, Script and ARexx programs. When you
start up an external program a script file is created in the T:
directory. This script file contains all the initialisation and
execution code needed to start up and manage your programs.@{PAR}

The DOpuRT program is called at the end of the script file, and
communicates with Directory Opus to inform it when the script file has
finished running. This is needed for functions that are not run
asynchronously. It also doubles as a wait command, which is needed for
the adjustable close delay.@{PAR}

To take advantage of the current directory changing, adjustable stack,
and priority you will need the commands CD, Stack and Change TaskPri
in your computer's C:directory. You will also need the commands Run,
Execute, FailAt, NewCLI and EndCLI. These are almost always present
in your C: directory anyway (if not in ROM), so you should not need to
install them.@{PAR}

There are a couple of other points to be aware of. Because external
programs are run via a script file, they can be aborted like any other
script file by pressing CTRL-D. This is only possible if you have an
output window selected. If the script file is aborted in this fashion,
the output window effectively turns into a CLI, so you must type ENDCLI
to remove the window.@{PAR}

The second point is that if the program was not run asynchronously,
Directory Opus will be frozen, waiting for the signal back from the
DOpusRT program. If you abort the script file before it reaches
DOpusRT, Directory Opus will never unfreeze. You can force Directory
Opus to unfreeze by activating the Directory Opus window and pressing
SHIFT-ESC (the shift key in conjunction with the escape key). This also
allows you to turn any non-asynchronous program into an asynchronous
program, while the program is running.@{PAR}

Note that when using NewCLI or NewShell as the Output command, an error
such as unknown command will abort the script file as well. You should
therefore make sure that all your buttons, filetypes, hotkeys or menus
do not try to run nonexistent programs.@{PAR}

@ENDNODE
@NODE Glos "Tech Guide/Glossary"
@{LINDENT 1}

@{b}Glossary@{ub}@{PAR}

Some terms used in this manual that you may need to know are:@{PAR}
@{LINDENT 4}

@{i}Active (directory window) @{ui}@{PAR}

Denoted by a highlighted disk name. This is the source
directory, the directory that all commands will act upon.@{PAR}

@{i}Buffers (directory) @{ui}@{PAR}

A Directory Buffer is an internal storage area for directory
information. Whenever Directory Opus reads directory
information from a disk, it stores the information in a
Directory Buffer. By storing the directory information in a
buffer, Directory Opus can avoid unnecessarily re-reading the
disk.@{PAR}

@{i}Click-M-Click @{ui}@{PAR}

This is a Directory Opus term. To click-m-click is to click
with the mouse button, move the mouse to another part of the
screen, and press the mouse button again, all with the
double-click time set from Preferences.@{PAR}

This is used for various tasks: @{" swapping " link 1.5.2} the content
of the two directory windows, @{" entering " link 1.5.3.entering} a sub-directory
by displaying it in the destination window and many more.@{PAR}

An alternative to Click-M-Click is Click-Drag-Release (see below).@{PAR}

@{i}Click-Drag-Release @{ui}@{PAR}

This is an alternative method to Click-M-Click (which requires less mouse pointer
gymnastics). Click and hold on an unselected entry. Then, without releasing the
left mouse button, press and release the right mouse button. Still holding the left
mouse button, move the mouse pointer to the other directory window. As you move the
mouse pointer, a copy of the selected entry will follow the mouse. Position the
mouse pointer over the inactive window and release the mouse button.@{PAR}

There's a variation of Click-Drag-Release for the sure handed mouse gymnast: Click
and hold on an unselected entry. Then, without releasing the left mouse button, move
the pointer to the unselected Directory Window and release the mouse button. The
trick to this method is to move the mouse pointer horizontally without moving up or
down.@{PAR}

Click-Drag-Release is only available if the appropriate @{" config setting " link 3.17.5} is
activated.@{PAR}

@{i}Directory Window @{ui}@{PAR}

One of the two windows on the screen in which entries are
displayed.@{PAR}

@{i}Double-click @{ui}@{PAR}

An Amiga term, this means to click twice with the mouse
button (usually the left button, but sometimes the right
button) on an object, within a pre-determined time. The time
is set from within Preferences, and you should consult your
Amiga manual for more information on this.@{PAR}

@{i}Drag'n Drop @{ui}@{PAR}

An Amiga Term. To Drag'n Drop is to click and hold an item with the left mouse button.
Then, without releasing the left mouse button, move the mouse pointer to an other part
of the screen. The item will follow the mouse pointer (you're "dragging" it). Position
the mouse pointer over another item and release the mouse button (now you're "dropping"
the item). DirOpus allowes you to @{" Drag'n Drop Workbench icons " link 1.10} onto its
window or its AppIcon.@{PAR}

@{i}Drive gadgets @{ui}@{PAR}

The 30 gadgets, of which only six are visible at once, that
enable you to easily read any directory.@{PAR}

@{i}Entry @{ui}@{PAR}

Either a file or a directory.@{PAR}

@{i}File types @{ui}@{PAR}

A file type is a set of user-defined tests to see whether a
file is of a certain type or not. Actions can then be
performed on the file, depending on its type.@{PAR}

@{i}Highlight @{ui}@{PAR}

Highlight is the term given to the changing or reversal of
colours, usually when an object is selected.@{PAR}

@{i}Inactive (directory window) @{ui}@{PAR}

Disk name is not highlighted. This is the destination
destination directory, and files may sometimes be written
here from the source directory.@{PAR}

@{i}Menu @{ui}@{PAR}

A pull-down menu is like a list of gadgets. A menu is
accessed by moving the mouse to the top of the screen and
holding the right mouse button.@{PAR}

@{i}Open @{ui}@{PAR}

A directory that currently displayed is said to be open.@{PAR}

@{i}Requester @{ui}@{PAR}

A requester is usually a box that appears on the screen,
soliciting a response. Some requesters require a string
input, others simply ask you to choose yes or no.@{PAR}

@{i}RMB Button @{ui}@{PAR}

A Directory Opus term. This is a button that is selected
with the right mouse button, not with the left mouse button.@{PAR}

@{i}Selected @{ui}@{PAR}

Entries are selected when they are highlighted. This is
usually done by clicking on them with the left mouse button.@{PAR}

@ENDNODE
@NODE faq "Frequently asked questions"
@{LINDENT 1}

@{b}Frequently Asked Questions@{ub}@{PAR}

@{FG highlight}1. Why do newer versions of DirOpus refuse to play music modules ?@{FG text}@{PAR}

DirOpus utilizes the inovamusic.library to play various sound/music @{" formats " link 1.6.play}.
This library is Copyright Inovatronics (the former publisher of DirOpus 4). We were not able to
get the rights to that library, as nobody knows the current whereabouts of the original author.@{PAR}

At the time of writing, you can download the Inovamusic.library from
http://www.amclust.de/software/archive/CanDoLibs.lha.@{PAR}

We recommend to use external players anyway, they're much more flexible and support much more
formats. Check Hippoplayer (mus/play/hippoplayer.lha), DeliTracker (mus/play/DeliTracker232.lha)
or EaglePlayer (mus/play/EaglePlayer201.lha, Shareware) for example.@{PAR}

@{FG highlight}2. DirOpus is slooow and my modem makes strange noises when running the program ?!@{FG text}@{PAR}

This only happens with beta releases. This is due to socalled "serial debug output" (the program
sends debugging information to the serial port). If you don't know how to handle this, don't download
beta versions, just stick with the public releases.@{PAR}

Note: Not all beta releases make serial debug output. *Always* read the notes on the homepage and
the "History" file included in the distribution to get informed about problems you might encounter
with a certain release.@{PAR}

If you still want to use beta versions, download "Sushi" or "Sashimi" from Aminet. Make sure
you read and understood the accompanying documentation and run one of those programs before
starting DirOpus.@{PAR}

@{FG highlight}3. But I use a modem to connect to the internet, can I still use beta releases ?@{FG text}@{PAR}

Yes. If you are using Sushi or Sashimi (see previous question), debug output will not
interfere with serial communication between your Amiga and the modem.@{PAR}

@{FG highlight}4. I'm using OS 3.9's XADmaster.library and depacking files will trash filenames !@{FG text}@{PAR}

This is a bug in the version of XADmaster.library distributed on the OS 3.9 CD. Please install
BoingBag 39-1 (available from Amiga Inc.'s homepage). This should cure the problem.@{PAR}

@{FG highlight}5. Support for XADmaster.library does not work !@{FG text}@{PAR}

Make sure the @{" FORCEOPENXAD " link 1.3.1} tooltype is set. If you've got any archive
filetypes defined, make sure their double-click and/or click-m-click actions are undefined.@{PAR}

@{FG highlight}6. When I try to start DOpus from CLI, a requester asks me to insert volume "DOpus:" !?@{FG text}@{PAR}

When starting DOpus from the CLI, you *must* switch to DOpus' directory first. Assuming The
programm can be found in "SYS:Tools/DirOpus", you would have to type the following:@{PAR}
@{LINDENT 4}

CD SYS:Tools/DirOpus@{PAR}
DirectoryOpus@{PAR}
@{LINDENT 1}

If you don't like this, you can either reintroduce the "DOpus:" assign or spread DOpus'
files to various system directories on your boot partition (see next question).@{PAR}

@{FG highlight}7. With previous versions, I had my DOpus files spread around my HD. Is this still possible ?@{FG text}@{PAR}

No problem, as long as you know what you're doing. If DirOpus can't find its files
in its own directory, it will will search them in standard System directories:@{PAR}
@{LINDENT 4}

C:      DirectoryOpus, ConfigOpus, DOpusRT, all Modules@{PAR}
S:      Configuration files, helpfiles@{PAR}
LIBS:   Libraries@{PAR}
LOCALE: Catalog files@{PAR}
@{LINDENT 1}

Just copy the files from the Directory Opus distribution to the appropriate directories
and you can start DirOpus simply by typing 'DirectoryOpus' in the CLI.@{PAR}

@{FG highlight}8. I'd like to continue using the DOpus: Assign. Is this still possible ?@{FG text}@{PAR}

Yes. DirOpus still uses this assign (as a last option, if everything else fails) to find
its files.@{PAR}

@{FG Highlight}9. What is neccessary to start DirOpus when booting without Startup-Sequence ?@{FG text}@{PAR}

If your Computer is equipped with a MC 68060 Processor, you should first start setpatch (simply
type SETPATCH in the CLI), otherwise problems may occur (see next question).@{PAR}

@{FG highlight}10. Why is there no version of DirOpus compiled for a 68060 ?@{FG text}@{PAR}

Compiling the complete Directory Opus Package takes quite much time and there would be no speed
gain for 68060 users. The benefits simply wouldn't justify the efforts. The only drawback is
that SetPatch has to be started before DirOpus on a 68060 equipped Amiga.@{PAR}

@ENDNODE
@NODE history "History"
@{LINDENT 1}

@{b}History@{ub}@{PAR}

In this section the changes since Directory Opus v4.12 will be monitored.
Only increased functionality will be covered here. For a detailed list of all
the bugfixes and other improvements that were done to the DirOpus source code,
have a look at the History.txt file that accompanies every release of DirOpus.@{PAR}

@{FG highlight}New in Version 4.16:@{FG text}@{PAR}
@{LINDENT 4}

- DOpus can @{" handle archives " link 1.11} now, using @{" XADmaster.library " link reqments}@{PAR}
- New argument @{" -X " link 1.3.2} and tooltype @{" FORCEOPENXAD " link 1.3.1} introduced@{PAR}
- New filetype testing directive @{" MatchI " link 3.12.4.MatchI} introduced@{PAR}
- You can specify a directory as an argument when @{" running DOpus " link 1.3}@{PAR}
- Assigns can be removed using @{" Delete " link 1.6.delete} function on device list entries@{PAR}
- @{" Text Viewer " link 2.7} can open its window on DirOpus' screen now@{PAR}
- File sizes can be displayed in @{" Kilobyte/Megabyte/GigaByte " link 3.17.7.displayed} now@{PAR}
- @{" Sysinfo.library " link reqments} can be used to calculate CPU load@{PAR}
- The AppIcon can be @{" changed " link 3.19.2.icon.an} now@{PAR}
- Updating sliders while reading directory can be @{" turned off " link 3.17.8}@{PAR}
- The assign "DOpus:" is @{" not needed " link installation} anymore@{PAR}
- OS 3.5/3.9 icons are supported now@{PAR}
- DirOpus supports file links now@{PAR}
@{LINDENT 1}

@{FG highlight}New in Version 4.15:@{FG text}@{PAR}
@{LINDENT 4}

- Powerpacker support replaced by @{" XFDMaster " link reqments} support@{PAR}
- New argument @{" -x " link 1.3.2} and tooltype @{" FORCEOPENXFD " link 1.3.1} introduced@{PAR}
- Increased maximum @{" displayed file name characters " link 3.17.7.displayed} to 64@{PAR}
- 'Bring to front' option added to 'DirOpus already running' requester@{PAR}
@{LINDENT 1}

@{FG highlight}New in Version 4.14:@{FG text}@{PAR}
@{LINDENT 4}

- @{" PopUp menu " link 1.5.2} added to allow changing the sorting order on the fly@{PAR}
- Additional keystrokes in @{" text viewer " link 2.7}@{PAR}
@{LINDENT 1}

@{FG highlight}New in Version 4.13:@{FG text}@{PAR}
@{LINDENT 4}

- Long filename support (up to 107 Characters).@{PAR}
@{LINDENT 1}

@ENDNODE
@NODE contact "Contact / Support"
@{LINDENT 1}

@{b}Contact / Support@{ub}@{PAR}

@{FG highlight}Support Homepage@{FG text}@{PAR}

The Support Homepage of the Directory Opus 4 Research Project is located at:@{PAR}
@{LINDENT 4}

http:\//dopus.amiga.pl@{PAR}
@{LINDENT 1}

A mirror can be found here:@{PAR}
@{LINDENT 4}

http:\//dopus.free.fr@{PAR}
@{LINDENT 1}

Latest public releases, beta versions, additional tools and support informations can be
found there, aswell as updated copies of this manual.@{PAR}

@{FG highlight}Mailing list@{FG text}@{PAR}

There's a support mailing list for Directory Opus. Join it if you have questions about
DirOpus, need advice on configuration settings or simply want to contribute to the
development of the program.@{PAR}

You can subscribe to that mailing list by sending a blank mail to:@{PAR}
@{LINDENT 4}

opus4-subscribe\@yahoogroups.com@{PAR}
@{LINDENT 1}

To unsubscribe (why would you want to do that ?), send a blank mail to:@{PAR}
@{LINDENT 4}

opus4-unsubscribe\@yahoogroups.com@{PAR}
@{LINDENT 1}

@{FG highlight}Contact Addresses@{FG text}@{PAR}

Jacek Rzeuski (Programming) - jrzeuski\@neptun.gdansk.tpsa.pl@{PAR}

Christoph Gutjahr (Manual)  - c.gutjahr\@gmx.de@{PAR}

@{FG highlight}Translators@{FG text}@{PAR}

This software was translated with the help of ATO, the Amiga Translators'
Organization. ATO is a non-profit organization that translates for the
Amiga community!@{PAR}

Czech:@{PAR}
@{LINDENT 4}

Boleslav Kristen    <agaslayer\@volny.cz>@{PAR}
Radek Hrdlicka      <lahve\@amigascne.org>@{PAR}
@{LINDENT 1}

Finnish:@{PAR}
@{LINDENT 4}

Jari Komulainen     <kom\@sci.fi>@{PAR}
Sami Raunio         <sr55059\@uta.fi>@{PAR}
Petri Koistinen     <pkoistin\@iki.fi>@{PAR}
@{LINDENT 1}

French:@{PAR}
@{LINDENT 4}

Philippe Ferrucci   <pferrucci\@free.fr>@{PAR}
Philippe Bovier     <bovier\@club-internet.fr>@{PAR}
Hervé Dupont        <herve.dupont\@nordnet.fr>@{PAR}
@{LINDENT 1}

German:@{PAR}
@{LINDENT 4}

Christoph Gutjahr   <c.gutjahr\@gmx.de>@{PAR}
Frank Weber (OPI)   <opi\@snafu.de>@{PAR}
@{LINDENT 1}

Italian:@{PAR}
@{LINDENT 4}

Massimo Mascia      <mashi\@tiscalinet.it>@{PAR}
Francesco Mancuso   <mcfrank\@mediatel.it>@{PAR}
@{LINDENT 1}

Norwegian:@{PAR}
@{LINDENT 4}

Per Martin Iversen  <pmiversen\@fm.telia.no>@{PAR}
@{LINDENT 1}

Polish:@{PAR}
@{LINDENT 4}

Daniel Sternik      <dxs2\@wp.pl>@{PAR}
Mariusz Danilewicz  <mandi\@box43.gnet.pl>@{PAR}
@{LINDENT 1}

Portuguese:@{PAR}
@{LINDENT 4}

Raul Silva          <luarsilva\@mail.telepac.pt>@{PAR}
Rúben Alvim         <alvim_r\@yahoo.com>@{PAR}
@{LINDENT 1}

Russian:@{PAR}
@{LINDENT 4}

Boris Kondratyev    <amiline\@chat.ru>@{PAR}
Oleg Sergeev        <bigblack\@mail.lanck.net>@{PAR}
@{LINDENT 1}

Spanish:@{PAR}
@{LINDENT 4}

Javier de las Rivas <javierdlr\@jazzfree.com>@{PAR}
David Rey           <david\@saug.org>@{PAR}
@{LINDENT 1}


Amiga Translators' Organization: http:\//ato.vapor.com/ato/@{PAR}
                                 mail: ato-info\@ato.vapor.com@{PAR}

@ENDNODE
