Help file for SHEZSET.BAT Shezset 1.8f 6/27/95 Oops, I had the 1.8e changes named and dated wrong. Corrected below. Since SHEZ creates a directory #Z as a subdirectory of the current directory on your configured work drive, that is the ONLY subdirectory that SHEZ ever needs to scan (for scanning ARCHIVES). Thus I have made a change to the SHEZSET.BAT file that looks to see if a filespec.ext is being scanned or if a PATH is being scanned. If a PATH is being scanned then *.* is added to cause TBScan to process any files in that directory. Be advised that using SHEZSCAN to scan CURRENT or EXTRACT directories will NOT process any subdirectories of those directories! Below is a detail of the reason why.... ThunderBYTE Anti-Virus scanner (TBSCAN) has an AllFiles switch AF that causes TBSCAN to process all the files it finds. If the user uses this switch then TBSCAN pauses before it starts the scanning and the user must press a key to continue. First, you will not detect ANY virus that has been renamed to a non-executable extension (ie, a file named virus.ex1 will NOT be scanned) without the AF switch or specifying a filespec.ext of *.* on the command line. Second, the *.* filespec.ext will cause TBSCAN to process AllFiles but ONLY IN THE SPECIFIED DIRECTORY. This is a problem because if the file is named VIRUS.EX1 and is later installed in a subdirectory one level deeper than the directory being scanned (-d), then even using *.* won't find the virus. Again, the user is stuck with using the AF switch and having to press a key for each archive scanned. This is not acceptable for BBS operators that want the scan process to clear the file for the users to download immediately. Make a choice if you want to add *.* to scan all files found but ONLY the specified directory or if you want to leave that off and scan ONLY executables in the specified directory and ALL subdirectories of the specified directory. Change the lines below :TBSCAN Enable... and :TBSCAN Disable... in the SHEZSET.BAT file. Shezset 1.8e 6/6/95 Two problems have been identified with TBScan that might affect how the SHEZSCAN.BAT file works. 1) You can not specify \*.* as a path for TBScan. TBScan fails to access the disk if this is used and NO scanning is done. 2) An old bug seems to have resurfaced in TBScan. If you specify multiple paths on the TBSCAN command line, they must be in the same order as they are found on the hard drive. ie. if you specify: TBSCAN C:\BIN C:\DOS TBScan will work as expected IF the BIN directory comes before the DOS directory on C:. However, if the command TBSCAN C:\DOS C:\BIN is used and the BIN directory is listed before the DOS directory then TBScan will NOT scan any files in the BIN directory, but will report a "no executables found" error message. If the IN (Ignore No executables) command line option is used, you will not see any failure. This could apply if you use either $CD$CP $ED$EP with SHEZSCAN.BAT. ThunderBYTE has been informed of these problems. Shezset 1.8d 3/6/95 ThunderBYTE 6.33 corrected a 'difference' that was noted in SHEZShow 1.3a. TBScan now works 'like other scanners' when the command line ends in \. ie, TBSCAN \BIN\ now scans files in the \BIN\ directory. Previously, TBScan worked for the root directory only when ending in \. All subdirectory entries ending in \ would not scan any files. ThunderBYTE 6.33 release changed the way it works when *.* (actually any filespec.ext) is on the command line. It only scans the specified directory. It worked this way a long time ago. Sometime during the continued development of TBScan, this changed and TBScan scanned subdirectories of the current directory unless the NoSub (NS) switch was used. Well, they went back to only scanning the specified directory if there is a filespec.ext on the command line. This change negates the work around I used in 1.8c to scan ALLFILES using *.* on the command line. Since TBScan will NOT scan any subdirectories when *.* is used, I have removed the work around in SHEZSET.BAT. You must specify AllFiles in the TBAV setup file (and live with the pause) if you want to scan allfiles. Also my SHEZ.INI sample file removed the *.* from the uSer Menu command lines when scanning the specific directories. First, TBScan now correctly scans the files when paths end in \ (ie., \BIN\). Second, if *.* is on the command line then subdirectories are not scanned as expected which would not work with the way SHEZ uses subdirectories when scanning archives in archives. Shezset 1.8c 2/20/95 Using the Allfiles (AF) switch with ThunderBYTE paused a pause. Well, I found that I could specify the filespec.ext of *.* on the command line and then TBScan would scan allfiles without the pause. This change is in SHEZSET.BAT. It works just like the command for F-Prot. It simply checks if the 'item' to scan is a file (IF EXISTS %1) or a directory (IF NOT EXIST %1). Now TBScan can once again scan Allfiles. Shezset 1.8b 2/7/95 ThunderBYTE changed the operation of their Allfiles switch AF and caused it to PAUSE and wait for a keyboard input even if the Batch BA - No Input Required - switch was used. This causes the Scanning process to stop and wait for a key for each file that is scanned. I had to remove the AF switch from SHEZSET.BAT for the TBSCAN program to allow for 'hands free' operations of scanning files. Shezset 1.7a 11/7/94 Added /NOEXPIRE to the SCAN V117 Command line in SHEZSET.BAT. The program now gives the "out of date" message and pauses the computer each time it is called. Hopefully the NEW Scan 2.1.4+ will finally detect and clean all the viruses that V117 did. Then, maybe, we can all change over to the new program. Shezset 1.7a 11/7/94 Added /V to AVScan command line in SHEZSET.BAT. This causes AVScan to ONLY log filenames of INFECTED files (and not all files processed). Shezset 1.7 10/12/94 Added AVScan 1.84a Virus scanner switches to the SHEZSET.BAT file. This virus scanner has a very good detection rate, is fairly fast, and works extremely well from the command line (no menu system). The detection rate was better than Scan V117, Scan 2.1.2 on my small collection of sample viri. Changed the keyword CHECKOUT to CKOT when using SHEZSET. The file SCANIT.BAT is no longer created. The SHEZSET.BAT file creates SHEZSCAN.BAT or CKOTSCAN.BAT files directly. Changed the LOG file filenames from the individual scanners to a generic LOG (i.e. TBAV.LOG is now either SHEZSCAN.LOG or CKOTSCAN.LOG. The reason for this change was the fact that Shez only SEES the errorlevel set by the LAST virus scanner used. Thus three of the four virus scanners could report problems and the last NOT report any problems and the SHEZ.LOG file would NOT show any problems! Two new files are included in this archive (SHEZFAIL.BAT and CKOTFAIL.BAT). These files echo "FAILURE PROCESSING %1" statement into the SHEZSCAN.LOG or CKOTSCAN.LOG file if ANY virus scanner exits with an errorlevel > 0. -------end of changes------- SHEZSET.BAT creates a file named SCANIT.BAT using the BATCH "ECHO" command to send the correct drive:\path\filename.ext and command line options for your virus scanner. It can easily be changed for any different virus scanners if you understand the BATCH file language. SHEZSET.BAT defaults to copying the newly created SCANIT.BAT to C:\SECURITY\SHEZSCAN.BAT. SHEZSET.BAT will optionally, copy the newly created SCANIT.BAT to C:\SECURITY\CKOTSCAN.BAT file for the Checkout 2.0 program. (See the CHECKOUT.DOC file provided with the Checkout program for proper use of the CKOTSCAN.BAT file.) -- You will probably need to change the path names, file names and command line options in SHEZSET.BAT to match your virus scanner(s) name, locations and preferences. You will then need to configure SHEZ to use SHEZSCAN.BAT as your virus scanner. Set the memory entry in SHEZCFG to the MAX value required by your viri scanner(s) (if they require 286K, 411K, 395K then configure for 411000). Once this has been done you are ready to Viri Scan your archives with the best of the best Viri scanners. To use SHEZSET.BAT you just call it up like: SHEZSET # where # is: 1=ALL, 2=TBSCAN, 3=FPROT, 4=SCAN, 5=SCAN2 To use SHEZSET.BAT with CHECKOUT you just call it up like: SHEZSET # CHECKOUT (Note: You must use caps for CHECKOUT. There is not test for lowercase.) If you have GET 2.5 or 2.6, batch file enhancer, you can specify SHEZSET G and you will presented with a menu to select from. You can replace this with your own batch file enhancer if you wish to. ----- Shez Show 1.5a 8/18/94 ThunderBYTE Anti-Virus 6.23 was released recently. This version corrected one 'difference' that was documented as a possible problem in the SHEZSET.TXT file. No changes to SHEZSET.BAT file. Shez Show 1.5 7/11/94 No changes to SHEZSET.BAT file. ShezShow 1.4 6/30/94 McAfee Assts released their 2.1.0 Release Candidate virus scanner. They changed their switches and defaults. The 2.0 series was originally released for maximum protection by DEFAULT. The switch /STD was used to process ONLY standard executable and overlay type files. Well, they just reversed this. Now the default IS standard executables and overlay type files and a new switch /ALL is provided to process ALL files. This switch change was put into the SHEZSET.BAT ECHO commands to insure that the SHEZSCAN.BAT processes ALL files. To restrict the scanning to only Executable type files, use SHEZCFG to change that option in SHEZ.CFG. ShezShow 1.3a 6/20/94 Virus scanner differences. The four virus scanners I have used in this demonstration file work alike (almost). A few differences you should be aware of follows: As of F-Prot V2.12 this viri scanner is different from the other scanners in that you can NOT specify a filespec.ext AND the option to SCAN ALL FILES FOUND (/ALL) on the command line at the same time. However, you CAN specify a drive:\dir AND /ALL. For this reason, there is a test to see if you called the scanner and ended with a filename.ext or a directory name, and the SCANIT, SHEZSCAN, CKOTSCAN files use the correct command line. A second item in F-Prot concerns the length of the command line. On more than one occasion I have had F-Prot create a log file which was named wrong. The indications are that if the path + command line gets too long; C:\SECURITY\F-PROT C:\TEMP\CKOT.1\CKOT.1\CKOT.3 /ALL /NOMEM /NOBOOT /REPORT= C:\TEMP\FPROT.LOG /APPEND seems to do it; that everything past "C:\TEMP\F" gets cut off and F-Prot creates a log entry named C:\TEMP\F (without the append). Because of this, I rearranged the ECHO command in SHEZSET.BAT and moved /NOMEM /NOBOOT to the end of the command line. -- As of ThunderBYTE 6.23 this viri scanner (TBSCAN) has a difference that I felt that you should be aware of. The difference is the way the command line is interpreted if you end with a \ on the target. Other virus scanners will let you specify a path like: SHEZSCAN C:\TEST\ and they default to "*.*" as the filespec.ext. TBScan does NOT work that way. If you end the target with a "\" it will NOT scan any files! To correct this, I have specified *.* on the end of the uSer Menu entries in the SHEZ.INI file for virus scanning entries. ShezShow 1.2 4/27/94 I revised SHEZSET.BAT file that creates SHEZSCAN.BAT. SHEZSET.BAT can now setup SHEZSCAN.BAT for one or ALL of the four Viri scanners that I know about: ThunderByte 6.20, F-Prot 2.12, Scan V115, and Scan 2.0.2. Have fun and stay viri free. Darrell Bivens