F-Prot on wireless lan

[James Egan]

On my small wireless lan my main machine gets the definition updates
from the f-prot site and the other machines update locally. When the
machines are turned on, they error out on the local update before
their wireless connection on the network is established so they don't
update unless I run the process again manually.

Does anyone know of a method to slow f-prot down until the wireless
connection is established? All the machines are xp.


Jim.

 

[Art]

On my small wireless lan my main machine gets the definition updates
from the f-prot site and the other machines update locally. When the
machines are turned on, they error out on the local update before
their wireless connection on the network is established so they don't
update unless I run the process again manually.

Does anyone know of a method to slow f-prot down until the wireless
connection is established? All the machines are xp.

Google "delay program startup" and you''ll find all kinds of utils and
techniques.

Art
http://home.epix.net/~artnpeg

 

[James Egan]

Google "delay program startup" and you''ll find all kinds of utils and
techniques.

I've already tried delayexec but f-prot checks it's own startup
registry entry, zaps delayexec and reinstates its own entry. Do you
have something similar on your wireless?


Jim.

 

[Art]

I've already tried delayexec but f-prot checks it's own startup
registry entry, zaps delayexec and reinstates its own entry. Do you
have something similar on your wireless?

No. My router was purchased strictly for sharing DSL service between
two PCs, and I don't use realtime av on either, or any kind of
auto-updating. I wonder if F-Prot uses a separate .exe file for
updating the way KAV does. It might wind up complaining and not
working right but my idea is to try delaying that .exe updater program
(if it exists as a separate module). Just another thought.

Art
http://home.epix.net/~artnpeg

 

[James Egan]

No. My router was purchased strictly for sharing DSL service between
two PCs, and I don't use realtime av on either, or any kind of
auto-updating. I wonder if F-Prot uses a separate .exe file for
updating the way KAV does. It might wind up complaining and not
working right but my idea is to try delaying that .exe updater program
(if it exists as a separate module). Just another thought.

Currently, there are two associated processes running. The scheduler
(f-sched.exe) starts via the usual HKLM...\CurrentVersion\Run key and
the update monitor (fpavupdm.exe) which runs automatically as a
service.

Since the scheduler controls if and when the updater is run (on
startup and expired timetasks) it was the scheduler I was attempting
to delay execution of. However, it didn't work. I haven't attempted to
delay the update monitor service yet. I thought I'd ask here instead.


Jim.

 

[Jim]

On my small wireless lan my main machine gets the definition updates
from the f-prot site and the other machines update locally. When the
machines are turned on, they error out on the local update before
their wireless connection on the network is established so they don't
update unless I run the process again manually.

Does anyone know of a method to slow f-prot down until the wireless
connection is established? All the machines are xp.


Jim.

If you open the OnDemand Scanner and select Scheduler, you can disable the
updater or select The Updater Schdule and modify the frequency to something
other than daily.

With the Updater Task selected in the Scheduler, you can also select
Settings and turn off Run on Startup.

Jim

 

[James Egan]

and turn off Run on Startup

I know I can turn it off but that rather defeats the objective. I
would like it to run a minute after startup.


Jim.

 

[me]

I know I can turn it off but that rather defeats the
objective. I would like it to run a minute after startup.


Jim.

Jim,

Try asking at alt.comp.freeware
Similar Qs (in different contexts) usually get more than one
answer (several alternatives).

J