 The InVircible Utilities
 ------------------------
 The utilities in this package are rarely used in IV's daily operation.
 Yet they facilitate performing certain tasks, that otherwise may
 require the use of an ASCII editor or of a disk management utility.

 FIND-SIG.
 ---------
 InVircible creates an integrity database that consists of a signatures
 file in each directory that contains binary-executable files. The
 filename of these signatures may contain high ASCII (unprintable)
 characters. Especially if the installation of IV was performed with
 IVLOGIN, with the random filename option ON (IVLOGIN /RANDOM). The
 purpose of the hi-ascii characters in the filename is to protect the
 database from being accidentally erased. The first three characters of
 the signature filename are always printable alphanumerics, so that they
 can be handled from DOS, when using the "?,*" wildcards.

 Many users depend on Windows and on its file manager. To their dismay,
 Windows is unable to handle files which's name contains high ascii
 characters. Most users ignore that Windows is handicaped in this
 aspect. If you read this file wth a DOS viewer then you'll be able to
 see in the following "" the sequence of four Greek characters
 starting with alpha (ASCII 224). Yet under windows you probably see
 only underscores, or maybe just one character, but not all four.

 FIND-SIG is a housekeeping utility. It will find and remove inactive or
 orphan IV signature files which you may have lost for whatever reason.
 Just type FIND-SIG and the drive name that you wish to scan (the
 default is the current drive). FIND-SIG will prompt the user on any IVB
 inactive signature file that it finds and ask if to skip the file,
 erase it, or erase all the orphan IVB files that it finds.

 FIND-SIG can also be used to cleanup periodically from the IVB.000
 backup signatures. Another usage of FIND-SIG is to remove all IVB
 signatures left after uninstalling InVircible from a computer.

 FIXBOOT.
 --------
 FixBoot can be used as a generic utility to clean the boot sector of
 floppies by installing a generic boot sector to them. FixBoot can
 process floppies from 360 kbyte to 2.88 mbyte. The floppy to be treated
 should be placed in drive A or B and the first argument following
 FIXBOOT on the command line should be either A: or B:.

 FixBoot will usually identify the size of the floppy and install an
 appropriate boot sector. In the instance that the diskette is
 inaccessible, such as after being infected by certain boot infectors,
 the /S (size) switch can be used. FixBoot will prompt for a floppy
 size. Just select from 1 to 5, according to the floppy size.

 FixBoot installs a standard MS-DOS 4+ boot sector, and the floppy will
 be bootable if it contains the system files. FixBoot will identify if
 the floppy has MS-DOS or PC-DOS/DR-DOS files and install an appropriate
 boot sector to keep it bootable. Yet the user may force an IBM boot
 sector (MS-DOS is the default) if needed, by adding the /IBM switch to
 the command line.

 This version of FixBoot will let process floppies in bulk. All the user
 need to do is to answer 'Yes' when prompted if to process another
 floppy in the same drive.

 Creating a CLEAN bootable floppy on a computer that is infected with a
 boot virus: Format a floppy in the boot drive with the system option
 (FORMAT /S). Issue the command FIXBOOT A: and remove the floppy from
 the drive immediately when done, or it may become infected again.


 GET-HD
 ------
 GET-HD will display the CMOS setup and the IDE parameters of the two
 first hard drives installed in a computer. For SCSI and MFM drive it
 will display the hard drive parameters found in the BPB (bios
 parameters block). The parameters shown by GET-HD are written in the
 HD_DATA.NTZ file, created on the rescue diskette at the time of its
 preparation.

 These parameters can be useful in disaster recovery scenarios or when
 asking for assistance from the IV online support.

 NOCMOS
 ------
 The CMOS setup parameters are backed up by InVircible the first time
 IVINIT runs from the autoexec. On every subsequent booting, the current
 CMOS configuration parameters are compared by IVINIT to those stored in
 the CMOS.NTZ file. If a change in configuration is detected, then the
 user is alerted.

 There are instances where multiple CMOS configurations are used, for
 example with notebooks, when docked or as a stand alone machine. In
 these cases the user may wish not to be bothered with the CMOS check
 every time the computer is booted. IVINIT will skip the CMOS test when
 invoked with the /NOCMOS switch.

 The NOCMOS utility edits the C:\AUTOEXEC.BAT file to enable, or disable
 the IVINIT CMOS test. Running NOCMOS E will enable the CMOS test, while
 running NOCMOS D will disable the CMOS test in the autoexec.

 SWAPBOOT.
 ---------
 There are instances in which you may want to swap roles between the
 physical floppy in drive A and B, without needing to open the
 computer's cover. For example, you may need to boot from a floppy that
 suits drive B's format, not drive A.

 SWAPBOOT will install a special boot sector to a floppy in drive A.
 When you boot from this special diskette, it will prompt with several 
 options. The default is booting from the hard drive, after a predetermined 
 delay, even if the floppy is left in drive A.

 If F2 is pressed during the boot delay sequence, then drive A and B
 swap roles. The BIOS will seek for a bootable diskette in drive B, and
 boot from it, if there is one. After booting, physical drive B will be
 assigned as A for ALL purposes, including formatting etc., and physical
 A will become B. Until rebooting the machine.

