************************************************************

SiteMeter Release Version 4.0 README.TXT      08/31/93

************************************************************

SiteMeter Product Components

    Smruser.bat                     Chksw.com
    Cin.exe       v1.43             Dsw.com       v1.0
    Cout.exe      v1.43             Swatcher.com  v4.0
    Sitemetr.exe  v4.0              Bdiabout.dll  v1.02
    Slook.exe     v4.0              Bwcc.dll
    Smragent.exe  v4.0              Bwlib.dll     v1.04
    Sreport.exe   v4.0              Commdlg.dll   
    Swinapp.exe                     Ctl3d.dll
    Sysmod.exe    v1.0              Nwipxspx.dll  v1.31
    Usage.exe     v4.0              Nwnetapi.dll  v1.30
    Sitemetr.ncf                    Site_dos.hlp
    Sitemetr.nlm  v4.0              Sitemetr.hlp     
    Smrproxy.nlm  v4.0              Usage.hlp  
    Sitemetr.vap  v4.0              Readme.txt
    Sitemetr.msg                    

Install Components (necessary to run the Custom Installation 
from the network to add or remove the Swatcher option)

    Bdi16.bmp                       Install.ex$
    Disk_1.3                        Install.inf
    Disk_2.3                        Install.ins
    Disk_3.3                        Install.lgo
    Sitemetr.inf                    Install.lib
    Setup.exe                               

************************************************************

New & Improved in This Version!!

************************************************************

SiteMeter has a new Windows interface!

    SiteMeter 4.0 offers new features that streamline the 
    software monitoring and virus protection processes with 
    easy pull down menus and the Multiple Document Interface 
    (MDI) which allows for application usage tracking on 
    multiple file servers at the same time.

    SiteMeter offers new non-TSR methods for software metering 
    and virus protection to provide the best method suited for 
    your LAN.

The various metering methods available:

    SITEMETER PROXY NLM

    The SiteMeter Proxy NLM runs on a NetWare/386 file server, 
    does not consume additional workstation memory, and is the 
    least intrusive method of protection.  The Proxy NLM 
    intercepts DOS user requests for file access, checks for a
    permission/denial response from the SiteMeter NLM and acts 
    as messenger between the file server and the workstation.

    SITEMETER AGENT

    The SiteMeter Agent is a Windows-native device driver
    which performs the same tasks as the Proxy NLM, but for 
    Windows applications.  Agent is started from the load= line
    of WIN.INI, and is totally transparent to all users; no 
    icon appears on the desktop.  See the Installation section
    1.4 for more information on the SiteMeter Agent.
    
    SWATCHER and SWINAPP

    Swatcher is a TSR that interacts with the SiteMeter VAP/NLM
    to meter and virus protect the network.  With Swatcher you
    can automatically log out users who try to circumvent 
    SiteMeter, prevent users from executing software on their 
    local drives, and deny any access to local drives.  This 
    essentially makes your computers diskless.
    
    If you choose to use Swatcher for metering, SWINAPP will
    be loaded into Windows, instead of the SiteMeter Agent, to 
    meter Windows applications.  See the Installation section 
    1.4 to find out more about how this addition can be done 
    automatically.
    
    NOTE:  If you are running 286/NetWare, Swatcher must be
	   loaded. 
    
    NOTE:  If you do not plan on using the Proxy NLM, then you
	   must have Swatcher loaded.

Other New Features:
    
    The SiteMeter Administration program now gives you the 
    ability to purge the SITEDATA and VIRUSDTA files.

    You can now monitor users graphically through the Console menu
    of SiteMeter Administration.  This ability is also offered to 
    the users themselves with the stand-alone USAGE program.  
    These components allow you to determine who is currently using
    an application and who is queued or waiting for the software.
    The administrator has the capability to contact anyone in 
    either the current or queued users group via a Novell Send 
    Message through SiteMeter's menus.  
    
    The Network Administrator can edit the queued users list, 
    change license counts and queue back time quickly from the 
    usage monitor.

    SiteMeter is now compatible with Novell's NMS.  Please 
    contact Brightwork to find out more about Smart Launching 
    SiteMeter from within NMS.


******************************************************************

SiteMeter At A Glance

