Otherware/Otherware_1_SB_Development.iso/amiga/programm/programi/powervis.lzh/s/PowerVisor-help

Text File | 1992-02-14 | 174.7 KB | 6,125 lines

@General commands
----------------
Help        : obvious                  Quit        : quit powervisor
Void        : do nothing               HOld        : hold powervisor
Disp        : display expression       Refresh     : control refresh rate
PRint       : print string             CLEANup     : deallocate pv-memory
VArs        : show all variables       SHowalloc   : show all pv-memory
REMVar      : remove variables         LOG         : log output
ATtach      : attach macro to key      TO          : log output from command
REMAttach   : remove command from key  SAVEConfig  : save config file
SCAn        : ask input from user      PREfs       : set powervisor prefs
GEtstring   : ask input from user      MOde        : set preferences
REQSave     : save file requester      ERror       : get error string
REQLoad     : load file requester      ALias       : set an alias
REQuest     : requester                UNALias     : remove an alias
LEd         : toggle powerled

Screen commands
---------------
CLs         : clear logical window     SCREen      : move pv to screen
LOCAte      : location in logical win  SIze        : size physical window
HOMe        : go to top location       MOVe        : move physical window
COLRow      : set logical size         SETfont     : set logical window font
FIT         : fit logical window       Xwin        : open/close Extra window
Active      : make logwin active       RWin        : open/close Refresh window
CURRent     : set current logical win  DWin        : open/close Debug window
ON          : on logical window do     AWin        : open/close Rexx window
COLor       : set rgb value for pv     OWin        : open/close PPrint window
CLOSELw     : close logical window     OPENLw      : open logical window
CLOSEPw     : close physical window    OPENPw      : open physical window
SETFLags    : set logwin flags         SCROll      : scroll logical window

Memory commands
---------------
Search      : search string            Copy        : copy memory
Next        : continue searching       Fill        : fill memory with string
CLEar       : clear unused memory

Special commands
----------------
ACCount     : task usage, stack check  STAck       : check stack usage
Kill        : cancel a task            REMRes      : remove resident
FReeze      : freeze a task            REMHand     : remove input handler
UNFreeze    : unfreeze a task          REMCrash    : remove a crash node
TASKPri     : set task priority        REMOve      : remove a node
OWNer       : show owner of memory     UNLOCk      : unlock
CLOsewindow : close a window           PAthname    : show pathname for lock
CLOSEScreen : close a screen           CUrdir      : set current dir
ADdfunc     : add function to monitor  LOADFd      : load an fd-file
REMfunc     : remove function          UNLoadfd    : unload fd-file
RBlock      : read a block from disk   LOAd        : load a file
WBlock      : write a block to disk    SAve        : save a file
Opendev     : open device              SPEEk       : peek supervisor
CLOSEDev    : close device             SPOke       : poke supervisor
DEVInfo     : device information       MMURESet    : reset MMU usage
DEVCmd      : give device command      GO          : jump to memory
FOR         : for each element in list PVcall      : call PowerVisor
SPRint      : print on serial terminal EVent       : add an input event
TRACK       : resource tracking

Debug commands
--------------
DEBug       : control debugtasks       DScroll     : scroll debug window
DUse        : set debug program        DSTart      : set debug window start
WITh        : with debug node do       DRefresh    : refresh debug display
Break       : set breakpoint           SYmbol      : control symbol table
TRace       : trace program            SOurce      : control source

Information commands
--------------------
MMutree     : show mmu tree            LList       : traverse list
MMURegs     : show mmu registers       List        : list item
MMUWtest    : test address for write   Info        : node information
MMURTest    : test address for read    Memory      : list memory
SPecregs    : show special registers   VIew        : show memory
DEVInfo     : device information       TAGs        : show tags
LIBInfo     : show lib function info   ADDTag      : add a tag
LIBFunc     : show lib function info   REMTag      : remove a tag
Gadgets     : list window gadgets      CHecktag    : check address in tag
ADDStruct   : add structure defs       LOADTags    : load tags from file
REMStruct   : remove structure def     SAVETags    : save tags to file
CLEARStruct : clear structure defs     CLEARTags   : clear tags
INTErprete  : interprete structure     USetag      : set current tag list
REGs        : show registers of task   TG          : temporarily set tag list
FREGs       : show floating pt regs    HUnks       : show hunks for process
MEMTask     : show memory of a task    Unasm       : unassemble memory

Script commands
---------------
SCRIpt      : start script             RESIdent    : make file resident
RX          : start rexx script        UNResident  : remove resident file

ARexx commands
--------------
SYNc        : synchronize pv to ARexx  HIde        : hide output
ASYnc       : undo SYNC command        UNHide      : undo HIDE command
FROnt       : pv screen to front       CLIp        : set/get clip
ASsign      : assign to var            REMCLip     : remove clip
STRIng      : return string

List commands (type 'help syslists' for info)
-------------
Exec  INTb  Task  LIBs  DEvs  RESO  MEMR  INTR  Port  Wins  ATTC  GRaf  COnf
SCrs  FOnt  DOsd  FUnc  SEMa  RESm  FILS  LOck  IHan  FDfi  CRsh  DBug  MONi
PUbs  STru  LWin  PWin
===
@PowerVisor help (1.13 Beta)    Wed Feb  5 17:50:38 1992
---------------------------
You can type one of the following for more information on a specific
item:

      help                 for this screen
      help general         for general information

      help commands        for a list of all available commands
      help functions       for a list of all available functions
      help syslists        for a list of all available lists
      help <command>_cmd   gives help for a specific command
      help <command>_tmp   gives a command template (or <command> ?)
      help <function>_func gives help for a specific function
      help <list>_list     gives help for a specific list

      help arguments       gives help for all possible argument types
      help libfuncs        information about library functions
      help bugs            for all bugs in the current version
      help debugging       for general debugging help

You can use abbreviations ('h gen' instead of 'help general')
Note that you could get the wrong help when you do this.
('help li' will probably not give what you wanted: list, libfuncs, ...)
===
@General functions
-----------------
ALLOC       : allocate memory          LASTMEM     : give last memory
FREE        : free memory              LASTBYTES   : last number of bytes
REALLOC     : reallocate memory        LASTLINES   : last number of lines
GETSIZE     : give size of memoryblock LASTFOUND   : last search address
ISALLOC     : is memory a pv-block ?   PEEK        : peek value in structure
KEY         : returns pressed key      APEEK       : peek address
QUAL        : qualifier for last key   STSIZE      : get structure size
GETCOL      : get logical col width    RFCMD       : refresh command
GETROW      : get logical row height   RFRATE      : refresh rate
TOPPC       : get debug win top pc     GETLWIN     : current logical window
BOTPC       : get debug win bottom pc  GETACTIVE   : ask active logwin
ISBREAK     : check if breakpoint      TAGLIST     : get current tag list
GETDEBUG    : get current debug ptr    EVAL        : evaluate argument string
GETX        : get the current x coord  IF          : conditional evaluation
GETY        : get y coord              CURLIST     : current list
GETCHAR     : get the current char     COLS        : get max nr of cols
GETERROR    : get error of routine     LINES       : get max nr lines
BASE        : get first listelem
GETSTACK    : get max stack usage
===
@Help arguments
--------------
There are two basic types for command arguments:

   - integers     : The command expects an integer
   - strings      : The command expects a string

Other help: integers strings expressions
            »»»»»»»»á»»»»»»»á»»»»»»»»»»»
===
@Help integers
-------------
The following are possible integers :


decimal integers:
      567, 1920003, ...
   Integers are 32 bits.

hexadecimal integers:
      034, $98f, $FA802, ...
   These start with a zero or a '$'

expressions:
      (5+5), 1+27*(1-2)

string pointers:
      "test", "test2 \10\F4\DD end\05", ...
   Please note that these strings only exist for a limited period. PowerVisor
   only remembers the 10 last strings and string pointers.
   If you want to use a string permanently, you must allocate memory for
   it, and copy the string to this place. (type 'help permstring' for an
   example)
   When evaluating a string you get a pointer to this string.
   For example "test"+2 points to 's'. A string pointer is in fact
   just another integer.

strings and names:
      a, var, exec, output(), ...
   There are four cases where you may use a string as an integer.

      - The name is a variable or function
        (no quotes, case insensitive, no abbreviations)
            a
            error
            debug()

      - The name is a library function you have loaded
        (no quotes, case insensitive, no abbreviations)
            output()

      - the name is an abbreviation for an element in the current list
        (quotes possible, case insensitive, abbreviations possible)
            trackdisk
            'trackdisk.dev'

      - the name is a symbol for the current debug task
        (quotes possible, case sensitive, no abbreviations)
            __main
            '@XCEXIT'

   When you use a string as an integer, PowerVisor will first check if
   it is a variable. If it is not a variable it will check if it is
   a symbol. If that is not the case it will check if it is an
   abbreviation for an element in the current list.
   If you use single quotes for the name, PowerVisor will skip the
   variable testing and only test if it is a symbol or a list element.
   If you use the ':' operator in front of the name, PowerVisor will
   only test if it is a list element.

You can mix all these integers whenever you want and for each command
that wants an integer as an argument. You can use them in expressions

Other help: expressions syslists libfuncs permstring strings
            »»»»»»»»»»» »»»»»»»» »»»»»»»» »»»»»»»»»» »»»»»»»
===
@Help strings
------------
A string is not the same as a string pointer. A string pointer is in fact
an integer. A string can also be an integer. This interpretation depends
on the command. Strings and names can be mixed.

You can use all characters in a string when you enclose the string in
quotes (single or double). Otherwise you are limited to alphanumeric
characters and the underscore.

You can in any case use the quote operator ('\') (even if you used
no quotes) in three ways.
   - When followed by 2 hexadecimal digits, the
     operator is replaced by the character represented by the two
     hexadecimal digits.
   - When followed by a left bracket '(', the character representation of
     the following expression is put in the string. After the expression
     you can close with the right bracket ')' or you can use an optional
     format string (C-style) to format the number. Using this format string
     you can even interprete the number as a character or a string.
   - When followed by another character, the character is simply copied.
     This is useful to include quotes and the quote operator in strings.

   'string'          is a string
   string            is a name
   "string pointer"  is a string pointer but can be used as a string when
                     the command expects a string
   'test\20hello'    is equal to 'test hello'
   'test\\hello'     is equal to 'test\hello'
   'test\'hello'     is equal to 'test'hello'
   'test\"hello'     is equal to 'test"hello'
   test\'            is equal to 'test'' (note that you don't need the
                     quotes)
   'Test\(3+4)hello' is equal to 'test7hello'
   '\(65,%lc)'       is equal to 'A'
   5+6               is also a string if the command expects a string

You can use the \(<number>,%s) operator if you want an integer to behave
like a string.
For example, when p points to a region of memory containing the string
'exec'. Then the command 'list \(p,%s)' will list the execbase.
You cannot only use the '\' operator if the command really expects a string.
'disp \(p,%s)' is illegal.

Other help: integers list syslists quote_op strongquote_op
            »»»»»»»» »»»» »»»»»»»» »»»»»»»» »»»»»»»»»»»»»»
===
@Help expressions
----------------
PowerVisor has a very powerfull expression evaluator. If you know C you will
probably notice the resemblance. The same priorities as used in C are used
in PowerVisor.

You can use the following binary operators. The list is from high to
low priority :

   * / %             multiply, integer divide, remainder
   + -               add, subtract
   << >>             left shift, right shift
   > < >= <=         integer comparisons
   != ==             not equal to, equal to
   &                 bitwise and
   ^                 bitwise xor
   |                 bitwise or
   &&                logical and
   ||                logical or
You can use the following unary operators:
   -                 negation
   !                 logical not
   ~                 bitwise not
   *                 contents operator
   @                 special operator
   \                 quote operator (only for strings)
   :                 list operator
   &                 list address operator
And you can of course use brackets

Examples:
   1<<(6+4*(10/2))            is equal to 67108864 (or 1<<26)
   libs:'exec.library'+$10    is equal to the address of ExecBase pluss 16
   *devs:audio.l              is equal to the contents of the first longword
                              pointed to at the start of the audio.device
                              node. (This is the next device node or ln_succ)
   output()                   is equal to the BPTR to your outputhandle
                              (you must have loaded dos functions to do
                              this)
   {disp 4}                   is equal to 4 ('disp' is executed)
   @d1                        is equal to the register d1 of the current
                              debug task

Note that you cannot use spaces in expressions. Spaces (and ',') are used
to separate expressions. If a command expects two arguments you can use a
space or a comma to seperate them.
When you are at the end of an expression, you need not close your brackets.
You MUST close the brackets when you want to terminate the argument list
for a library function or a normal function.

Other help: contents_op list_op special_op listaddr_op
            »»»»»»»»»»» »»»»»»» »»»»»»»»»» »»»»»»»»»»»
            disp_cmd debugging libfuncs integers strings variables
            »»»»»»»»á»»»»»»»»» »»»»»»»» »»»»»»»» »»»»»»» »»»»»»»»»
            group_op quote_op
            »»»»»»»» »»»»»»»»
===
@Help variables
--------------
PowerVisor has the capability to store an integer in a variable.
You can use variablenames of arbitrary length and as many variables as
you wish.
A variablename must start with a letter or an underscore. You can use digits
in the rest of the name.

Examples:
   a5=4
   a5=a5+1
   outputhandle=output()
   nc=write(outputhandle,"testing",7)
   _test_=00C02536

There are 5 reserved variables:
   'mode'
      This variable contains the current mode settings. Changing this variable
      has more or less the same effect as using the 'mode' command
   'rc'
      This variable contains the returncode for some commands. You may use
      'rc' for your own purposes but you must remember that certain commands
      change this variable
   'version'
      The current PowerVisor version. You can not change this constant
      ($113 = 1.13)
   'error'
      The last error number
   'input'
      A pointer to the last input string entered with 'scan', 'getstring'
      'reqload' or 'reqsave'. You can't change this constant

PowerVisor has four variable types.
   0 : normal variables, you can create these with the assignment operator.
   1 : constant variables, only PowerVisor can create these.
   2 : special variables, only PowerVisor can create these.
   3 : functions.

It is recommended that you use the following name convention for your
variables:
   single letter variables for temporary variables.
   multiple letter variables for more permanent uses.
   names starting with an underscore ('_') for internal script use.
This convention is especially useful in scripts. For example, you should
not use multiple letter variables in scripts except in special cases.
It is good programmer practice to always remove all used variables in
a script ('remvar').

Other help: assignment_op mode_cmd vars_cmd remvar_cmd
            »»»»»»»»»»»»» »»»»»»»» »»»»»»»» »»»»»»»»»»
===
@Help assignment_op
------------------
The assignment operator is used to store an integer in a variable or in
memory.

Left from the assignment you can put a variable, a register or an
contents operator. The variable will be created if it does not
exist. In order to use register assignment you must have a current
debug task.

Examples:
   ad=alloc(n,100)            Allocate 100 bytes memory
   *ad=5                      Put long integer 5 at our newly allocated
                              memory
   *(ad+5).b=50*2             Put byte 100 at address ad+5
   *ad.w=*(ad+2).w            Copy the 2nd word to the first word
   @d1=4                      Assign 4 to register d1 of the current
                              debug task

Other help: variables libfuncs expressions debugging alloc_func
            »»»»»»»»» »»»»»»»» »»»»»»»»»»» »»»»»»»»» »»»»»»»»»»
===
@Help contents_op
----------------
The contents operator is used to get the contents of an address.
You can also use this operator at the left side of an assignment.


Examples:
   *4       is the contents of address 4 as a long (this is execbase)
   *4.l     is the same
   *4.w     is the contents of address 4 as a word
   *4.b     is the contents of address 4 as a byte
   **4      is the contents of the contents of address 4 (both as long)
   *5       will give an odd address error (you will not crash)

Other help: expressions
            »»»»»»»»»»»
===
@Help list_op
------------
The list operator is used to address an element of a specific list.

Examples:
   libs:exec         is the pointer to exec library
   li:ex             is probably the same (unless you have another library
                     beginning with 'ex')
   task:'trackdisk.device'
                     is a pointer to the trackdisk device
   task:'trackdisk.d'
                     is probably the same
   :input            will give the pointer to the input.device if the
                     current list is the task list

When 'libs' is the current list (for example) you can also type the
following to obtain the pointer to the exec library.
   exec or 'exec.library'

Some command use the 'autodefault' feature.

When you want to be absolutely sure that the string evaluates to a
list element and not to a variable or such, you can use the ':' operator
without a preceding list name.
   :'trackdisk.device'

Other help: syslists expressions strings listaddr_op autodefault
            »»»»»»»» »»»»»»»»»»» »»»»»»» »»»»»»»»»»» »»»»»»»»»»»
===
@Help listaddr_op
----------------
The list address operator is used to obtain the address of an element
in a list. This list must be the execbase, grafbase or intuitionbase list.
This operator is provided as a clumsy interface to change something to
a variable in one of the library bases. In future this interface may
be cleaner.

Examples:
   &exec:vblankfreq  is the pointer to the VBlankFrequency variable in
                     the exec library
   &e:Quantum        is the pointer to the Quantum variable in the exec
                     library

Example:
   *&e:quantum.w=20  will change the quantum variable to 20.

Other help: syslists expressions strings list_op assignment contents_op
            »»»»»»»» »»»»»»»»»»» »»»»»»» »»»»»»» »»»»»»»»»» »»»»»»»»»»»
===
@Help libfuncs
-------------
PowerVisor gives you the ability to execute library functions.
Therefore you must first load the fd-file for the library you want to
call.

Example:
   output()       calls the dos function output (no arguments)
   write(output(),"test",4)
                  writes the string 'test' to the current output.
   a=allocmem(1000,1<<16)
                  allocates memory and put the address in the variable 'a'
   ib=openlibrary("intuition.library",0)
                  opens the intuition library

The order in which the arguments appear are the same as in C (or as specified
in the fd-file).

You must use the notation described above as an argument for a command
(because it is an expression). If you are not interrested in the result of a
library function you still have to preceed it with a command. Simply use the
'disp' command.

Example:
   disp output()

If you don't want to load the fd-file you can call library functions with:
   offs lib:exec -30 ()
You can not use arguments when using this notation

Other help: loadfd_cmd disp_cmd expressions
            »»»»»»»»»» »»»»»»»» »»»»»»»»»»»
===
@Example permstring
------------------
When you use a string pointer ('"'<bytes>'"'), this string only exists during
the lifetime of the current command. This could cause problems.

Example:
   if you use

      void setwindowtitles(win:'test window',"window title",0)

   to set the window title for 'test window' it will work at first.
   But when you use another string at a later time you will notice that
   your window will get another title (mostly rubbish).
   To prevent this from happening you must allocate some memory for
   this string.

   You can do this is as follows:
      loadfd intuition fd:intuition_lib.fd
      ad=alloc(s,'window title')
      void setwindowtitles(win:'test window',ad,0)
      ...
   Later you can free this title with:
      void free(ad)

Other help: loadfd_cmd alloc_func void_cmd variables libfuncs strings
            »»»»»»»»»» »»»»»»»»»»á»»»»»»»»á»»»»»»»»»á»»»»»»»» »»»»»»»
===
@Help quote_op
-------------
To include integers, characters and strings in a string you can use
the quote operator.

\<x><x> is equal to a character. <x> is one hexadecimal digit

\(<expression>) is equal to the string representing the result of
                the expression

\(<expression>,<format>) is equal to the string representing the
                result of the expression formatted by <format>
                <format> is a C-style formatting string

\<other char> is equal to <other char>


Example:

   test\0a\\\'          is equal to test<newline>\'
   test\(5+6)hello      is equal to test11hello
   test\(65,%lc)hello   is equal to testAhello
   test\("hello",%s)    is equal to testhello
   test\(6+7,%03ld)     is equal to test013

Other help: strings strongquote_op
            »»»»»»» »»»»»»»»»»»»»»
===
@Help strongquote_op
-------------------
In some rare cases it is possible that you want to quote a lot of
characters without having to worry about anything at all. This is
(almost) possible with the strong quote (╖ = <alt>+8).

The character directly after the strong quote is the character
used to recognize the end of the strong quote operator.

╖<char> All chars of all different kinds <char>

The only character you can't use is the one needed to close the
strong quote operator (<char>).


