

		Brightwork Fusion 1.0 2/15/94
				  READ ME
	    *****************************************************        
This README.TXT file contains information on LAI 3.1,
the integrated Fusion product, and SiteMeter 4.01.  To skip 
ahead to the information that pertains solely to SiteMeter, please 
search for the string "begin_meter" .
*************************************
1. Technical Specifications
*************************************

  1.1   Compatible with NetWare 2.2, and 3.xx.

  1.2   The Fusion 1.xx console PC must have MS/PC DOS 3.3 (or 
	later), a *minimum* of 4Mb installed RAM, and be capable 
	of running Microsoft Windows 3.1x in Enhanced Mode.  
	Fusion 1.xx also requires a mouse.

	Please Note:    The Fusion console (and install program) 
	only supports Windows 3.1x in Enhanced Mode.  Windows 
	3.0x is not supported.

  1.3   A *minimum* of 12mb of local or fileserver disk space is 
	required to install the Fusion 1.0 program files and 
	databases.  Additional space is required for upgrading 
	from previous versions of LAI or SiteMeter.

  1.4   If you are using DOS v6.0 please use NETX v3.32.

  1.5   If you are using server based Btrieve, you must use 
	BREQUEST ver. 6.1 or higher.  Because of Novell licensing 
	restrictions, we are not able to ship BREQUEST.EXE.  
	However, the file is available in the Novell Libraries 
	on Compuserve, and can be downloaded from:

		    Forum:      GO NOVLIB
		    Section:    Library 7
		    Filename:   BTRREQ.ZIP  (69760 bytes)

	After downloading, set up a separate directory to unzip 
	BTRREQ.ZIP into.  Then copy BREQUEST.EXE to your Fusion 
	directory.

	The latest Novell drivers can also be obtained on Compuserve:

		    Forum:        GO NOVFILES

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

		
*************************************
2. Installation Requirements 
*************************************

  2.1   Notes on upgrading from LAI:

	If you plan on upgrading your installed copy of LAI, 
	please consider the following before proceeding:

	(a) Disk space requirements:  make sure that you have 
	    enough available space on your network (or local) 
	    drive.  A pretty good rule-of-thumb is that you will 
	    require at least 4 times the space that is currently 
	    being occupied by your copy of LAI.  Use the VOLINFO, 
	    CHKDIR, or CHKVOL commands to determine your available 
	    space.

	(b) Time:   The routine to convert your LAI data can take 
	    quite a bit of time to complete.  Depending on a lot 
	    of variables, the conversion routine can require from 
	    1 to 6 hours -- possibly more, if your existing LAI 
	    2.xx directory is greater than 9 Mb in size.  Given 
	    this, you may want to dedicate a PC to the task of 
	    converting from your existing LAI installation. 
	    
	(c) Workstation Environmental Precautions: IF YOU ARE NOT 
	    USING v1.13 of VIPX.386, MAKE sure that IPX/SPX (or 
	    IPXODI) is not loaded into high memory BEFORE you begin 
	    the UPGRADE.

	(d) PC Software List:  Fusion 1.0 includes an updated PC 
	    Software list that provides improved identification of 
	    installed applications on your network.  During the 
	    upgrade installation you have the option of using the new 
	    list, or preserving your old list. Brightwork HIGHLY 
	    recommends using the new list for the most complete and 
	    accurate identification of software packages. 
		 
							
  2.2    NetWare Global Naming Service
	 If you are using the NetWare Naming Service, place EQUIP 
	 in the PROFILE login script.  EQUIP will not run from 
	 the DOMAIN login script.


