home *** CD-ROM | disk | FTP | other *** search
- [Beta Release][19-Dec-96]
-
- AWACS 3.00
- Copyright (C)1997 Cornel Huth
-
- Part 1. Overview.
- Part 2. Files included.
- Part 3. Installation.
- Part 4. Command switches.
- Part 5. Tips and traps.
- Part 6. Registering.
-
-
- Part 1. Overview
- ----------------
-
- AWACS is a basic system state monitor for display to either a MDA (mono,
- digital) screen or to a PM window on the desktop (or both at the same
- time). Figure 1 shows a typical screen shot from the author's system.
- The monitor stations are:
-
- 1. Swap file size, and amount of swap used.
- 2. RAM installed and the amount: free, locked, and resident.
- 3. Working set desired and minimum memory needed to run that instant.
-
- The Swap used % is just that, the amount of used up swap file space. For
- RAM and working set, the % figure is relative to installed RAM. Requires
- AWACST2.DLL and THESEUS2.SYS. If an ISA-busmaster DASD controller is
- used (Adaptec 1542, for example) a message pops up indicating that only
- the first 16MB of memory will be used for user programs (unless the -noAbout
- is used). The memory above 16MB is then added to the Swap file size. This
- is the way OS/2 works, and it's determined by your .ADD driver.
-
-
- 4. AWACS control state:
-
- a. System status priority (LOW, MID, HIGH, HOLD) and check interval.
- b. Working set status priority (same as Sys) and check interval.
- c. Caller ID check priority (LOW, MID, HIGH, CLOSED) and check interval.
-
- The check interval is in seconds. The swap file is checked at an interval
- synchronized to the System interval (see -swapX: AWACS switch).
-
- The status priorities are thread priorities:
-
- Set CLASS LEVEL
- ---- ------- -----
- LOW idle 31
- MID normal 0
- HIGH critical 0
- HOLD idle 1 (CID is "CLSD", since the com port is closed)
-
-
- 5. CPU idle reserves.
-
- The more dots the less idle time is available. When pegged at 100%, this
- means that the CPU is busy all the time. This does not mean, necessarily
- that the computer will respond slowly. It only means that there's no idle
- time. For an accurate reading, no other pulse-like program should run at
- the same time as AWACS. If you were, for example, to run Warp's Pulse, the
- AWACS CPU idle reserve status would indicate 50% or so, as it should since
- there are now two idle+0 processes, each getting half the CPU (if nothing
- else significant is running). Warp's Pulse, however, is not so accurate.
- This pulse is in 1-second intervals and is on the same priority as "Sys".
-
-
- 6. A 24-hour clock, in large numerals.
-
-
- 7. COM port status line:
-
- This show the async device's state, in real-time. This requires COM40.SYS.
-
- The status line is available at any time, no matter which program has the
- com port open if an MDA (mono) screen is used; the status is updated
- directly by the async driver as it happens.
-
- If an MDA (mono) screen is not being used, the PM window can be still be
- updated every second if MONYiii.SYS has been installed with the -c
- MONY switch. If the mony driver is not installed, then the status line
- can only be monitored when AWACS has the port open, which limits the
- usefulness.
-
- Therefore, if COM40.SYS is installed, and:
-
- An MDA (mono) screen is used with the MONYiii.SYS driver, the COM status
- line is updated instantly no matter who owns the COM port begin monitored.
-
- If a PM window is used with the MONYiii.SYS driver installed using
- the -c MONY switch, the COM status line is updated within a second, no
- matter who owns the COM port begin monitored.
-
- If a PM window is used -without- the MONYiii.SYS driver installed,
- the COM status line is updated within a second, but only when AWACS owns
- the COM port.
-
-
- 8. Caller-ID:
-
- If your modem has a caller-ID feature, you can use AWACS to see who's calling.
- The top line is the most recent caller. Up to nine calls can be logged if
- the working set graphics is turned off (see -gc:0), or up to two calls if the
- graph is displayed. Not all calling areas provide caller-ID info (inbound
- or outbound). Contact your telco for details. When an incoming call is from
- an area that does not provide caller-ID, a "NOT AVAILABLE" is shown. If a
- caller blocks his caller-ID info, "NOT AVAIL/SNEAK" is shown.
-
-
- 9. Working set graphic:
-
- The last minute or so of the working set usage is logged. Use the included
- allocmem.exe program to watch how it works. The numbers along the right are
- the memory level, in MB. Amounts over 96MB are limited to the first 96MB.
-
-
- Figure 1: Typical Screen Shot on either MDA or PM Window.
- ┌─────────────────┬─────────────┬──────────────────────────────────────────────┐
- │Swap: 32768 │Sys· LOW 3.0│ COM2:02F8 115200 8N1 DCD · DSR CTS RTS DTR │
- │used: 0 ≈ 0%│Wks LOW 2.0│ FOYT A J (713)555-1212 12/19/96 07:45 │
- ├─────────────────┤CID LOW 1.0│ │
- │ RAM: 48768 ├─────────────┤ 48│
- │free: 26052 ≈ 53 │10 :: │ 42│
- │lckd: 284 ≈ 0 │ :: . │ 36│
- │rsdt: 5480 ≈ 11 │. : ::: :. . │ ::: 30│
- │ ├─────────────┤ ::: 24│
- ├─────────────────┤┌─┐┌─┐ ┌ ┌─┐│ ::: 18│
- │wMin 6412 ≈ 13%││ │ │:└─┼│ ││ :: ..::: 12│
- │wSet: 6900 ≈ 14 │└─┘ ┘ ┴└─┘│........::..........................:::::...06│
- └─────────────────┴─────────────┴──────────────────────────────────────────────┘
- AWACS 3.0 1 day, 08:56 Thu 19 Dec 1996
-
-
- The last line shows the version, OS running time (to 999 days) and the date.
-
-
-
- Part 2. Files included
- -----------------------
-
- The following files are included in this AWACS package. Specific installation
- instructions follow in the next part. This file you are reading is awacs.doc.
-
- 1. awacs.exe
-
- AWACS.EXE is the Warp 3 or later, PM executable. It provides a simple
- interface to set the priorities and interval times. All other settings are
- made on the command-line, or from a program object's Settings' entry for
- Parameters.
-
-
- 2. monyiii.sys
-
- MONYiii.SYS serves two functions: 1) it's an MDA (mono) screen driver, and
- 2) it provides an interface to the COM port status when using the PM window.
- See "Part 1. Overview", "7. COM port status line" for more. It is
- recommended that this be installed whether you have an MDA or not. If MDA
- (mono) hardware is not available, use the -c MONY switch.
-
-
- 3a. theseus2.sys
- 3b. awacst2.dll
-
- THESUES2.SYS and AWACST2.DLL handle the monitoring of the swap, system, and
- working set state. It is recommended that they be used. Both must be used
- together; rename AWACST2.DLL to awacst2.dxx if you do not intend to use them,
- or use both the -noSys and -noWks AWACS switches.
-
-
- 4. awacst32.dll
-
- AWACST32.DLL handles the PM window updating. If you intend to only use the
- MDA (mono) dispaly, this is not needed. Either rename it or use the -noVio
- AWACS switch.
-
-
- 5a. com40.sys
- 5b. vcom40.sys
-
- COM40.SYS handles the regular async duties (it is based on the Warp 4 COM.SYS
- driver) and adds caller-ID and com port status monitoring. VCOM40.SYS is a
- standard replacement for VCOM.SYS and adds no features.
-
- Even if you do not have a caller-ID modem, or caller-ID telco service, you can
- still use COM40.SYS to monitor the com port. See "Part 1. Overview", "7. COM
- port status line" for more.
-
-
- 6. monypage.exe
-
- Auxilliary program that is useful for programmers using a licensed version of
- the Mony MDA driver. It requires MONYiii.SYS. It's purpose is to switch to
- any of the up-to 8 mony video pages, or to disable the MDA (mono) screen.
-
-
- 7. allocmem.exe
-
- Auxilliary program that allocates, commits, then touches memory pages. Useful
- for exercising the working set analysis features.
-
-
- 8. zocevent.cm_
-
- A sample of using the -close and -open switches to control AWACS's com port
- use.
-
-
-
- Part 3. Installation
- ---------------------
-
- Copy AWACS.EXE to a directory in your PATH= statement. Also copy ALLOCMEM.EXE
- to the same directory (optional). \OS2\APPS\ is a good location, if it's in
- your PATH.
-
- Copy the AWACST2.DLL and AWACST32.DLL to a directory in your LIBPATH=
- statement. \OS2\APPS\DLL\ is a good location, if it's in your LIBPATH.
-
- Copy the four .SYS files to your boot drive's root directory. If any of these
- files already exist, save your old ones and use the ones provided in this
- package.
-
- If you want MDA (mono) screen support, or even if you don't, but you do want
- real-time COM port status monitoring, add the line:
-
- DEVICE=monyiii.sys [-p#] [-q] [-c] [-f]
-
- -p# is not required unless you plan on using AWACS on Mony page other than
- the default (page 0). This is not useful unless you have a Mony license
- and are using page 0 already (e.g., -p8).
-
- -q quiets the bootup message copyright.
-
- -c should be used if you do NOT have MDA hardware, but you do want the
- real-time COM status monitoring feature for your PM window.
-
- -f forces the MDA (mono) hardware to always be found. The Mony driver
- checks for MDA hardware by checking the MDA cursor. If for some reason
- the check fails (unlikely), -f may be used. Do not use it if you don't
- have an MDA.
-
- A typical config.sys entry would be
-
- DEVICE=G:\monyiii.sys -q (if you have MDA hardware)
-
- or, DEVICE=G:\monyiii.sys -q -c (if you do NOT have MDA hardware)
-
-
- Add this entry to config.sys:
-
- DEVICE=G:\THESEUS2.SYS
-
-
- First, find your current async drivers. They most likely will be named
- COM.SYS and VCOM.SYS. Comment their lines out and directly below each,
- put the new ones in. Be sure your MOUSE drivers come before.
-
- DEVICE=G:\OS2\BOOT\MOUSE.SYS SERIAL=COM1
- DEVICE=G:\OS2\MDOS\VMOUSE.SYS
-
- ...
-
- rem rem DEVICE=G:\OS2\BOOT\COM.SYS
- DEVICE=G:\COM40.SYS
-
- ...
-
- rem rem DEVICE=G:\OS2\MDOS\VCOM.SYS
- DEVICE=G:\VCOM40.SYS
-
-
-
- In order for these new files to be loaded, you have to reboot. Be sure to have
- an OS/2 boot floppy nearby with an editor available in case you have to re-edit
- you CONFIG.SYS file if, for whatever reason, your system no longer boots.
- After the reboot, you are ready to start up AWACS.
-
- AWACS' default state is for just about everything to be OFF. You can control
- everything from command-line parameters, covered in the next part. The PM
- control box lets you adjust priorities and intervals, and you can reset the
- working-set and caller-ID sub-systems.
-
-
- Note: The PM window has a title bar and a minimize button, but these are
- obscured. To move the PM window, grab where the title bar would be and
- drag the PM window about. To minimize it, push where the minimize button
- would be. To restore the PM window, select the AWACS control box and click
- anywhere on the control box (except the title bar line).
-
-
-
- Part 4. Command swiches
- ------------------------
-
- It's recommended that you create a program object so that you can start up
- AWACS with just the click-click of a mouse button. To do this, open up the
- TEMPLATES folder and drag a Program object onto the desktop. The Settings
- page pops up. Fill out the path. For the Parameter entries, consult the
- following. An example would be something like:
-
- -com2 -bell -sys:3L -wks:2L -cid:1L -swapX:5 -cHeight:8
-
- If you have MDA hardware, you probably want to add -noVio, and use -cls.
- After a while you'll probably want to use -min and -noAbout.
-
- -cHeight:n Specifies the PM window character size. For 1024x768
- displays, the default is fine (8). For 640x480, a
- cell height of 14 is about right. If you see "white"
- space below the PM window's background, you need to
- increase the cHeight value; if some lines are chopped
- off, you need to decrease it. See Figure 1. for how
- the full display appears. The range for n is 6 to 32.
- For example: -cHeight:14
-
- -com# Specifies com port to use for both monitoring and CID use com0
- to disable monitor and any CID (the default is disabled). For
- example, -com2 (no colon).
-
- -istr:aaa Specifies init string for caller ID, raw format.
- The default is -istr:AT#CID=2
-
- -bell Sound bell on CID.
-
- -noSys Disable performance monitoring ("Sys" becomes ghosted).
-
- -noWks Disable working set analysis ("Wks" becomes ghosted).
-
- Note: If both -noSys and noWks are specified. AWACST2.DLL is not loaded.
- Swap file stats are also disabled if -noSys.
-
- -noCID Disables caller ID monitoring ("CID" becomes ghosted).
-
- -noPulse Disables pulse graphic.
-
- -sys:TP T=1 to 9 secs, P=h,l,m,x for hold, low, medium,
- time-critical priority for System monitoring. Finer
- timing is available from the PM control box. For
- example, -sys:3L
-
- -wks:TP As -sys:TP
-
- -cid:TP As -sys:TP, except hold results in closed com port if hold
- is true longer than 1.5 seconds
-
- -gc:n If n is 0, working set graphic is disabled and caller ID
- logging extends to 9 entries (rather than 2). If n is 1
- (default), graphic uses . and : for markers. If n is 2,
- block/half-block are used. For example, -gc:0
-
- -rst:ddd ddd is the working set calls to do before resetting. The
- default is 120. No real need to change this, but the limit
- is 250.
-
- -page:n The Mony (with MDA hardware) page to use for display. n=0-7,
- but must be valid mony page from DEVICE=monyiii.sys -pn. This
- page is 0-based, wherease DEVICE= line is 1-based. No effect
- on PM window. For example, -page:0 (the default).
-
- -cls Clears the MDA (mono) screen on startup. No effect on PM
- window.
-
- -noAbout Skips driver versions' box at startup; also skips ISA/16MB
- busmaster driver limit notice (if applicable).
-
- -min Start the PM control box minimized.
-
- -swapX:n Rate at which the swap file status is check relative the "Sys"
- rate. The default is 2 (swap checked every other "Sys" check.
- n=1 to 99, where n=1 causes a swap-check at every system check,
- n=2 (default) every other system check.
-
- -bg:n PM window background color, n=0 to 15, default=0 (black).
-
- -fg:n PM window foreground color, n=0 to 15, default=6, yellow).
-
- -hi:n PM window intense color, n=0 to 15, default=14, bright yellow).
-
- -noMony Do not use the Mony MDA hardware. Useful only if MDA is
- actually installed.
-
- -noVio Do not use the PM window. Also causes the AWACST32.DLL to
- not be loaded.
-
- Note: Using both -noMony and -noVio results in no display. Not very useful.
-
- -minVio Start PM window minimized.
-
- Note: The PM window has a title bar and a minimize button, but these are
- obscured. To move the PM window, grab where the title bar would be and
- drag the PM window about. To minimize it, push where the minimize button
- would be. To restore the PM window, select the AWACS control box and click
- anywhere on the control box (except the title bar line).
-
-
- AWACS only runs one instance of itself. Additional attempts just exit unless
- one of the following, mutually-exclusive switches are used:
-
- -close Closes the open com port (see the included zocevent.cm_ file).
-
- -open Re-opens the previously-closed com port (see same file).
-
- -exit Exit AWACS.
-
-
-
- 5. Tips and Traps
- ------------------
-
- 1. If you are in other than 1024x768 the PM window may not appear to
- fill the display properly. Use -cHeight:14 for 640x480. The range is
- from 6 to 32.
-
- 2. The working set analysis can use up lots of CPU time. or more specifically,
- keep interrupts off for longer than you'd like. If you have problems
- downloading files (get CRC error, for example), consider turning Wks to HOLD
- while downloading. The more main memory you have, the more work needs to be
- done. Also, the more active processes, the more work needed. However, if
- you have a very fast CPU, or not a lot of memory (32MB or less), you may not
- notice.
-
- 3. If you use LOW priority (as I almost always do), you may notice that when
- the CPU is really busy, AWACS appears to stop. It stops, indeed, because LOW
- priority is the same as idle, and if there's no idle time, AWACS just doesn't
- get any timeslices. If this is a problem, for example, you need to monitor a
- heavy CPU-use process, just bump up the priority to MID or HIGH. Another
- possibility is to set PRIORITY=ABSOLUTE in CONFIG.SYS (for this to make a
- difference, you still need to use MID or HIGH). You may also want to reduce
- the interval: 1.0 seconds is the lowest. I use Sys:3L, Wks:2L, CID:1L and
- SwapX:5 most of the time.
-
- 4. If the Pulse seems to no longer respond, except in drastic changes (0%
- most of the time, but if you move a big window, then 30%, but just for a
- second), then you just exit and restart AWACS. I've seen it, though it
- doesn't happen often.
-
-
-
- 6. Registration
- ----------------
-
- Why register? Because if you don't, you can only use AWACS for 30 minutes at
- a time, and only for the first 2 hours after booting. If you want to
- get rid of those time limits you need to register. The cost is $17.50 plus
- $2.50 shipping and handling. Payment may be check, money-order, or cash.
- Payment must be in US funds drawn on a US bank. Send $20 to:
-
- Cornel Huth
- 6402 Ingram Rd
- San Antonio TX 78238
- USA
-
- Questions on registering? Contact info@40th.com or call the 40th Floor BBS
- at 1(210)684-8065. If you have registered AWACS 1.x already (before 1997)
- contact me and I'll get you a free 3.0 registration. For those that only
- need an MDA (mono) version, AWACS 2.10 is still available at no cost (at most
- OS/2 BBSes and internet sites). Sorry, no credit cards (it's only $20!).
-
- ^A
-