Auto Update

Avast Free Antivirus / Premium Security
1

Since latest program updates, Avast attempts to contact the download server while DUN is still negotiating the connection. I get a message saying that the Avast server is down, which it is not. I can manually connect to the server after the connection is established. Is there some seting that controls this behavior that I am missing, or or is there a bug in the program?

Ver 4.1.289

2

I think Rod is correct. I have posted something before in this forum but I get no answer… :cry:

3

Rod, do you have the “I only connect to the Internet using a dial-up connection” option set in avast settings?

Vlk

4

Vlk, I don’t know if Rod did what you say but I’m sure my Windows 98 machine is correctly set for it. Is there any reason for server down troubles of these weeks? :wink:
Is Rod (and I) correct when he says avast attempts to contact the download server while DUN is still negotiating the connection?

5

I have settings for dialup, and not for always connected. In ini file :
[InetWD]
UseRAS=1
AssumeAlwaysConnected=0

I get the red alert message before the modem finishes sending user and password to provider. It just started doing this since the last 2 updates.

I can set for manual upates if necessary, but would like to continue using auto update.

Thanks for replies.

6

Rod, do you also use Windows 9x?
The thing is, the modem (the Windows’ RAS subsystem, to be more specific) is probably reporting the ‘connected’ status before the connection is actually established…

I’ll try to make an updated version and deliver it to you.

Thanks for your help,
Vlk

7

Thanks for the quick response. I apologize for not stating the OS. On this machine, I am using Win 2k SP4. The modem is an internal Zoom Win Modem on a dialup connection. Windows lists it as a CNXT V92 data fax modem.

Thanks,
Rod

8

Please download the updated version here: http://www2.asw.cz/~vlk/ashServ.exe . Just replace the ashServ.exe file in your avast directory with this one, and see if it helps.

The file will be locked so you’ll first need to stop the ‘avast antivirus’ service (Control Panel/Administrative Tools/Services).

Also it’s little tricky that the avast’s auto-correct feature will actually try to replace the patched version by the original one; but unless you reboot, it will not be able to do this (but will ask you to reboot which you’ll refuse :))

Thanks
Vlk

9

I replaced the file, and so far no problem. If I ask Avast to do an update, it tells me that I am up to date, but then asks if I want to reboot. What happens when I reboot the machine? Will Avast replace the file, and then I have to reinstall again? Will I get this reboot screen every time I want to update?

Thanks,
Rod

10
What happens when I reboot the machine? Will Avast replace the file, and then I have to reinstall again?

Yes.

Will I get this reboot screen every time I want to update?

Yes.

Sorry, but this is how it works. It doesn’t like patched files :slight_smile:
But this is just a temporary thing, just to test it helped.
If you’ve got some time (and still have the original setup exe file), it may be worth trying to reinstall the program, replacing the ashServ.exe file upon installation, and leting it to do the VPS update as you connect to the Internet (the original setup exe doesn’t contain the latest VPS file, of course).

Thanks for your help,
Vlk

11

Uninstalled, and reinstalled and replaced file before rebooting. When I updated the program, it reinstalled the original file. I’ll se if problems pop up again.

Thanks for your help.

Rod

12

…so that means the auto-update feature worked this time?

13

Seems to be working so far. I’ll post if I have problems.

Thanks,
Rod

14

I´ll post my results (If I remember of course…) on my Windows 98 machine…
Thanks Rod for your tests and Vlk for your wisdom :wink:

15

Auto update worked fine until iAVS was updated today. When I next started dun, got the red box before connection was completed again. Will try replacing ashserve.exe file again, and see if this solves anything.

16

Why don’t you try to delay the starting of the update with NetRun. This application detects the connection state and lauch programs automatically. You can set the programs or just drag & drop them into the main window.

Put there the C:\Arquivos de programas\Avast\aswUpdSv.exe and set it for running some seconds after the connection be done. Probably in Windows 98 you will have to delete some Startup item (in Windows XP is a service called avast! iAVS4 Control Service that must be stoped).

I know it’s not the final solution but untill there… Anyway, you will love NetRun… :wink:

17

I am using win98se with a dial-up connection and seem to be having the same problem. I have Avast set for dial up connection only, and auto update. The problem is that if I execute IE or Ms Outlook, my default connection box comes on and tries to dial out as normal, but after 15 seconds into the dial up process, another box with my default connection box comes up again cancelling the first one and tries to dial out a second time. Zone Alarm reports that it is Avast trying to establish the connection. Seems Avast is a little gung ho and is trying to update before a connection is established. I then have to go into the task manager to quit the first dial up connection to get rid of the connection box that is up on the screen. For the meantime I have set my updates to manual until a fix is provided. This problem happened right after the last Avast Program update. Hope it gets fixed, I would rather have auto updates anytime.

18

I have to agree with you :cry:
But, just to some technical troubleshotting, what is your setting for dialing up into Internet Explorer options (Connections): Never dial or Always dial up the default connection? :wink:

19

I have it set to always dial my default connection if that helps any.

20

I reinstalled Vlk’s patched ashserve.exe file and all appears to be working well. An update of iAVS worked fine today. The program asks for a reboot, which must be declined, but everything works fine until you have to reboot, and then the patched file has to be reinstalled. I hope that the patched file can be made part of the std installation, so that reinstallation won’t have to be done.