home *** CD-ROM | disk | FTP | other *** search
- #
- # Default .newpoprc file for NewPop v4.0.
- # Started: Fri Jan 18 20:44:29 1991 Loren J. Rittle
- # Last Update: Wed Apr 24 01:00:26 1991 Loren J. Rittle
- #
- # NewPop searches for this file at startup time in the
- # following directories, in order: Current Directory, S: Directory.
- # If found, NewPop processes the file and then starts running unless
- # any parse error whatsoever occurs! These setting override compile
- # time options. Command line options are now considered obsolete
- # and are no longer used.
- #
- # All error messages are of the form:
- # NewPop: parse error on line 112 of .newpoprc
- #
- # It is up to you (in this release) to determine the exact error
- # on the given line. A parse error could be as simple as a
- # bad value or misspelled keyword. Or, it could be as complex
- # as a value out of range. Basically, there are limits on
- # what values NewPop is willing to accept for a given integer
- # parameter and NewPop does a sanity check on the values in this
- # configuration file. If it is out of range you get the generic
- # error message stating which line has the error. Also of note,
- # strings have a maximum length; if your string exceeds the length
- # the you get the generic error message. This will be fixed in the
- # future, perhaps. Or it *could* be a bug in NewPop's parser :-).
- #
- # Random notes:
- # Some people didn't figure this out in the first release:
- # You can and are supposed to edit this file to taste, it will be
- # read in at startup time and overrides all hard coded values in
- # the NewPop binary. This allows people without C compilers to
- # modify how NewPop works. Some people thought that it was somehow
- # used at compile time... Nope, it is only looked at at runtime.
- #
- # Only changes to the [hard coded] defaults need be listed here, in any
- # order. If you received this .newpoprc file in its original form
- # (as you are supposed too!), then all settings listed in this file ARE
- # the hard coded defaults and can be safely removed. It only takes a
- # little time to read this file at startup time, so why not keep every
- # option listed here...
- #
- # Comment lines must start with a pound sign. Option names can appear
- # in any case. Blank lines are permitted. Any amount of white space
- # may precede option names and the pound sign of a comment line. Also,
- # any amount of white space may trail an option's value. A comment
- # may start after an option's value appears (There must be a bit of
- # white space after the value and before the pound sign).
- # Finally, note that some options have no meaning if other
- # options are turned off, it is not an error to set a value
- # for an option that is turned off. For example, WEWANTWINDOWDRAG
- # is meaningless if NEWPOPLITE is set to TRUE, and BLANKERPRIORITY
- # has no meaning if NICENEWPOP is set to FALSE, etc.
- #
- # Boolean options must be set to ON, OFF, TRUE or FALSE (in any case).
- # Boolean options are: NICENEWPOP NEWPOPLITE WEWANTWINDOWDRAG LOCK
- # HIDEWBINFO BACKDROPWINDOW WIMPYCLOCK
- #
- # Integer options must be in decimal with no intra-number spaces.
- # Integer options are: MAXSCSIUSAGE SCSIIOMONWIDTH CPULOADMONWIDTH
- # MEMORYMONWIDTH GAPBETWEEN3 GAPBETWEEN2 GAPBETWEEN FONTSIZE
- # STARTYOFFSET MAXTEXTWIDTH STARTXOFFSET WINDOWHEIGHT TIMEOUT
- # POPKEY BLANKERPRIORITY ULC LLC LRC URC INSTANTKEY DEFEATKEY
- #
- # Strings options must begin and end with double quote marks.
- # String options are: SCSITASKNAME FONTNAME COMMAND PASSWORD
- # No double quotes or newlines are allowed in strings, but spaces
- # are allowed.
- #
- # PS: Comments are parsed fast, so don't delete these comments!
- # Or, if you must, save a backup of this file and strip the
- # comments out of the copy that will be used (i.e the one
- # in the s: directory). - LJR
- #
- # The only comment from the source code that you all must see:
- # * LJR recoded the entire thing to allow dynamic (at startup
- # * time) configuration instead of hardcoded compile time
- # * configuration. This added many (2.5K) bytes! Why did I
- # * do it? Because my public asked for it. Will I ever get
- # * a pizza out of this deal? YOW 1/27/90.
- #
-
-
- # If NICENEWPOP is set to TRUE then we use a detached task, with a
- # priority of BLANKERPRIORITY [default -20], method for drawing the Q*X
- # pattern. We give it a boost to priority 10 once every second, so it
- # will keep moving, even if other user tasks are hogging the system, most
- # likely with good reason. This will lessen the overhead the NewPop
- # blanker imposes upon the system, but the Q*X will look like it is
- # running on a Mac, PC or UNIX box if CPU-bound tasks (with a priority
- # greater than BLANKERPRIORITY) are running. :-)
- #
- # With NICENEWPOP set to FALSE, the graphic code will run under the
- # NewPop process. With an '030 Amiga the overhead for updating the
- # Q*X lines is very small and you should not need this as NewPop
- # tries to be nice to the system by only changing one line per
- # 1/60 of a second anyways. BLANKERPRIORITY is unused in this
- # configuration.
-
- NICENEWPOP TRUE
- BLANKERPRIORITY -20
-
-
- # John, this option is for you!
- # NEWPOPLITE, if TRUE, makes a small, features wise,
- # version on newpop. Leaves only timed screen blanking,
- # instant-blanking, defeat-blanking and popcli features.
- # A few local people wanted this. :-)
- #
- # Note you now need to set POPKEY to 0 to turn the PopCli feature
- # off. In the past, NEWPOPLITE would do this by default.
-
- NEWPOPLITE FALSE
-
-
- # TIMEOUT is the time, in seconds, before the screen blanker kicks in.
- # Set TIMEOUT to 0 to disable the timed screen blanking feature.
-
- TIMEOUT 180
-
-
- # INSTANTKEY and DEFEATKEY control which key, if any, invokes the
- # instant-blanking and defeat-blanking features.
- # Tap the INSTANTKEY (while holding down the left Amiga key)
- # once to turn on instant-blanking and then again to turn it off (i.e.
- # it acts as a toggle). Defeat-blanking will always be turned off
- # when the INSTANTKEY is hit. The above works the same for DEFEATKEY.
- # Any mouse move whatsoever, resets all blanking features to what they
- # should be based upon the current pointer position...
- #
- # Note that to be compatible with past releases of NewPop, INSTANTKEY and
- # DEFEATKEY are off by default. Set them to some non-zero value to enable
- # instant/defeat blanking hot keys. Note the raw key code for F1 is 80 and
- # F2's code is 81. NewPop will not check to make sure that there are no
- # conflicts between your choices for POPKEY, INSTANTKEY and DEFEATKEY, but
- # no harm will come if they overlap.
-
- INSTANTKEY 0 # 0 means OFF! To be compatible with old
- # releases, the default is off!
- # I use F1 - code 80
- DEFEATKEY 0 # See above. You must manually change 0 to 81
- # (or whatever) to turn the feature on.
- # I use F2 - code 81
-
-
- # Aris B. and John C., these options are for you!
- # ULC, LLC, LRC, URC tell NewPop what to do when the mouse
- # pointer enters the respectively; upper left, lower left, lower
- # right and upper right corners of the screen. 0 means do nothing,
- # 1 means instant-blank, 2 means defeat-blank.
- #
- # Using these options one can turn off all pointer related
- # instant- and defeat-blanking by setting them all to 0.
- # As shipped, NewPop v3.x functions as v3.[0-2] did, i.e., the lower
- # right corner invokes defeat-blanking and the upper right corner
- # invokes instant-blanking.
-
- ULC 0
- LLC 0
- LRC 2
- URC 1
-
-
- # POPKEY defines the raw key code needed with left Amiga in order to pop
- # a cli. Be default, escape (Raw Key Code 69) is the POPKEY. COMMAND is
- # the command string NewPop will execute upon seeing the pop key.
- # Set POPKEY to 0 to turn off the PopCli feature. Of course, COMMAND is
- # never used if POPKEY is set to 0.
-
- POPKEY 69
- COMMAND "NEWCLI >NIL:"
-
-
- # MEMORYMONWIDTH is the number of pixels wide the memory monitor (the
- # far left one) should be. GAPBETWEEN3 is the number of pixels between
- # the end of the disk I/O monitor and the start of the memory meter.
- # Set MEMORYMONWIDTH to 0 to turn the memory meter off. With no memory
- # monitor, GAPBETWEEN3 is set (by NewPop) to 0 also. Note the memory
- # monitor is off by default to stay compatible with older releases.
-
- MEMORYMONWIDTH 0 # 100 -are good values...
- GAPBETWEEN3 0 # 16 /
-
-
- # SCSITASKNAME is the name of the task to monitor SCSI I/O for.
- # Warning: this feature might not work with all SCSI device drivers,
- # all I can say is that if you have any problem, don't use this feature!
- # gvpscsi.device is the GVP Impact II controller SCSI device driver name.
- # scsidev.device is the GVP Impact I device driver name.
- # "SCSI bus handler" is the name of the A3000 device driver. Don't use
- # scsi.device!
- #
- # MAXSCSIUSAGE should be set to the maximum number of times the named
- # device will be dispatched per second under the heaviest of SCSI I/O
- # loads. 80 worked good for my GVP '030 based non-DMA GVP Impact I
- # system. 55 works good for my GVP '030 based DMA GVP Impact II system.
- # I have no idea what is good for other systems. DMA based controllers
- # would, I would guess, be better off with a smaller MAXSCSIUSAGE value
- # as less task switching would, in theory at least, be needed to
- # transfer data over the SCSI bus.
- #
- # Note: I added a bit of debugging code to find this value by trial and
- # error. You can perform the same trial and error method by running
- # NewPop, if the I/O graph never peaks then lower MAXSCSIUSAGE. If it
- # peaks to often then raise MAXSCSIUSAGE.
- #
- # SCSIIOMONWIDTH is the number of pixels wide the SCSI I/O monitor (the
- # middle one) should be. GAPBETWEEN2 is the number of pixels between
- # the end of the CPU load monitor and the start of SCSI I/O monitor.
- # Set SCSIIOMONWIDTH to 0 to turn the SCSI I/O monitor off. GAPBETWEEN2
- # is set to 0 (by NewPop), if the SCSI I/O monitor is turned off.
-
- SCSITASKNAME "gvpscsi.device"
- MAXSCSIUSAGE 55
- SCSIIOMONWIDTH 100
- GAPBETWEEN2 16
-
-
- # CPULOADMONWIDTH is the number of pixels wide the CPU load monitor
- # (the far right one) should be. GAPBETWEEN is the number of pixels
- # between the time and the start of the load monitor. Set CPULOADMONWIDTH
- # to 0 to turn off the CPU load monitor. GAPBETWEEN is also set to 0
- # (by NewPop), if the CPULOADMONWIDTH monitor is turned off.
-
- CPULOADMONWIDTH 100
- GAPBETWEEN 16
-
-
- # FONTNAME is the name of the font to use for the title bar clock at size
- # FONTSIZE. Note that you must add '.font' to the name.
- #
- # STARTYOFFSET is how far down the baseline of the date should be from
- # the top of the window. If FONTNAME, FONTSIZE or WINDOWHEIGHT is
- # changed then play with this number until the date looks right :-).
- # It should be about:
- # WINDOWHEIGHT - ((WINDOWHEIGHT - font_height_in_pixels(not FONTSIZE!))/2).
- # For example ``Helvetica'' size 9 is 6 pixels high! Go figure.
- #
- # MAXTEXTWIDTH is the maximum value that the TextLength function
- # can return for all possible dates! For fixed fonts
- # MAXTEXTWIDTH is just horizontal_character_size_in_pixels * 24.
- # Newpop supports proportional fonts, you just have to do
- # a little leg work to figure this number out for them.
- # To find this number, run CalcTextWidth (included) and answer
- # the questions it asks, this parameter will pop out! :-)
- #
- # If WIMPYCLOCK is set to TRUE, then a 12 hour clock is displayed,
- # else a 24 clock is used.
- #
- # Set MAXTEXTWIDTH to 0 to turn off the titlebar clock.
-
- FONTNAME "Helvetica.font"
- FONTSIZE 9
- MAXTEXTWIDTH 107
- STARTYOFFSET 7
- WIMPYCLOCK FALSE
-
-
- # STARTXOFFSET is the distance from the right edge of the titlebar
- # window to the right edge of the workbench screen. 56 leaves both
- # screen gadgets uncovered under 1.3 and below.
- # Change if more gadgets are ever added to WBScreen, or
- # in 2.0's case, you may actually want to lower this number!
- #
- # WINDOWHEIGHT should, most likely, be the (real WB) titlebar height - 3.
- # I know under 2.0 that all bets are off as to it's real height,
- # thus for now it is hard coded. Once I get 2.0, all this
- # will be fixed up. Be careful setting this! (Should be 8, for
- # standard 1.3 and below system)
- #
- # BACKDROPWINDOW tells NewPop whether or not a BACKDROPWINDOW window
- # should be used for the titlebar window. The default is TRUE to stay
- # compatible with past releases, plus I like it that way :-).
- #
- # Set WEWANTWINDOWDRAG to TRUE if you want to be able to move the
- # titlebar clock window in the standard click drag release way.
- # If FALSE, the window stays put when clicked! NewPop's clock, etc
- # was designed to be a titlebar clock, but some people might
- # want this feature...
- #
- # The boolean option HIDEWBINFO allows one to specify whether or not the
- # space after `Workbench Screen' up to the start of the titlebar monitors
- # should always be covered by NewPop's titlebar window, thus hiding those
- # nasty WB memory free statements. The default is off to stay compatible
- # with NewPop v3.x.
-
- STARTXOFFSET 56
- WINDOWHEIGHT 8
- BACKDROPWINDOW TRUE
- WEWANTWINDOWDRAG FALSE
- #HIDEWBINFO FALSE #not yet implemented
-
-
- # If LOCK is set to TRUE then PASSWORD refers to the only word which
- # NewPop will accept to stop blanking. "Amiga" is the default password.
- # Note that the case of the password is important.
- #
- # If LOCK is set to FALSE then no protection to stop people from
- # unblanking is implemented and PASSWORD is ignored.
- #
- # The req.library must be present for this to work! If not present,
- # then all LOCK related stuff *will* *not* function, but it will not
- # function gracefully :-).
-
- LOCK FALSE
- PASSWORD "Amiga"
-