If the script ran fine, then you have the updater. F-Prot for Window's updater is
called updater.exe. We use the Windows command line version fpcmd.exe as it is 32-bit
and should run more efficiently.
What new version? F-Prot for Windows is at version 3.12c. It includes the DOS 16 bit
Thanks all for the help. I decided to just go to the frisk web site and download the
new version which indeed updated the fpcmd.exe. I guess I'll change to scheduling the
updater.exe for definitions and just check with frisk for new releases. I appreciate
all the help and suggestions.
Now
is that the option now then? Only use frisk's updater and not a batch scheduled job?
I like the batch proccess as I get an e-mail that I can check to see new definition
files and for success of transfer and install. Maybe the updated does that now too
although I like what I get from my batch
This was discussed a few weeks ago. I use:
@echo off
REM start the F-Prot Anti-Virus Updater
cd C:\progra~1\fsi\f-prot\fp-upd~1
updater.exe /RUN /INTERNET /QUIT
cd \
and start it from AT scheduler. Works well.
--Dan
Bob McGregor wrote:
ok, I purchased the windows version so I assume I
Doesn't the Windows version of F-Prot, which is where the fpcmd.exe is
from,
have it's own updater?
Yes and this is what we use here. So far it works great for us.
Sheldon
Sheldon Koehler, Owner/Partnerhttp://www.tenforward.com
Ten Forward Communications 360-457-9023
Scott, can I still just use f-prot.exe for scanning or do I have to use
fpcmd.exe?
F-Prot.exe will work fine for virus scanning. There are a *few* servers
that have problems with 16-bit programs that cause performance issues under
heavy volume (that fpcmd.exe fixes), but if you were not
