Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: Rod on October 31, 2003, 01:08:12 AM
-
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
-
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
I think Rod is correct. I have posted something before in this forum (http://www.avast.com/forum/index.php?board=2;action=display;threadid=1604;start=msg9872#msg9872) but I get no answer... :'(
-
Rod, do you have the "I only connect to the Internet using a dial-up connection" option set in avast settings?
Vlk
-
Rod, do you have the "I only connect to the Internet using a dial-up connection" option set in avast settings?
Vlk
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? ;)
Is Rod (and I) correct when he says avast attempts to contact the download server while DUN is still negotiating the connection?
-
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.
-
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
-
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
-
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
-
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
-
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 :)
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
-
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
-
...so that means the auto-update feature worked this time?
-
Seems to be working so far. I'll post if I have problems.
Thanks,
Rod
-
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
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 ;)
-
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.
-
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.
Why don't you try to delay the starting of the update with NetRun (http://www.ticon.net/~jclogon/NetRunBetaSetup.exe). 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... ;)
-
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.
-
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.
I have to agree with you :'(
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? ;)
-
I have it set to always dial my default connection if that helps any.
-
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.
-
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.
Cochise, why don't you give a try on Rod's solution (and Vlk link for new ashserve.exe)?
The update of today (November 5th) was just a virus database update (VPS 0310-7) and do not ask for reboot in my system, but maybe Rod's have some other stuff to be updated... ;)
-
I gave it a try and like Rod said, it works but Avast will ask you to reboot which I declined it.
Where do we go from here?
-
I do recommend a new full download of avast! setup.
Desinstall / Boot / Download and run avast 4.0 Uninstall (http://www.avast.com/files/eng/avclear4.exe) / Boot / Install again
Try to update and see what happens. This is the text of the update of today (November 5th):
----------------------------------------------------------------------------------
New iAVS update for avast!4 and avast32 has been released recently.
Related files could be also found on our Internet sites.
Note: This is a standard update
----------------------------------------------------------------------------------
-
Avast asks for a reboot, because it wants to replace the ashserve.exe file with the original file. It will ask for a reboot every time it updates, which must be declined, or else the file will be replaced, requiring a replacement of the file again.
I guess this will be the way it is until the program has been changed to include the patched file as the default. I hope this is being worked on.
Rod
-
Avast asks for a reboot, because it wants to replace the ashserve.exe file with the original file. It will ask for a reboot every time it updates, which must be declined, or else the file will be replaced, requiring a replacement of the file again.
I guess this will be the way it is until the program has been changed to include the patched file as the default. I hope this is being worked on.
Rod
I think you're right... Troubles with avast! setup file (and consequently with the updates) are being discussed and posted here (http://www.avast.com/forum/index.php?board=2;action=display;threadid=1662). ;)
-
Another reason to be able to turn off automatic updating :) ....
-
Another reason to be able to turn off automatic updating :) ....
This feature, like a lot of others, relays on user's freedom of choice...
But I disagree of you. Automatic updating is quite the best feature of avast! In a working system, with no installation errors, everything goes fine. I had only a trouble, in the past, with an update. Two hours later, avast! team correct a bug in the update... The price for not automatic updates does not worth the tranquility and peace to get rid and avoid viruses infection. ;)
I do believe in avast! team and users! ;D
-
You may disagree with me purely based on the difficulty to remove such a feature, but as I've said before I understand and agree with that point.
But to me as long as the interface is good and clearly seperates basic and advanced options with good documentation then there is no such thing as a bad option.
I assume that in avast every option that is reasonably easy to turn off or on is integrated (otherwise why would you allow the resdient scanner to be disabled. If a virius were targeted at avast it could in theory shut the engine down.)
Again if the complexity of the situation makes it not productive to do its understandable....My comment had a smile by the way and was a half joke.
-
You may disagree with me purely based on the difficulty to remove such a feature, but as I've said before I understand and agree with that point.
But to me as long as the interface is good and clearly seperates basic and advanced options with good documentation then there is no such thing as a bad option.
I assume that in avast every option that is reasonably easy to turn off or on is integrated (otherwise why would you allow the resdient scanner to be disabled. If a virius were targeted at avast it could in theory shut the engine down.)
Again if the complexity of the situation makes it not productive to do its understandable....My comment had a smile by the way and was a half joke.
Ok, I understand your point of view. By now, just avast! team could say something... It is out of my hands... See you round, bro ;)
-
I do recommend a new full download of avast! setup.
Desinstall / Boot / Download and run avast 4.0 Uninstall (http://www.avast.com/files/eng/avclear4.exe) / Boot / Install again
Try to update and see what happens. This is the text of the update of today (November 5th):
----------------------------------------------------------------------------------
New iAVS update for avast!4 and avast32 has been released recently.
Related files could be also found on our Internet sites.
Note: This is a standard update
----------------------------------------------------------------------------------
I removed Avast with Avclear and downloaded the new Avast file and installed it. I have not seen the double dial that I was getting before but I will see how it works for a few days and keep you posted as far as if the problem goes away.
-
but now UseRAS=1 DOES IT WORK ???? :o :o :o