************************************* 
3. Fusion 1.0 Installation 
*************************************

  3.1   "Whoami":

	You must login as Supervisor or equivalent in order to 
	install Fusion.

  3.2   Installation:

	Insert install disk #1 into drive A: or B:.  Start 
	Windows as you normally do. In Program Manager, select 
	Run from the File menu. The file to execute is SETUP.EXE, 
	located on install disk #1. You can either Browse to 
	select the file, or type "<floppy drive>:\setup.exe".  
	Once SETUP begins to execute, follow the instructions 
	on the screen.

  3.3  "Installation Reminders":

	During the initial stages of the install, an "Information"
	box will be displayed. The message will be: 

	    "-MAP ROOT drives are not permitted for the install
	    target"

	    "You MUST have a mapping to the SYS: Volume of the 
	    target server to install."

	This message is intended to be informational only. It 
	will always be displayed during the initial stage of the 
	install. It does not mean that the install has encountered 
	an error.  Its intent is to inform the user that Novell 
	drives that are MAP ROOTed *may* not be recognized by 
	the install -- which *could* eventually precipitate 
	errors such as "file not found" or "error decompressing 
	<filename>" during the course of the installation.

	As a precaution, make sure that the drive that is mapped 
	to the Fusion directory (or mapped to the volume that 
	contains the Fusion directory) is a straight MAP (not a 
	MAP ROOT).  If your copy of Windows is installed on a 
	network drive, make sure that both the Windows directory 
	on the network and the directory that contains your 
	".INI" files are straight MAPs.

	Install needs to be able to find the SYS: volume to install
	smrproxy.nlm,sitemtr.nlm, sitemtr.ncf and to make changes 
	to the autoexec.ncf.  Make sure that you have a mapping 
	to your SYS: volume before you begin the installation.
	
	If you need to break out of the install to make these 
	changes, simply click on OK in the  warning box, 
	then click on the EXIT button located in the lower right 
	hand corner of the Install's main screen.

  3.5   Product Serialization:

	During the installation, you will be asked to perform the 
	"product serialization".  You'll be prompted to enter the 
	last 7 digits of your Fusion serial number.  This number 
	can be found on the installation diskette(s) label(s).  
	You will then be asked for an 8 character password --
	this is also listed on the disk label(s).

	Three executables will be serialized during the install 
	process. Those files are fusion.exe, usage.exe and 
	sreport.exe. You will see the serializing and stamping 
	product popup windows three times during the installation.

3.6     File Server Configuration for Metering:

	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 

3.7     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.

3.8     Fusion.ini

	The FUSION.INI file is created in the Windows directory of the
	PC that runs Fusion.  Two sections may be added to the file to 
	allow the user to "downgrade" the version of Fusion that is 
	installed even if a full version of Fusion is installed on
	the fileserver.

	The sections that may be added are:

	     [Downgrade]
	     Module=Inventory

	The next time that Fusion is launched on that PC only the 
	inventory module of Fusion will be available and visible
	to that user.

	      [Downgrade]
	      Module=Metering

	The next time that Fusion is launched on that PC only the
	metering module of Fusion will be available and visible
	to that user.

	To allow the user to use the full Fusion product again simply
	remove the [Downgrade] section from the FUSION.INI file.

	Another section may be added to the FUSION.INI that will allow
	you to disable the Set Policy and Security Scan Interval commands
	for the metering module of fusion. Add the following to disable 
	these commands:

		[Restrictions]
		EditLevel=4

