MCUP - McAfee AntiVirus DAT Updater
(c)2003 Art Kopp - artnpeg@epix.net
http://home.epix.net/~artnpeg/
___________________________________
Dox by Eepē - http://tnlc.com/eep/

____________
Introduction

If you only use McAfee AntiVirus' DOS-based scanners (scan.exe, scanpm.exe, and/or scan86.exe), and don't even bother with the bloatware, CPU/memory-wasting Windows scanner (and now "Security Center" nonsense), but find manually updating the DATs (virus definition files) annoying--having to download the dat-####.zip file from:

ftp://ftp.mcafee.com/pub/antivirus/datfiles/4.x/
ftp://ftp.mcafee.com/pub/datfiles/english/
ftp://ftp.nai.com/pub/datfiles/english/

(and who knows where else), unzipping it just for the updated files, and moving them to the virus scanner's directory, then you need MCUP!

MCUP updates the DATs by checking ftp.nai.com (built-in, unfortunately) for a newer dat-####.zip file than listed in OLDZIP$ (created the first time MCUP is run, after it downloads the initial dat-####.zip file).

__________
Batch File

Since only clean.dat, internet.dat (rarely updated), names.dat, and scan.dat are needed, I just use a batch file (the included mcup.bat) to delete the unnecessary files and move the above ones to wherever my virus scanner is installed (in a path directory):

mcup
if exist file_id.diz del file_id.diz
if exist packing.lst del packing.lst
if exist pkgdesc.ini del pkgdesc.ini
if exist readme.txt del readme.txt
if exist reseller.txt del reseller.txt
if exist validate.exe del validate.exe
move /y clean.dat c:\utils
move /y internet.dat c:\utils
move /y names.dat c:\utils
move /y scan.dat c:\utils

____________________________________
Command-Line Scanner Updater Request

If anyone is willing to create a scan engine (scan.exe, scanpm.exe, scan86.exe) updater (unfortunately, only available in sdat####.exe, which changes every time a DAT version is released, at ftp://ftp.nai.com/pub/antivirus/superdat/intel/), please email Eep (http://tnlc.com/eep/email.html for email address). The scan engine changes perhaps annually but since there's no way to tell when that occurs for the command-line scanners, an updater would, presumably, like MCUP, need to download the sdat####.exe file, extract it ("sdat#### /e <path>") check for newer command-line scanners, and update the existing ones accordingly (without a batch file would be nice).