Version 1.1 of FLU_SHOT+ has a few enhancements:

1.	If you use the '-B' switch when you first run FLU_SHOT+,
	the machines BIOS will be used instead of direct screen
	writes.  Useful for machines which are less than IBM-PC
	compatible.  Or those people still running CGA's who don't
	like snow.  It's a little slow.  For the CGA users: you
	ever think of how nice it would be to see an unblurred
	screen?  EGA's aren;t that expensive anymore....

2.	I neglected to remove some comments, and there was a hole
	in FLU_SHOT+ V1.0 that a worm could have exploited.  The
	hole has been patched securely....

3.	An additional option in the FLUSHOT.DAT file:
		X=<ambigious_filename>
	allows a matching program to "turn off" the triggering of
	FLU_SHOT+ for the entire duration of its run.  This could
	leave a security hole if you're not careful....so be careful!
	Do not use an ambigious directory: running a trojan from there
	would not trigger FLU_SHOT+.  I use it for programs like 
	FORMAT, Norton Utilities and that kind of stuff.  I'm very
	careful when using it, though.  And you should be, too!

4.	The in-memory protection table is now checksummed so that
	worms can't change the files you're attempting to protect.
--
Version 1.2 of FLU_SHOT+ has a few enhancements:

1.	A new option, '-I<num>' has been added.  This allows you to
	determine the frequency, in 1/18 seconds, of how often the CMOS
	Check (if enabled) and the Protection Table Check are going to
	run.  The lower the number, the higher your protection, but
	the more impact it will have on system operations:  they'll
	be a little slower.  The default is set to one second.

2.	Some complaints from those having FSP in their AUTOEXEC.BAT and
	having a line of the the form R=\AUTOEXEC.BAT.  FSP was protecting
	the AUTOEXEC.BAT file (an intended option), but the boot sequence
	was causing people to have to hit a 'G' to continue with their
	boot.  I've installed a '-S<num>', where <num> represents how many
	1/18 seconds to sleep before activating the R= option.
	The default is set to 10 seconds.  It will also immediately
	expire on the first key hit.

3.	Because CMOS and Prot Table checks are done via the timer tick
	in Version 1.2, there is no need for the counter to be associated
	with the CMOS flag any longer.  As such, '-C' is the full option
	to turn on CMOS checking.
--
Version 1.4 of FLU_SHOT+ has a few enhancements:

1.	I've skipped Version 1.3 - something about the number having
	bad luck and all.

2.	A major bug, due to programmer stupidity, has been fixed. Alas,
	this bug actually could cause some damage to your disk.

3.	The X= switch works better now - it was ignored on Direct Disk
	Writes

4.	Some of the error messages have been made a bit clearer.

5.	Complaints from some of the users have caused me to increase the
	size of the checksum buffer internal to FLU_SHOT+.  This has the
	sad result of increasing the TSR size of the program itself -- but
	I consider it a reasonable increase for speeding up the checksumming
	of files.

6.	If a file to be checksummed could not be found at startup time,
	the previous files checksum was displayed -- this has been fixed.

7.	Certain holes in FLU_SHOT's security system have been patched.

8.	The size of the FLUSHOT.DAT buffer has also been increased to allow
	users to specify more files to be checksummed and/or protected.

--
Version 1.41 of FLU_SHOT+ has a few minor enhancements:
1.	Version information will now show up on the alert screen,
	which should make things easier for tech support calls

2.	FLUSHOT+, V1.41 now does some more adequate checking on certain
	IOCTL calls, providing a slightly better level of protection.


Ross, 7/13/88