Hello Eddy (and Everybody else),
Several days again waiting for several times new updates being available. Sorry to insist, but this leads back to what I had found at the beginning :
- since there is a modem to detect on the proxy PC, not on the client station,
- since the proxy PC does dial-on-demand indistinctly for any Internet access query from the station,
- since the proxy PC has Windows auto-dial disabled, only the proxy software can dial on a query from another station only,
So:
= on the proxy PC:
- auto-update is enabled, but since Avast! cannot force to dial, its correctly waits for a connection to be open, then it pings its server and maybe updates. That's fine.
= on the station:
- auto-update is enabled, and depending on the "permanently connected" setting, two cases may occur:
- - if not checked, Avast! never detects that a connection is open, probably because it cannot ping outside, and so it never updates as the proxy PC does, anytime the connection could keep alive (I waited for much more than 40mn),
- - if checked, Avast! queries the proxy PC and gets connected immediately then at every session opening (I suppose when the systray component starts). So I must conclude that it has no need to detect a connection since it is able to connect whenever it wants.
So maybe what you said is what it should do, but what I say is what it actually does in such a configuration.
Misc topic:
Also, I wonder if it coudn't be safer if the Avast! service was able to start with a high priority (as my firewall does), since currently its icon in the systray is the last one to appear (after Money and other less important services). I will try to change this order by hand from the registry as I'm able to do it, but it would be nice it Avast! could do it by itself on installing (suggestion to evaluate).
Greetings.
CD