1. 4NHCT_Update.exe Driver
2. readme.txt File Contents

readme.txt Driver File Contents (4NHCT_Update.exe)

HCT Kit Monitor Software:
========================
Consists of 3 pieces:
	Client Monitor (clientmon.exe)
	Server Monitor (servermon.exe)
	Entry DLL (initdll.dll)

Build Instructions:
==================

	cd cl
	Build cl.lib with INCLUDE=.,..\include

	cd tcpip
	Build tranport.lib with INCLUDE=.;..\include

	cd perflib
	Build perflib.lib with INCLUDE=.,..\include

	cd server
	Build servermon.exe with INCLUDE=..\include,..\tcpip,..\cl
	      and LIB=..\transport\transport.lib
                      ..\cl\cl.lib
                      ..\perflib\perflib.lib
                      wsock32.lib

	cd initdll
	Build initdll.dll

	cd client
	Build clientmon.exe with INCLUDE=..\include,..\tcpip,..\cl
	      and LIB=..\transport\transport.lib
                      ..\cl\cl.lib
                      ..\perflib\perflib.lib
                      wsock32.lib

Usage:
=====
Run the client:
clientmon.exe

Run the server:
servermon.exe debug-sys 1 \\daastan\daastanc c:\temp 

where
	debug-system	name of the debugger system
	n		minimum number of clients
			e.g. 8
	share-root	root of the share point where clients see
			the HCT software
			e.g. \\ntserv\c-drive
	hct-install-root
			root of the installed HCT software
			e.g. c:\hct


Important Notes:
===============

Currently the servermon.exe and clientmon.exe are configured to run
for 24:30 and 24:00 hours respectively. They use TCP/UDP port 2000
for network communication. Both client and server gather system
statistics every half hour. The minimum required clients is 8.
These parameters are defined under
include\hctproto.h and can be modified if desired.

#define HCT_CLIENT_SHUTDOWN_TIMEOUT  24*60*60 // 24 hours
#define HCT_CLIENT_WAIT_TIMEOUT      30*60 // 30 mins - additional time
                                           // for server
#define HCT_SYSINFO_SAMPLE_TIME      30*60 // 30 minutes
#define HCT_MINIMUM_CLIENTS          8


Additional Notes:
================
All the basic features envisioned in the initial specification are 
implemented. Some of the features that were suggested later are not
all implemented. For example, the final report is in simple text
format, and not in HTML format. The "synchornization" protocol
between server and client timers is not implemented (the code is there
but is turned off) because it can potentially cause the server monitor to
deadlock if one of the client monitors dies and doesn't respond.
A modified version of this protocol can be implemented in a later
version of the software.