*************************************
4. Install Error Messages
*************************************

  4.1   "Internal Error: -999"

	This indicates that you are running install in Windows 
	v3.0.  The NetWare function to provide the version 
	information does not work properly with V3.0 Windows.

	[Solution: install Fusion from a machine that is capable 
	of running Windows 3.1x in Enhanced Mode.  (See next note)]

	Please Note:    The Fusion 1.0 console (and install 
	program) only support Windows 3.1x in Enhanced Mode.  
	Windows 3.0x is not supported.

  4.2   "ValidateIPXNETXVersion Error: 254"

	This error may be due to one of the following:

	(a) You are running a version of IPX/SPX less than v3.10.

	    [Solution: upgrade your IPX/SPX to v3.10.  The OBJ 
	    file for IPX 3.10 can be found on Compuserve --in 
	    the Novell Libraries: GO NOVLIB; LIBrary 5; filename
	    (as of this writing) DOSUP8.ZIP]  

	    Please Note:  if you are using the ODI drivers, v1.20 
	    or 2.10 are recommended over v2.00.

	(b) You are not logged in as a supervisor (or equivalent), 
	    and the following has occurred: 
	    1)  Run Windows 
	    2)  Exited out of Windows 
	    3)  And have run Windows again.

	    [Solution: Issue (b) is due to a bug in the VIPX.386 
	    drivers version 1.11 and earlier.  This has been fixed 
	    in version 1.13, which is available on Compuserve --
	    in the Novell Libraries: GO NOVLIB; LIBrary 5; filename 
	    (as of this writing) WINUP7.ZIP]

	(c) IPX/SPX (or IPXODI) is loaded high.
	    Solution:  UPDATE to v1.13 of VIPX.386 or take IPX/SPX 
	    (or IPXODI)out of upper memory.

	(d) This error can also occur on workstations that have 
	    EMSNETX loaded.

	    [Solution: either reboot the workstation, loading a 
	    "straight" NETX shell, or run the install from a 
	    workstation that loads a straight NETX.]


    4.3    "Btrieve Error 90":

	    A Btrieve Error 90 is a "Redirection Device Table 
	    Full" error.  If you're getting this message, 
	    it usually means that you have an older version of 
	    BREQUEST.EXE in your search path, and *it* is loading 
	    instead of BREQUEST v6.10.

  4.5   How to revert to using "local Btrieve":

	If you would like to disable the Btrieve Requester for 
	Windows and have Fusion access client-based Btrieve 
	instead, follow these steps: 

	(1) From a DOS prompt -- outside of Windows, and in the 
	    Fusion 1.0 directory -- execute USEBTR.BAT.  This 
	    batch file will "enable" the client-based version 
	    of WBTRCALL.DLL by first  renaming the server-based 
	    version of WBTRCALL.DLL to WBTRCALL.BRQ, then rename 
	    the client-based version to WBTRCALL.DLL.
	

*************************************
5. Helpful Hints for Inventory
*************************************

5.1.  In order for EQUIP to collect system files such as system.ini, 
      win.ini, shell.cfg, etc., you must have these files in the 
      PATH statement in the autoexec.bat or in the search path 
      statements.

5.2.  To audit multiple sites, the files that are required from the 
      remote sites are:

		WEQLOG.DAT
		WEQTRN.DAT
		WSYSFLOG.DAT
		WSYSFTRN.DAT
		WTRSOFTT.DAT

    These files are commonly referred to as the "Transaction Files".

  

5.3.  SA_EQUIP was created and is intended to be run on workstations 
      that are NOT connected to the Network.

5.4.  Creation of Collector's Diskette MUST be done from the Fusion 
      console using the Create Collector Diskette command.  
      DO NOT copy the information from one diskette to another via 
      DOS copy commands.

 
5.5 If you would like to use Microsoft's screen savers during an 
    Audit please follow these steps: 
	
	1. In Windows, go under MAIN, Control Panel, 386 Enhanced 
	   and increase Windows in Background to 500.
	2. Begin to run your Audit or schedule an Audit to run.
	3. Go back into MAIN, Control Panel, Desktop and invoke 
	   the screen saver by clicking on test.
    
Note:  This procedure only needs to be followed for Microsoft 
       screen savers. If you experience any problems with any 
       other type of screen savers, please contact Technical
       Support.
	

5.6. If your Windows is set up to use the 1024x768 Large Font driver, 
     headers will be shown misaligned with the respective columns.  

5.7.  If you are using VLMs on the workstation where you run Fusion
      Inventory will not detect serial numbers on fileservers.  
      Inventory will also not be able to detect CPU and RAM info
      for 2.x fileservers when Fusion is run from a workstation that
      uses the VLMs.

