Club Amiga de Montreal

home *** CD-ROM | disk | FTP | other *** search

/ Club Amiga de Montreal - CAM / CAM_CD_1.iso / files / 545a.lha / PowerVisor_v1.0 / docs.LZH / docs / InstallingPowerVisor < prev next >

Wrap

Text File | 1991-09-01 | 26.7 KB | 760 lines

*----------------------------------* * Tutorial : installing PowerVisor * Sun Sep 1 14:48:14 1991 *----------------------------------* ===================== Commands used in this tutorial ========================= mode Set PowerVisor preferences prefs Set preferences screen Set PowerVisor on another screen ===================== Functions used in this tutorial ======================== ============================== Introduction ================================== At this moment (after you have read the 'GettingStarted', the 'Expressions' and the 'Screen' chapters) you are probably ready to ²customize PowerVisor. This is a complex business and you will probably have to change some parameters later when you use PowerVisor. =========================== The 'mode' command =============================== With the 'mode' command you can set some parameters. The 'mode' command expects any number of keywords. These keywords need not be in any particular order. The following keywords are supported : pal set ¹monitor to ¹pal (only AmigaDOS 2.0) the ¹non-interlaced resolution is 640x256 and the ¹interlaced resolution is 640x512. This resolution will be bigger if you use ¹overscan. ntsc set monitor to ¹ntsc (only AmigaDOS 2.0) non-interlaced : 640x200 interlaced : 640x400 vga set monitor to ¹vga (only AmigaDOS 2.0 and new denise) non-interlaced : 640x480 interlaced : 640x960 viking set monitor to ¹a2024 (only AmigaDOS 2.0) resolution : 1024x1008 lace use ¹interlace nolace no interlace (default) fancy use ²two bitplanes for the PowerVisor screen (default) nofancy use only ²one bitplane sbottom include the ²size gadget in the ²bottom border. This means that you loose a line but you gain some columns (default) nosbottom include the size gadget in the ²right border of the window. You loose some columns but you gain a line or so space add a space after a ²snapped word (default) nospace don't add a space. Simply snap the word as it is lonespc snap a space if you click on an empty place in a logical window nolonespc don't snap a space (default) shex ³show hex words when ²disassembling instructions. The disadvantage is that these words could overwrite the right side of the ¹symbolname if present (default) noshex don't show hex words. Symbols will be completely visible dec display all printed ¹integers as ²decimal only hex display all printed integers as ²hexadecimal only hexdec first display hex, than display decimal (default) more enable ²-MORE- check for the 'Main' ²logical window (default) nomore disable -MORE- check auto perform an ²automatic list whenever the ²current list changes noauto don't do this (default) byte ²list memory as ¹bytes (for the 'memory' command) word list memory as ¹words long list memory as ¹longs (default) ascii list memory as ¹ascii fb ¹feedback each command as it is typed in by the user on the current logical window (default) nofb don't do this patch ¹patch the Exec AddTask function. When this function is patched by PowerVisor ¹crashtrapping will work better for all new tasks created after the patch is applied. This is recommended if you use ²resident breakpoints (see the 'Debug' file). Note that it is not safe to run other debuggers (like ¹CodeProbe or ¹MonAm) when the patch is applied. They will probably crash when you try to trace with them. There will (probably) be no problems if you start the other debugger and load the debug program with this debugger BEFORE you apply the patch (before you start PowerVisor or before you type 'mode patch'). (default) nopatch Don't patch the ²Exec AddTask function. When the ¹AddTask function is not patched, PowerVisor will trap a crash a bit later (too late if you plan to use resident breakpoints). With the patch applied PowerVisor traps crashes just on the spot while if the patch is not applied PowerVisor will only trap the crash just before the ¹guru would normally arrive (you will even have to press 'cancel' on the ²'task-held' requester before PowerVisor notices the crash). But 'mode nopatch' is the only safe way to run ²other debuggers concurrently with PowerVisor. Example, to set everything other than default you can use : < mode lace fancy nospace lonespc noshex dec nomore auto byte nofb nopatch < <enter> All the parameters set with the 'mode' command will be saved with the 'saveconfig' command (see later). =========================== The 'prefs' command ============================== Using the 'prefs' command you can install some additional parameters. All parameters installable with the 'prefs' command will be saved when you use 'saveconfig'. =============== The maximum number of lines in the history =================== Using 'prefs history' you can get or set the maximum number of lines in the history. The default is 20. < prefs history <enter> > 00000014 , 20 You can set another value with : < prefs history 500 <enter> Note that the ²history buffer is dynamic. If there are 10 lines in the history buffer you only loose memory for 10 lines even if the maximum number of lines is 500. The command also clears the history buffer. =========================== Some standard keys =============================== Using 'prefs key' you can get or set ¹keycodes for standard keys. The following keys are supported : nr name default key code qualifier ------------------------------------------------------------------------- 0 interrupt key <esc> 045 0 1 hot key <r-shift>+<r-alt>+'/' 03A 022 2 pause key <r-alt>+<help> 05F 020 3 cycle active logwin <tab> 042 0 4 history up <arrow up> 04C 0 5 history down <arrow down> 04D 0 You can get the default using : < prefs key 2 <enter> > 0000005F 00000020 Or you can set it to other values with : < prefs key 0 16 0 <enter> This command will set the interrupt key to the 'q' key (or the 'a' key if you have an AZERTY keyboard). This is only an example. I recommend that you choose better keys :-) Here are some codes that are often used : <esc> 045 <tab> 042 <F1> 050 . . . . . . <F10> 059 <backspace> 041 <help> 05F <del> 046 <up> 04C <down> 04D <left> 04F <right> 04E <return> 044 <enter> (numeric keypad) 043 Here are the ¹qualifers. You must add two qualifiers if you want to use a combination : Left shift 0001 Right shift 0002 Capslock 0004 (this one is ignored by PowerVisor) Control 0008 Left alt 0010 Right alt 0020 Left Amiga 0040 Right Amiga 0080 ======================== Setting some startup bits =========================== With 'prefs startup' you can get or set some ²startup bits. The startup variable is a longword. Only two bits are supported at this time. bit 0 if true we start PowerVisor on the ²workbench screen if this bit is true we ignore bit 1 bit 1 if true we open the 'Main' physical window on a ¹non-backdrop window instead of a ²backdrop window. This is equivalent to the 'screen' command with argument 0. Default is 0. < prefs startup <enter> > 00000000 , 0 To set another value use : < prefs startup 1 <enter> You need to quit PowerVisor and start it again to see the result of this command. ===================== Setting the startup window size ======================== With 'prefs window' you can define the size of the 'Main' physical window to be used when it is not a ²backdrop window (only just after startup). This value is thus only used if the ²'startup' variable (see the previous section) is either 1 or 2. The default is (0,0,640,200). Which is x = 0, y = 0, width = 640 and height = 200. You must not worry if the size is too big. PowerVisor will check and make the window smaller if it would not fit on the screen. < prefs window <enter> > 00000000 , 0 > 00000000 , 0 > 00000280 , 640 > 000000C8 , 200 Set new values with : < prefs window 0 200 640 200 <enter> You need to quit PowerVisor and start it again to see the result of this command. ===================== Setting the startup screen size ======================== With 'prefs screen' you can define the width and height of the PowerVisor screen. If you have AmigaDOS 2.0 you can use any size for the screen. If this size is big you can scroll by moving the mouse out of the visible part of the screen. The default is (65535,65535) (or (-1,-1) as words).Which means that PowerVisor will take the default width and height for the screen. < prefs screen <enter> > 0000FFFF , 65535 > 0000FFFF , 65535 For example, to make the screenheight equal to 1024 use the following command : < prefs screen -1 1024 <enter> You need to quit PowerVisor and start it again to see the result of this command. ====================== Setting the stack fail level ========================== With 'prefs stack' you can set or get the amount of ¹stackspace left before PowerVisor will halt the task and give a warning (only if account is on with the 'account' command). The default value is 40. < prefs stack <enter> > 00000028 , 40 Change it with : < prefs stack 80 <enter> Be careful not to make it too big, or else all tasks will be stopped even if nothing is wrong. ================ Setting default logical window parameters =================== Using 'prefs logwin' you can set or get default parameters for the standard logical windows ('Main', 'Extra', 'Refresh', 'Debug', 'Rexx' and 'PPrint'). Four values are remembered for each ³standard logical window : - the ³number of columns - if 0 we scale the number of columns to the visible size at the moment the logical window is created. After that the number of columns is fixed - if -1 we use horizontal autoscale. The number of columns is adapted to the visible size everytime the horizontal visible size changes. The disadvantage of this is that the logical window is cleared - every other value sets a fixed number of columns - the ³number of rows - (like the number of columns) - the ²flag mask - the flag values in this mask The following flags are supported (also see the 'Screen' chapter) : (bit 0/bit 1) -MORE- disable/enable 4 top-visible/real-top 32 statusline on/off 64 interrupt on/off 128 auto output snap 256 All other bits are used or reserved and should not be used in the mask. For example. To set the ²-MORE- check off, the statusline off and leave all other flags as default you can use : mask = 4+64 value = 64 Or with -MORE- check on : mask = 4+64 value = 4+64 The following default values are used when a logical window is opened : -MORE- disabled ¹Interrupt/Pause enabled ²Home position is top-visible ²Status line on ³Auto Output Snap off The standard logical windows have the following defaults (Note that the -MORE- setting of the 'Main' logical window is dependent on the 'mode' command) : - Main (0,0,160,0) number of columns and rows is set to a fixed value. This value is the maximum number of columns and rows at the time the logical window is created. Interrupt/Pause enabled Home position is top-visible Auto Output Snap is on - Extra (0,0,160,0) number of columns and rows is set to a fixed value. This value is the maximum number of columns and rows at the time the logical window is created. Interrupt/Pause enabled Home position is top-visible Auto Output Snap is on - Refresh (0,50,160,160) the number of columns is set to a fixed value. This value is the maximum number of columns at the time the logical window is created. The number of rows is fixed and always set to 50. Interrupt/Pause disabled Home position is real-top Auto Output Snap is off - Debug (82,42,160,160) the number of columns is fixed and set to 82. The number of rows is fixed and set to 42. Interrupt/Pause disabled Home position is real-top Auto Output Snap is off - Rexx (0,50,160,128) the number of columns is set to a fixed value. This value is the maximum number of columns at the time the logical window is created. The number of rows is fixed and always set to 50. Interrupt/Pause disabled Home position is top-visible Auto Output Snap is off - PPrint (0,50,160,128) the number of columns is set to a fixed value. This value is the maximum number of columns at the time the logical window is created. The number of rows is fixed and always set to 50. Interrupt/Pause disabled Home position is top-visible Auto Output Snap is off To get the defaults : < prefs logwin debug <enter> > 00000052 , 82 > 0000002A , 42 > 000000A0 , 160 > 000000A0 , 160 To set other defaults : < prefs logwin debug 100 50 160 160 <enter> You need to quit PowerVisor and start it again to see the result of this command when applied to the 'Main' logical window. For all other logical windows you can simple close/open them to see the changes. You can also use the 'setflags' command to set the flags for a logical window immediatelly (also for 'Main'), and the 'colrow' command to set the ³number of columns and rows immediatelly. ===================== The default commandline length ========================= With 'prefs linelen' you can set or get the maximum length of the ²stringgadget commandline. This is also the maximum number of columns that may be used in ¹scripts (not ²ARexx scripts). The default is 400. Note that you loose 800 bytes with a linelength of 400 (always double). To get the default : < prefs linelen <enter> > 00000190 , 400 To set another value : < prefs linelen 1000 <enter> You need to quit PowerVisor and start it again to see the result of this command. ========================= Some debug preferences ============================= With 'prefs debug' you can set or get some preferences for the ¹debugger. The first argument is the ³number of instructions to disassemble after each ¹trace and the second argument is 0 or 1 if you want the disassemble the ²previous instruction (no or yes resp.) after each trace. The values set with this command are also used by the ²fullscreen debugger. Default is 5,1. This means 5 instructions and yes, disassemble the previous executed instruction too. < prefs debug <enter> > 00050001 , 327681 You can set other values using : < prefs debug 15 0 <enter> (15 instructions and no previous instruction) =============================== Debug mode =================================== Using 'prefs dmode' you can set the information that should be displayed after a trace. This parameter is not used by the ²fullscreen debugger since the fullscreen debugger always shows all information. You can set the following parameters : n show no info at all. This is useful when you are using the fullscreen debugger and you do not want to be disturbed by output on the current logical window r show only ¹registers c show only code (using the format describe in the previous section) f show registers and code (default) For example : < prefs dmode n <enter> ============================= Installing pens ================================ Every color you see on the PowerVisor screen or window can be changed. You can do this with the 'color' command. This command changes the RGB values for a color. The disadvantage is of course that this change affects all uses of that color. But don't worry, PowerVisor gives you the option to change virtually every color. This is because PowerVisor uses a pen array (the idea is stolen from AmigaDOS 2.0) to access each color. Using 'prefs pens' you can view or change this pen array. There are 32 ¹pens. The first 16 are for ²fancy screens (2 or more bitplane screens) and the last 16 are for 1 bitplane screens. The 16th pens for both the fancy and no-fancy screens are reserved for future use and are not displayed by this command. With no arguments this command lists all pens on two lines: the first line containing all pens for fancy screens and the second line for no-fancy screens. Here follow the currently defined pen numbers and there default color values. Add 16 to the pen number to get the no-fancy screen pen number : nr name default fancy default no-fancy ------------------------------------------------------------- 0 BoxBackground 0 0 1 LogWinBackground 0 0 2 NormalText 1 1 3 PrompText 1 1 4 StatusTextInActive 1 1 5 StatusTextActive 2 0 6 InActiveBar 0 0 7 ActiveBar 3 1 8 TopLeft3D 2 1 9 BottomRight3D 1 1 10 BoxLine 1 1 11 PositionBox 0 0 12 TopLeftBox 1 1 13 BottomRightBox 2 1 14 PositionIndicator 3 1 (To see the effect of pen changes you should open/close your windows first. For most pens the effect is immediatelly visible) The 'BoxBackground' pen is used to draw the background of a box (see the 'Screen' tutor file for more information about boxes). This pen color is usually the same as the 'LogWinBackground' pen explained below. If you insist on using another value you will see a small border in each of your logical windows. This small border will grow if you make the number of columns and lines in the logical window smaller than the visible size. The 'LogWinBackground' pen is the background pen used in a logical window. This pen is only used on places where characters CAN appear. This explains the small border that you see when you change the 'BoxBackground' pen. The small border is the region of the logical windows where no characters can appear. The 'NormalText' pen is used to print all text in logical windows. This pen should be different from 'LogWinBackground', otherwise you will see nothing. The 'PromptText' pen is used to print the prompt (the current list indicator). This pen should be different from 'BoxBackground', otherwise the prompt will be invisible. The 'StatusTextInActive' pen is used to print the name of the logical window in the logical window bar when the logical window is inactive (the active logical window is the window where you can scroll). The 'StatusTextActive' pen is used to print the name of the logical window in the logical window bar when the logical window is active. The 'InActiveBar' pen is used as background for the logical window bar when the logical window is inactive. This pen should be different from 'StatusTextInActive'. The 'ActiveBar' pen is used as background for the logical window bar when the logical window is active. This pen should be different from 'StatusTextActive'. The 'TopLeft3D' and 'BottomRight3D' pens are used for all 3D borders (at this moment only the border round the logical window bar uses these pens). The 'TopLeft3D' pen should be a light color and 'BottomRight3D' should be dark. This is to ensure the raised 3D effect of the border. The 'BoxLine' pen is used to draw the line between horizontally arranged logical windows. It should be different from 'BoxBackground'. The 'PositionBox' pen is used to draw the background of the position indicator at the right of the logical window bar. The 'TopLeftBox' and 'BottomRightBox' pens are used for the recessed 3D border round the position indicator. Note that this border is dithered when PowerVisor is in no-fancy mode. The 'PositionIndicator' pen is used for the little knob in the position indicator. This pen should be different from the 'PositionBox' pen. Example : < prefs pens <enter> > 0 0 1 1 1 2 0 3 2 1 1 0 1 2 3 > 0 0 1 1 1 0 0 1 1 1 1 0 1 1 1 Change the color of normal text to blue (or the color installed on color 3) : < prefs pens 2 3 <enter> ============================= The config file ================================ All parameters set with the 'mode' or 'prefs' command can be saved using the 'saveconfig' command. This command will create a file called ¹s:PowerVisor-config. If this file is not present when PowerVisor starts, the default values are used. Example : < saveconfig <enter> ======================= Other installation factors =========================== There are still other things that you can install. But these things are not saved in the s:PowerVisor-config file. If you want to set them automatically you'll have to include the right commands in the ¹s:PowerVisor-startup file. See the 'Scripts' tutor file for more information about scripts in general. =========================== Setting the colours ============================== With the 'color' command you can set the default ¹colours for the PowerVisor screen. Example, to get the ²3D colours used by ²Workbench 2.0 when you have opened PowerVisor on a ²2 bitplane screen you can use : < color 0 10 10 10 <enter> < color 1 0 0 0 <enter> < color 2 15 15 15 <enter> < color 3 6 7 9 <enter> If you use these values the 3D design (the ¹statusline) will be very nice. You can't use the 'color' command when PowerVisor is on another screen. ============================== Setting fonts ================================= Using the 'setfont' command you can use another ¹font for a ²logical window. See the 'Screen' chapter for more information. ========================= Setting alias commands ============================= Using the ¹¹'alias' command you can ³define other commands. See the 'CommandReference' file for more details. Some extra examples : < alias lfd 'loadfd [] fd:[]_lib.fd' <enter> You have defined a command 'lfd'. When you type something like : < lfd exec <enter> The command will be expanded and the following command will be executed : < loadfd exec fd:exec_lib.fd <enter> > ... This command loads an ¹fd-file in memory. < alias opwin '{openpw [] 0 0 300 200;openlw [] [] 80 40}' <enter> Defines an alias 'opwin' that opens a ²physical window and a ²logical window in this physical window. Another (stupid) example : If you use the group operator in the alias string, alias expansion will be done again. So you can use aliases in an alias allowing for recursive alias definitions. The following two commands define a new command 'fact' to compute the facultaty of its argument : < alias _fact 'void if(([])==1,1,{_fact ([])-1}*([]))' <enter> < alias fact 'disp {_fact []}' <enter> < fact 5 <enter> > 00000078 , 120 '_fact' is the ²recursive alias. 'fact' is only provided to give a more command like syntax. Note that this recursion is limited by both the available stack (PowerVisor will give an error when the end of the stack is getting close) and the maximum length of the commandline (you can increase this maximum length with the 'prefs' command). If you want to use [] in the string you can use quotes : < alias test 'print \\[\\]' <enter> The first ²string expansion leads to the definition of 'test' as the command 'print \[\]'. The expansion done by 'print' leads to the correct execution. ======================= Attaching commands to keys =========================== Using the 'attach' command you can ³³attach a command to a key. Example : To add the 'list' command to the <F1> key you can use : < attach 'list' 050 0 <enter> If you press <F1> 'list' is put on the stringgadget and an enter is simulated (this means that 'list' is also put in the history buffer). If you do not want the stringgadget to be disturbed you can use : < attach 'list' 050 0 e <enter> Some other examples : < attach '{pv 26 #{pv 12};pv 4;pv 5}' 046 32 e <enter> This command defines the <r-alt>+<del> key. When you press this key the command currently in the stringgadget will be deleted from the ²history buffer. The 'pv' command is a shorthand for 'pvcall' and this is a command normally only provided for ¹wizards (see the last section of this chapter). With 'remattach' you can remove ²key attachements. ============================= Logical windows ================================ Although there are already a lot of logical window parameters you can set with the 'prefs' command, there can be times that you need more. See the 'Screen' chapter to see how you can open logical and physical windows. Here is an example : This sequence of commands opens two extra logical and physical windows and ¹tile them in a certain fashion : Make the 'Main' physical window a ²non-backdrop window : < screen 0 <enter> Go to two bitplane mode and interlace : < mode fancy lace <enter> Open two physical windows and two logical windows : < openpw debug 0 0 500 200 <enter> < openpw rexx 500 0 140 200 <enter> < openlw debug debug 82 42 <enter> < openlw rexx rexx 80 40 <enter> Size the main physical window : < size main 640 200 <enter> < move main 0 200 <enter> ============================== And last ... ================================== And last for the maximum flexibility... the 'PVCALL' command ! Note that this command is not for the casual user. It is also not for the experienced PowerVisor user. It is for the PowerVisor ¹wizard :-) !!! See the 'TheWizardCorner' file if you think you are a wizard.