; ; ********* THIS FILE IS NOT REQUIRED! ********* ; ; Neither VirHUNT nor RESSCAN require a configuration file, it is OPTIONAL! ; It has been renamed with a .CF extension instead of .CFG so that time ; is not wasted on processing it. ; ; However, its use DOES allow you to set custom colors, custom messages, ; special flags, and command line options within VIRHUNT. For RESSCAN, ; the custom messages and command line parameters are used. ; ; Note that ANY invalid line (such as a line starting with a semi-colon ';', ; or lines with errors in them) are taken to be comments. The preferred ; comment is to start a line with a semi-colon, as VirHUNT knows not to ; even try to process such a line. ; ; Although the examples in this file are set up for clarity, upper/lower ; case does NOT matter for either configuration parameters or their ; options. ; ; VirHUNT and RESSCAN will attempt to process 2 copies of VIRHUNT.CFG ; every time they are run. First, they will attempt to process the ; VIRHUNT.CFG in the current directory, then the VIRHUNT.CFG in the source ; directory of the current program (i.e. where VIRHUNT.EXE or RESSCAN.COM ; came from). Thus, using a network environment as an example, local ; parameters (such as colors or left-hand mouse) may be set by every user, ; while system-wide parameters (such as messages) may be set in a ; global VIRHUNT.CFG file. ; ; The color names and values are: ; BLACK 00h ; BLUE 01h ; GREEN 02h ; CYAN 03h ; RED 04h ; MAGENTA 05h ; BROWN 06h ; LTGREY 07h ; DKGREY 08h ; LTBLUE 09h ; LTGREEN 0ah ; LTCYAN 0bh ; LTRED 0ch ; LTMAGENTA 0dh ; YELLOW 0eh ; WHITE 0fh ; MNORMAL 07h ; MUNDERLINE 09h ; MBOLD 0fh ; MINVERSE 78h ; ; Notice that there are 2 types of colors, with the second type ; (MNORMAL, MUNDERLINE, MBOLD, MINVERSE) for Monochrome displays. ; ; Colors may be specified in the form: ; [BLINKING ]forgroundcolor[ ON backgroundcolor] ; or ; Mcolor ; If a background is not specified, it is assumed to be BLACK. ; ; There are a number of different colors used within VIRHUNT. The colors, ; their names, their uses, and their standard definitions are given ; below. ; ; standard backgrounds and text while scanning STND:green on black ; ; accent to make text stand out from surrounding ACNT:white on blue ; ; highlite used for options or attention HILT:black on ltgrey ; ; error used for errors or warnings ERRC:yellow on black ; ; poptext for text in "popup" boxes PTXT:white on brown ; ; pop_border border for "popup" boxes PBRD:white on brown ; ; pop_highlite accented text in "popup" boxes PHLT:yellow on red ; ; menubar the main menu bar, when active MBAR:ltgrey on blue ; ; menubar_highlite current option on main menu bar MBHL:white on blue ; ; menubar_hotchar "hot char" on main menu bar MBHT:ltcyan on blue ; ; menubar_dull the main menu bar, when inactive MBDL:ltgrey on blue ; ; dropmenu items in a "drop" menu, when active DROP:ltgrey on blue ; ; dropmenu_border border of a "drop" menu, when active DRBR:white on blue ; ; dropmenu_highlite current option in a "drop" menu DRHL:white on black ; ; dropmenu_dull items in a "drop" menu, when inactive DRDL:black on cyan ; ; dropmenu_br_dull border of a "drop" menu, when inactive DRBD:white on cyan ; ; dropmenu_hotch "hot char" in a drop menu DRHT:ltcyan on blue ; ; mousecolor color at location of mouse cursor MOUS:white on red ; ; If a monochrome display is in use, VirHUNT uses the color set: ; ; STND:mnormal ; ACNT:mbold ; HILT:mbold ; ERRC:mbold ; PTXT:mnormal ; PBRD:mnormal ; PHLT:mbold ; MBAR:mnormal ; MBHL:minverse ; MBHT:munderline ; MBDL:minverse ; DROP:mnormal ; DRBR:mnormal ; DRHL:minverse ; DRDL:minverse ; DRBD:minverse ; DRHT:munderline ; MOUS:minverse ; ; Another color scheme, and one I personally like (programmers vanity) is: ; STND:black on ltgrey ; ACNT:white on blue ; HILT:red on ltgrey ; ERRC:yellow ; PTXT:black on brown ; PBRD:white on brown ; PHLT:ltgreen on brown ; MBAR:white on blue ; MBHL:white ; MBHT:green ; MBDL:dkgrey on ltgrey ; DROP:ltgrey on blue ; DRBR:white on blue ; DRHL:white ; DRDL:dkgrey on ltgrey ; DRBD:dkgrey on ltgrey ; DRHT:green ; MOUS:white on red ; ; ; Command line parameters may also be specified in this configuration file: ; CMDL: ; ; Scanning is not automatic when configuration parameters are processed. ; You can tell VIRHUNT to scan without stopping at the main menu by ; using the SCAN parameter. Note that any error in a CMDL: specification ; will over-ride the SCAN parameter, as VirHUNT is NOT in the state you ; expect. RESSCAN will automatically do a scan when it is run unless ; the SWN command line parameter is given, so SCAN is ignored. ; ; SCAN ; ; So, for example, to have VirHUNT or RESSCAN automatically scan memory, ; boot records, and executable files on the C:, D:, and E: drives and ; return to DOS, the follwing command line parameters can be used ; (removing, of course, the proceeding ';' from the commands): ;CMDL:c: d: e: ;CMDL:qu ;SCAN ; Note that command line parameters take precedence over any VIRHUNT.CFG ; file, although once a parameter like QU is set to there is no way ; to "undo" it. ; ; There are 3 places where custom messages may be placed in the ; VirHUNT and RESSCAN programs: ; a) When the system is halted due to a virus found in a memory ; scan. ; b) When the system is halted due to a virus found during a normal ; virus scan (using HALT as the virus action). ; c) When the scan summary is displayed after a scan in which ; viruses were found. ; ; In these cases, up to 2 lines may be displayed. For a) and c), the ; user message is displayed in addition to the normal VirHUNT or RESSCAN ; message, for b) the user lines are displayed instead of the VirHUNT ; or RESSCAN message. ; ; Also, when RESSCAN is resident with the halt option set, the HLT1 ; message is used instead of the internal default message. ; ; For a), the memory resident virus message, an example would be: ;MRM1:This system is not to be used until disinfected by Tom Savage. ;MRM2:Contact Data Processing Security at x3-4567. ; ; For b), the system halted message, an example would be: ;HLT1:Please turn off this machine, and contact DP administration ;HLT2:at (222)555-6969 for further instructions ; ; For c), the virus summary message, an example would be: ;INF1:This system should NOT be connected to the network until ;INF2:cleared by the Security Office, x5-1723. ; ; Network managers, take note: ; Since the VIRHUNT.CFG in the source directory takes precendence over ; a local VIRHUNT.CFG, any locally defined messages may be removed ; by giving the message parameter (such as INF1:) with no message. ; ; ; VirHUNT and RESSCAN can also be set to run on or after a specific date, ; which is kept current by the program. ; ; This date must be in the format MM/DD/YY, with 2-digits for EACH field ; (i.e., use leading 0's if necessary!) following the date is the ; incrment, a number from 1 to 99, which specified the days between dated ; runs. On or after this date, VirHUNT or RESSCAN will automatically do ; a scan. Note that the DATE parameter for RESSCAN does NOT prevent ; RESSCAN from going resident if it is not the target date, it only ; prevents RESSCAN from doing the inital scan before going resident. ; ; There are two modes for the date parameter, after and every. In ; the after mode, the date is reset every time the program is run, so ; that the next scan will be no more than days after the current ; scan. This is signaled in the configuration file by seperating the ; date increment from the date with a plus sign ('+'). ; ; In the every mode, VirHUNT uses the date parameter to run every ; days, regardless of when it was last run. This would be useful for ; doing weekly scans (for example, every Monday or every Friday). The ; every mode is signaled to VirHUNT in the configuration file by ; seperating the date increment from the date with a space. ; ; So, for example, a date parameter for the every mode would be: ;date:03/05/92 07 ; while a date parameter for the after mode would be: ;date:03/05/92+07 ; ; NOTE: The -D command line parameter (do not scan/quit if not target ; date) must be used with VirHUNT and RESSCAN to take full ; advantage of the DATE parameter. ; ; People hate waiting, and so scanner programs like VirHUNT and RESSCAN ; are annoying to many people as they check out a system. This tempts ; many people into aborting a scan, saving time but thwarting the purpose ; of the program. To help this problem, the NOABort parameter is ; available, which turns-off the ability to abort a scan. ; ; The noabort parameter is available in two versions, NOAB which turns ; off abort at all times, and NOAB:SS-EE, which turns off abort between ; the hours of SS and EE. SS and EE are two-digit numbers, in the range ; 00 .. 23, which are the starting hours and ending hours of the ; noabort times. Outside this range, abort is allowed. This version ; could be used, for example, to set noabort hours between 5 and 10am, ; so that with VirHUNT in the AUTOEXEC.BAT file, the first boot of the ; day would be forced to be completed, while the rest could be halted ; by the user. ; ; RESSCAN does not process the time associated with the NOAB parameter, ; and so turns off aborts at all hours. ; ; The noabort parameter is most useful in a corporate/network environment, ; where a central directory or server has the noabort parameter in the ; global VIRHUNT.CFG file. ; ; An example of the timed noabort is: ;noab:05-10 ; and an example of the general noabort is: ;noab ;