It just reports the signature file is up to date no matter how many times I 
run it.  I wondering if this may have something to do with the Network 
Inspection System definitions.
-- 


Brought to you from Anchorage, Alaska

"VanguardLH"  wrote in message 
news:eibif5Fg0mkU1@mid.individual.net...
> Bill Bradshaw wrote:
>
>> Thanks for your response.  I have run this program from the command 
>> prompt.
>> Is the signature update different from updating the virus definitions 
>> from
>> within MSE Update?  I guess basically I am asking are there 2 database(?)
>> files involved because I know the definitions get updated every morning
>> because I do it manually as my first step after turning on the computer.
>
> The GUI frontend probably checks status to determine if the database
> file is newer than the last retrieved database.  I haven't used the
> command-mode mpcmdrun tool to know if it bypasses the download by first
> checking if the database's datestamp is newer than the local one's
> datestamp.
>
> The -SignatureUpdate switch can take additional arguments on the command
> line.  The only one that I know about is the -unc argument which
> specifies an alternate path to a definition file using a UNC; see
> https://en.wikipedia.org/wiki/Path_(computing)#Uniform_Naming_Convention.
> Sometimes users will download the definition file and then use mpcmdrun
> to use that one.  For example, they may disable auto-update and decide
> when to update using the downloaded def file and either run mpcmdrun
> themself or have it as a scheduled task.
>
> If you run "mpcmdrun.exe -signatureupdate" in a command shell, what do
> you see for its console output?  Do an update, then following with
> another update.  Does it just go ahead and push in the same update or
> does it notify you that the database is already up to date? 


--- NewsGate v1.0 gamma 2