Example:

   Test╖/ ('){}])' ((''\\\\'(/TheEnd

      is equal to

   Test( ('){}])' ((''\\\\'(TheEnd

Other help: strings quote_op
            »»»»»»» »»»»»»»»
===
@Help syslists
-------------
PowerVisor uses lists to give the user the possibility to examine system
information.
The following lists are available:

   Exec        the listing of the ExecBase structure (no list operator
               possible)
   Intb        IntuitionBase structure (no list op possible)
   Graf        Graphics base structure (no list op possible)
   Task        The listing of the tasks in the system (default list)
   Libs        Libraries
   Devs        Exec-devices
   Reso        Resources
   Memr        Memory list
   INTR        Interrupts
   Port        Message ports
   Wins        All windows
   Scrs        Screens
   Font        Fonts currently in memory
   DOsd        Dos-devices
   FUnc        Function monitor nodes (see 'addfunc_cmd')
   SEma        Semaphores
   RESM        Resident modules
   FIls        Open files
   LOck        Locks
   IHan        Input handlers
   FDfi        All fdfiles loaded (see 'loadfd_cmd')
   Attc        All attached keys (see 'attach_cmd')
   Crsh        All crashed programs (see 'crash')
   DBug        All debug nodes (see 'debugging')
   STru        All structure defines (see 'addstruct')
   COnf        AutoConfigs
   MOni        Monitors (DOS 2.0 only)
   PUbs        Public Screens (DOS 2.0 only)
   LWin        All logical windows for PowerVisor
   PWin        All physical windows for PowerVisor

You can see in which list you are by examining your prompt.
You can change your current list by typing the new listname.
If you use 'mode autolist' you will get a list when you change the
current list.

Type 'help <list>_list' for specific help on each list.

Other help: libfuncs attach_cmd crash mode_cmd debugging list_op
            »»»»»»»»á»»»»»»»»»»á»»»»» »»»»»»»»á»»»»»»»»» »»»»»»»
            addfunc_cmd loadfd_cmd <list>_list info_cmd addstruct_cmd
            »»»»»»»»»»» »»»»»»»»»» »»»»»»»»»»» »»»»»»»» »»»»»»»»»»»»»
===
@Command: pvcall_cmd
-------------------

   <result> <- PVcall <number> [<arguments>]


Call internal PowerVisor functions. This command is only useful for the
very experienced PowerVisor user. See the 'The Wizard Corner' chapter for
more info.

         number  name
         ------------------------
         0       CreateFunction
         1       Error
         2       AdvanceHistory
         3       LowerHistory
         4       GetHistoryLine
         5       RefreshStringG
         6       InstallPreCmd
         7       Evaluate
         8       RemVar
         9       ParseString
         10      CopyString
         11      AddStringToHist
         12      GetStringGBuf
         13      AppendString
         14      SkipSpaces
         15      SetCursorPos
         16      InstallPostCmd
         17      SetDebugMode
         18      GetExecLevel
         19      OBSOLETE
         20      GetStringInfo
         21      GetSnapBuffer
         22      InstallSnapCmd
         23      OBSOLETE
         24      Beep
         25      GetVarAddress
         26      OBSOLETE
         27      CreateConstant
         28      CompareStrings
         29      CallMLScript
         30      GetEvalBase
         31      GetARexxBase
         32      GetDebugBase
         33      GetFileBase
         34      GetGeneralBase
         35      GetListBase
         36      GetMainBase
         37      GetRoutines
         38      GetModeRoutines
         39      GetRexxList
         40      GetScreenBase
         41      GetMemoryBase
         42      OBSOLETE
         43      GetStringGadget
         44      OBSOLETE
         45      OBSOLETE
         46      ErrorHandler
         47      InstallQuitCmd
         48      ConvertAlias
         49      AddAutoClear
         50      AllocPVBlock
         51      FreePVBlock
         52      ComputeGadgetSignal
         53      Print
         54      PrintNum
         55      AddGlobalAutoClear
         56      RemoveGlobalAutoClear
         57      ClosePVHandle
         58      ReAllocPVMemoryBlock
         59      ReAllocPVQuickBlock
         60      OBSOLETE
         61      RefreshLogWin
         62      SnapWord
         63      Disassemble
         64      CmdDisassemble
         65      PutChar
===
@Command: prefs_cmd
------------------

   PREfs ('history' | 'key' | 'screen' | 'stack' | 'logwin' | 'linelen' |
         'debug' | 'dmode' | 'pens' | 'font') [<arguments> ...]


You can set/get preferences with this command. <prefname> is one of
(followed by the specific argument template) :

   - history [<history value>]
   - key <key number> [<code> <qualifier>]
         0 = interrupt key
         1 = hot key
         2 = pause key
         3 = cycle active logwin
         4 = history up
         5 = history down
   - screen [<w> <h>]
   - stack [<stack fail level>]
   - logwin <full standard logwin name> [<cols> <rows> <mask> <flags>]
         supported logwins :
            Main,Extra,Refresh,Debug,Rexx,PPrint
         bits in flag :
            4   = -MORE- enabled
            32  = real-top
            64  = statusline off
            128 = interrupt off
            256 = auto snap to output
   - linelen [<line length>]
   - debug [<instructions> <show previous instruction>]
   - dmode 'n'|'r'|'c'|'f'
   - pens [<pen offset number> <pen color>]
   - font [<font name> <font size> <style> <flags>]

All parameters set with this command can be saved with the 'saveconfig'
command.

Other help: saveconfig_cmd mode_cmd
            »»»»»»»»»»»»»» »»»»»»»»
===
@Command: event_cmd
------------------

   EVent <class> <subclass> <code> <qualifier> <x> <y>


Send an input event to the input device. This is useful in macros.

Other help: attach_cmd
            »»»»»»»»»»
===
@Command: owner_cmd
------------------

   OWNer <address>


This command tries to see who is the owner of the address you specify.
This command is not completely ready but it is safe to use.
===
@Command: speek_cmd   (only 68030 or 68040)
------------------

   <value> <- SPEEk <address>


Peek a longword from memory. <address> is a PHYSICAL address. The MMU tree
is completely ignored.

Other help: mmutree_cmd spoke_cmd
            »»»»»»»»»»»á»»»»»»»»»
===
@Command: saveconfig_cmd
-----------------------

   SAVEConfig


Save the current 'mode' and 'prefs' settings to the file s:PowerVisor-config.
They will automatically be loaded when you start PowerVisor.

Other help: mode_cmd prefs_cmd
            »»»»»»»» »»»»»»»»»
===
@Command: spoke_cmd   (only 68030 or 68040)
------------------

   SPOke <address> <value>


Poke a longword in memory. <address> is a PHYSICAL address. The MMU tree
is completely ignored.

Other help: mmutree_cmd speek_cmd
            »»»»»»»»»»»á»»»»»»»»»
===
@Command: mmutree_cmd   (only 68020 with 68851 or 68030 or 68040)
--------------------

   MMutree


This command shows the current MMU tree (CRP only).

FC code trees are not implemented yet.
8 byte format pages are not implemented yet.
indirect pages are not implemented yet.

Other help: mmuregs_cmd mmurtest_cmd mmuwtest_cmd specregs_cmd mmureset_cmd
            »»»»»»»»»»»á»»»»»»»»»»»»á»»»»»»»»»»»»á»»»»»»»»»»»» »»»»»»»»»»»»
===
@Command: mmureset_cmd   (only 68020 with 68851 or 68030 or 68040)
---------------------

   MMURESet


This command resets all U and M flags in the MMU tree to false.

Other help: mmutree_cmd mmuregs_cmd
            »»»»»»»»»»»á»»»»»»»»»»»
===
@Command: mmuregs_cmd   (only 68020 with 68851 or 68030 or 68040)
--------------------

   MMURegs


Show all special mmu registers (except MMUSR).

Other help: mmutree_cmd mmurtest_cmd mmuwtest_cmd specregs_cmd
            »»»»»»»»»»»á»»»»»»»»»»»»á»»»»»»»»»»»»á»»»»»»»»»»»»
===
@Command: openlw_cmd
-------------------

   RC,<lwin> <- OPENLw <physical window> <logwin name> <cols> <rows>
                [<brother> <where> [<number of columns or lines>]]


Open a logical window on a physical window. If the physical window is empty
you need not specify the two last arguments. Otherwise <brother> is the
logical window which will be your brother and <where> specifies where
our new logical window should appear relative to the <brother>.
The <where> string can be like :

   u     above brother
   d     below brother
   r     right from brother
   l     left from brother
   pd    take parent from brother and appear below this box
   pppr  take parent from parent from parent and appear right from this box
   ...

If <number of columns or lines> is specified it is used as the number
of lines or columns for the new logical window (<number of columns or
lines> is interpreted as <number of columns> if the new window is positioned
left or right of <brother>, otherwise <number of columns or lines>
is interpreted as <number of lines>).


Other help: closelw_cmd openpw_cmd closepw_cmd lwin_list pwin_list
            »»»»»»»»»»»á»»»»»»»»»»á»»»»»»»»»»» »»»»»»»»»á»»»»»»»»»
===
@Command: openpw_cmd
-------------------

   RC,<pwin> <- OPENPw <physical window name> <x> <y> <w> <y>


Open a physical window. It will be empty (no logical windows).

Other help: closelw_cmd openlw_cmd closepw_cmd lwin_list pwin_list
            »»»»»»»»»»»á»»»»»»»»»»á»»»»»»»»»»» »»»»»»»»»á»»»»»»»»»
===
@Command: closepw_cmd
--------------------

   CLOSEPw <physical window>


Close a physical window. All logical windows on this physical window
are automatically removed.
You can't remove the 'Main' physical window.

Other help: closelw_cmd openlw_cmd openpw_cmd lwin_list pwin_list
            »»»»»»»»»»»á»»»»»»»»»»á»»»»»»»»»» »»»»»»»»»á»»»»»»»»»
===
@Command: closelw_cmd
--------------------

   CLOSELw <logical window>


Close a logical window.
You can't remove the 'Main' logical window.

Other help: closepw_cmd openlw_cmd openpw_cmd lwin_list pwin_list
            »»»»»»»»»»»á»»»»»»»»»»á»»»»»»»»»» »»»»»»»»»á»»»»»»»»»
===
@Command: setflags_cmd
---------------------

   RC,<oldflags> <- SETFLags <logical window> <mask> <flags>


Set flags for a logical window.
Bits in <mask> and <flags> :

   4   = -MORE- enabled
   32  = real-top
   64  = statusline off
   128 = interrupt off
   256 = auto snap to output

Other help: openlw_cmd closelw_cmd lwin_list
            »»»»»»»»»»á»»»»»»»»»»»á»»»»»»»»»
===
@Function: isbreak_func
----------------------

   ISBREAK( <address> )


Test if there is a breakpoint on this address. If true this function returns
the breakpoint number and the breakpoint type in one longword :

   NNNNTTTT
===
@Function: getstack_func
-----------------------

   GETSTACK( )


This function returns the maximum stack usage for the last task monitored
with the 'stack' command.


Other help: stack_cmd
            »»»»»»»»»
===
@Command: track_cmd
------------------

   TRACK 't' <task> | 's' | 'c' | 'l'


With this command you can control the resource tracker. This resource
tracker remembers all memory allocations (AllocMem, AllocVec) and
all opened libraries (OpenLibrary, OldOpenLibrary). With this information
you can see if the task (or process) cleans everything up.
Note that you can only track resources for one task or process at a
time.

'track' uses ╣autodefault to the 'task' list for the <task> argument.

   track t     Take a task or process in the task list and start resource
               tracking for that task
   track s     Stop tracking and free all track information. Note that
               the memory that the task forgot to free is NOT freed with
               this function
   track c     Stop tracking and free all track information (like 'track s')
               In addition this function also clears all memory that is
               not freed by the program
   track l     List all memory and libraries current allocated or open
===
@Command: mmurtest_cmd   (only 68020 with 68851 or 68030 or 68040)
---------------------

   MMURTest <address>


Test an address for read access in MMU tree.
MMUSR is dumped. (does not work yet)

Other help: mmutree_cmd mmuregs_cmd mmuwtest_cmd specregs_cmd
            »»»»»»»»»»»á»»»»»»»»»»»á»»»»»»»»»»»»á»»»»»»»»»»»»
===
@Command: mmuwtest_cmd   (only 68020 with 68851 or 68030 or 68040)
---------------------

   MMUWtest <address>


Test an address for write access in MMU tree.
MMUSR is dumped. (does not work yet)

Other help: mmutree_cmd mmuregs_cmd mmurtest_cmd specregs_cmd
            »»»»»»»»»»»á»»»»»»»»»»»á»»»»»»»»»»»»á»»»»»»»»»»»»
===
@Command: specregs_cmd   (only 68020 or 68030 or 68040)
---------------------

   SPecregs


Show all special 68020 registers.

Other help: mmutree_cmd mmuregs_cmd mmurtest_cmd mmuwtest_cmd
            »»»»»»»»»»»á»»»»»»»»»»»á»»»»»»»»»»»»á»»»»»»»»»»»»
===
@Command: setfont_cmd
--------------------

   SETfont <logical window> <fontname> <fontheight>


Set a font for a logical window. The font must be either memory resident
or available in the 'fonts:' directory. Proportional fonts are not supported.

See the 'lwin' list for all available logical windows.

Other help: lwin_list
            »»»»»»»»»
===
@Function: geterror_func
-----------------------

   GETERROR( <expression string> )


Evaluate an expression and return the error. If there was no error, 0
is returned.

Example:
   d geterror("7")
   returns 0 since 7 is a valid expression.

   d geterror("7+")
   returns 16 since there is a missing operand.

Other help: error_cmd
            »»»»»»»»»
===
@Command: error_cmd
------------------

   <pointer to error string> <- ERror <error number>


This command returns a pointer to an error string corresponding with
<error number>. Note this pointer has very limited use since the space
it points to is almost immidiatelly overwritten by PowerVisor. You can
make a copy of the string with the following construction :

   cs=alloc(s,\({error 17},%s))

17 is the error number (in this case 'Missing operand'). Alloc allocates
a string and puts the pointer to this string in 'cs'. This string is
more permanent than the one returned by 'error'.

'error' is more useful when used from ARexx. The error string is returned
in the 'result' variable.

Other help: geterror_func alloc_func
            »»»»»»»»»»»»» »»»»»»»»»»
===
@Command: colrow_cmd
-------------------

   COLRow <logical window> <columns> <rows>


Set the number of columns and rows (in characters) for the specified
logical window. If <columns> or <rows> are equal to -1, PowerVisor
will scale them to the maximum size available.
If <colums> or <rows> are equal to -1, PowerVisor will clear the window
everytime the size changes. This is not the case when both values are
not equal to -1 but to a fixed value.
Note that you can use the 'fit' command to automatically size the number
of columns and rows to the visible size.

See the 'lwin' list for all logical windows.

Use the 'getcol' and 'getrow' functions to get the current values.

Other help: getcol_func getrow_func lwin_list fit_cmd
            »»»»»»»»»»»á»»»»»»»»»»» »»»»»»»»» »»»»»»»
===
@Function: getcol_func
---------------------

   GETCOL( <logical window> )


Get the current number of columns (or -1) for the logical window.

Other help: getrow_func colrow_cmd lwin_list
            »»»»»»»»»»»á»»»»»»»»»» »»»»»»»»»
===
@Function: getrow_func
---------------------

   GETROW( <logical window> )


Get the current number of rows (or -1) for the logical window.

Other help: getcol_func colrow_cmd lwin_list
            »»»»»»»»»»»á»»»»»»»»»» »»»»»»»»»
===
@Function: eval_func
-------------------

   EVAL( <string pointer> )


Evaluate the string at <string pointer> and return the result.
If <string pointer> is 0, 'eval' returns 0.

Example:
   disp eval("1+2")
   displays 3.

   scan    (enter 4+4)
   disp eval(input)
   displays 8.

Other help: if_func
            »»»»»»»
===
@Function: if_func
-----------------

   IF( <condition>,<expression 1>,<expression 2> )


If <condition> is true, evaluate <expression 1>, else evaluate
<expression 2>.

Example:
   d if(1,2,3)
   displays 2.

   d if(0,2,3)
   displays 3.

   a=1
   b=2
   c=3
   d=4
   e=5
   d if(a,if(b,c,d),e)
   displays 3.

Other help: eval_func
            »»»»»»»»»
===
@Command: view_cmd
-----------------

   VIew [<address> [<bytes>]]


View memory following certain requirements. The default format is
Long/Ascii combined view. You can change the format used to display
the memory for a specific range of memory to something else.

Use the 'addtag' command to define how a specific range of memory
should be viewed.

Other help: addtag_cmd remtag_cmd tags_cmd checktag_cmd memory_cmd
            »»»»»»»»»»á»»»»»»»»»»á»»»»»»»»á»»»»»»»»»»»» »»»»»»»»»»
===
@Command: addtag_cmd
-------------------

   ADDTag <address> <bytes> <type> [<structure>]


With this command you can define the view mode to be used for a range of
memory. The 'view' command uses these tags to determine how to dump
memory.
The <address> is the starting address for the memory range. This range
continous for <bytes> bytes. <type> can be one of the following :

   BA       byte/ascii format (default for all memory not in tags)
   WA       word/ascii format
   LA       long/ascii format
   AS       ascii only format
   CO       code format
   ST       structure format

(case is not important).
Other types can be supported in future.

If your type is 'ST' you must supply an extra argument <structure>.
This is the pointer to the structure definition you must have loaded
with the 'addstruct' command. You can use the 'stsize' function to
obtain the size of a structure.

Other help: view_cmd remtag_cmd tags_cmd checktag_cmd addstruct_cmd
            »»»»»»»»á»»»»»»»»»»á»»»»»»»»á»»»»»»»»»»»» »»»»»»»»»»»»»
            stsize_func cleartags_cmd loadtags_cmd savetags_cmd tg_cmd
            »»»»»»»»»»» »»»»»»»»»»»»» »»»»»»»»»»»»á»»»»»»»»»»»» »»»»»»
            taglist_func usetag_cmd
            »»»»»»»»»»»» »»»»»»»»»»
===
@Command: loadtags_cmd
---------------------

   LOADTags <file> <base>


Load tags from a file. All tags in the file are added to the tags in
the current tag list. When an old tag collides with a new tag, the
old tag will be removed (two tags collide when they use the same
address).

If the tagfile contains structures (type 'ST') you must load these
structure in memory (with 'addstruct') before loading the tags. Otherwise
the type of the tag will be changed to Long/Ascii ('LA') and you will get
a warning :

   'Warning ! Unknown structure types have been changed to LA !'


<base> is an address to compare with the address saved in the tag
list. When these two are the same, the tags will remain on the
same address as when they were saved. <base> is useful if you want
to add tags to a piece of memory that may be somewhere else everytime
you use PowerVisor.


Other help: savetags_cmd cleartags_cmd addtag_cmd remtag_cmd tags_cmd
            »»»»»»»»»»»»á»»»»»»»»»»»»» »»»»»»»»»»á»»»»»»»»»»á»»»»»»»»
            taglist_func usetag_cmd addstruct_cmd
            »»»»»»»»»»»» »»»»»»»»»» »»»»»»»»»»»»»
===
@Command: savetags_cmd
---------------------

   SAVETags <file> <base>


Save tags in current tag list to a file.
<base> is an address to include in the saved tag file. With <base> you
can relocate the tags later if the memory element is located on
another position.


Other help: loadtags_cmd cleartags_cmd addtag_cmd remtag_cmd tags_cmd
            »»»»»»»»»»»»á»»»»»»»»»»»»» »»»»»»»»»» »»»»»»»»»» »»»»»»»»
            taglist_func usetag_cmd
            »»»»»»»»»»»» »»»»»»»»»»
===
@Command: cleartags_cmd
----------------------

   CLEARTags


Clear all tags in the current tag list.

Other help: loadtags_cmd savetags_cmd addtag_cmd remtag_cmd tags_cmd
            »»»»»»»»»»»»á»»»»»»»»»»»» »»»»»»»»»» »»»»»»»»»» »»»»»»»»
            taglist_func usetag_cmd
            »»»»»»»»»»»» »»»»»»»»»»
===
@Command: remtag_cmd
-------------------

   REMTag <address>


Remove the range in the tag list beginning with <address>.

Other help: view_cmd addtag_cmd tags_cmd checktag_cmd cleartags_cmd
            »»»»»»»»á»»»»»»»»»»á»»»»»»»»á»»»»»»»»»»»» »»»»»»»»»»»»»
            taglist_func usetag_cmd
            »»»»»»»»»»»» »»»»»»»»»»
===
@Command: tags_cmd
-----------------

   TAGs


List all tags currently defined in the current tag list.

Other help: view_cmd addtag_cmd remtag_cmd checktag_cmd
            »»»»»»»»á»»»»»»»»»»á»»»»»»»»»»á»»»»»»»»»»»»
            taglist_func usetag_cmd
            »»»»»»»»»»»» »»»»»»»»»»
===
@Command: checktag_cmd
---------------------

   <bytes remaining> <- CHecktag <address>


Check if an address resides in the current tag list. If it is, PowerVisor
will print the type of the tag list followed by the remaining number of bytes
after <address> in this tag.
If the address is not in the tag list, PowerVisor will print the number
of bytes remaining before the next tag. If there is no next tag, PowerVisor
will print $7fffffff.

Other help: view_cmd addtag_cmd remtag_cmd tags_cmd
            »»»»»»»»á»»»»»»»»»»á»»»»»»»»»»á»»»»»»»»
            taglist_func usetag_cmd
            »»»»»»»»»»»» »»»»»»»»»»
===
@Command: usetag_cmd
-------------------

   USetag <number>


Set the current tag list to <number> (0 .. 15). The current tag list is
used by all tag commands and by 'view'.

Other help: tg_cmd addtag_cmd remtag_cmd tags_cmd taglist_func
            »»»»»»á»»»»»»»»»»á»»»»»»»»»»á»»»»»»»»á»»»»»»»»»»»»
===
@Command: tg_cmd
---------------

   TG <number> <command>


Temporarily set the current tag list to <number> and execute the command.

Other help: usetag_cmd addtag_cmd remtag_cmd tags_cmd taglist_func
            »»»»»»»»»»á»»»»»»»»»»á»»»»»»»»»»á»»»»»»»»á»»»»»»»»»»»»
===
@Function: taglist_func
----------------------

   TAGLIST( )


Return the current tag list. This is a number between 0 and 15.

Other help: usetag_cmd tg_cmd
            »»»»»»»»»»á»»»»»»
===
@Command: interprete_cmd
-----------------------

   INTErprete <structure pointer> <struct def pointer>


Show the contents of a structure at <structure pointer> using the
<struct def pointer> structure definition. You can load and add
structure definitions with the 'AddStruct' command.

Other help: addstruct_cmd stru_list
            »»»»»»»»»»»»» »»»»»»»»»
===
@Command: clearstruct_cmd
------------------------

   CLEARStruct


Clear all structure definitions loaded with 'addstruct'.

Other help: addstruct_cmd remstruct_cmd stru_list
            »»»»»»»»»»»»»á»»»»»»»»»»»»»á»»»»»»»»»
===
@Command: addstruct_cmd
----------------------

   ADDStruct <filename>


Add the structure definitions from the file to the PowerVisor 'stru'
list. You can then use these structures with the 'interprete', 'peek'
and 'apeek' commands.
PowerVisor will first check in the current directory for the file and
than in the s:pv directory. This is the recommended place for scripts
and pvsd files.

You can look in the 'stru' list to see which structures are allready
in memory.

Other help: remstruct_cmd stru_list interprete_cmd peek_func apeek_func
            »»»»»»»»»»»»»á»»»»»»»»» »»»»»»»»»»»»»»á»»»»»»»»»á»»»»»»»»»»
            stsize_func
            »»»»»»»»»»»
===
@Command: string_cmd
-------------------

   <string> <- STRIng <string pointer>


This command is only useful in ARexx. It returns an ARexx string containing
the string pointed to by <string pointer>.


Other help: assign_cmd rx_cmd
            »»»»»»»»»» »»»»»»
===
@Command: assign_cmd
-------------------

   ASsign <assignment string>


Assign a value to a PowerVisor variable.
This command also works for memory assignments.

Example:

   The following ARexx script (type in and execute with 'rx')

      /* */
      address rexx_powervisor
      a=1
      assign 'a=2'
      disp a
      disp 'a'

   Will have as output :

      00000001 , 1
      00000002 , 2

Other help: rx_cmd clip_cmd remclip_cmd string_cmd
            »»»»»» »»»»»»»»á»»»»»»»»»»» »»»»»»»»»»
===
@Command: rx_cmd
---------------

   RX <file name>


Execute an ARexx script. The default extension for ARexx scripts is '.pv'.
You do not need to type this extension unless you use a different one.

The name of the PowerVisor ARexx port is :

   REXX_POWERVISOR

Other help: script_cmd assign_cmd hide_cmd unhide_cmd sync_cmd async_cmd
            »»»»»»»»»» »»»»»»»»»»á»»»»»»»»á»»»»»»»»»»á»»»»»»»»á»»»»»»»»»
            clip_cmd remclip_cmd
            »»»»»»»»á»»»»»»»»»»»
===
@Command: remstruct_cmd
----------------------

   REMStruct <struct def pointer>


Unload a structure definition previously loaded with 'addstruct'.

Other help: addstruct_cmd stru_list
            »»»»»»»»»»»»»á»»»»»»»»»
===
@Function: peek_func
-------------------

   PEEK( <structure pointer>,<struct def pointer>,<field name> )


Returns the value of <structure>.<field>.

Other help: addstruct_cmd interprete_cmd apeek_func stru_list
            »»»»»»»»»»»»»á»»»»»»»»»»»»»»á»»»»»»»»»»á»»»»»»»»»
===
@Function: stsize_func
---------------------

   STSIZE( <structure pointer> )


Return the size of the structure represented by <structure pointer>.

Other help: addstruct_cmd stru_list
            »»»»»»»»»»»»»á»»»»»»»»»
===
@Function: apeek_func
--------------------

   APEEK( <structure pointer>,<struct def pointer>,<field name> )


Returns the address of <structure>.<field>.

Other help: addstruct_cmd interprete_cmd peek_func stru_list
            »»»»»»»»»»»»»á»»»»»»»»»»»»»»á»»»»»»»»»á»»»»»»»»»
===
@Command: for_cmd
----------------

   FOR <listname> <command>


For each element in list <listname> execute <command>.
The command is executed with the pointer to the current element from the
list in the 'RC' variabele.

Example:
   for task disp rc
   display all tasks.

Other help: list_cmd <list>_list
            »»»»»»»» »»»»»»»»»»»
===
@Command: llist_cmd
------------------

   LList <node> ['start']


Traverse a system list and prints all nodes in the list.
If 'start' is specified, 'LList' will automatically search to the
start of the list.

Other help: list_cmd
            »»»»»»»»
===
@Command: vars_cmd
-----------------

   VArs ['all']


This command shows all variables. You will notice the variables
'rc' and 'error'.
When you use the 'all' option, PowerVisor will show all variables
including constants and functions.
Notice the 'mode' special variable and the 'version' constant.


Other help: variables mode_cmd remvar_cmd functions
            »»»»»»»»»á»»»»»»»»á»»»»»»»»»» »»»»»»»»»
===
@Command: remvar_cmd
-------------------

   REMVar {<variables>}


This command removes all variables in the commandline if they exist.
'remvar' is very useful in scripts.


Other help: variables vars_cmd
            »»»»»»»»» »»»»»»»»
===
@Command: alias_cmd
------------------

   ALias [<alias cmd> <alias string>]


Alias without arguments lists all current aliases.
You can set a new alias <alias cmd> to <alias string> with this
command.
When you create a new alias with the same name, the old one will
be removed.
You can use [] to specify where the arguments must be positioned.
When you want to use quotes you must precede them with '\'.

Example:
   alias lfd 'loadfd [] fd:[]_lib.fd'
      When you type 'lfd exec' on the command line, the command line
      will be expanded to 'loadfd exec fd:exec_lib.fd' before
      execution.

   alias execute li[]bs
      When you type 'execute st li' on the command line,
      the command line will be expanded to 'list libs'.
      (The previous example is ofcourse completely useles).

   alias writeln 'print \'[]\\0a\''
      'writeln we are testing' will result in
      'print 'we are testing\0a''

Note:
   You can use the [] operator as many times as you wish (even in
   the command).

Note:
   You cannot use alias commands in the alias string. So the
   following will NOT create an infinite loop:
      alias disp 'list []'
      alias list 'disp []'
   This sequence of command simply swappes the two commands 'disp'
   and 'list'.

Note:
   You must type an alias in full. You can not use abbreviations for
   aliases on the command line. (If you want an abbreviation, you can
   define one with another alias).

Other help: unalias_cmd
            »»»»»»»»»»»
===
@Command: unalias_cmd
--------------------

   UNALias <alias cmd>


Remove an alias from the alias list.

Other help: alias_cmd
            »»»»»»»»»
===
@Command: hold_cmd
-----------------

   HOld


This command closes the PowerVisor screen and waits for the <Right-Alt>+
<Right-Shift>+? combination to reopen it again.
If a crash happens PowerVisor will reopen its screen automatically.

Other help: crash quit_cmd
            »»»»» »»»»»»»»
===
@Command: quit_cmd   (commandline and scripts only)
-----------------

   Quit


Quit PowerVisor. Everything will be cleaned up.
Frozen tasks are lost. Monitor functions will be cleaned. Crash trapping
is disabled. Stack checking is disabled. All debug
tasks are put back in the task list (they continue to run).
All FDFiles will be removed from memory.
If one of your debug tasks is tracing 'Quit' will print an error message.
First halt this task with 'trace h'.

Warning: Everything you allocated or opened using library functions will
         NOT be cleaned up. Remember to do it yourself.

         All crashed tasks are left in memory. They will simply wait.

         All freezed tasks are lost forever (and their memory too).
         UnFreeze or kill your tasks before you quit.

         All memory allocated with the 'alloc' function is automatically
         freed.

         All tasks you were debugging will simply be put back on their
         task list and continue executing.

         All physical windows and logical windows are closed.

If 'quit' is called from within a script, the script is stopped.
'quit' will be ignored if called from within a group operator. 'Quit' will
only work when called from the commandline.

Other help: hold_cmd trace_cmd
            »»»»»»»» »»»»»»»»»
===
@Command: gadgets_cmd
--------------------

   Gadgets <window>


Lists all gadgets in the specified window.

Other help: wins_list list_cmd info_cmd
            »»»»»»»»» »»»»»»»»á»»»»»»»»
===
@Command: size_cmd
-----------------

   SIze <physical window> <w> <h>


Set the width and height (in pixels) for the physical window. This command
only works if the physical window is a non-backdrop window.

Other help: screen_cmd move_cmd pwin_list
            »»»»»»»»»» »»»»»»»» »»»»»»»»»
===
@Command: move_cmd
-----------------

   MOVe <physical window> <x> <y>


Move the physical window to a specified position. This command only works
if the physical window is a non-backdrop window.

Other help: screen_cmd size_cmd pwin_list
            »»»»»»»»»» »»»»»»»» »»»»»»»»»
===
@Command: screen_cmd
-------------------

   SCREen [<screen>]


Move the PowerVisor window to another screen. If you want PowerVisor on its
own screen, type 'screen' without arguments (this is default).
You can use the 'size' command to change the size for this window (or you
can use the sizinggadget).
If <screen> is 0, PowerVisor will go to its own screen but will remain
on a non-backdrop window.

Example:
   screen workbench         move PowerVisor to workbench screen

Other help: size_cmd move_cmd
            »»»»»»»» »»»»»»»»
===
@Command: remres_cmd
-------------------

   REMRes <resident pointer>


Remove a resident module.

Example:
   remres resm:exec

Other help: syslists
            »»»»»»»»
===
@Command: remove_cmd
-------------------

   <node> <- REMOve <node>


Remove a node from a list. Be carefull with this command. No checking is done
if you are really removing a node. The memory for this node is not freed.

Other help: remres_cmd remhand_cmd kill_cmd
            »»»»»»»»»»á»»»»»»»»»»»á»»»»»»»»
===
@Command: curdir_cmd
-------------------

   CUrdir <process> <directory name>


Set a new current directory for a process.

Example:
   curdir task:Shell ':langua/sources'

Other help: strings list_op
            »»»»»»»á»»»»»»»
===
@Command: clear_cmd
------------------

   CLEar [<value>]


Fill all unused memory with <value> (or 0 if value is not specified).
===
@Function: lines_func
--------------------

   LINES( LOGWIN )


This function gets the maximum number of lines available on the
PowerVisor logical window.

Example:
   disp lines(main)

Other help: cols_func locate_cmd lwin_list
            »»»»»»»»» »»»»»»»»»» »»»»»»»»»
===
@Function: cols_func
-------------------

   COLS( LOGWIN )


This function gets the maximum number of columns available on the
PowerVisor window.

Example:
   disp cols(main)

Other help: lines_func locate_cmd lwin_list
            »»»»»»»»»» »»»»»»»»»» »»»»»»»»»
===
@Function: getlwin_func
----------------------

   GETLWIN()


This function returns a pointer to the current logical window.

Other help: lwin_list xwin_cmd current_cmd getactive_func active_cmd
            »»»»»»»»»á»»»»»»»» »»»»»»»»»»» »»»»»»»»»»»»»»á»»»»»»»»»»
===
@Command: scroll_cmd
-------------------

   SCROll <logical window> <x> <y>


Scroll the logical window. <x> and <y> is the new top-left visible
position. This command checks for illegal values.

Other help: active_cmd lwin_list
            »»»»»»»»»»á»»»»»»»»»
===
@Command: active_cmd
-------------------

   Active <logwin>


Make a logical window the active one. The active logical window is
the logical window where you can scroll with the keys, and where all
input is redirected to (see The 'Screen' tutorial file for more info).

Other help: list_list getactive_func current_cmd getlwin_func
            »»»»»»»»»á»»»»»»»»»»»»»»á»»»»»»»»»»»á»»»»»»»»»»»»
===
@Function: getactive_func
------------------------

   GETACTIVE()


This function returns a pointer to the active logical window. This
is the logical window where you can scroll with the keyboard.

Other help: lwin_list xwin_cmd current_cmd active_cmd getlwin_func
            »»»»»»»»»á»»»»»»»» »»»»»»»»»»» »»»»»»»»»» »»»»»»»»»»»»
===
@Function: getx_func
-------------------

   GETX()


Get the current x coordinate on the current logical window (in columns).

Example:
   a=getx()

Other help: gety_func locate_cmd getchar_func variables current_cmd
            »»»»»»»»»á»»»»»»»»»»á»»»»»»»»»»»» »»»»»»»»» »»»»»»»»»»»
            getlwin_func
            »»»»»»»»»»»»
===
@Function: gety_func
-------------------

   GETY()


Get the current y coordinate on the current logical window (in lines).

Other help: getx_func locate_cmd getchar_func variables current_cmd
            »»»»»»»»»á»»»»»»»»»»á»»»»»»»»»»»»á»»»»»»»»» »»»»»»»»»»»
            getlwin_func
            »»»»»»»»»»»»
===
@Function: getchar_func
----------------------

   GETCHAR()


Get the character at the current screenposition in the current logical
window.

Example:
   locate 10,10
   a=getchar()

Other help: getx_func gety_func locate_cmd variables current_cmd getlwin_func
            »»»»»»»»»á»»»»»»»»»á»»»»»»»»»»á»»»»»»»»» »»»»»»»»»»»á»»»»»»»»»»»»
===
@Command: current_cmd
--------------------

   CURRent <logical window>


Set the current logical window. Only 'extra' and 'main' are allowed.
Before you can use the 'extra' logical window you must open it with
the 'xwin' command.

Other help: xwin_cmd lwin_list getlwin_func on_cmd active_cmd getactive_func
            »»»»»»»»á»»»»»»»»» »»»»»»»»»»»» »»»»»» »»»»»»»»»»á»»»»»»»»»»»»»»
===
@Command: on_cmd
---------------

   ON <logical window> <command>


With this command you can execute an other command, so that it's output
appears on the logical window of your choice (except 'debug').
This command temporary sets the current window to <logical window>.

Example:

   open 'extra' logical window :
      xwin

   execute a list on that window :
      on xwin list task

Other help: xwin_cmd lwin_list getlwin_func current_cmd
            »»»»»»»»á»»»»»»»»» »»»»»»»»»»»» »»»»»»»»»»»
===
@Command: cls_cmd
----------------

   CLs


This command clears the current logical window.

Other help: current_cmd getlwin_func
            »»»»»»»»»»»á»»»»»»»»»»»»
===
@Command: led_cmd
----------------

   LEd


Use this command to toggle the powerled on or off. This is useful when
a program is crashed or when you are using the led monitor.

Other help: addfunc_cmd
            »»»»»»»»»»»
===
@Command: load_cmd
-----------------

   <bytes loaded> <- LOAd <filename> <start> [<max bytes>]


Load a file into memory. Only <max bytes> are read in if specified.
Please allocate the memory you use.

Example:
   pointer=alloc(n,10000)
   load file pointer 10000
   disp pointer

Don't forget to free you memory later (with 'free').

Other help: save_cmd free_func
            »»»»»»»» »»»»»»»»»
===
@Command: save_cmd
-----------------

   <bytes written> <- SAve <filename> <start> <bytes>


Save memory to disk.

Other help: load_cmd
            »»»»»»»»
===
@Command: fregs_cmd
------------------

   FREGs <task>|<debug node>


Show the floating point registers for a task in a primitive way.
Each floating point register (fp0..fp7) is shown in the internal
Exec stackframe format (12 bytes).

Future enhancements will provide better output and more support in
general for floating point debugging.


Other help: regs_cmd
            »»»»»»»»
===
@Command: regs_cmd
-----------------

   REGs <task>|<crash node>|<debug node>


Show the registers for a task.
When a task is crashed use the crash node pointer instead. If you don't
do this, some registers may contain wrong information.

Other help: debugging crash special_op fregs_cmd
            »»»»»»»»»á»»»»» »»»»»»»»»» »»»»»»»»»
===
@Command: print_cmd
------------------

   PRint <string>


Print a string on the current logical window. (Useful for script and ARexx
programs)

Example:
   print 'testing'
   print test

To print a newline after the string, use:

   print 'testing\0a'
   print testing\0a

Other help: disp_cmd locate_cmd strings current_cmd getlwin_func
            »»»»»»»» »»»»»»»»»» »»»»»»» »»»»»»»»»»»á»»»»»»»»»»»»
===
@Command: sprint_cmd
-------------------

   SPRint <string>


Print a string on a serial terminal or printer (Useful for 'addfunc'
for example).

Other help: addfunc_cmd
            »»»»»»»»»»»
===
@Command: locate_cmd
-------------------

   LOCAte <x> [<y>]


Adjust the current location on the current logical window.

Other help: getx_func gety_func getchar_func lines_func cols_func  print_cmd
            »»»»»»»»»á»»»»»»»»»á»»»»»»»»»»»» »»»»»»»»»»á»»»»»»»»» á»»»»»»»»»
            current_cmd getlwin_func home_cmd
            »»»»»»»»»»»á»»»»»»»»»»»» »»»»»»»»
===
@Command: home_cmd
-----------------

   HOMe


Adjust the current location on the current logical window to the top location
visible. Note that this is not always the same as 'locate 0,0'.

Other help: getx_func gety_func getchar_func lines_func cols_func  print_cmd
            »»»»»»»»»á»»»»»»»»»á»»»»»»»»»»»» »»»»»»»»»»á»»»»»»»»» á»»»»»»»»»
            current_cmd getlwin_func locate_cmd
            »»»»»»»»»»»á»»»»»»»»»»»» »»»»»»»»»»
===
@Function: lastmem_func
----------------------

   LASTMEM()


This function returns the address that 'memory' and 'unasm' will use
to continue their listing.

Other help: memory_cmd unasm_cmd lastbytes_func lastlines_func lastfound_func
            »»»»»»»»»» »»»»»»»»» »»»»»»»»»»»»»»á»»»»»»»»»»»»»»á»»»»»»»»»»»»»»
===
@Function: lastlines_func
------------------------

   LASTLINES()


This function returns the last number of lines used with the 'unasm'
command (default is 20).

Other help: unasm_cmd lastbytes_func
            »»»»»»»»» »»»»»»»»»»»»»»
===
@Function: lastbytes_func
------------------------

   LASTBYTES()


This function returns the last number of bytes used with the 'view'
or 'memory' commands (default is 320).

Other help: memory_cmd view_cmd lastlines_func
            »»»»»»»»»» »»»»»»»» »»»»»»»»»»»»»»
===
@Function: lastfound_func
------------------------

   LASTFOUND()


This function returns the address of the second byte of the string found
with 'search' or 'next'. This is the address where 'next' will continue
with the search.

Other help: search_cmd next_cmd
            »»»»»»»»»» »»»»»»»»
===
@Function: alloc_func
--------------------

   ALLOC( ('n',<size>) | ('c',<size>) | ('s',<string>) )


Use this function for easy memory allocation.

Example:
   a=alloc(n,1000)
   allocates 1000 bytes and stores the pointer to this memoryblock in 'a'.

   a=alloc(c,1000)
   allocates 1000 bytes and stores the pointer to this memoryblock in 'a'.
   The memory will be allocated in chip ram.

   a=alloc(s,'PowerVisor')
   allocates 11 bytes and copies the string 'PowerVisor' to this
   memory region. 'a' is the pointer to this memoryblock.

Use the 'free' function to free this memory.
Note that memory allocated with this command is automatically freed
when PowerVisor quits.
Also note that this memory is not guaranteed to be in chip ram.

When the blocksize is smaller than 65533 bytes the result from this function
is a pointer after a word containing the size. This pointer is thus word
alligned but not longword alligned.
When the blocksize is bigger the result is a pointer after a longword
containing the size. This pointer is longword alligned.
Using word or longword allignment you can determine the size of a memory
block. An easier way to do this is to use the 'getsize' function.

Other help: realloc_func free_func strings variables getsize_func cleanup_cmd
            »»»»»»»»»»»»á»»»»»»»»»á»»»»»»» »»»»»»»»» »»»»»»»»»»»» »»»»»»»»»»»
            showalloc_cmd isalloc_func
            »»»»»»»»»»»»» »»»»»»»»»»»»
===
@Function: realloc_func
----------------------

   REALLOC( <memoryblock>,<new size> )


Use this function to reallocate a memoryblock allocated with the
'alloc' function. Only memoryblocks smaller than 64K are supported.

Other help: alloc_func free_func strings variables getsize_func
            »»»»»»»»»» »»»»»»»»»á»»»»»»» »»»»»»»»» »»»»»»»»»»»»
            cleanup_cmd showalloc_cmd isalloc_func
            »»»»»»»»»»»á»»»»»»»»»»»»»á»»»»»»»»»»»»
===
@Function: free_func
-------------------

   FREE( <pointer> )


Free a block previously allocated with 'alloc' or 'getstr'.

Other help: alloc_func getstr_cmd getsize_func showalloc_cmd cleanup_cmd
            »»»»»»»»»»á»»»»»»»»»» »»»»»»»»»»»» »»»»»»»»»»»»»á»»»»»»»»»»»
===
@Function: getsize_func
----------------------

   GETSIZE( <memoryblock> )


This function determines the size of a memoryblock allocated with the
'alloc' function or some other PowerVisor commands.

Other help: alloc_func free_func getstr_cmd isalloc_func showalloc_cmd
            »»»»»»»»»»á»»»»»»»»»á»»»»»»»»»» »»»»»»»»»»»» »»»»»»»»»»»»»
            cleanup_cmd realloc_cmd
            »»»»»»»»»»» »»»»»»»»»»»
===
@Function: isalloc_func
----------------------

   ISALLOC( <pointer> )


This function checks if <pointer> points to a memoryblock allocated
with the 'alloc' function. If it is, isalloc returns a pointer to
the pointer, otherwise 0.

Other help: alloc_func free_func getsize_func showalloc_cmd cleanup_cmd
            »»»»»»»»»» »»»»»»»»»á»»»»»»»»»»»»á»»»»»»»»»»»»»á»»»»»»»»»»»
===
@Command: showalloc_cmd
----------------------

   SHowalloc


This command shows all memory blocks allocated with the 'alloc'
function. All memory blocks that are in this list will be
automatically freed when PowerVisor quits.

Other help: alloc_func free_func getsize_func isalloc_func cleanup_cmd
            »»»»»»»»»»á»»»»»»»»»á»»»»»»»»»»»»á»»»»»»»»»»»»á»»»»»»»»»»»
            realloc_func
            »»»»»»»»»»»»
===
@Command: cleanup_cmd
--------------------

   CLEANup


This command frees all memory blocks that are allocated with the
'alloc' function. This is done automatically when PowerVisor quits.

Other help: alloc_func free_func getsize_func isalloc_func realloc_func
            »»»»»»»»»»á»»»»»»»»»á»»»»»»»»»»»»á»»»»»»»»»»»»á»»»»»»»»»»»»
            showalloc_cmd
            »»»»»»»»»»»»»
===
@Command: color_cmd
------------------

   COLor <col num> <red> <green> <blue>


Change the rgb value of a PowerVisor screen color.

This command gives an error when you try to use it when
PowerVisor is on a window.

Other help: screen_cmd
            »»»»»»»»»»
===
@Function: rfrate_func
---------------------

   RFRATE( )


Give the current refresh rate.

Other help: refresh_cmd rfcmd_func
            »»»»»»»»»»»á»»»»»»»»»»
===
@Function: rfcmd_func
--------------------

   RFCMD( )


Give a pointer to the current refresh command (or 0 if no refresh).

This function returns a string if used from ARexx.

Other help: refresh_cmd rfrate_func
            »»»»»»»»»»»á»»»»»»»»»»»
===
@Function: curlist_func
----------------------

   CURLIST( )


Give a pointer to the name of the current list.

This function returns a string if used from ARexx.

Other help: syslists
            »»»»»»»»
===
@Command: request_cmd
--------------------

   <result> <- REQuest <body string> <gadget string> <argument>


Show a requester on the PowerVisor screen. This command uses
reqtools.library (V37 or higher) (⌐ Nico Franτois) is available, otherwise
this command is simulated using the 'key' function.
The result of this command is a number indicating the button that was
pressed (this number is also what you should press on the keyboard if
you don't have reqtools.library). The rightmost button is 0. All other
buttons are numbered from left to right starting with 1.

<body string> is the string for the requester title bar.
<gadget string> is the string with all the button text below.
Note that you can use one % C-formatting character (optionally) in one
of the above strings. If you do this <argument> is used for the value.
Note that <argument> is NOT an optional argument.


Other help: scan_cmd reqload_cmd reqsave_cmd getstring_cmd key_func
            »»»»»»»»á»»»»»»»»»»»á»»»»»»»»»»»á»»»»»»»»»»»»»á»»»»»»»»
===
@Command: reqload_cmd
--------------------

   INPUT,<ptr to filename> <- REQLoad <title>


Ask the user for a filename with a filerequester. This command uses
reqtools.library (V37 or higher) (⌐ Nico Franτois) if available, otherwise
this command is equivalent to the 'scan' command.
The result of this command (in INPUT), is a pointer to the file name
(or 0 if the user pressed 'cancel'). This string is remembered until you
quit PowerVisor or until you use another input command ('scan', 'reqload',
'reqsave' or 'getstring').

This command returns a string if used from ARexx.

<title> is the title to be put in the requester window

The filerequester is a 'load' requester. This means that you can
double click on filenames.


Other help: scan_cmd request_cmd reqsave_cmd getstring_cmd key_func
            »»»»»»»»á»»»»»»»»»»»á»»»»»»»»»»»á»»»»»»»»»»»»»á»»»»»»»»
===
@Command: reqsave_cmd
--------------------

   INPUT,<ptr to filename> <- REQSave <title>


Ask the user for a filename with a filerequester. This command uses
reqtools.library (V37 or higher) (⌐ Nico Franτois) if available, otherwise
this command is equivalent to the 'scan' command.
The result of this command (in INPUT), is a pointer to the file name
(or 0 if the user pressed 'cancel'). This string is remembered until you
quit PowerVisor or until you use another input command ('scan', 'reqload',
'reqsave' or 'getstring').

This command returns a string if used from ARexx.

<title> is the title to be put in the requester window

The filerequester is a 'save' requester. This means that you can't
double click on filenames.


Other help: scan_cmd request_cmd reqload_cmd getstring_cmd key_func
            »»»»»»»»á»»»»»»»»»»»á»»»»»»»»»»»á»»»»»»»»»»»»»á»»»»»»»»
===
@Command: getstring_cmd
----------------------

   INPUT,<ptr to inputline> <- GEtstring <title> <max number of chars>


Ask the user for input. This command uses reqtools.library (V37 or
higher) (⌐ Nico Franτois) if available, otherwise this command is equivalent
to the 'scan' command.
The result of this command (in INPUT), is a pointer to the result string
(or 0 if the user pressed 'cancel'). This string is remembered until you
quit PowerVisor or until you use another input command ('scan', 'reqload',
'reqsave' or 'getstring').

This command returns a string if used from ARexx.

<title> is the title to be put in the requester window
<max number of chars> is the maximum number of characters that is allowed
in the requester

Both parameters are ignored if 'scan' is used

Other help: scan_cmd request_cmd reqload_cmd reqsave_cmd key_func
            »»»»»»»»á»»»»»»»»»»»á»»»»»»»»»»»á»»»»»»»»»»»á»»»»»»»»
===
@Command: scan_cmd
-----------------

   INPUT,<pointer to inputline> <- SCAn [<number>]


Ask the user for input. This command is very useful for ARexx scripts.
The result of this command (in INPUT), is a pointer to the result string.
This string is remembered until you quit PowerVisor or until you use another
input command ('scan', 'getstring', 'reqload' or 'reqsave')

This command returns a string if used from ARexx.

Normally the prompt is '????'. If you want another 4 letter prompt you
can use <number>.

Example:
   scan *"TEST"

   will ask for a line of text (with the 'TEST' prompt) and store the
   pointer to this line in 'input'.

Other help: key_func showalloc_cmd free_func cleanup_cmd getstring_cmd
            »»»»»»»» »»»»»»»»»»»»» »»»»»»»»» »»»»»»»»»»» »»»»»»»»»»»»»
            reqload_cmd reqsave_cmd
            »»»»»»»»»»»á»»»»»»»»»»»
===
@Function: key_func
------------------

   KEY( )


Wait for a key and return the ascii value.

Example:
   a=key()

Other help: variables qual_func scan_cmd
            »»»»»»»»» »»»»»»»»» »»»»»»»»
===
@Function: qual_func
-------------------

   QUAL( )


Return the qualifier for the last pressed key (with 'key').

Example:
   a=key()
   disp qual()

Other help: variables key_func
            »»»»»»»»» »»»»»»»»
===
@Command: disp_cmd
-----------------

   <value of expression> <- Disp <expression>


Use this command to display an expression.
Also use this command to execute a library function if you don't want
to put the result in a variable.

Other help: variables expressions libfuncs print_cmd void_cmd
            »»»»»»»»»á»»»»»»»»»»»á»»»»»»»» »»»»»»»»» »»»»»»»»
===
@Command: refresh_cmd
--------------------

   Refresh [<refresh rate> <command>]


This command installs <command> to be executed every <refresh rate>
IntuiTick (one IntuiTick is a tenth of a second).

With no arguments 'refresh' removes the refresh command.

Note that before you can execute this command you must open the refresh
logical window with the 'rwin' command.

Other help: syslists list_cmd rfrate_func rfcmd_func rwin_cmd
            »»»»»»»»á»»»»»»»» »»»»»»»»»»»á»»»»»»»»»» »»»»»»»»
===
@Command: fit_cmd
----------------

   FIT <logical window>


This command adjusts the number of columns and number of rows of a logical
window to fit exactly in the visible size. This is useful after a switch
from non-interlace to interlace for example.

You can achieve the same result with the 'colrow' command, but then you have
to compute the number of columns and rows for yourselves.

Other help: colrow_cmd lwin_list
            »»»»»»»»»» »»»»»»»»»
===
@Command: awin_cmd
-----------------

   AWin [<number of lines>]


Open/close the Rexx window. This logical window is used when it is present
for Rexx output. If it is not present the current logical window is used.

If <number of lines> is specified, the logical window is opened with
<number of lines> lines (for the 'topaz 8' font).


Other help: dwin_cmd owin_cmd rwin_cmd xwin_cmd lwin_list
            »»»»»»»»á»»»»»»»»á»»»»»»»»á»»»»»»»»á»»»»»»»»»
===
@Command: owin_cmd
-----------------

   OWin [<number of lines>]


Open/close the PPrint window. This logical window is used when it is present
for PortPrint output. If it is not present the current logical window is
used.

If <number of lines> is specified, the logical window is opened with
<number of lines> lines (for the 'topaz 8' font).


Other help: dwin_cmd awin_cmd rwin_cmd xwin_cmd lwin_list
            »»»»»»»»á»»»»»»»»á»»»»»»»»á»»»»»»»»á»»»»»»»»»
===
@Command: rwin_cmd
-----------------

   RWin [<number of lines>]


Open/close the Refresh window. (required if you want to use the 'refresh'
command).

If <number of lines> is specified, the logical window is opened with
<number of lines> lines (for the 'topaz 8' font).


Other help: awin_cmd owin_cmd dwin_cmd xwin_cmd lwin_list
            »»»»»»»»á»»»»»»»» »»»»»»»»á»»»»»»»»»»»»»»»»»
===
@Command: xwin_cmd
-----------------

   Xwin [<number of lines>]


Open/close the Extra window.

If <number of lines> is specified, the logical window is opened with
<number of lines> lines (for the 'topaz 8' font).


Other help: awin_cmd owin_cmd dwin_cmd rwin_cmd lwin_list
            »»»»»»»»á»»»»»»»» »»»»»»»»á»»»»»»»»»»»»»»»»»
===
@Command: dwin_cmd
-----------------

   DWin [<number of lines>]


Open/close the Debug window. (required if you want to use fullscreen
debugging).

If <number of lines> is specified, the logical window is opened with
<number of lines> lines (for the 'topaz 8' font).


Other help: owin_cmd awin_cmd rwin_cmd xwin_cmd lwin_list
            »»»»»»»»á»»»»»»»» »»»»»»»»á»»»»»»»» »»»»»»»»»
===
@Command: mode_cmd
-----------------

   MOde <mode argument> {<mode argument>...}


Install preferences.

The following arguments are supported:
   byte        to list memory in byte notation
   word        to list memory in word notation
   long        to list memory in long notation (default)
   ascii       to list memory in ascii notation

   lace        interlace on
   nolace      no interlace (default)

   dec         integers are displayed as decimal
   hex         integers are displayed as hex
   hexdec      both formats are displayed (default)

   more        display prompt when scrolling to much (default)
   nomore      continue scrolling

   fb          feedback on screen (default)
   nofb        no command feedback

   auto        do an automatic list whenever the user uses a 'change
               current list' command.
   noauto      don't do this (default)

   pal         pal screen
   ntsc        ntsc screen
   vga         vga screen
   viking      a2024 screen

   shex        show hex data when disassembling memory (default)
   noshex      do not show hex data

   space       add a space after a snapped word (default)
   nospace     don't add a space

   sbottom     size gadget is in bottom border (default)
   nosbottom   size gadget is in right border

   fancy       use two bitplane screen. If you have AmigaDOS 2.0, a newlook 3D
               screen will be used (default)
   nofancy     normal one bitplane screen

   lonespc     snap space when user clicks on empty space in window
   nolonespc   don't do this (default)

   patch       patch the Exec AddTask function so that all new tasks will
               have full protection for PowerVisor (default)
   nopatch     do not patch Exec AddTask. You must use 'mode nopatch' if you
               want to use another debugger (like CodeProbe or MonAm)
               when PowerVisor is still in memory. Otherwise the Amiga can
               crash.

   intui       Open a physical window when you open a standard logical window
               with one of the standard logical window commands
   nointui     Only open the logical window on the 'Main' physical window
               (default)

Example:
   mode byte lace

You can set and examine the 'mode' variable.
Parameters set with this command can be saved with the 'saveconfig' command.

Other help: variables saveconfig_cmd
            »»»»»»»»» »»»»»»»»»»»»»»
===
@Command: copy_cmd
-----------------

   Copy <source> <destination> <bytes>


Copy <bytes> bytes from <source> to <destination>.
Be cautious with this command. It can be very destructive.

Other help: fill_cmd search_cmd
            »»»»»»»»á»»»»»»»»»»
===
@Command: fill_cmd
-----------------

   Fill <dest> <bytes> <with>


Fill the memory starting at <dest> with the string <with>. Do this
for <bytes> bytes.

For example:
   fill $c50000 22 'test\41'

will copy 4.4 times the string "testA" beginning at $c50000.
The memory map looks something like:
00C50000: testAtestAtestAt
00C50010: estAte

Be cautious with this command. It can be very destructive.

Other help: copy_cmd search_cmd
            »»»»»»»»á»»»»»»»»»»
===
@Command: search_cmd
-------------------

   RC,<address> <- Search <start> <bytes> <string>


Search to a string in memory starting at <start>. Search until the
string is found, or until you have searched <bytes> bytes.

Example:
   search $1000 2000 'test'

Will search for the string "test" beginning at $1000. If after 2000 bytes
the string is not found, 0 is the result.

The result for this command will also be stored in the 'rc' variable.

Other help: copy_cmd fill_cmd variables next_cmd lastfound_func
            »»»»»»»»á»»»»»»»»á»»»»»»»»» »»»»»»»» »»»»»»»»»»»»»»
===
@Command: next_cmd
-----------------

   RC,<address> <- Next


Continue searching at the last position.
This command prints 0 if not found.

The result is stored in the 'rc' variable.

Other help: search_cmd variables lastfound_func
            »»»»»»»»»»á»»»»»»»»» »»»»»»»»»»»»»»
===
@Command: stack_cmd
------------------

   STAck [<task> <micro seconds>]


Use this command to check stack usage for a specific task. You can only
check one task at the time. With no arguments this command removes the
stack checker.

'stack' uses the UNIT_MICROHZ timer device. This means that <micro seconds>
must be greater or equal than 2. This command has a better check resolution
than 'account' (if your <micro seconds> value is low enough).

'stack' freezes the task when a stack overflow is about to occur (see the
'prefs' command for the minimum number of bytes allowed in the stack).
Note that this behaviour is different from 'account'. Stack overflows
trapped with the 'account' stack checker are put in the 'crsh' (crash)
list (This behaviour may change in future).

In addition to stack checking this command also computes the maximum stack
usage for the task. You can display this maximum with the 'getstack'
function.


Other help: prefs_cmd stack_cmd getstack_func
            »»»»»»»»»á»»»»»»»»» »»»»»»»»»»»»»
===
@Command: account_cmd
--------------------

   ACCount


This command enables stack checking and task accounting.
Note that only 64 tasks are checked. You can see the accounting
info in the 'task' list.

Other help: prefs_cmd stack_cmd
            »»»»»»»»» »»»»»»»»»
===
@Command: kill_cmd
-----------------

   Kill <task>|<crash node>


Cancel the specified task. This command works even if the task was
frozen.

Example:
   kill arp          when the current list is 'task' and 'arp' is an
                     abbreviation of a task or process
   kill 00C05063

If the task you want to kill has crashed, PowerVisor will also remove
the corresponding crash node. You can also kill a crashed task with a
pointer to the crash node instead of the task node.
Do not kill a debug task. Remove this with the 'debug' command.

Other help: crash debug_cmd debugging freeze_cmd
            »»»»»á»»»»»»»»»á»»»»»»»»» »»»»»»»»»»
===
@Command: freeze_cmd
-------------------

   FReeze <task>


Freeze a task. Remember that when you quit PowerVisor all frozen tasks
are lost.

Other help: kill_cmd unfreeze_cmd
            »»»»»»»»á»»»»»»»»»»»»
===
@Command: unfreeze_cmd
---------------------

   UNFreeze <task>


Unfreeze a task you have frozen.

Other help: freeze_cmd
            »»»»»»»»»»
===
@Command: addfunc_cmd
--------------------

   RC,<func node> <- ADdfunc (<libfuncname> | 'offs' <library> <offset>)
                     ['only' <task>] [<type> [<command>]]


This is a very powerfull command which enables you to monitor library
functions. I will explain this command with examples:

   loadfd exec fd:exec_lib.fd
                                 If you had not already done this
   addfunc openlibrary           Whenever some task uses the openlibrary
                                 function call, the usage count increments
                                 and the information for the last 8 tasks
                                 using this function is updated. (See
                                 'help info' and 'help syslists')
   addfunc putmsg led            Whenever a task uses the putmsg function
                                 the powerled switches its state.
   addfunc wait only trackdisk.device full
                                 Everytime 'trackdisk.device' uses the
                                 Wait function, the usage count is
                                 incremented. The registers used to
                                 call this function are also remembered.
   addfunc offs lib:exec -30     If you don't want to load the fd-file
                                 and you know the offset, you can use this
                                 construct.

You can find the usage counter in the list 'func'. Type 'func' to set
this list to the current one and type 'list'.

The following <type>s are available :

   none     Simply remember the 8 last tasks that called this function and
            update the usagecounter.
   LED      remember the 8 last tasks, update the usagecounter and blink
            the powerled.
   FULL     remember the 8 last tasks with their registers at the moment
            they called the function and update the usagecounter.
   FULLLED  remember the 8 last tasks with their registers at the moment
            they called the function, update the usagecounter and
            blink the powerled.
   EXEC     PowerVisor will call <command> everytime the function is called.
            The variable 'rc' will point to a copy of the function node.
            Warning ! Don't use this option for the following library
            functions :
               AllocSignal
               FreeSignal
               AllocMem
               FreeMem
               FindPort
               GetMsg
               PutMsg
               WaitPort
               PP_InitPortPrint
               PP_StopPortPrint
               PP_ExecCommand
            You can find the structure of the function node in the
            'The Wizard Corner' chapter.
   SCRATCH  After the library function is executed, PowerVisor will
            destroy the contents of 'd1', 'a0' and 'a1'. (They will
            contain the following values respectively : $BADBADD1,
            $BADBADA0, $BADBADA1)


Other help: remfunc_cmd libfuncs syslists list_cmd info_cmd func_list
            »»»»»»»»»»»á»»»»»»»»á»»»»»»»»á»»»»»»»»á»»»»»»»» »»»»»»»»»
===
@Command: remfunc_cmd
--------------------

   REMfunc <function monitor node>


Use this function to remove a patch you installed with 'addfunc'.
This function checks if you are removing patches of the same function
in the wrong order. You should always remove the most recent patch
first.
You can find the nodes for the function monitor in the 'func' list

Example:
   addfunc putmsg only 00C23516
   addfunc putmsg only 00C036D0 led
   ...
   remfunc 00C20AB2        assuming this is the one with 'led'
   remfunc putmsg          the other one.

Other help: addfunc_cmd syslists func_list
            »»»»»»»»»»» »»»»»»»» »»»»»»»»»
===
@Help crash
----------
PowerVisor traps crashes. These include 'task helds' and 'gurus'.

Note that a crashed task is not frozen but simply put to wait state.
Use the command 'kill' to cancel the task

You can debug a crashed task with 'debug t'.

When PowerVisor crashes, you get a warning. If this happens you should
try to find out why it happened. If this crash is reproducable and is not
caused by dangerous actions by you, you should write me a bug report.


Other help: kill_cmd remcrash_cmd debug_cmd
            »»»»»»»»á»»»»»»»»»»»» »»»»»»»»»
===
@Command: unasm_cmd
------------------

   Unasm [<start> [<instructions>]]


This command disassembles machinelanguage beginning at <start>.
<instructions> instructions are disassembled.
This command also shows symbols and breakpoints if there are any.

With no arguments this command continues the disassembly.

<instructions> is 20 by default.

Normally you will also see the hex data corresponding with the code.
You can disable this (and thus provide for longer labels in symbolic
disassembly) with the mode command (noshex).

Other help: debugging break_cmd mode_cmd view_cmd
            »»»»»»»»» »»»»»»»»» »»»»»»»» »»»»»»»»
===
@Command: libinfo_cmd
--------------------

   LIBInfo <library function name>


This command shows you the library, the offset and the register usage
for a library function. You must have loaded the corresponding fd-file
first.

Other help: libfuncs loadfd_cmd libfunc_cmd
            »»»»»»»»á»»»»»»»»»» »»»»»»»»»»»
===
@Command: libfunc_cmd
--------------------

   LIBFunc <library> <offset>


This command shows you the name of the library function corresponding
with a library and an offset (offset must be negative).
You must have loaded the corresponding fd-file first.
Only the 16 least significant bits of <offset> are used.

This command is the reverse of 'libinfo'.

This command returns a string if called from ARexx.

Other help: libfuncs loadfd_cmd libinfo_cmd
            »»»»»»»»á»»»»»»»»»» »»»»»»»»»»»
===
@Command: list_cmd
-----------------

   List [<list>]


With arguments this command lists the current list. With an argument
'list' lists <list> :-)

Other help: syslists
            »»»»»»»»
===
@Command: memory_cmd
-------------------

   Memory [<start> [<bytes>]]


This command shows memory beginning at <start>.
<bytes> bytes are shown.

With no arguments this command continues the memory list.

<bytes> is 20 lines for default.

Use the 'mode' command to install preferences for list memory:
   mode long         for longword grouping (default)
   mode byte         for byte grouping

Look at the 'view' command for a more powerful dump routine.

Other help: mode_cmd view_cmd lastmem_func
            »»»»»»»» »»»»»»»» »»»»»»»»»»»»
===
@Command: info_cmd
-----------------

   Info <object address> [<list>]


This command gives additional information about an object.
When this object is not in the current list you must specify the list
where this object belongs.
Note that the information this command gives will never be a BPTR. These
are automatically converted to APTR's.

Example:
   info task:track task
   info win:'test window' win
 or
   task
   info task:track
   info 'trackdisk.device'

Be cautious with this command. When you give wrong arguments to this
function you could crash the machine.

Other help: syslists list_cmd <list>_list
            »»»»»»»»á»»»»»»»» »»»»»»»»»»»
===
@Command: memtask_cmd
--------------------

   MEMTask <task>


Show memory for a task. This is the memory which is allocated via
AllocEntry and is attached to the task.

Other help: task_list
            »»»»»»»»»
===
@Command: remcrash_cmd
---------------------

   REMCrash <crash node>


When a task crashes, PowerVisor makes a crash node. You can find this
node in the Crsh list. You can remove this node with the remcrash command.
Note that this command will not remove the task. The task will simply be
left waiting for a signal that will never come.

Other help: crash
            »»»»»
===
@Command: loadfd_cmd
-------------------

   RC,<number of functions> <- LOADFd <library> <file-name>


This command loads a fd-file in memory. After you have loaded an fd-file
you can use the library functions defined in it.

Example:
   loadfd exec fd:exec_lib.fd

When a fd-file already exists, loadfd will do nothing.
The number of functions loaded is returned.
The pointer to the fd-file node is stored in the 'RC' variable.

Other help: libfuncs unloadfd_cmd
            »»»»»»»» »»»»»»»»»»»»
===
@Command: unlock_cmd
-------------------

   UNLOCk <pointer to a lock>


This command unlocks a lock. The pointer to the lock must be an APTR,
not a BPTR !

Other help: pathname_cmd
            »»»»»»»»»»»»
===
@Command: sync_cmd
-----------------

   SYNc


Use this command to synchronize PowerVisor with ARexx. Normally you can
execute an ARexx script (with 'rx') and while this script is executing
you can still use PowerVisor for other things. When you use this command,
PowerVisor will disable user input. Only ARexx commands are accepted.

Do not forget to 'async' in your ARexx script.

Other help: async_cmd rx_cmd
            »»»»»»»»»á»»»»»»
===
@Command: async_cmd
------------------

   ASYnc


Use this command to disable the synchronization enabled with 'sync'.

Other help: sync_cmd rx_cmd
            »»»»»»»»á»»»»»»
===
@Command: clip_cmd
-----------------

   [RC,<Pointer to data>] <- CLIp <Clip name> [<Pointer to data> <Length>]


Install a new ARexx clip in the system or return the pointer to the
string in the RexxArg for the given clip name.

Pointer to data (when you ask a clip) is returned in 'RC'.

Other help: remclip_cmd assign_cmd rx_cmd
            »»»»»»»»»»»á»»»»»»»»»»á»»»»»»
===
@Command: remclip_cmd
--------------------

   REMCLip <Clip name>


Remove an ARexx clip from the system.

Other help: clip_cmd assign_cmd rx_cmd
            »»»»»»»»á»»»»»»»»»»á»»»»»»
===
@Command: hide_cmd
-----------------

   HIde


Hide all output from commands issued from an ARexx script.
This is equivalent to using the '-' operator in front of a commandline
(when you are typing commands from PowerVisor).

Other help: unhide_cmd
            »»»»»»»»»»
===
@Command: unhide_cmd
-------------------

   UNHide


Unhide all output from commands issued from an ARexx script.

Other help: hide_cmd
            »»»»»»»»
===
@Command: front_cmd
------------------

   FROnt


Bring the PowerVisor screen to the front from within an ARexx script.
===
@Command: closewindow_cmd
------------------------

   CLOsewindow <window>


This command closes a window. The menu's are cleared. The DMRequest is
cleared. All requesters attached to this window are removed and the IDCMP
flags are set to zero.

Other help: closescreen_cmd
            »»»»»»»»»»»»»»»
===
@Command: hunks_cmd
------------------

   HUnks <process>


Show all the hunks for a process
===
@Command: attach_cmd
-------------------

   <attach node> <- ATtach <command string> <code> <qualifier>
                    [('e' | 'c') ['+']]


This command attaches a command to a key. You can use this command to
initialize your functionkeys. A command attached to a key is also
called a macro.

Example:
   attach 'list' 80 0
      attaches
         list
      to the <F1> key.
   attach 'info task:\'trackdisk.device\' task' 81 2 e
      attaches
         info task:'trackdisk.device' task
      to the <F2> key with the <right-shift> pressed
      and when you press the key, PowerVisor will not add the command
      to the history buffer.

Use remattach to remove an attached key

If you do not want the command to be feedbacked on your screen if you
press the assigned key, you may want to precede the commandline with a '~'.

Example:
   attach '~list' 80 0

or you can use the 'e' option for a similar effect.

Other help: remattach_cmd attc_list redirection
            »»»»»»»»»»»»» »»»»»»»»» »»»»»»»»»»»
===
@Command: remattach_cmd
----------------------

   REMAttach <attach node>


Remove a macro.

Example:
   attc                    Goto the attachement list
   list                    To see all the keys
Node     Code Qualifier Command
-----------------------------------------------------------------------------
00C184E0   81         2 'info task:'trackdisk.device' task                  '
00C34268   80         0 'list                                               '
   remattach 00c34268      To remove the 'list' key

Other help: attach_cmd list_cmd syslists attc_list
            »»»»»»»»»»á»»»»»»»»á»»»»»»»» »»»»»»»»»
===
@Command: closescreen_cmd
------------------------

   CLOSEScreen <screen>


This command closes a screen and all attached windows.

Other help: closewindow_cmd
            »»»»»»»»»»»»»»»
===
@Command: log_cmd
----------------

   LOG [<logical window> <filename>]


This command enables or disables the logging of all output in a logical window
to a file. PowerVisor only supports one log file. If you open one for a logical
window, PV will automatically close the other log file (if there is one).

You can disable (and close) command logging if you give no arguments to
this command.

Other help: redirection to_cmd
            »»»»»»»»»»» »»»»»»
===
@Command: to_cmd
---------------

   TO <file> <command>


Log the output of one command to a file. After the command has executed
restore the current log file.

Other help: log_cmd
            »»»»»»»
===
@Command: taskpri_cmd
--------------------

   TASKPri <task ptr> <priority>


Set the priority for a task.

Example:
   taskpri task:test -5
===
@Command: pathname_cmd
---------------------

   PAthname <lock>


This command prints the pathname for a lock. If <lock> does not point to
a lock, 'pathname' prints an error. Note that <lock> must be an APTR and
not a BPTR !

This command returns a string if used from ARexx.

Other help: unlock_cmd
            »»»»»»»»»»
===
@Command: unloadfd_cmd
---------------------

   UNLoadfd <fd-file node>


Remove all functiondefinitions in a fd-file. You can find the
nodes for fd-files in the 'FDFi' list.
After this command you cannot use the library functions from this
fd-files anymore.

Other help: syslists loadfd_cmd libfuncs
            »»»»»»»»á»»»»»»»»»» »»»»»»»»
===
@Command: script_cmd
-------------------

   <result> <- SCRIpt <script file> [<commandline>]


The 'script' command executes the <script file>.
PowerVisor will first search the file in the current directory and than
in the s:pv subdirectory which is the recommended place for scripts.
You can use comments in script files by preceding the line with ';'.

You can also execute machinelanguage scripts with this command.
See the 'Scripts' tutorial file for more info about ML-scripts.

Other help: go_cmd resident_cmd unresident_cmd
            »»»»»» »»»»»»»»»»»»á»»»»»»»»»»»»»»
===
@Command: resident_cmd
---------------------

   RC,<Pointer to code> <- RESIdent [<filename>]


The 'resident' command loads a given file (with 'LoadSeg') and stores a
pointer to the start of the program in 'RC'. You can use this pointer
with the 'go' command.

You can make ML-scripts resident but you must make sure that the
routines are pure.

If you give no argument to 'resident' you will get a list with all
loaded code pointers.

This command returns the pointer to the code in 'RC'.

Other help: unresident_cmd script_cmd go_cmd
            »»»»»»»»»»»»»»á»»»»»»»»»»á»»»»»»
===
@Command: unresident_cmd
-----------------------

   UNResident <Pointer to code>


Unload a file loaded with 'resident'. All resident files are automatically
unloaded when PowerVisor quits.

Other help: resident_cmd script_cmd go_cmd
            »»»»»»»»»»»»á»»»»»»»»»»á»»»»»»
===
@Help general
------------
You can type one of the following for more information on a specific
item:

      help snap            for the screen snap feature
      help keys            for information about keys
      help input           for info about the input editing possibilities
      help redirection     for redirection to a file
      help files           for all the files PowerVisor uses
      help historybuf      the history buffer
      help portprint       for the portprint facility
      help autodefault     for the automatic default feature
      help templates       for the template feature
===
@Help templates
--------------
If you are not sure about the syntax for a command you can ask the
command template.


Examples :

   list?
   List [<list>]

   tr ?
   TRace [ 'n' <number> | 'b' | 'r' <register> | 'u'['t'] <address>
         | 'o'['t'] | 'c' <condition> | 's' | 'g'['t'] | 'h' | 'f'
         | 't' | 'j' ]

   openlw ?
   RC,<lwin> <- OPENLw <physical window> <logwin name> <cols> <rows>
                [<brother> <where> [<number of columns or lines>]]



To use this feature you must have PowerVisor-help and PowerVisor-ctrl
in your s: directory.
You can also show the template with the 'help' command :

   help list_tmp


The third example ('openlw ?') is a bit special. The '<-' arrow indicates
that the command returns something. In this case the command returns
something to the 'RC' variable and also to the command caller. If you want
to see the result of a command (without looking at the 'RC' variable) you
must use the group operator :

   result={openlw ...}
===
@Help files
----------
PowerVisor uses the following files:

      PowerVisor-startup (*)
          script file with all the initialization commands you find
          useful. This file is not necessary.
      PowerVisor-menus (*)
          This file is only used by the AmigaDOS 2.0 version of
          PowerVisor. It contains the description of all menus
          used in PowerVisor. This file is not really needed, but
          you won't have any menus if you don't have this file
      PowerVisor-help (*)
          This is the help file. If this file does not exist, you have no
          online help.
          You can change the help file if you like. After you have changed
          it you must type:
              'makehelp PowerVisor-help PowerVisor-ctrl word 2'
          to update the PowerVisor-ctrl file.
      PowerVisor-ctrl (*)
          This is the control file for the help file. Without this file
          you have no online help. See the QuickHelp manual for more
          details about this help format.
      PowerVisor-errors (*)
          This file contains all errormessages. When this file is not
          available PowerVisor will print errornumbers rather than messages.
          You can change this file. Please make sure that each line in this
          file is 70 bytes long (return included).
      s:PowerVisor-config
          This file contains config information for PowerVisor. All things
          you can install with the 'mode' and 'prefs' commands are in this
          file. If this file is not present, default values are used.
      libs:powervisor.library
          This is the portprint library. PowerVisor needs this library.
      s:pv/
          This subdirectory is the prefered subdirectory for scripts
          and structure definition files.

PowerVisor will search all filenames ending with (*) in the following
subdirectories :

      PROGDIR: (only for AmigaDOS 2.0) This is the subdirectory where
               the PowerVisor executable is located. If you have AmigaDOS 2.0
               this is the recommended place for the (*) files
      S:       If you have AmigaDOS 1.3 or earlier, this is the recommended
               place for the (*) files
      current  If the above failed, PowerVisor will look in the current
               directory
===
@Screen snap feature
-------------------
When you press the leftmousebutton PowerVisor will copy the word under
the mousepointer to the commandline.

Example:
   Let's say you want to list some information for a task
   You type:
      task                 to go to the current list 'task'
      list                 list all tasks
      memory input         to list the memory for the input device
                           task
   Let's say you want to continue the memory list at the second longword
   on your screen (in the memory list).
   Simply take your mouse and click on the longword you want.
   It will appear in the commandline.

Other help: mode_cmd
            »»»»»»»»
===
@Help keys information
---------------------
You can interrupt a command at any time by pressing <Esc>.

When you want PowerVisor to appear. Simply press the hotkey
<Right-Alt>+<Right-Shift>+'/' (the key at the left of the <right-shift>)
to bring the PowerVisor screen in front of all other screens. This is
also the key to return from 'hold' mode (see the 'hold' command).

If your last command was a memory list (with 'memory' or 'view') or a
disassembly (with 'unasm') you can press <enter> to continue this listing.

Using the <Left-Alt> key in combination with the numeric keypad you can
scroll the logical window. With the <Tab> key you can select the logical
window to scroll (this is called the active logical window).

Using the <Ctrl> key in combination with the numeric keypad you can scroll
in the debug logical window.

To pause the output of PowerVisor use the <Right-Alt>+<Help> key.


Note that almost all these keys can be changed with the 'prefs' command.
For example, you could prefer <ctrl>-'C' instead of <Esc>.


Other help: hold_cmd memory_cmd unasm_cmd prefs_cmd
            »»»»»»»» »»»»»»»»»»á»»»»»»»»» »»»»»»»»»
===
@Help input editing capabilities
-------------------------------
PowerVisors editing field is a stringgadget. You can use all editing
possibilities you have in any other stringgadget. In addition you
can use the 'snap' facility.
You can also use the 'history' facility.
The stringgadget is 400 chars long (default).

Other help: historybuf variables snap prefs_cmd
            »»»»»»»»»»á»»»»»»»»»á»»»» »»»»»»»»»
===
@Help redirection
----------------
You can redirect the output of a command to a file.

Example:
      log ram:outputfile
      list libs
      unasm $1000 50
      log

or to nil.

Example:
      -list
      (is useful when you log output to a file for example)

If you want no feedback you can use :

      ~list
      (This ~ operator is useful when you want to attach a command to
      a key for example)

Or no output and no feedback :

      ~-list      (Note ! don't change the order or it won't work)

If you only want to redirect one command you can use the 'to' command :

      to file list task

      or

      to file -list task

Other help: log_cmd attach_cmd to_cmd
            »»»»»»» »»»»»»»»»» »»»»»»
===
@Help historybuf
---------------
PowerVisor has a history buffer (like ConMan or Shell).
The default number of lines for this history buffer is 20. You can specify
another number with:
   prefs history <lines>
lines must be between 2 and 1000.

Starting with PowerVisor V1.10 the history buffer behaves exactly like
the history buffer in the AmigaDOS 2.0 shell (except for the search
history feature, but this is provided in the standard s:PowerVisor-startup
file).

Use the <up> key to go to the previous command. Use the <down> key to go
back.

Other help: variables prefs_cmd
            »»»»»»»»» »»»»»»»»»
===
@Help portprint
--------------
When you have the powervisor.library installed in your libs: directory
you can use the portprint facility.

Simply open the powervisor.library in your program and use the correct
functions.

Look at 'pptest.asm' for an example.

   PP_InitPortPrint()
      This function initializes the msgport for you. You need only
      do this once. The result you get in d0 is the pointer to the
      replyport (or null if no success). Use this pointer in all
      following commands.
   PP_StopPortPrint(a0)
      Clear the msgports for portprint. You need only do this once.
      a0 is the pointer to the replyport (the result from InitPortPrint).
   PP_ExecCommand(a0,a1,a2,d0)
      This routine is provided for the use of the 'addfunc' command, but
      you are free to use it for your own purposes.
      a0 is the pointer to the replyport. a1 is a pointer to data (may
      be 0), a2 is a pointer to a commandstring that you want to execute.
      d0 is the size of the data (may be 0). When you call this routine
      PowerVisor will first make a copy of your data. PowerVisor will
      then execute the command (note ! PowerVisor will execute it, the
      calling task will only wait until PowerVisor is ready). The command
      that is executed will get the pointer to the copy of the data in
      the 'rc' variable. You can return a result from this command (using
      the 'void' command for example). This result will be returned in
      d0.
   PP_DumpRegs(a0)
      Dump all registers on the PowerVisor screen.
      a0 is the pointer to the replyport.
   PP_Print(a0,a1)
      Print one line of text on the PowerVisor screen.
      a0 is the pointer to the replyport.
      a1 is the pointer to the text to print.
   PP_PrintNum(a0,d0)
      Print a number on the PowerVisor screen.
      a0 is the pointer to the replyport.
      d0 is the number to print.
===
@Help group_op
-------------
You can use the group operator to group several commands together for
sequential execution.

There are two possible forms:

   - As a command:
       {a=1000;b=2000;disp a*b}
     will execute a=1000, b=2000 and disp a*b in that order.

   - As an expression:
       disp {a=1000;b=2000;void a*b}+1
     will execute a=1000, b=2000 and void a*b in that order. Because
     'void' is the last command, the result from this command is taken
     as the result of the group operator. In this case this is 2000000.
     So the result on screen will be 2000001.

Other help: expressions disp_cmd void_cmd
            »»»»»»»»»»» »»»»»»»» »»»»»»»»
===
@Help special_op
---------------
The special '@' operator is used for the registers of the current debug
task.

   When you are debugging a task you can display a register for this task
   with
      disp @d4
   or
      disp @pc
   or
      disp @sp
   or
      disp @a0

   You can also change registers
   with
      @d0=4


Other help: variables expressions debugging assignment_op
            »»»»»»»»»á»»»»»»»»»»»á»»»»»»»»» »»»»»»»»»»»»»
===
@Help autodefault
----------------
There are a lot of commands that expect arguments that quite often
reside in some list. Most of these commands only expect one type
of list. For these commands PowerVisor implements the autodefault
feature. Normally when you type a string as an integer argument,
this string will be interpretated as a member of the current list.
However, when a command uses autodefault, it can set it's own default
list. For example, the CloseWindow command should only be used
on windows. Therefore you can always use CloseWindow as if 'wins'
is the current list. Simply type closewindow with the title of
the window regardless of the current list.
If it should happen that you really want to closewindow something
else (you never know), you can always specify the list using the
list operator.

Here are some of the commands that use this feature and their current list
they use:
   RemFunc        : func
   LoadFd         : libs
   AddFunc        : libs
   UnloadFd       : fdfi
   RemCrash       : crsh
   Freeze         : task
   UnFreeze       : task
   Kill           : task
   TaskPri        : task
   Hunks          : task
   CurDir         : task
   RemStruct      : stru
   Interprete     : stru
   Peek           : stru
   APeek          : stru
   DUse           : dbug
   RemAttach      : attc
   Gadgets        : wins
   CloseWindow    : wins
   CloseScreen    : scrs
   RemHand        : ihan
   RemRes         : resm
   LINES          : lwin
   COLS           : lwin
   GETCOL         : lwin
   GETROW         : lwin
   SetFont        : lwin
   ColRow         : lwin
   ...

Other help: list_op syslists
            »»»»»»» »»»»»»»»
===
@Help debugging
--------------
PowerVisor has powerfull debugging features.
You can debug multiple tasks at the same time.

The following commands are available:

   debug          to control the debug tasks
   trace          to trace execution
   duse           to set a new debug task
   dscroll        scroll the debug logical window
   dstart         set the start address of the debug logical window
   drefresh       refresh the debug display
   break          set breakpoints
   symbol         control symboltable
   source         control source

You can find the debug nodes in the 'dbug' list.

Also look at the 'prefs' command. You can install preferences for
the debug display.

Note: It is possible to set breakpoints in a program BEFORE PowerVisor
is started. These are not real breakpoints in the strict sense. When
you include an ILLEGAL instruction in your program PowerVisor will trap
the crash (if PowerVisor is running of course). Using 'debug t' with
the crashnode or tasknode you can then resume debugging starting at
that point. Make sure that 'mode patch' is installed to get consistent
results. If 'mode nopatch' is used PowerVisor will trap the crash too
late (before the guru in fact).

Other help: debug_cmd trace_cmd duse_cmd syslists source_cmd
            »»»»»»»»»á»»»»»»»»»á»»»»»»»»á»»»»»»»» »»»»»»»»»»
            break_cmd symbol_cmd getdebug_func dscroll_cmd dstart_cmd
            »»»»»»»»» »»»»»»»»»» »»»»»»»»»»»»» »»»»»»»»»»»á»»»»»»»»»»
            prefs_cmd
            »»»»»»»»»
===
@Command: dscroll_cmd
--------------------

   DScroll <offset>


Scroll <offset> bytes up in the full screen debugger. You can only use this
command when the 'debug' logical window is open (with 'dwin'). <offset>
can be negative.

Other help: debug_cmd dwin_cmd dstart_cmd toppc_func botpc_func
            »»»»»»»»»á»»»»»»»» »»»»»»»»»» »»»»»»»»»»á»»»»»»»»»»
===
@Command: dstart_cmd
-------------------

   DSTart <address>


Set the start of the debug logical window. You can only use this
command when the 'debug' logical window is open (with 'dwin').

Other help: debug_cmd dwin_cmd dscroll_cmd toppc_func botpc_func
            »»»»»»»»»á»»»»»»»» »»»»»»»»»»» »»»»»»»»»»á»»»»»»»»»»
===
@Function: toppc_func
--------------------

   TOPPC( )


This function returns the program counter visible at the top of the 'debug'
logical window.
You can set this program counter using the 'dstart' or 'dscroll' commands.

Other help: dscroll_cmd dstart_cmd botpc_func dwin_cmd
            »»»»»»»»»»»á»»»»»»»»»»á»»»»»»»»»» »»»»»»»»
===
@Function: botpc_func
--------------------

   BOTPC( )


This function returns the program counter visible at the bottom of the
'debug' logical window.
You can set this program counter using the 'dstart' or 'dscroll' commands.

Other help: dscroll_cmd dstart_cmd toppc_func dwin_cmd
            »»»»»»»»»»»á»»»»»»»»»»á»»»»»»»»»» »»»»»»»»
===
@Command: debug_cmd
------------------

   RC <- DEBug 'n' | 'c' | 'l' <filename> | 't' <task node> | ('r'|'f'|'u')
                [<debug node>] | 'd' <name>


Use this command to control the debug tasks.

   debug n     Waits for the next 'LoadSeg' and make a debugtask from that
               process.
   debug c     Waits for the next 'AddTask' and make a debugtask from that
               task.
   debug l <filename>
               Load an executable program to debug.
               Symbols are automatically loaded if they exist.
               Warning ! If you use the AmigaDOS 1.3 version, PowerVisor
               will NOT create a CLI for the loaded program. Therefore
               it is better to use 'debug n' if possible. In AmigaDOS 2.0
               the CLI structure is properly allocated (using
               'CreateNewProc')
   debug t <task node>
               Take an existing running task to debug.
               You can also take a crash node to debug. In that case
               you can singlestep the task from where it crashed.
   debug f     Remove the current debugnode and freeze the task
   debug f <debug node>
               Remove the specified debugnode and freeze
               This command is mostly used when 'debug n' or 'debug t' was
               used to start the debugging.
   debug r     Remove the current debugnode.
               The task will simply continue executing from where it
               was interrupted.
               This command is mostly used when 'debug n', 'debug c' or
               'debug t' was used to start the debugging
               If you have AmigaDOS 2.0 you may also use 'debug r' with
               'debug l'
   debug r <debug node>
               Remove the specified debugnode.
   debug u     Remove the current debugnode.
               The task will be stopped ('RemTask') and the program will
               be unloaded (UnLoadSeg) if the debug task was loaded with
               'debug l'. This command is mostly used when 'debug l' was
               used
               If you have AmigaDOS 2.0 you may also use 'debug u' with
               'debug n'
   debug u <debug node>
               Remove the specified debugnode.
   debug d <name>
               Create dummy debugnode for symbols only.

When a new debug task is created, it is taken from the task list
and put in the 'dbug' list. The current debug task is set to the
new debug task.

Other help: debugging duse_cmd trace_cmd break_cmd
            »»»»»»»»»á»»»»»»»»á»»»»»»»»»á»»»»»»»»»
            symbol_cmd dbug_list
            »»»»»»»»»» »»»»»»»»»
===
@Command: drefresh_cmd
---------------------

   DRefresh


This command refreshes the debug display.

Other help: debugging debug_cmd duse_cmd
            »»»»»»»»» »»»»»»»»»á»»»»»»»»á
===
@Command: duse_cmd
-----------------

   DUse <debug node>


Set the current debug task.
Use the debug function to determine the current debug node.

Other help: debugging debug_cmd trace_cmd
            »»»»»»»»»á»»»»»»»»»á»»»»»»»»»á
            break_cmd getdebug_func symbol_cmd drefresh_cmd with_cmd
            »»»»»»»»» »»»»»»»»»»»»» »»»»»»»»»» »»»»»»»»»»»» »»»»»»»»
===
@Command: with_cmd
-----------------

   WITh <debug node> <command>


This command temporarily sets another current debug task and executes
<command>. This is useful if you want to view memory with another set
of symbols.

Example:

   with MyBuggyProgram memory 070540

Other help: debugging debug_cmd trace_cmd
            »»»»»»»»»á»»»»»»»»»á»»»»»»»»»á
            break_cmd getdebug_func symbol_cmd drefresh_cmd duse_cmd
            »»»»»»»»» »»»»»»»»»»»»» »»»»»»»»»» »»»»»»»»»»»» »»»»»»»»
===
@Function: getdebug_func
-----------------------

   GETDEBUG( )


Return the current debug node.

Other help: duse_cmd with_cmd dbug_list
            »»»»»»»» »»»»»»»» »»»»»»»»»
===
@Command: trace_cmd
------------------

   TRace [ 'n' <number> | 'b' | 'r' <register> | 'u'['t'] <address>
         | 'o'['t'] | 'c' <condition> | 's' | 'g'['t'] | 'h' | 'f'
         | 't' | 'j' ]

Use this command to singlestep a program (Use 'debug' first to make
a debug task).

   trace                   Trace one instruction.
   trace n <number>        Trace <number> instructions. Tracing is done
                           in singlestep mode.
   trace b                 Trace until the next branch (singlestep mode).
   trace t                 Skip BSR or JSR. If not a BSR or JSR simple
                           trace is used. This function works in ROM.
                           Execute mode is used.
   trace j                 Trace until use of library ROM function:
                           JSR or JMP (a6).
                           Tracing is done in singlestep mode.
   trace r <register>      Trace until a specified register is changed
                           (singlestep mode).
                           register can be d0-d7, a0-a6 or sp.
   trace u <address>       Trace until the programcounter is equal to
                           <address>. Tracing is done in execute mode.
   trace ut <address>      Same as above but use singlestep mode instead.
   trace o                 Trace over the current instruction. Tracing
                           is done in execute mode.
   trace ot                Same as above but use singlestep mode instead.
   trace c <condition>     Trace until a condition is satisfied. This
                           condition is a string. Example:
                           trace c '@d1==@d2' will trace until register
                           d1 is equal to register d2. Tracing is done
                           in singlestep mode.
   trace s                 Skip an instruction
   trace i                 Do not trace. Simply show the current registers
                           and instructions.
   trace g                 Execute until a breakpoint is encountered
   trace gt                Same as above but tracing is done in singlestep
                           mode.
   trace h                 Interrupt the tracing or executing of the
                           current debug task.
   trace f                 Interrupt the tracing or executing of the
                           current debug task as soon as this task is
                           in ready state.

Other help: debugging debug_cmd duse_cmd break_cmd
            »»»»»»»»»á»»»»»»»»»á»»»»»»»»á»»»»»»»»»
            symbol_cmd
            »»»»»»»»»»
===
@Command: break_cmd
------------------

   RC <- Break ('a'|'c'|'n'|'t'|'p'|'r') <address> [<condition>|<timeout>]


Install a breakpoint for the current debugtask.

   break a <address> <timeout>   Breakpoint only breaks after the <timeout>
                                 counter becomes zero.
   break c <address> <condition> Only break if the condition is true.
   break n <address>             Normal breakpoint.
   break t <address>             Temporary breakpoint.
   break p <address>             Profiler breakpoint. Does not break. Only
                                 increments a counter.
   break r <breakpoint number>   Remove a breakpoint.

Examples:
   break c 00c05320 '(@d0<@d1)&&(@pc>00c05380)'

      This breakpoint will cause a break if d0 is lower than d1 and
      the programcounter is greater than 00c05380 (a bit stupid to
      include the programcounter in such an expression because the
      breakpoint is on a fixed position :-)

Other help: debugging debug_cmd duse_cmd
            »»»»»»»»»á»»»»»»»»»á»»»»»»»»
            break_cmd trace_cmd symbol_cmd
            »»»»»»»»»á»»»»»»»»» »»»»»»»»»»
===
@Command: source_cmd
-------------------

   SOurce 'l' <filename> [<hunkaddress>] | 'w' <address> | 's' |
          't' <tab size> | 'r' | 'c' | 'g' <line>


Control the source for the current debugtask. Note that the source
for the current debug task is always displayed in the 'Source' logical
window. You must compile or assemble your program with debug hunk
information if you want to use this feature. PowerVisor currently
understands the debug hunk format used by 'Macro68' (include the 'debug'
statement in your source) and by 'SAS/C' (compile with '-d1', do not
use any number other than 1!). This format is also compatible with the
debug hunk format used by Devpac3. The 'source' command could work for
other compilers too but this is not tested.

   source l <filename> [<hunkaddress>]
               Load the source for the current debug task.
               If you give <hunkaddress>, PowerVisor will load the source
               for the given hunks. This is extremely useful when you have
               created a dummy debug task.
               Note that <hunkaddress> is 4 more than the number given in
               the hunklist with the 'hunks' command.
               Note that <hunkaddress> is not optional when you are loading
               the source for a dummy debug task
   source w <address>
               Use this command to see in which source file and on which
               line a specific address is located
   source t <tab size>
               Set the tab size used for the source display. The default
               tab value is 8
   source s
               Show all sources for the current debug task
   source r
               Redisplay the sourcein the 'Source' logical window
   source c
               Clear all sources and unload them
   source g <line>
               Goto a line in the current loaded source. Note that you can
               also scroll in the current file with the mouse. Simply press
               the left mouse button in the first or the last line of the
               'Source' logical window



Other help: debugging debug_cmd trace_cmd duse_cmd
            »»»»»»»»»á»»»»»»»»»á»»»»»»»»»á»»»»»»»»á
            break_cmd trace_cmd symbol_cmd
            »»»»»»»»»á»»»»»»»»» »»»»»»»»»»
===
@Command: symbol_cmd
-------------------

   SYmbol 'l' <filename> [<hunkaddress>] | 'c' | 'a' <symbol> <value> |
          'r' <symbol> | 's'


Control the symboltable for the current debugtask.

   symbol l <filename> [<hunkaddress>]
               Load the symbols for the current debug task.
               If you give <hunkaddress>, PowerVisor will load the symbols
               for the given hunks. This is extremely useful when you have
               created a dummy debug task.
               Note that <hunkaddress> is 4 more than the number given in
               the hunklist with the 'hunks' command.
               Note that <hunkaddress> is not optional when you are loading
               symbols for a dummy debug task.
   symbol c    Clear all the symbols for the current debug task.
   symbol a <symbol> <value>
               Add a symbol with a specified value the the symbol list
               for the current debug task.
   symbol r <symbol>
               Remove a symbol from the symbol list for the current
               debug task.
   symbol s    List all symbols for the current debug task.

Other help: debugging debug_cmd trace_cmd duse_cmd
            »»»»»»»»»á»»»»»»»»»á»»»»»»»»»á»»»»»»»»á
            break_cmd trace_cmd source_cmd
            »»»»»»»»»á»»»»»»»»» »»»»»»»»»»
===
@Command: rblock_cmd
-------------------

   RC,<address> <- RBlock <Unit number> <block number> [<address>]


Read a block from a disk. This command will allocate the memory for it
if you do not specify <address>. The pointer to this memory will be
stored in RC. You can read a block in your own memory if you specify
the address. This address must be in chip ram.
You can free the memory this command allocated with 'free'.

When you let 'rblock' allocate the memory for you you can also free
this memory with 'cleanup'. It will also be cleaned up when you
quit PowerVisor.


Other help: wblock_cmd alloc_func free_func variables cleanup_cmd
            »»»»»»»»»»á»»»»»»»»»» »»»»»»»»»á»»»»»»»»» »»»»»»»»»»»
===
@Function: base_func
-------------------

   BASE()


This function returns the ptr to the first element in the current list.

Example:
> task           ;Goto the task list
> list           ;To get the following output:
Task node name      : Node     Pri StackPtr  StackS Stat Command         Acc
-----------------------------------------------------------------------------
RAM                 : 00C20C68 00  00C2117A    1200 Rdy             PROC -
golem.device        : 00C05C8A 05  00C064B6    2048 Wait            TASK -
NEWCON              : 00C2CAA8 05  00C2DAA2    4000 Wait            PROC -
ARP Shell Process   : 00C26180 00  00C270F2    4000 Wait            (03) -
PowerVisor1.0.task  : 00C31C28 00  00C76132    1024 Wait            TASK -
File System         : 00C16758 0A  00C16AF6     840 Wait            PROC -
File System         : 00C172E8 0A  00C17686     840 Wait            PROC -
trackdisk.device    : 00C068DE 05  00C09F2E     512 Wait            TASK -
trackdisk.device    : 00C17846 05  00C17A5E     512 Wait            TASK -
DH0                 : 00C0DF08 0A  00C0E356    1000 Wait            PROC -
input.device        : 00C03BFA 14  00C04C00    4096 Wait            TASK -
ARP Background She  : 00C66EB8 00  00C75CD2    4000 Run  pv         (01) -
> d base()       ;And you get:
00C20C68,12717160

Other help: list_cmd lists
            »»»»»»»»á»»»»»
===
@Command: void_cmd
-----------------

   <result> <- Void {<argument>...}


This command does absolutely nothing except evaluating it's arguments.
You can use this command to execute library functions. It is also useful
to return a result from a command group. And finaly you can use it to
copy a PowerVisor variable to ARexx.

Other help: arguments integers expressions disp_cmd
            »»»»»»»»»á»»»»»»»» »»»»»»»»»»» »»»»»»»»
===
@Command: wblock_cmd
-------------------

   WBlock <Unit number> <block number> <address>


Write a block to disk. <address> must be in chip ram.
A block is 1024 bytes big.

Other help: rblock_cmd
            »»»»»»»»»»
===
@Command: opendev_cmd
--------------------

   RC,<pvdevice> <- Opendev <device name> [<unit> [<flags>]]


Open a device for use with the 'closedev','devinfo' and 'devcmd' commands.
The result (in RC) is a pointer to a block containing the pointer to the
port and the pointer to the IORequest (256 bytes big) in that order.
Use this block as the argument to 'closedev','devinfo' and 'devcmd'.

Example:
   opendev "trackdisk.device"
   dev=rc
   devcmd dev 9 0 1              ;Put the drive motor on
   ...
   devcmd dev 9 0 0              ;Off again
   devinfo dev
   closedev dev

The first two lines in this example could also be written as:

   dev={opendev "trackdisk.device"}


Other help: closedev_cmd devcmd_cmd devinfo_cmd group_op
            »»»»»»»»»»»»á»»»»»»»»»»á»»»»»»»»»»» »»»»»»»»
===
@Command: closedev_cmd
---------------------

   CLOSEDev <device block>


Close a device opened with 'opendev'.

Other help: opendev_cmd devcmd_cmd devinfo_cmd
            »»»»»»»»»»»á»»»»»»»»»»á»»»»»»»»»»»
===
@Command: devinfo_cmd
--------------------

   DEVInfo <device block>


Show port and iorequest information for a device opened with 'opendev'.

Other help: opendev_cmd closedev_cmd devcmd_cmd
            »»»»»»»»»»»á»»»»»»»»»»»» »»»»»»»»»»
===
@Command: devcmd_cmd
-------------------

   RC <- DEVCmd <dev> <command> [<flags> [<length> [<data> [<offset>]]]]


Give a command to a device opened with 'opendev'. The parameters specified
are for the IORequest. If you do not specify these parameters ('flags',...)
the IORequest will remain unchanged.

Other help: opendev_cmd closedev_cmd devinfo_cmd
            »»»»»»»»»»»á»»»»»»»»»»»»á»»»»»»»»»»»
===
@Command: remhand_cmd
--------------------

   REMHand <input handler>


Remove an input handler. You can list the inputhandlers in the 'IHan' list.

Other help: syslists
            »»»»»»»»
===
@Command: go_cmd
---------------

   <result> <- GO <address> [<commandline>]


Start executing at <address>.
You can make inline code with this command.
The register are preset to certain values (see the 'script' command).

Example:
   go "Nu"  does nothing because "Nu" is a 'RTS'.

Other help: script_cmd pvcall_cmd
            »»»»»»»»»» »»»»»»»»»»
===
@Lists: exec_list
----------------

   Exec

This is the listing of the ExecBase.
You can use the listaddress operator to change values in this list.
'Info' is not possible.
There is more info in DOS 2.0.

Other help: syslists info_cmd list_cmd base()
            »»»»»»»» »»»»»»»» »»»»»»»» »»»»»»
===
@Lists: intb_list
----------------

   Intb

This is the listing of the IntuitionBase.
You can use the listaddress operator to change values in this list.
'Info' is not possible.

Other help: syslists info_cmd list_cmd base()
            »»»»»»»» »»»»»»»» »»»»»»»» »»»»»»
===
@Lists: graf_list
----------------

   Graf

This is the listing of the Graphics base.
You can use the listaddress operator to change values in this list.
'Info' is not possible.
There is more info in DOS 2.0.

Other help: syslists info_cmd list_cmd base()
            »»»»»»»» »»»»»»»» »»»»»»»» »»»»»»
===
@Lists: task_list
----------------

   Task

This is the listing of all the current tasks and processes.
The listaddress operator is not available.

Simple information ('list'):
   Task node name    : name for this task or process
   Node              : pointer to this node
   Pri               : task priority
   StackPtr          : SP register for task
   StackS            : stacksize
   Stat              : task state: (wait,rdy,run,cold,...)
   Command           : command if process is a cli followed by
                       an indication 'TASK', 'PROC' or cli number
   Acc               : accounting info if account is enabled

Expanded information ('info'):
   If task: listing of task structure
   if process: listing of task structure and process structure
   if cli: listing of task, process and cli structure

There is more info in DOS 2.0 (for Process).

Other help: syslists info_cmd list_cmd base()
            »»»»»»»» »»»»»»»» »»»»»»»» »»»»»»
===
@Lists: libs_list
----------------

   Libs

This is the listing of all the available libraries.
The listaddress operator is not available.

Simple information ('list'):
   Library node name : name for this library
   Node              : pointer to this node
   Pri               : library priority
   NegSize           : negative library size
   PosSize           : postive library size
   Sum               : checksum
   OpenCnt           : library usage count

Expanded information ('info'):
   You get the idstring, version and revision of this library.

Other help: syslists info_cmd list_cmd base()
            »»»»»»»» »»»»»»»» »»»»»»»» »»»»»»
===
@Lists: devs_list
----------------

   Devs

This is the listing of all the available devices.
The listaddress operator is not available.

Simple information ('list'):
   Device node name  : name for this device
   Node              : pointer to this node
   Pri               : device priority
   NegSize           : negative device size
   PosSize           : postive device size
   Sum               : checksum
   OpenCnt           : device usage count

Expanded information ('info'):
   You get the idstring, version and revision of this device.

Other help: syslists info_cmd list_cmd base()
            »»»»»»»» »»»»»»»» »»»»»»»» »»»»»»
===
@Lists: reso_list
----------------

   Reso

This is the listing of all the available resources.
The listaddress operator is not available.

Simple information ('list'):
   Resource node name: name for this resource
   Node              : pointer to this node
   Pri               : resource priority
   NegSize           : negative resource size
   PosSize           : postive resource size
   Sum               : checksum
   OpenCnt           : resource usage count

Expanded information ('info'):
   You get the idstring, version and revision of this resource.

Other help: syslists info_cmd list_cmd base()
            »»»»»»»» »»»»»»»» »»»»»»»» »»»»»»
===
@Lists: memr_list
----------------

   Memr

This is the listing of all the available memory lists.
The listaddress operator is not available.

Simple information ('list'):
   Memory node name  : name for this memorylist
   Node              : pointer to this node
   Pri               : memory priority
   Attr              : attributes needed with AllocMem
   First             : first free memory chunk
   Lower             : lower memory
   Upper             : upper memory
   Free              : free memory

Expanded information ('info'):
   For each free memoryblock you get the pointer and the size.

Other help: syslists info_cmd list_cmd base()
            »»»»»»»» »»»»»»»» »»»»»»»» »»»»»»
===
@Lists: intr_list
----------------

   INTR

This is the listing of all the available interrupts.
The listaddress operator is not available.

Simple information ('list'):
   Interrupt node name : name for this interrupt
   Node                : pointer to this node
   Pri                 : interrupt priority
   Data                : pointer to data
   Code                : pointer to code

Expanded information ('info'):
   ?

Other help: syslists info_cmd list_cmd base()
            »»»»»»»» »»»»»»»» »»»»»»»» »»»»»»
===
@Lists: port_list
----------------

   Port

This is the listing of all the available message ports.
The listaddress operator is not available.

Simple information ('list'):
   MsgPort node name : name for this MsgPort
   Node              : pointer to this node
   Pri               : port priority
   SigBit            : signal bit
   SigTask           : task to signal

Expanded information ('info'):
   No more information (in future I will list all pending messages).

Other help: syslists info_cmd list_cmd base()
            »»»»»»»» »»»»»»»» »»»»»»»» »»»»»»
===
@Lists: wins_list
----------------

   Wins

This is the listing of all the available windows on all screens.
The listaddress operator is not available.

Simple information ('list'):
   Window name       : window title
   Address           : pointer to this window
   Left              : leftedge
   Top               : topedge
   Width             : width
   Height            : height
   WScreen           : window screen

Expanded information ('info'):
   A listing of the window structure.

There is more info in DOS2.0.

Other help: syslists info_cmd list_cmd base()
            »»»»»»»» »»»»»»»» »»»»»»»» »»»»»»
===
@Lists: scrs_list
----------------

   Scrs

This is the listing of all the available screens.
The listaddress operator is not available.

Simple information ('list'):
   Screen name       : screen title
   Address           : pointer to this screen
   Left              : leftedge
   Top               : topedge
   Width             : width
   Height            : height
   FirstWindow       : first window

Expanded information ('info'):
   A listing of the screen structure.

There is more info in DOS2.0.

Other help: syslists info_cmd list_cmd base()
            »»»»»»»» »»»»»»»» »»»»»»»» »»»»»»
===
@Lists: font_list
----------------

   Font

This is the listing of all the available fonts.
The listaddress operator is not available.

Simple information ('list'):
   Font node name    : font name
   Node              : pointer to this node
   Pri               : font priority
   YSize             : y size
   XSize             : x size
   Style             : style flags
   LoChar            : lowest defined character
   HiChar            : highest defined character

Expanded information ('info'):
   A listing of the font structure.

Other help: syslists info_cmd list_cmd base()
            »»»»»»»» »»»»»»»» »»»»»»»» »»»»»»
===
@Lists: dosd_list
----------------

   DOsd

This is the listing of all the available dos devices.
The listaddress operator is not available.

Simple information ('list'):
   Dos device name   : name for device
   Address           : pointer to this device
   Type              : device, volume or directory
   Task              : pointer to task
   Lock              : pointer to lock
   LockList          : pointer to outstanding locks
   DiskType          : disktype

Expanded information ('info'):
   No more information.

Other help: syslists info_cmd list_cmd base()
            »»»»»»»» »»»»»»»» »»»»»»»» »»»»»»
===
@Lists: func_list
----------------

   FUnc

This is the listing of all the available function monitor nodes.
The listaddress operator is not available.

Simple information ('list'):
   Function monitor  : function name we are monitoring
   Node              : pointer to this node
   Library           : library this function belongs to
   Offset            : offset for this function
   TrapTask          : last task using this function
   Count             : usage counter
   Type              : LED or NORM

   if Type is LED, TrapTask and Count are zero.

Expanded information ('info'):
   If type is LED: no more info
   If type is NORM: the last 8 tasks using this function.

Other help: syslists info_cmd list_cmd base()
            »»»»»»»» »»»»»»»» »»»»»»»» »»»»»»
===
@Lists: sema_list
----------------

   SEma

This is the listing of all the available semaphores.
The listaddress operator is not available.

Simple information ('list'):
   Semaphore name    : name for semaphore
   Node              : pointer to this node
   Pri               : semaphore priority
   NestCount         : ?
   QueueCount        : ?
   Owner             : semaphore owner

Expanded information ('info'):
   ?

Other help: syslists info_cmd list_cmd base()
            »»»»»»»» »»»»»»»» »»»»»»»» »»»»»»
===
@Lists: resm_list
----------------

   RESM

This is the listing of all the available resident modules.
The listaddress operator is not available.

Simple information ('list'):
   Resident name     : name for resident structure
   Address           : pointer to this resident module
   Pri               : priority
   Version           : resident version
   Flags             : flags
   IDString          : id string

Expanded information ('info'):
   No more info.

Other help: syslists info_cmd list_cmd base()
            »»»»»»»» »»»»»»»» »»»»»»»» »»»»»»
===
@Lists: fils_list
----------------

   FIls

This is the listing of all open files. (note that the files listed are
in fact locks).
The listaddress operator is not available.

Simple information ('list'):
   FileName          : name for file
   Lock              : pointer to this lock
   Access            : access type (READ or WRITE)
   Size              : current file size
   Key               : disk key

Expanded information ('info'):
   No more info.

Other help: syslists info_cmd list_cmd base()
            »»»»»»»» »»»»»»»» »»»»»»»» »»»»»»
===
@Lists: lock_list
----------------

   LOck

This is the listing of all locks.
The listaddress operator is not available.

Simple information ('list'):
   FileName          : name for lock
   Lock              : pointer to this lock
   Access            : access type (READ or WRITE)
   Size              : current file size
   Key               : disk key

Expanded information ('info'):
   No more info.

Other help: syslists info_cmd list_cmd base()
            »»»»»»»» »»»»»»»» »»»»»»»» »»»»»»
===
@Lists: ihan_list
----------------

   IHan

This is the listing of all input handlers.
The listaddress operator is not available.

Simple information ('list'):
   Handler name      : name for input handler
   Node              : pointer to this node
   Pri               : input handler priority
   Data              : pointer to inputhandler data
   Code              : pointer to inputhandler code

Expanded information ('info'):
   No more info.

Other help: syslists info_cmd list_cmd base()
            »»»»»»»» »»»»»»»» »»»»»»»» »»»»»»
===
@Lists: fdfi_list
----------------

   FDfi

This is the listing of all loaded fdfiles.
The listaddress operator is not available.

Simple information ('list'):
   Library name      : name for this fd file
   Node              : pointer to this node
   Library           : pointer to library
   Funcs             : number of functions loaded

Expanded information ('info'):
   A list of all library functions loaded.

Other help: syslists info_cmd list_cmd base()
            »»»»»»»» »»»»»»»» »»»»»»»» »»»»»»
===
@Lists: attc_list
----------------

   Attc

This is the listing of all macros.
The listaddress operator is not available.

Simple information ('list'):
   Node              : pointer to this node
   Code              : key code
   Qualifier         : key qualifier
   Command           : corresponding command

Expanded information ('info'):
   No more info.

Other help: syslists info_cmd list_cmd base() attach_cmd
            »»»»»»»» »»»»»»»» »»»»»»»» »»»»»» »»»»»»»»»»
===
@Lists: crsh_list
----------------

   Crsh

This is the listing of all crashed tasks.
The listaddress operator is not available.

Simple information ('list'):
   Node              : pointer to this node
   Task              : pointer to crashed task
   TrapNr            : trapnumber or gurunumber
   2ndInfo           : 2nd info (for guru only)
   Guru              : 0 if task held, 1 if guru

Expanded information ('info'):
   No more info.

Other help: syslists info_cmd list_cmd base()
            »»»»»»»» »»»»»»»» »»»»»»»» »»»»»»
===
@Lists: dbug_list
----------------

   DBug

This is the listing of all debug tasks.
The listaddress operator is not available.

Simple information ('list'):
   Debug task        : name of the task to debug
   Node              : pointer to this node
   Task              : pointer to task
   InitPC            : initial pc for task

Expanded information ('info'):
   The listing of all breakpoints:
      Node           : pointer to breakpoint node
      Number         : breakpoint number
      Where          : breakpoint address
      UsageCnt       : breakpoint usagecount
      Type           : type of breakpoint
      Condition      : break condition (if Type='C')

Other help: syslists info_cmd list_cmd base()
            »»»»»»»» »»»»»»»» »»»»»»»» »»»»»»
===
@Lists: stru_list
----------------

   STru

This is the listing of all structure definitions.
The listaddress operator is not available.

Simple information ('list'):
   Structure name    : name of the structure
   Node              : pointer to this node
   Pri               : priority
   InfoBlock         : pointer to structure definition
   Strings           : pointer to field string block

Expanded information ('info'):
   None.

Other help: syslists info_cmd list_cmd base()
            »»»»»»»» »»»»»»»» »»»»»»»» »»»»»»
===
@Lists: conf_list
----------------

   COnf

This is the listing of all auto configs.
The listaddress operator is not available.

Simple information ('list'):
   Config name       : name of autoconfig node
   Node              : pointer to this node
   Pri               : autoconfig priority
   Flags             : autoconfig flags
   BAddr             : BoardAddress
   BSize             : BoardSize
   Driver            : Driver

Expanded information ('info'):
   The listing of the config structure.

Other help: syslists info_cmd list_cmd base()
            »»»»»»»» »»»»»»»» »»»»»»»» »»»»»»
===
@Lists: moni_list
----------------

   MOni

This is the listing of all available monitors (only DOS 2.0).
The listaddress operator is not available.

Simple information ('list'):
   Monitor name      : name of monitor
   Node              : pointer to this node
   Pri               : monitor priority
   SubSys            : subsystem of monitor
   SubType           : subtype of monitor
   Library           : library for monitor
   Init              : Init routine

Expanded information ('info'):
   The listing of the monitor structure.

Other help: syslists info_cmd list_cmd base()
            »»»»»»»» »»»»»»»» »»»»»»»» »»»»»»
===
@Lists: pubs_list
----------------

   PUbs

This is the listing of all public screens (only DOS 2.0).
The listaddress operator is not available.

Simple information ('list'):
   PubScreen name    : name of public screen
   Node              : pointer to this node
   Pri               : priority
   Screen            : pointer to screen
   Visitors          : number of visitors on public screen
   SigTask           : task to signal
   SigBit            : signal bit

Expanded information ('info'):
   The listing of the public screen structure.

Other help: syslists info_cmd list_cmd base()
            »»»»»»»» »»»»»»»» »»»»»»»» »»»»»»
===
@Lists: lwin_list
----------------

   LWin

This is the list of all logical windows in PowerVisor. There is always
at least one logical window (Main) in this list. Some other possible logical
windows are: Rexx, PPrint, Refresh, Extra and Debug.

Simple information ('list'):
   Logical win name  : name of logical window
   Node              : pointer to this node
   PWin              : pointer to physical window
   width             : visible width of logical window
   height            : visible height of logical window
   col               : current column
   row               : current row
   viscol            : first visible column
   visrow            : first visible row

Expanded information ('info'):
   The complete listing of the 'LogWin' structure (see 'TheWizardCorner'
   for more info).

Other help: syslists info_cmd list_cmd base()
            »»»»»»»» »»»»»»»» »»»»»»»» »»»»»»
===
@Lists: pwin_list
----------------

   PWin

This is the list of all physical windows in PowerVisor. There is always
at least one physical window (Main) in this list.

Simple information ('list'):
   Physical win name : name of physical window
   Node              : pointer to this node
   Window            : pointer to the Intuition window
   Code              : last code
   Qualifier         : last qualifier

Expanded information ('info'):
   The complete listing of the 'PhysWin' structure (see 'TheWizardCorner'
   for more info).

Other help: syslists info_cmd list_cmd base()
            »»»»»»»» »»»»»»»» »»»»»»»» »»»»»»
===
@¼Error e-6
Stack overflow !!!
   PowerVisor detected a stack overflow in another program. The program
   is halted. You can find a crash node (a node or structure containing
   information about the crash) in the 'crsh' list.
===
@¼Error e-5
A program has crashed !!!
   PowerVisor detected a crash in another program. The program is
   halted. You can find a crash node (a node or structure containing
   information about the crash) in the 'crsh' list.
===
@¼Error e-4
A stack overflow was getting close !
   There could have been a stack overflow for PowerVisor. Don't worry,
   everything is nicely cleaned up.
   Stack checking occurs in the expression evaluator and in the
   command parser.
===
@¼Error e-3
You should never be able to see this line. Do you see me ? Then something
is astray.
===
@¼Error e-2
Break...
   You have interrupted some command. Nothing to worry about
===
@¼Error e-1
PowerVisor has crashed ! Normally this could not happen. Try to see what
is wrong and make a bug report if you think you have not caused the crash
yourselves.
===
@¼Error e0
There is no error !
===
@¼Error e1
Not enough memory !
   You have not enough memory to do something. Free some memory and
   try again.
===
@¼Error e2
Syntax Error !
   You typed a command that powervisor did not understand, or some
   of your arguments are badly formed.
===
@¼Error e3
This is not a device created with OpenDev !
   You can only use the 'devcmd' and 'devinfo' commands with devices
   opened with the 'opendev' command.
===
@¼Error e4
Bad list element type !
   The operation you want to do does not work for the current list.
   For example: you cannot use named shortcuts for the elements
   in the 'lock' list. You must use the node address.
===
@¼Error e5
Variable is a constant !
   You wanted to assign a value to a constant variable (eg 'version').
   This is of course not possible.
===
@¼Error e6
Only <B>yte, <W>ord or <L>ong !
   You can only use .B (byte) .W (word) or .L (long) with the contents
   operator (case is not important).
===
@¼Error e7
Odd address error !
   You tried to read a word or long from an odd address with the
   contents operator. Even though your processor (68020/30/40) may
   support this, PowerVisor won't allow you to do this to remain compatible
   with the 68000 processor.
===
@¼Error e8
Could not Lock!
   The argument you gave to 'curdir' is not a valid filename or
   subdirectory name.
===
@¼Error e9
Bracket '(' expected !
   Functions and library functions need an opening bracket for
   their argument list, even if they have no arguments. Note that
   the left bracket must IMMEDIATELLY follow the function name, no
   spaces are allowed.
===
@¼Error e10
To many arguments for library function !
   The number of arguments to a library function is fixed. You
   must close the argument list with a bracket ')'.
===
@¼Error e11
Missing operand !
   The command expected another argument but you did not supply it.
===
@¼Error e12
Lock is not a subdirectory !
   The filename you gave to 'curdir' is not a subdirectory but a file.
===
@¼Error e13
Error while opening device !
   The 'opendev' command failed (or some other command opening a device
   (like 'stack')).
   Maybe because the device does not exist, or you gave illegal
   arguments to the device.
===
@¼Error e14
Unknown list element !
   PowerVisor does not know the list you gave as an argument for 'list'.
   Type 'help syslists' for a list of all available lists.
===
@¼Error e15
Not implemented yet !
   You tried something that does not work yet.
   Maybe for a future version of PowerVisor.
===
@¼Error e16
Unknown mode argument !
   The argument you gave to 'mode' is unknown to PowerVisor.
   Type 'help mode_cmd' for more info about mode.
===
@¼Error e17
Unknown AddFunc argument !
   The argument you gave to 'addfunc' is unknown to PowerVisor.
   Type 'help addfunc_cmd' for more info about addfunc.
===
@¼Error e18
This is not a process !
   The command needs a process, but you gave it something else.
   'curdir' needs a process and not a task as its first argument.
   'hunks' only works with a process.
   You can only load symbols for a debug process.
===
@¼Error e19
Node is not a task or process !
   The command needs a process or a task, but you gave it something else.
   Here are some of the commands that need a process or task:
      'regs', 'freeze', 'unfreeze', 'kill' and 'debug'.
===
@¼Error e20
This task is not freezed !
   You can't unfreeze a task that isn't freezed.
===
@¼Error e21
This task is already freezed !
   You can't freeze a freezed task.
===
@¼Error e22
Node type is wrong !
   You try a command that expects a specific node and it finds that
   this node is not a good one.
   This error can be caused by one of the following commands:
      'remfunc' when you give something other than a 'function' node.
      'unloadfd' when you give something other than a 'fd-file' node.
      'remcrash' when you give something other than a 'crash' node.
      'remattach' when you give something other than a 'keyattach'
         node.
===
@¼Error e23
Addressed element not found !
   PowerVisor really does not know what to do with your string or name
   you gave on the commandline. It is not a variable, not a symbol for
   the current debug task and not an abbreviation of a list element in
   the current list.
===
@¼Error e24
Window is not sizeable !
   You can't size a physical window if it is a backdrop window (like
   the PowerVisor window is by default).
===
@¼Error e25
This is no supported library function !
   You tried 'libinfo' on a library function that does not exist.
   Or 'addfunc' complains about the fact that the library function
   does not exist.
   Check all the loaded fd-files.
===
@¼Error e26
No help available for this subject !
   'help' does not know what you are talking about.
===
@¼Error e27
Error while opening file !
   PowerVisor could not open a file.
   This error can be caused by one of the following commands:
      'load', 'save', 'loadfd', 'symbol l', 'script', 'addstruct', ...
===
@¼Error e28
Error while reading file !
   PowerVisor could not read from a file.
===
@¼Error e29
Not a resident module !
   You tried to use 'remres' on something that is no resident module.
   All resident modules are in the 'resm' list.
===
@¼Error e30
Not a lock !
   You cannot unlock something that is not a lock. Also 'pathname'
   does not like unlocking tasks or something.
===
@¼Error e31
Bad History value (2..1000)
   The history value must be something between 2 and 1000.
===
@¼Error e32
Error opening trackdisk device !
   The 'wblock' or 'rblock' commands could not open the trackdisk.device.
===
@¼Error e33
DoIO returned with a non zero value !
   There was an error for DoIO. ('rblock' command).
===
@¼Error e34
There is no task to debug !
   You tried a debug command without a debug task. Load a debug task
   with 'debug'.
===
@¼Error e35
Unknown argument for trace !
   The argument you gave is unknown to the mighty 'trace' command.
   Please rethink your request or type 'help trace_cmd' for more info.
===
@¼Error e36
Unknown argument for debug !
   The argument you gave is unknown to the 'debug' command.
===
@¼Error e37
Address is in ROM ! Can't set breakpoint !
   You cannot put a breakpoint in ROM. You can avoid this problem by
   using one of the 'trace' commands. Some of them allow you to
   set pseudo breakpoints in ROM.
===
@¼Error e38
Not a debug node !
   When you want to do something with a debug node, you must do it
   with a debug node.
===
@¼Error e39
Bad '@' argument
   The argument you give to the '@' operator (special_op) is malformed
   or something.
   You must use a valid register specification.
   Type 'help special_op' for more info.
===
@¼Error e40
LoadSeg error !
   PowerVisor could not load the program. You probably mistyped the name.
   Or there is not enough memory to load the program.
===
@¼Error e41
Unknown argument for dmode !
   The argument you gave is unknown to the 'prefs dmode' command.
===
@¼Error e42
There is no current debug task !
   You tried a debug command without a debug task.
   You must first load a debug task with 'debug' or set the
   current debug task with 'duse'.
===
@¼Error e43
Unknown argument for break !
   The argument you gave is unknown to the 'break' command.
===
@¼Error e44
Breakpoint does not exist !
   You try to clear a nonexisting breakpoint.
===
@¼Error e45
There are no symbol hunks !
   You try to load symbol hunks for a program without symbol hunks.
===
@¼Error e46
Symbol not found !
   You get this errormessage if you try to remove a nonexisting symbol.
===
@¼Error e47
You can only remove variables !
   You should not remove constants, functions and special variables.
===
@¼Error e48
You can not assign to a function !
   You can't assign to a function. Note that functions and variables
   are internally the same. This means that you can't have a variable
   and a function with the same name.
===
@¼Error e49
You must use brackets with functions !
   A function wants brackets, even if there are no arguments.
===
@¼Error e50
Unknown argument for symbol !
   The argument you gave to 'symbol' is unknown.
===
@¼Error e51
There are no symbols !
   There are no symbols. ('symbol s')
===
@¼Error e52
You can only realloc blocks smaller than 64K !
   Use the 'realloc' function only for memory block smaller than
   64K.
===
@¼Error e53
Your brackets are really out of order !
   You seem to have done something wrong with your brackets.
===
@¼Error e54
The debug task is busy, please try again later !
   You cannot trace when you are already tracing. Also, before you 'quit'
   or try to remove the debug task, you should stop the tracing.
===
@¼Error e55
The task is not tracing !
   You cannot stop the tracing if the task is not tracing.
===
@¼Error e56
File does not have the right format !
   You must use a 'pvsd' file for the 'addstruct' command.
   These files are made by 'mstruct' (external utility).
===
@¼Error e57
This is not a structure definition !
   You must use structure definitions (in the 'stru' list) with
   commands like 'interprete' and 'remstruct'.
===
@¼Error e58
Bad argument value !
   You must use acceptable values for the 'prefs debug' (and other) commands.
===
@¼Error e59
No colorchange allowed when PowerVisor is on a window !
   Only use the 'color' command when PowerVisor is on it's
   own screen.
===
@¼Error e60
Could not open font !
   PowerVisor could not open the font. Maybe it is not in the 'fonts:'
   directory ?
===
@¼Error e61
Can't execute script file in script file !
   Recursive script executing is not allowed.
===
@¼Error e62
Refresh window is not open !
   You tried to use the 'refresh' command before you opened the 'refresh'
   window. Use 'rwin' to do this.
===
@¼Error e63
Unknown tag type !
   The tag type you used with 'AddTag' is invalid (use ba,wa,la,st or as).
===
@¼Error e64
No output allowed on debug logical window !
   You cannot use the 'on' or 'current' commands for the 'debug' logical
   window. The 'debug' logical window only receives output from the
   full screen debugger.
===
@¼Error e65
Error writing file !
   Error while writing to file !
===
@¼Error e66
Not a Tag file !
   This file is not a tag definition file !
===
@¼Error e67
Bad tag list value (0 .. 15) !
   PowerVisor only supports 16 tag lists (0 .. 15).
===
@¼Error e68
Unknown or invalid register !
   PowerVisor does not know this register. You can only use :
   d0,...,d7,a0,...,a6 or sp (and sometimes pc).
===
@¼Error e69
There is a more recent patch then this one installed !
   You can't remove this patch. You must first remove the more recent
   one. Note that there may be other programs patching library functions.
===
@¼Error e70
There is no fd file loaded for this library !
   You can't use 'libfunc' when there is no fd file loaded for the
   library.
===
@¼Error e71
Unknown logical window !
   I don't know about this logical window. Note that you must
   give the logical window name in full for the 'prefs logwin'
   command.
===
@¼Error e72
Resulting commandline too long after converting from alias string !
   While the alias line is converted we got an overflow. Either increase
   the maximum linelength (with 'prefs linelen'), decrease what you
   type on the commandline or make the alias shorter.
===
@¼Error e73
Missing left bracket '(' in fd file !
   Where is the left bracket that should come after the function name ?
===
@¼Error e74
Missing right bracket ')' in fd file !
   Where is the right bracket that should come somewhere after the
   function name ?
===
@¼Error e75
Bad '##bias' statement in fd file !
   The ##bias statement in the fd-file is bad since it refered to a
   function entry that is already used.
===
@¼Error e76
You can't close the 'Main' physical window !
   Well, you really can't do that.
===
@¼Error e77
You can't close the 'Main' logical window !
   Sorry, but if you really want you can close another logical window
   instead.
===
@¼Error e78
Bad argument for 'openlw' ! Arg must be one of 'r','l','d' or 'u' !
   The direction argument for the new logical window is wrong. It must
   be one of u,d,r or l preceded with an arbitrarily number of p's.
===
@¼Error e79
Brother logical window must be on same physical window !
   No, you really can't open a logical window on one physical window with
   the brother on another physical window. That's like having a brother
   on Mars.
===
@¼Error e80
Window is not movable !
   The physical window is like a brick. You can't move it. This is because
   the physical window is a backdrop window.
===
@¼Error e81
There is no father for this box !
   You used the p (parent) direction argument to 'openlw' but there is
   no parent for the logical window you choose as a brother.
===
@¼Error e82
Unknown preferences argument !
   I don't know the preference argument you gave to the 'prefs' command.
   See the 'prefs' command for more info.
===
@¼Error e83
Please close visitor windows first !
   Before you can quit PowerVisor or before you can change some screen
   attributes you must make sure that there are no visitor windows
   opened on the PowerVisor public screen.
===
@¼Error e84
Divide by zero !
   You tried to divide by zero.
===
@¼Error e85
No group operators allowed for the debug task !
   You can't use group operators in expressions used for conditional
   tracing or conditional breakpoints.
===
@¼Error e86
Error opening screen !
   PowerVisor could not open the screen.
===
@¼Error e87
You can't remove the 'rc' and 'error' variables. These are private !
   This is fairly obvious.
===
@¼Error e88
'LoadSeg' failed !
   'Resident' did not succeed in loading the executable file.
===
@¼Error e89
Variable names must start with a letter or an underscore !
   You used assignment with an illegal object left of the '=' operator.
   Only variables, the contents operator ('*') and the special operator
   ('@') are allowed.
===
@¼Error e90
Error opening physical window !
   Not enough memory or no more signals to open the physical window.
===
@¼Error e91
Error opening logical window !
   Not enough memory to open the logical window.
===
@¼Error e92
Bracket ')' expected !
   You must always close all brackets with expressions.
===
@¼Error e93
Bracket '}' expected !
   You must always close all curly brackets with groups.
===
@¼Error e94
Bus error !
   One of your debug tasks is halted because of a bus error.
===
@¼Error e95
Address error !
   One of your debug tasks is halted because of an address error.
===
@¼Error e96
Illegal instruction !
   One of your debug tasks is halted because it executed an illegal
   instruction.
===
@¼Error e97
Division by zero !
   One of your debug tasks is halted because it tried to divide by zero.
===
@¼Error e98
CHK instruction !
   One of your debug tasks is halted because it tried to execute a CHK
   instruction.
===
@¼Error e99
TRAPV instruction !
   One of your debug tasks is halted because it tried to execute a TRAPV
   instruction.
===
@¼Error e100
Privilege Violation !
   One of your debug tasks is halted because it tried to execute a
   priviledged instruction.
===
@¼Error e101
Trace error !
   This should never occur. One of your debug tasks is halted because
   it enable trace mode.
===
@¼Error e102
Unimplemented 1010 opcode !
   One of your debug tasks is halted because it tried to execute an
   unimplemented 1010 instruction.
===
@¼Error e103
Unimplemented 1111 opcode !
   One of your debug tasks is halted because it tried to execute an
   unimplemented 1111 instruction.
===
@¼Error e104
Unknown argument for track !
   The argument you gave to 'track' is unknown.
===
@¼Error e105
PowerVisor is allready tracking for a task !
   You can only track one task at a time with the 'track' command.
   Stop the tracking of the other task or do something else.
===
@¼Error e106
PowerVisor is not tracking !
   You can perfrom this operation only if PowerVisor is tracking something.
===
@¼Error e107
Unknown argument for source !
   The argument you gave to 'source' is unknown.
===
@¼Error e108
There are no debug hunks in this executable file !
   Use the correct compiler or assembler option to generate debug hunks.
===
@¼Error e109
There is no source loaded for this debug node !
   You are trying to do some operation on a source you have not loaded
   with the 'source' command.
===
@¼Error e110
This address is not in the source !
   The program counter does not occur in the debug hunks information.
===
@¼Error e111
This command only works on the 68030 or 68040 !
   This error can occur if you use the 'speek' and 'spoke' commands on
   a system without an 68030 or 68040. Note that the 68020 with 68851
   is not enough.
===
@¼Error e112
You need a MMU for this command !
   You need a 68851, 68030 or 68040.
===
@¼t exec_tmp
Exec
===
@¼t intb_tmp
INTb
===
@¼t task_tmp
Task
===
@¼t libs_tmp
LIBs
===
@¼t devs_tmp
DEvs
===
@¼t reso_tmp
RESO
===
@¼t memr_tmp
MEMR
===
@¼t intr_tmp
INTR
===
@¼t port_tmp
Port
===
@¼t wins_tmp
Wins
===
@¼t attc_tmp
ATTC
===
@¼t graf_tmp
GRaf
===
@¼t conf_tmp
COnf
===
@¼t scrs_tmp
SCrs
===
@¼t font_tmp
FOnt
===
@¼t dosd_tmp
DOsd
===
@¼t func_tmp
FUnc
===
@¼t sema_tmp
SEMa
===
@¼t resm_tmp
RESm
===
@¼t fils_tmp
FILS
===
@¼t lock_tmp
LOck
===
@¼t ihan_tmp
IHan
===
@¼t fdfi_tmp
FDfi
===
@¼t crsh_tmp
CRsh
===
@¼t dbug_tmp
DBug
===
@¼t moni_tmp
MONi
===
@¼t pubs_tmp
PUbs
===
@¼t stru_tmp
STru
===
@¼t lwin_tmp
LWin
===
@¼t pwin_tmp
PWin
===
@¼t help_tmp
Help [<topic>]
===
@¼t pvcall_tmp
<result> <- PVcall <number> [<arguments>]
===
@¼t prefs_tmp
PREfs ('history' | 'key' | 'screen' | 'stack' | 'logwin' | 'linelen' |
      'debug' | 'dmode' | 'pens' | 'font') [<arguments> ...]
===
@¼t event_tmp
EVent <class> <subclass> <code> <qualifier> <x> <y>
===
@¼t owner_tmp
OWNer <address>
===
@¼t speek_tmp
<value> <- SPEEk <address>
===
@¼t saveconfig_tmp
SAVEConfig
===
@¼t spoke_tmp
SPOke <address> <value>
===
@¼t mmutree_tmp
MMutree
===
@¼t mmureset_tmp
MMURESet
===
@¼t mmuregs_tmp
MMURegs
===
@¼t openlw_tmp
RC,<lwin> <- OPENLw <physical window> <logwin name> <cols> <rows>
             [<brother> <where> [<number of columns or lines>]]
===
@¼t openpw_tmp
RC,<pwin> <- OPENPw <physical window name> <x> <y> <w> <y>
===
@¼t closepw_tmp
CLOSEPw <physical window>
===
@¼t closelw_tmp
CLOSELw <logical window>
===
@¼t setflags_tmp
RC,<oldflags> <- SETFLags <logical window> <mask> <flags>
===
@¼t mmurtest_tmp
MMURTest <address>
===
@¼t mmuwtest_tmp
MMUWtest <address>
===
@¼t specregs_tmp
SPecregs
===
@¼t setfont_tmp
SETfont <logical window> <fontname> <fontheight>
===
@¼t colrow_tmp
COLRow <logical window> <columns> <rows>
===
@¼t view_tmp
VIew [<address> [<bytes>]]
===
@¼t addtag_tmp
ADDTag <address> <bytes> <type> [<structure>]
===
@¼t loadtags_tmp
LOADTags <file> <base>
===
@¼t savetags_tmp
SAVETags <file> <base>
===
@¼t cleartags_tmp
CLEARTags
===
@¼t remtag_tmp
REMTag <address>
===
@¼t tags_tmp
TAGs
===
@¼t checktag_tmp
<bytes remaining> <- CHecktag <address>
===
@¼t usetag_tmp
USetag <number>
===
@¼t tg_tmp
TG <number> <command>
===
@¼t interprete_tmp
INTErprete <structure pointer> <struct def pointer>
===
@¼t clearstruct_tmp
CLEARStruct
===
@¼t addstruct_tmp
ADDStruct <filename>
===
@¼t assign_tmp
ASsign <assignment string>
===
@¼t string_tmp
<string> <- STRIng <string pointer>
===
@¼t rx_tmp     (Commandline and scripts only)
RX <file name>
===
@¼t remstruct_tmp
REMStruct <struct def pointer>
===
@¼t for_tmp
FOR <listname> <command>
===
@¼t llist_tmp
LList <node> ['start']
===
@¼t vars_tmp
VArs ['all']
===
@¼t remvar_tmp
REMVar {<variables>}
===
@¼t alias_tmp
ALias [<alias command> <alias string>]
===
@¼t error_tmp
<pointer to error string> <- ERror <error number>
===
@¼t unalias_tmp
UNALias <alias command>
===
@¼t hold_tmp
HOld
===
@¼t quit_tmp
Quit
===
@¼t gadgets_tmp
Gadgets <window>
===
@¼t size_tmp
SIze <physical window> <w> <h>
===
@¼t move_tmp
MOVe <physical window> <x> <y>
===
@¼t screen_tmp
SCREen [<screen>]
===
@¼t remres_tmp
REMRes <resident pointer>
===
@¼t resident_tmp
RC,<Pointer to code> <- RESIdent [<filename>]
===
@¼t unresident_tmp
UNResident <Pointer to code>
===
@¼t clip_tmp
[RC,<Pointer to data>] <- CLIp <Clip name> [<Pointer to data> <Length>]
===
@¼t remclip_tmp
REMCLip <Clip name>
===
@¼t remove_tmp
<node> <- REMOve <node>
===
@¼t curdir_tmp
CUrdir <process> <directory name>
===
@¼t clear_tmp
CLEar [<value>]
===
@¼t active_tmp
Active <logwin>
===
@¼t scroll_tmp
SCROll <logwin> <x> <y>
===
@¼t current_tmp
CURRent <logical window>
===
@¼t on_tmp
ON <logical window> <command>
===
@¼t cls_tmp
CLs
===
@¼t led_tmp
LEd
===
@¼t load_tmp
<bytes loaded> <- LOAd <filename> <start> [<max bytes>]
===
@¼t save_tmp
<bytes written> <- SAve <filename> <start> <bytes>
===
@¼t fregs_tmp
FREGs <task>|<debug node>
===
@¼t regs_tmp
REGs <task>|<crash node>|<debug node>
===
@¼t print_tmp
PRint <string>
===
@¼t sprint_tmp
SPRint <string>
===
@¼t locate_tmp
LOCAte <x> [<y>]
===
@¼t home_tmp
HOMe
===
@¼t showalloc_tmp
SHowalloc
===
@¼t cleanup_tmp
CLEANup
===
@¼t color_tmp
COLor <col num> <red> <green> <blue>
===
@¼t request_tmp
<result> <- REQuest <body string> <gadget string> <argument>
===
@¼t reqload_tmp
INPUT,<ptr to filename> <- REQLoad <title>
===
@¼t reqsave_tmp
INPUT,<ptr to filename> <- REQSave <title>
===
@¼t getstring_tmp
INPUT,<ptr to inputline> <- GEtstring <title> <max number of chars>
===
@¼t scan_tmp
INPUT,<pointer to inputline> <- SCAn [<number>]
===
@¼t disp_tmp
<value of expression> <- Disp <expression>
===
@¼t refresh_tmp
Refresh [<refresh rate> <command>]
===
@¼t fit_tmp
FIT <logical window>
===
@¼t awin_tmp
AWin [<number of lines>]
===
@¼t owin_tmp
OWin [<number of lines>]
===
@¼t rwin_tmp
RWin [<number of lines>]
===
@¼t xwin_tmp
Xwin [<number of lines>]
===
@¼t dwin_tmp
DWin [<number of lines>]
===
@¼t mode_tmp
MOde <mode argument> {<mode argument>...}
===
@¼t copy_tmp
Copy <source> <destination> <bytes>
===
@¼t fill_tmp
Fill <dest> <bytes> <with>
===
@¼t search_tmp
RC,<address> <- Search <start> <bytes> <string>
===
@¼t next_tmp
RC,<address> <- Next
===
@¼t stack_tmp
STAck [<task> <micro seconds>]
===
@¼t account_tmp
ACCount
===
@¼t kill_tmp
Kill <task>|<crash node>
===
@¼t freeze_tmp
FReeze <task>
===
@¼t unfreeze_tmp
UNFreeze <task>
===
@¼t addfunc_tmp
RC,<func node> <- ADdfunc (<libfuncname> | 'offs' <library> <offset>)
                  ['only' <task>] [<type> [<command>]]
===
@¼t remfunc_tmp
REMfunc <function monitor node>
===
@¼t unasm_tmp
Unasm [<start> [<instructions>]]
===
@¼t libinfo_tmp
LIBInfo <library function name>
===
@¼t libfunc_tmp
LIBFunc <library> <offset>
===
@¼t list_tmp
List [<list>]
===
@¼t memory_tmp
Memory [<start> [<bytes>]]
===
@¼t info_tmp
Info <object address> [<list>]
===
@¼t memtask_tmp
MEMTask <task>
===
@¼t remcrash_tmp
REMCrash <crash node>
===
@¼t loadfd_tmp
RC,<number of functions> <- LOADFd <library> <file-name>
===
@¼t unlock_tmp
UNLOCk <pointer to a lock>
===
@¼t sync_tmp
SYNc
===
@¼t async_tmp
ASYnc
===
@¼t hide_tmp
HIde
===
@¼t unhide_tmp
UNHide
===
@¼t front_tmp
FROnt
===
@¼t closewindow_tmp
CLOsewindow <window>
===
@¼t hunks_tmp
HUnks <process>
===
@¼t attach_tmp
<attach node> <- ATtach <command string> <code> <qualifier>
                 [('e' | 'c') ['+']]
===
@¼t remattach_tmp
REMAttach <attach node>
===
@¼t closescreen_tmp
CLOSEScreen <screen>
===
@¼t log_tmp
LOG [<logical window> <filename>]
===
@¼t track_tmp
TRACK 't' <task> | 's' | 'c' | 'l'
===
@¼t to_tmp
TO <file> <command>
===
@¼t taskpri_tmp
TASKPri <task ptr> <priority>
===
@¼t pathname_tmp
PAthname <lock>
===
@¼t unloadfd_tmp
UNLoadfd <fd-file node>
===
@¼t script_tmp
<result> <- SCRIpt <script file> [<commandline>]
===
@¼t dscroll_tmp
DScroll <offset>
===
@¼t dstart_tmp
DSTart <address>
===
@¼t debug_tmp
RC <- DEBug 'n' | 'c' | 'l' <filename> | 't' <task node> | ('r'|'f'|'u')
             [<debug node>] | 'd' <name>
===
@¼t drefresh_tmp
DRefresh
===
@¼t duse_tmp
DUse <debug node>
===
@¼t with_tmp
WITh <debug node> <command>
===
@¼t trace_tmp
TRace [ 'n' <number> | 'b' | 'r' <register> | 'u'['t'] <address>
      | 'o'['t'] | 'c' <condition> | 's' | 'g'['t'] | 'h' | 'f'
      | 't' | 'j' ]
===
@¼t break_tmp
RC <- Break ('a'|'c'|'n'|'t'|'p'|'r') <address> [<condition>|<timeout>]
===
@¼t source_tmp
SOurce 'l' <filename> [<hunkaddress>] | 'w' <address> | 's' |
       't' <tab size> | 'r' | 'c' | 'g' <line>
===
@¼t symbol_tmp
SYmbol 'l' <filename> [<hunkaddress>] | 'c' | 'a' <symbol> <value> |
       'r' <symbol> | 's'
===
@¼t rblock_tmp
RC,<address> <- RBlock <Unit number> <block number> [<address>]
===
@¼t void_tmp
<result> <- Void {<argument>...}
===
@¼t wblock_tmp
WBlock <Unit number> <block number> <address>
===
@¼t opendev_tmp
RC,<pvdevice> <- Opendev <device name> [<unit> [<flags>]]
===
@¼t closedev_tmp
CLOSEDev <device block>
===
@¼t devinfo_tmp
DEVInfo <device block>
===
@¼t devcmd_tmp
RC <- DEVCmd <dev> <command> [<flags> [<length> [<data> [<offset>]]]]
===
@¼t remhand_tmp
REMHand <input handler>
===
@¼t go_tmp
<result> <- GO <address> [<commandline>]
===
@Help bugs
---------
Bugs

   locks          Break... is not printed when we interrupt the lock listing
                  This harmless bug is a replacement for a memory loosing
                  bug. I prefer this bug :-)
   Stack overflow There seem to be some problems with 'killing' a task
                  that has crashed because of a stack overflow
                  ('account' command). The solution is of course not to
                  kill the program :-) PowerVisor has halted the program
                  so it will do no more (!) harm
   kill           kill does not work for tasks using floating point (floating
                  point with the 68881 or 68882)
   fmove.d        bug in disassembling of the following instruction :
                  F23C 5400 3FF1 9999 9999 999A : FMOVE.D  #$3FF19999,FP0

Bugs for AmigaDOS 1.2/1.3 version of PowerVisor only

   debug          PowerVisor looses 24 bytes when you do 'debug l' and
                  'debug u'.
   cursor         The cursor in the stringgadget sometimes disappears in
                  the AmigaDOS 1.2/1.3 version of PowerVisor (this happens
                  the first time you use the <up> key to go in history)
   stringgadget   I know of no way to unactivate a stringgadget in AmigaDOS
                  1.3 and older. Therefore cycling through the windows
                  with <tab> is not enough to deactivate the stringgadget.
                  You will have to press <enter> first (or click next to
                  the stringgadget) before you can press the key (with
                  -MORE- or -HALT-)

Things that could be better and maybe should be supported

   mmu            'mmutree' does not support indirect pages and 8 byte
                  descriptors
                  'mmutree' does not support FC trees (function codes)
   signals        maybe we should share some signals, we have only five
                  signals left
   'mode'         The mode variable is not restored when an error occurs
                  while assigning to 'mode'
   disp 1a        should give an error
   trace u        PowerVisor may disturb other programs if you set your
                  breakpoint in shared memory
   free           The Free function should check if the memory you
                  try to free is OK
   trace          Tracing is very hazardous for multitasking. You can
                  scarcely move your mouse
   crashes        There are still some guru's PowerVisor does not trap
   crash trapping Address Errors are not recoverable
   fonts          We should not permit proportional fonts
   search/copy/fill
                  These routines are very sensitive to bad arguments
                  (negative for example)
   Overflows      Powervisor does not always check for overflow (especially
                  with string parsing) Make sure that your string are always
                  smaller than the maximum line length in the stringgadget
                  (set with 'prefs linelen', default 400)

Future enhancements (note that these are NOT promises :-)

   owner          Owner should be expanded to handle more system lists
   load           Load must have an extra argument : offset to start loading
   customize      I plan to make a seperate file containing all command
                  strings, function strings and some other strings. That way
                  the user will be able to customize PowerVisor by changing
                  this file. This file will not be resident in memory.
                  PowerVisor will build internal data structures using this
                  file
   pvcall         Instead of only one command for each installable post or
                  pre command I plan to incorporate a list system (see the
                  TheWizardCorner file for the 'pvcall' command)
   mmu            I have been thinking about a very powerful system to
                  use the mmu for protecting memory. PowerVisor could be
                  protected from other programs and some extra commands
                  could be provided to read or write protect regions
                  of memory
   Floating pt    I plan full floating point support for PowerVisor. The first
                  steps have been set with the primitive 'fregs' command and
                  the bug fix in tracing with floating point. Future
                  enhancements will include floating point register
                  modification and others
   a4             I plan a new scheme to allow setting labels for local
                  variables (in C for example)
   switch         Task switching monitor. Using this monitor you will be
                  able to debug communication problems between two or
                  more tasks
===