5.8   If you are loading BREQUEST or BTRIEVE from a login script 
      in order to run EQUIP  you  may experience problems with 
      BREQUEST or BTRIEVE hanging if you are using LOGIN.EXE 
      version 4.xx.  There are two workarounds for this problem:

      A.   In a mixed environment of NetWare 2.xx, 3.xx and 4.xx
	   where the fileserver you are logging into is NOT a 
	   NetWare 4.xx fileserver you may add a PREFERRED SERVER=
	   statement to your SHELL.CFG or NET.CFG file. This will
	   prevent your workstations for invoking a copy of 
	   LOGIN.EXE v4.xx and will thus avoid the potential BTRIEVE
	   or BREQUEST hang.

     B.    If your environment is all NetWare v4.xx or if you are in 
	   a mixed environment but you are attempting to log into a 
	   NetWare 4.xx server you should load BREQUEST or BTRIEVE 
	   and execute EQUIP from a batch file. This batch file can 
	   be called from within the login script by using Novell's
	   External Execution switch (#). 

	   The login script should resemble the following:

	   MAP F:=VOL1:APPS\FUSION ; map F: to the Fusion directory
	   DRIVE F:                          ; change to F:
	   #COMMAND /C DOEQUIP.BAT ; shell out and call DOEQUIP.BAT

	   The batch file should resemble the following:
	   (it should be created in the Fusion directory)

	   ENDBTRV                        ;unload Brequest (or Btrieve) if loaded
	   BREQUEST /D:17000     ;load Brequest with parameters
	   rem If you prefer to load BTRIEVE.EXE instead, use
	   rem BTRIEVE /P:3072 /F:22 /T:BTR.TRN /E
	   EQUIP /H /Y /S /SHOW         ;inventory hw, sw and system files w/echo
	   ENDBTRV                        ;unload Brequest (or Btrieve)

5.9     Users may wish to consolidate inventory data from remote
	sites and incorporate this information in their local databases.
	This may be accomplished by either consolidating transaction
	information or by consolidating baseline information.  
	Instructions for both methods follow:

	A.   Consolidating Transaction Information:

	     Copy the five Transaction files (weqtrn.dat,wtrsoftt.dat,
	     weqlog.dat, wsysftrn.dat, wsysflog.dat) from the remote
	     site to a directory you have created for them on your 
	     local network. If you are consolidating more than one site
	     you will need to create a directory for each of these sites.
	     Then from within the Fusion (or LAI) console define that 
	     directory (or directories) as a Site from the Define Sites
	     screen.  Include the Site(s) in your Scope of Audit and 
	     perform the Audit.  The Audit will incorporate the 
	     Transaction information into your local Baseline, where the 
	     data can be edited, viewed and reported on from within the
	     Fusion (or LAI) console.

       B.    Consolidating Baseline Information:
	     
	     In order to get fileserver information from a local site
	     merged with your local Baseline you must consolidate
	     Baseline information.  If you want to include any edits
	     made to inventory you must also use this method when
	     consolidating information from remote sites.

	     Export the baseline using the copy of Fusion (or LAI) 
	     at the remote site.  The Export Baseline command is found 
	     under the Administration/Inventory menu.  Once you have
	     exported the baseline data you may then import it into
	     your local copy of Fusion (or LAI) using the Import Baseline
	     command under the Administration/Inventory menu.

	     Once you have imported the data there is no need to do a
	     susequent Audit since the Import process will merge the
	     remote Baseline information into your local Baseline
	     as long as the site names for the data are unique.  The 
	     data can now be edited, viewed and reported on from 
	     within the local Fusion (or LAI) console.

5.10         Due to a limitation of Microsoft's Common Dialogs, you
	     may encounter a message "The number of files retrieved is
	     less than the number specified..." when adding files to a
	     Fileset.  The message will return what the last file retrieved was,
	     and you can then go in and specify additional files.       

5.11          NIC Cards with multiple protocols bound to them (as possible
	      with ODI drivers) may return incorrect NIC card information in 
	      the inventory.    
		


begin_meter             
************************************************************

6.0  New and Improved in Metering.

************************************************************
    
6.1     Suite Metering
	
	A 'set' of files can be defined under one Metered
	Application name and metered as one unit.  This applies
	to both DOS and Windows applications.
	
6.2     User Release

	If an occasion should arise that a user must be
	released from a particular license count, this can be
	accomplished from the View Application Screen.  The user
	can continue to use the application, but is no longer on
	the metered list.

6.3     Modifying Metered Applications

	By double clicking on a Metered Application Name in the
	View Application window, the Modify Metered Application
	windows is displayed.

6.4     Authorized Files

	Multiple files can be selected for authorization by 
	holding down the left mouse button and 'dragging' the 
	mouse down the Browse file list.

6.5     Bug Fixes:        

	The NLMs can be loaded while Novell Accounting is turned 
	on.

	Map rooted applications are correctly metered.

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

7.0 SiteMeter At A Glance

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

 7.1  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.    

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

8.  Helpful Hints for Metering

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

IMPORTANT!  SiteMeter and the metering portion of Brighwork Fusion 
are 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.  SiteMeter and the metering portion of Brightwork 
Fusion is not compatible with 1000 user NetWare.

8.1   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.

8.2     Setting the Security Scan Interval

	This setting tells the NLMs to scan the network at a set
	interval for those users who do not have SWATCHER loaded
	on their workstations.  If this interval is set to any
	number other that zero, and users do not have SWATCHER
	loaded,  these users will be disconnected from the network
	within 30 seconds of the scan.  This includes any
	Macintoshes that are on the network.  If you wish to use
	this feature, and have users that are to be exempt from 
	the network disconnect, add those users to the Security
	Exceptions list from the Security menu.

8.3     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.

8.5   Upgrading Your Novell Software

      This product was not regression tested with releases
      earlier than NetWare 2.2.
     
      Swatcher does not support Suite Metering on Netware 386.

      Also, we recommend you upgrade to the latest supportable 
      shells and drivers released from Novell.
	 
8.6   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.

8.7   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 10,000).  

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

      :load smrproxy -t90000 -l500 -e7500.