******************************************************************

 1.1  Installation 
       
      The installation process is now a standard Windows 
      procedure.  SiteMeter can be installed on any volume,
      in any subdirectory, as long as you have a drive 
      mapped correctly to the SYS: volume and your 
      destination server volume (if NOT the SYS: volume).  
      Mapped roots are not supported in the installation 
      procedure.  Please note that the Basic Install will 
      default SiteMeter's installation into the SYS:\SITEMETR
      directory.  You can change the destination by typing 
      over the text.
     
      Installation Requirements:

      Although Install will run with VIPX Version 1.10, it is
      highly recommended that your version of VIPX.386 be v1.13.

      IPXODI versions greater than 1.2 will not be recognized
      by the installation procedure but Install only issues a
      warning and will proceed.  SiteMeter 4.0 will run with 
      IPXODI versions 2.0 and above.
      
      Install creates a log file in the Windows directory, 
      gathers server information and checks the following for
      the configuration and the environment:

      Install Requirements                 Minimum Version
 
      NetWare                              2.2  or 3.x
      IPX                                  3.10
      NETX                                 3.26a
      NetWare Driver                       1.03
      CPU                                  386 
      Windows                              3.1
      Windows Mode                         Enhanced
      Memory                               2 MB 
					   (Windows requirement) 
      VIPX.386 (in user's system.ini)      1.10
      User Rights                          Supervisor
  
     
      If any of these configuration checks fail, the install is 
      aborted.

      The "default installation drive" is the first drive mapped 
      to the chosen server.

      To install, select File, Run from the Program Manager and 
      type the floppy source drive letter, a colon, and SETUP, or 
      open File Manager, choose the floppy source drive letter
      and select SETUP.EXE from the file list.

 1.2  Product Licensing 

      During installation you will be prompted for the product 
      serialization.  Enter the last 7 digits of the serial 
      number that is found on the installation diskette label.  
      Then enter the 8 character password which is listed below 
      the serial number.

 1.3  File Server Configuration

      NetWare version 286 
	 - copies Sitemetr.vap to SYS:\SYSTEM. 
	 - copies swatcher.com, dsw.com to SYS:\LOGIN
	 - copies Swinapp.exe to SYS:\PUBLIC 
      
      NetWare version 386 
	 - copies Sitemetr.nlm, Sitemetr.ncf, Smrproxy.nlm 
	   to SYS:\SYSTEM  
	 - backs up Autoexec.ncf as Autoexec.bdi 
	 - modifies the Autoexec.ncf file to add the statements:
	   Load sitemetr
	   Load smrproxy
	   These changes must be made to load SiteMeter upon
	   file server bootup.
	 
	 - creates SYS:\SYSTEM\SITEMETR
	 - copies Sitemetr.msg to SYS:\SYSTEM\SITEMETR
	   It is here that SiteMeter will create the SITEDATA
	   and VIRUSDTA files for reporting purposes.

	 - copies Sysmod.exe, Smruser.bat, Smragent.exe, 
           Nwnetapi.dll, Nwipxspx.dll to SYS:\PUBLIC

      Optional Technologies: Swatcher
	 - prompts user for option of using Swatcher
	 - copies swatcher.com, dsw.com to SYS:\LOGIN
	 - copies Swinapp.exe to SYS:\PUBLIC 
	 
 1.4  Workstation Configuration

      During the installation, Smruser.bat is modified according
      to the administrator's installation choices.  All
      necessary files are copied to SYS:\PUBLIC. Smruser.bat 
      should be executed from the system login script with either
      the INCLUDE or EXIT command.  View Smruser.bat at the 
      conclusion of the install to observe the modifications which
      will be made to the Win.ini, System.ini, and the
      Autoexec.bat files.  Each user must have a search drive
      mapping (for shared Windows) or local path statement (local
      drive Windows) pointing to their personal Windows directory
      in order for the Win.ini file to be accessed.

 1.5  Re-installation
       
      To re-install or reconfigure SiteMeter, run the SETUP 
      program from either the original installation diskettes or 
      from the network directory where SiteMeter resides, choosing
      the Custom option of your choice.  To move SiteMeter to 
      another file server, you must run COUT to uninstall the
      current license.

 1.6  Upgrading 
      
      If any of your older SiteLock files have been virus 
      protected, remove them from the authorized list before
      upgrading to SiteMeter 4.0.  Remember to change any RO
      (ReadOnly) flagged files to RW (ReadWrite) before 
      beginning the install procedure.  Also, turn the 'Run 
      Authorized Files' flag ON if it is OFF.

      If you have chosen to continue with our Wrapping
      Technology, the SiteMeter NLM can be made backwards
      compatible by loading the NLM with the -o flag. 

      Example:
      
      :LOAD SITEMETR -O
	
      SiteMeter will log in as the user SiteLock and be compatible
      with your wrapped files.    

Software Metering

 2.1  Directory Security Masks ( For NetWare/386 Only )

      OVERVIEW:

      SiteMeter v4.0 has the ability to grant special directory 
      security rights (i.e. Trustee Assignments) while choosing
      Metered Applications.  These applications will be granted 
      rights to specified directories only when those named 
      applications are executing.

      The following outlines some important points concerning 
      SiteMeter's Directory Security.

      USE GROUP INHERITANCE FOR CONTINUOUS RIGHTS INHERITANCE.
      If you have the need for a continuous "base" of rights in
      a directory affected by a secured directory definition, 
      you MUST define those rights via SYSCON's GROUP INHERITANCE
      (or similar mechanism).

      SYS:\WPDATA is a Secured Directory.  The base rights of 
      "F" (File scan) are required, but rather than defining 
      this right on a user by user basis use GROUP INHERITANCE
      (as activated via Novell's SYSCON or similiar utility).
      You would define a Novell GROUP with Trustee Assignments
      in SYS:\WPDATA of "F".  Add your USERS as members of this 
      GROUP so that they may be set up to receive their 
      directory rights via GROUP INHERITANCE.

      If different rights are granted to a specific user, those 
      rights will disappear the first time they use the Metered 
      Application that has directory security definitions for 
      the specified directory.

      SUPERVISOR EQUIVALENCE USERS ARE NOT AFFECTED BY DIRECTORY 
      SECURITY.  If a user with SUPERVISOR equivalence (as
      opposed to Supervisory rights in a particular directory) 
      uses the Metered Application, they will ALWAYS have all 
      rights at all times.  
      
      SPAWNED APPLICATIONS WILL NOT AUTOMATICALLY RECEIVE 
      SECURITY.  If you define trustee rights for an 
      application and that application spawns another (for 
      instance, a MENU system), the spawned application will not 
      automatically receive the directory security defined for 
      the calling application.  For the spawned application to 
      "inherit" the same rights, you must also define the 
      Directory Security specifically for that spawned application
      (this implies that it must also be set up as a Metered 
      Application).

      Example:

      Select Metering from the main menu, select Add or Modify
      an existing Metered Application.  Select the Directories
      button, choose a drive/directory, select OK. 

      You will now be presented with a Rights Available to
      Grant window. Select the rights you wish to grant during 
      the execution of the named Metered Application by selecting 
      that right and pressing the Include button.  

      You may enter up to 127 directories per Metered Application 
      for Directory Security.

      To change the rights mask, highlight the desired directory 
      path and select Modify Mask.  You will now be able to
      modify the rights as needed.

 2.2  Path Specific Metered Applications 

      You have the OPTION to specify a path when defining a
      metered application to meter multiple copies or versions
      of an application.  For example, if your Accounting 
      Department has ten copies of a wordprocessing package and
      the Sales Department has five copies, you may want to set
      up SiteMeter in the following manner:

      Metered Application: WP_ACT
      File Name: F:\Accounting\WP.EXE
      Maximum Number of Concurrent Users: 10

      Metered Application: WP_SALES
      File Name: F:\Sales\WP.EXE
      Maximum Number of Concurrent Users: 5

      You may use either drive letters (F:, Z:, etc.) or 
      volumes (SYS:, BIN:, etc.) in your path specification. If
      you do NOT specify a path when defining a metered 
      application, the software metering is in effect for ALL 
      files with the given filename. 

 2.3  Password Protected Metered Applications

      You can protect the settings of the metered application
      by assigning a password to the definition.  If a metered
      application is password protected, the Administrator
      must enter the correct password or the Supervisor's LOGIN 
      password to access the settings or to delete the metered 
      application definition.  To remove the password protection,
      the administrator can delete the metered application 
      definition and reenter it without specifying a password.

Graphical View Application Usage 

      You can see how applications are being used in graphic
      format.  Through the Multiple Document Interface (MDI)
      you can now monitor multiple file servers from one 
      administrative workstation.

 3.1  Improved Metered Application Maintenance

      You can access the Metered Application settings from the 
      Console, View Application Usage window even when people 
      are using the applications. For example, you have defined a 
      metered application for 3 concurrent users.  Three people 
      are currently using the program and one person is in the 
      queue. You can increase the maximum number of users to 4 
      by dragging the license count line to the right; a window 
      will appear to confirm your change and the queued user will
      be notified that a copy is available.  If you decrease the 
      maximum number of users (making it less than the current 
      number of active users by dragging the license count line
      to the left), no current users will be affected.  The new 
      setting will go into effect for all future users.

 3.2  Queue Manipulation  

      You can see a list of the users who are currently using the
      applications and those who are waiting in the queue for 
      software.  With supervisor rights, you can insert new users 
      into the queue or delete users from the queue.  You can
      also send messages to these users and view user information,
      including network address, connection ID, and network login 
      time.

 3.3  Active Monitoring 
     
      Application usage, and its non-supervisory equivalent,  
      USAGE.EXE, show who is using software in real time.  You
      can see changes as they occur through customizable, color-
      coded bars representing queued, current and peak users.  
      Queries are on user-defined timed intervals, and can be  
      activated by typing Ctrl-Q.

 3.4  Scale Control

      The graphical display can be shown with any scale desired.
      The user can specify a particular value, or the display can
      be autoscaled to your largest license count.
 
*****************************************************************

Helpful Hints Department

*****************************************************************

IMPORTANT!!  SiteMeter 4.0 is not compatible with NetWare 4.0 or
the NetWare 4.0 shells.  Please do not attempt to load the 
SiteMeter NLMs on a NetWare 4.0 server.

To Determine What Files To Meter

      If you are having trouble metering an application, and
      you have defined the application's .EXE file as the file
      to meter, the one you have chosen may not be the correct
      one.  By using the MONITOR console utility from your file
      server, (or from a workstation using RCONSOLE), you can 
      determine what files are being opened, and which files 
      stay open.  Enter Connection Information, choose a user
      and have that user open the troublesome application.  
      MONITOR displays all files that are opened and closed.   
      Meter the file that stays open throughout the user's
      whole session.

Using Virus Protection

      Be sure to select the files for File Authorization
      before setting the option to *NOT* allow Authorized Files
      to be run.  Include LOGIN.EXE, and COMMAND.COM at the very 
      least.  To run Windows, also authorize WIN.COM, WIN386.EXE, 
      KRNL386.EXE, GDI.EXE, USER.EXE, PROGMAN.EXE, and 
      SITEMETR.EXE.

      **CAUTION**  If you set up SiteMeter so that Authorized 
      Files are *NOT* allowed to run and no files have been 
      registered for File Authorization, you will not be able to 
      run ANY files on your network.  

      If you find yourself in this situation, unload the NLMs 
      from the server console and reload.  For Netware 286, 
      rename the VAP, down the server and reboot or run the
      Sitemetr.exe from a local drive.

Upgrading Your Novell Software

      This product was not regression tested with releases
      earlier than NetWare 2.2.
     
      Also, we recommend you upgrade to the latest supportable 
      shells and drivers released from Novell.
	 
NetWare FCONSOLE/MONITOR

      Do not use FCONSOLE or MONITOR to disconnect the users 
      SITEMETR and SMRPROXY. If you disconnect these users, 
      software metering and file authorization will be disabled.  
      In addition, an "Abend: Invalid Server Number" error may 
      occur and the fileserver will lock up.  If this occurs, 
      reboot the file server. 
 
      NOTE: When running SITEMETR.VAP, there will be TWO users
      logged in called SITEMETR.  Do not disconnect either of
      these two users.

SMRPROXY.NLM

      There are three values that can be set from the console
      prompt. 

      -e is the maximum size of the event queue.  If you 
      experience EVENT QUEUE IS FULL, EVENTS MISSED!! messages 
      at the file server console, reload Smrproxy with an -e 
      option.  The default event queue number is 5000.  If your
      network traffic is quite heavy, this number may need 
      increasing.

      -t represents a timeout value in which the shell will wait
      for a response from the SITEMETR.NLM.  A slow network, a 
      large number of authorized files, or a number of large
      authorized files may benefit from an increased -t option.
      The timeout default is 60000 or 60 seconds.  
      
      -l is the maximum locksets the queue will hold.  If your 
      user demand is high (ratio between license count and 
      application usage) increase this option (default is 100).  

      To change Smrproxy's values, at the console prompt type:

      :load smrproxy -t90000 -l500 -e7500.

Graphical Representation of Peak Users

      A definition of peak users:  the maximum total of current
      and queued users at any one time between queries is the
      "peak".  This figure reflects the true demand for any one 
      application over one viewing session's time.

      Here is an example.  Say Word is being metered with a 
      lockset of two.  Two users open Word, and quit, leaving 
      a peak of two.  Then, the lockset is changed to one.  The 
      same two users try to use Word again.  One succeeds, but 
      the other is queued.  After both are finished, the peak is
      still two, because there were never more than two users 
      attempting to use Word at once.  

      One note:  this definition may cause some interesting 
      effects in the usage screens.  One example: with a lockset
      of one and a peak of one, a user is placed on the queue by
      the administrator.   Because there is one user now, and the
      peak is one, the peak bar will disappear from the graph!  
      The display is still correct, however.  The peak is one, and
      the total of current and queued users is still at one.
   
Metering Lotus 1-2-3 applications
     
      To meter Lotus 1-2-3 applications use 123.EXE in the Metered
      Applications section.  With Lotus 1-2-3 for Windows meter 
      MAIN123W.EXE.
       
Metering WordPerfect applications

      To meter WordPerfect for Windows use the WPWINFIL.EXE file
      only in the Metered Applications section.  Metering both
      WP.EXE and WPWINFIL.EXE receives an ERROR 8: when exiting
      the application.  

Metering Freelance

      To meter Freelance for Windows use FLWMAIN.EXE.

Metering Harvard Graphics 3.0

      To meter Harvard Graphics 3.0 use HG3.EXE

Network Security Scans on Multi-Server Networks

      The network security scan, which ensures that all users have
      Swatcher loaded, will scan anyone either logged in to or
      ATTACHED to a given server.  One server cannot expel a user 
      from another server unless that user is attached to both 
      servers in some way.  This includes any CAPTUREs to print 
      queues, since a capture involves attaching to another 
      server as GUEST, a user subject to the security scan.  To 
      avoid these difficulties, GUEST may be included on the 
      Security Exceptions List (in the Security menu) or Swatcher 
      can be loaded on workstations using GUEST as a login.

Disabling Local File Execution
    
      If local file execution is disabled, attempting to run 
      Windows from a local drive will receive a message that says 
      "Invalid COMMAND.COM, system halted".  Also, COMMAND.COM
      may not be found if DOS needs to refresh itself in memory
      after running a sizeable application, or even during normal
      use. To avoid these problems, the environment variable
      COMSPEC must be set to a network copy of COMMAND.COM.  In 
      the login script, add the line:

      dos set COMSPEC="[path]"

      where [path] is the complete pathname of COMMAND.COM (for 
      example, f:\dos\command.com).
      
      A similar problem may occur with EMM386.EXE while starting 
      Windows.  To solve this, use the undocumented /Y switch in 
      CONFIG.SYS to point to a copy of EMM386.EXE on the network.  
      For example:

	DEVICE=EMM386.EXE RAM /Y=F:\DOS\V5.00\EMM386.EXE

Running SiteMeter from a Different Server

      If you install SiteMeter on one file server and try to run 
      SiteMeter from another file server that you have logged 
      into, you may receive a message that says "SiteMeter is not 
      installed on [current server]".  If this happens, highlight 
      SiteMeter's icon, and select File, Properties.  Then, make
      the Working Directory the one from which SiteMeter should 
      be mapped.  If no directory is specified, you may experience
      erratic behavior.

Using Swatcher.com

      You must load Swatcher AFTER loading IPX and NETx shells.
      This should be done from the AUTOEXEC.BAT file.

*****************************************************************

Using SiteMeter with Microsoft Windows

*****************************************************************

If you have chosen the SiteMeter Proxy method and Swatcher is not
loaded, SiteMeter requires a utility run from within Windows in
order to meter Windows applications.  This utility, called the
SiteMeter Agent, is loaded from each user's WIN.INI file
automatically.  Agent runs hidden in the background of each user's
desktop, and is customized to the unique ways that Windows
applications are opened and closed.

To meter Windows applications while loading Swatcher, SiteMeter 
depends on a different utility run from Windows, SWINAPP.EXE 
(short for Swatcher WINDOWS APPLICATION).  SWINAPP is also loaded
from the win.ini file.  Users will still need to load the
Swatcher TSR when they attach to the network. If you do not load
Swatcher before running Windows and SWINAPP is loaded from the 
Win.ini file, Windows will exit you back out to the DOS prompt.

Please refer to Chapter 4 of your SiteMeter Manual for
complete instructions for metering software under Windows.

NOTE:  The SiteMeter Agent will not load if it detects the 
       presence of Swatcher.  In this case, the Agent will
       report an "Error 9" in a dialog box and exit.  You 
       will not be returned to DOS, however.  To rectify 
       this, edit the WIN.INI file (as outlined below) in 
       Notepad, or your favorite text editor, and replace
       SMRAGENT.EXE with SWINAPP.EXE, or unload Swatcher 
       and re-run Windows.

     The batch file Smruser.bat, when included in the system login
     script, will automatically alter each user's WIN.INI file for
     you.  Here are some notes on manually editing WIN.INI if you 
     should choose to do so.

     Create (or edit) the LOAD statement under the [Windows] 
     section header within the WIN.INI file, so Swinapp or the 
     SiteMeter Agent will be loaded properly.

     1) SWINAPP.EXE or SMRAGENT.EXE must be in the Load statement 
	in order to meter Windows applications.
     2) Windows only recognizes the first LOAD statement it finds,
	so all files to be loaded must be included in one LOAD
	statement.
     3) Each filename should be separated with a space.  For 
	example: 
	
        The Swatcher (TSR) method:

	load=f:\public\SWINAPP.EXE NWPOPUP.EXE CLOCK.EXE
	
	OR

        Non-TSR method:

	load=NWPOPUP.EXE f:\public\SMRAGENT.EXE CALENDAR.EXE

	       ********CRITICAL NOTE!!!!*******

     When using SiteMeter and Microsoft Windows with NetWare
     versions 2.2 and 3.11, the group "EVERYONE" must have 
     read (R) and file scan (F) rights to SYS:PUBLIC in order 
     to access SWINAPP.EXE or SMRAGENT.EXE.


