* Introducing * - beta version of upcoming avast update (4.7.807)

Avast 4.7 has now been officially released (build number is 4.7.817). Use the Program Update menu option in avast GUI to install it. Thanks.

Hi *,

here I’m again. A new version, 4.7, of avast Home/Pro coming soon (my guess is in about a week) and as usual, it’s my pleasure to announce the availability of a pre-release version of this update.

How to install it (for starters - most people already know this trick anyway ): simply download and run the following program: http://files.avast.com/files/beta/aswbeta.exe . That’s about all it takes (provided you have the latest version of avast Home/Pro already installed, of course; if you don’t, you can easily download it from the main www.avast.con website).

As the new version number suggests, this update is quite a big one and brings significant number of changes and improvements. Most of them, however, are hidden under the hood so most users will not even notice them (but they’re real, trust me :)).

The improvements include:

  • a new data storage (called "SQLT). Both ODBC and XML data storage is now OBSOLETE. We will be removing the reference to the XML storage from our FAQ entries. RejZoR should remove the storage-manipulation option from his AEC, if it’s still there.

  • WinXP+: the Standard Shield now implements a nice new feature, “do not scan system libraries” (by default on). This should dramatically decrease the number of files scanned during computer boot. For now, it only works with XP SP2 in the following language versions English, French, German, Italian, Portuguese (Brazil), Polish, Czech. And the English version of Windows 2003 Server

  • the boot-time scanner now has considerably improved support for archive scanning

  • the mail scanner module (“Internet Mail” provider) has been significantly changed to improve the overall user experience, especially in case of slow connections (dial-up…). Namely, most of (if not all) the “Timeout expired”-related problems should be gone now.

  • the action “delete/move files on next reboot” has now been made malware resistant. We now use the boot-time scanner engine to perform those actions.

A more complete list of changes and fixes will be published when the update goes official.

Any comments on this milestone release are welcome and appreciated!

Thanks
Vlk

In the Internet Mail scanner, I notice that the connection timeout box is now unchecked after I installed the update. I suppose that is one way of stopping the timeouts … but was it intended?

Inexperienced users (like me) should be warned that Beta means just that? In other words, instal at your own risk as v 4.7 not yet ‘finished’? Any time scale as to when it might be finalised, Vlk?

ODBC/XML tweak was removed from avast! External Control when you added the option for it under Troubleshooting menu :wink:
No need to have tweaker for something that program ca do itself :slight_smile:

Just updated, here is report if you need it:

Information about current update: Total time: 2:08
  • Program: Updated
    (previous version: 4.6.763, updated version: 4.7.807)
  • Vps: Already up to date
    (current version 0615-0)
  • Setup: Updated
    (previous version: 4.6.763, updated version: 4.7.807)

Server: www2.asw.cz (195.47.75.56)
Downloaded files: 9 (5.179,68 KB)
Download time: 1:34

@Greenhatch
As Vlk said in about a week, we’ll get the final release :wink:

In the Internet Mail scanner, I notice that the connection timeout box is now unchecked after I installed the update. I suppose that is one way of stopping the timeouts ... but was it intended?

Yes; the way it works now, it is not needed anymore because your mail client ITSELF will report the timeout if there’s really one. That is, the two pipes (client → avast, and avast → mailserver) that the mail scanner maintains are now kept in synch…

Any time scale as to when it might be finalised, Vlk?

As I said in the original post, very soon. In about a week.

Thanks
Vlk

Vlk, just spotted first bug.

There are “Tlen” entries listed 3 times under Instant Messaging provider.

Vlk,

I admit I have complained loudly about the ineffectiveness of the inbound (port 110) timeout check but what about the avast users who have only become aware of a spambot infestation because avast warned them of a timeout condition on the outbound side (port 25) that had nothing whatsoever to do with their mail client?

I use Internet mail provider just because of heuristics it has, even though i don’t use POP3 mail.
It will warn you about timeouts and about mass mail worms.
Since you’re still not prepared for file heuristics, maybe you should improve this feature to take advantage of difefrent kind of heuristics already available in Internet Mail provider. There is also lots of space for improvements for currently pretty much useless Blocker. But thats a topic for some other day.

Spotted another minor glitch, two options under Troubleshooting menu are separated with way too big gap (where ODBC/XML switch used to be placed).

Installed it without problems. But… Look at IM provider settings window. 3 times repeated the same program ???

There are "Tlen" entries listed 3 times under Instant Messaging provider.

You’re right, this will be easily fixed. :slight_smile: Thx.

but what about the avast users who have only become aware of a spambot infestation because avast warned them of a timeout condition

Well, I don’t believe anyone has become aware of an infection BECAUSE of the timeout message itself. I mean, the message was so cryptic that even most seasoned computer users were confused by it. I agree that it might’ve given a hint to someone who knows how avast works - but there are other ways to do this.

I mean, the Internet Mail provider is still there, and filtering all email traffic. So if the spambot is really sending out spam, it should be detected (at least by the heuristics module)…

Web Shield uses much less memory!!!

From what I have experienced so far, Web Shield appears to use much less memory then before. Possibly because of the new data storage type?

I pounded the piss out of Web Shield with Firefox opening 10 to 15 tabs at once, going through each section of my bookmarks. Highest I got Web Shield was 8,000 K and would quickly settle back down to around 5,000 K. Prior to this beta it regular web browsing Web Shield was around 12,000 K and up.

One glitch to point out. The providers all say version “4.6-807” but all other areas seem to be correct saying “4.7-807”.

Cheers!

It’s correct, during beta testing they’ll release updates which will slowly progress toward to version 4.7 (so we can test if reported stuff was fixed properly). And thats the day when 4.7 final will be released :wink:

I don’t think it’s a bug. ;D Yes, the same here. Startup and memory scan screen shows 4.6 too. ;D But I know it’s 4.7 ;D

Yeah, the version labels are probably not changed in all places yet. We will most likely settle this tomorrow…

Well, I don't believe anyone has become aware of an infection BECAUSE of the timeout message itself. I mean, the message was so cryptic that even most seasoned computer users were confused by it. I agree that it might've given a hint to someone who knows how avast works - but there are other ways to do this.

You are, of course, absolutely right. They did almost always need the help of the forum to explain the condition.

I mean, the Internet Mail provider is still there, and filtering all email traffic. So if the spambot is really sending out spam, it should be detected (at least by the heuristics module)...

Perhaps we can agree that spambots really do send out spam. I think I can recall one, maybe two, instance(s) of heuristics catching mass spam mailings reported in the forum. I recall very many more indicated by the timeout warning. Have the heuristics been modified in this release?

Hm, another thing which is probably not related to beta directly (or is it?)

http://img156.imageshack.us/img156/15/vpsdefs9pl.png

I thought VPS 0XXX-0 means the first update of the week, even though it’s not the new week at all (it’s sunday, though update shows 8.4 so saturday!)

And i think i’ve seen the same version yesterday.

Btw, looks like providers version is wrong after all. Or the one in About box. See the program version on picture above…

RejZoR,

  • VPS 0615-0 was released yesterday around midnight (that is, night from Saturday to Sunday)
  • it does not show on the VPS history page because it doesn’t have any new virus names in it (this has happened a couple of times in the past, already)
  • while the rule that the “-0” VPS is always released first in a week generally holds, it’s not an axiom. There are some technical reasons why we may choose to release a “-0” VPS e.g. on Saturday on Sunday :slight_smile:

Has update tray icon been fixed or is it still workin old way (showing on every update check instead just on actual VPS updates?)

Just installed the beta, works great here, exept for the things reported here :slight_smile:
And one more thing, I’ve found one translation problem which appear only in the main program Window, the tooltip help is not correctly shown (well for the Bulgarian translation) Here’s and screen shoot:

http://i16.photobucket.com/albums/b38/xmas3/987545.jpg

And I’ve noticed one new thing when a scan is in prograss i see this:

http://i16.photobucket.com/albums/b38/xmas3/45624.jpg

I already found the next error!!! One cannot access no more the container, which more imer terminated, with the error message: “0” that is the only one, which comes as Fehlermeldungt. One could access the system container and continues to stand there meanwhile nothing more in it, in the new version, there is still some suspect.

That is the error message of the virus container: Initialization of container files Action was terminated with errors! Program cannot use container Client: (zero) – description: Access refuses Initialization of container files ----------------------------------------------------------------------------------------- Program tries shop of all container files of the following server: (zero) ----------------------------------------------------------------------------------------- Action was terminated with errors!