8.8   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.
   
8.9   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.
       
8.10  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.  

8.11  Metering Freelance

      To meter Freelance for Windows use FLWMAIN.EXE.

8.12  Metering Harvard Graphics 3.0

      To meter Harvard Graphics 3.0 use HG3.EXE

8.13  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.

8.14  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

8.15  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.

8.16  Using Swatcher.com

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


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

9.   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.


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, 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.

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

10.  Known Problems With the Metering Portion of Fusion

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

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

10.2    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.

10.3    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.

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

10.5    These applications create unpredictable results when metered.

	R:BASE 3.1
	LapLink III
	Lotus 123 r3.1  

	There is a known problem with locksets being released when 
	using QEMM.  The workaround for this problem is to remove 
	the LoadHigh verb from the config.sys:

	LH shell=c:\command.com /r

	or remove the shell statment from the config.sys 
	and add the following to the autoexec.bat:

	set comspec=c:command.com  

10.6    SMRAgent will *not* work in Standard Mode Windows.

10.7    The limit on Metered Applications on any fileserver is 500
	files.  There is a bug that will allow you to add more than
	500 files to this list.  If more than 500 files are added the
	product will stop metering.  The workaround for this problem
	is to enter ONLY up to 500 files to the Metered Applications
	list.
*******************************************************************************

   User Feedback Department
*******************************************************************************

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

   Fax:                                 (908) 576-8867

   Or by Internet                       Customer_Service@Brightwork.com

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

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

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