Known Problems

    With NetWare 2.2 using the VAP, active user names sometimes 
    appear twice in View application usage.

    Opening a metered file through File, Properties will cause 
    SiteMeter to incorrectly start metering that application.  One
    workaround is to edit the PROGMAN.INI under [Restrictions] and
    add the following line:  Editlevel=4.  This will disallow 
    anyone from editing the icon, but will allow it to be opened 
    for reading.

    Not using a full path when defining a Metered Application 
    that will be an iconized DOS application on a Windows user's 
    desktop may or may not meter.

    Files flagged as Execute-Only can not be authorized for file 
    integrity.

    Accounting must be turned off before SMRPROXY can log in.
    Turn accounting back on after the NLMs are loaded.

    These applications create unpredictable results when metered.

    R:BASE 3.1
    LapLink III
    Lotus 123 r3.1    

*****************************************************************

User Feedback Department

*****************************************************************

   Send written comments to:      Brightwork Development, Inc.
				  766 Shrewsbury Avenue
				  Tinton Falls, N.J. 07724

   Compuserve:                    Mail Box:   73500,1415
				  Forum:      go BRIGHT

   Internet:                      Customer_Service@Brightwork.com

   Or call our technical support  (908) 530-9650
   from 9:00 AM to 7:00 PM, 
   Monday - Friday, Eastern Time

   Or Fax comments to:            (908) 530-8867 (FAX)
******************************************************************

