Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: nightshade on April 26, 2008, 03:19:19 AM
-
I have the 4.1.1178 Free home version, as I have 98 S.E and am unable to de-activate the self defence module, what is the correct method to update my Free 4.8.1178 home version to the 1178 Free Home version?
-
As I have Windows 98 S.E i don't have the access to disable the self defence module, so I just clicked on program update and it seemed to update ok, will this be ok, or would I have had to uninstall and reinstall the pre-release 1185 from scratch?
I right clicked the (a) icon on system tray, and selected program update, it all downloaded successfully, and it now says it's build 1185.
It asked for a system re-boot.
Does this all sound the right thing to do?
-
Also I just had a look at the Zone Alarm settings after the manual program update, and they are as follows on the entry detail.
Avast Anti-Virus Update version 4.8.0.0
Avast Email scanner service 4.8.1169
Avast Web Scanner 4.8.1184,0
I know the question was answered recently that the executables dont record the actual program version update, but wondered if these settings were ok.
All the builds show as 1185 in the On Access Protection Control for the installed providers.
-
I found that all I had to do was use the program update feature and I was updated to new beta build 1185 This was consistent with previous beta refreshes.
I suspect that the previous concern was the need to take care of self-defence when first entering the beta program (and I get the impression from VLk's post that the same procedure will be needed when entering future beta programs).
I would not worry too much about the version information being shown by ZoneAlarm. It seems to be a regular feature of the beta program that these are not completely "tidied up" until the new final release is made available.
-
Thank you alanrf,
As I say all the builds show as 1185 in the On Access Protection Control for the installed providers, so it looks ok like you mention.
It's a good program I like it alot.
-
I suspect that the previous concern was the need to take care of self-defence when first entering the beta program (and I get the impression from VLk's post that the same procedure will be needed when entering future beta programs).
In that case though in my position with 98 S.E, what would I need to do given that I am unable to disable the self defence module for future beta programs?
btw, is there a difference between future beta refreshes and future beta programs?
I ask because was this recent update not a beta program update?
-
Please see the current beta thread at the top of the forum. Build 1185 is a refresh within the present beta program. I think that you got into a discussion in another thread about how you more or less stumbled into this beta program.
So let's see if I can explain -
When avast decides to start a beta program then they announce it in the forum. Then avast users willing to participate normally join by downloading and running the aswbeta.exe program. This flags the user's avast configuration as now in the beta program stream and causes the beta version of avast to be installed.
Once the beta program is running there may be 0, 1, 2 (or more but unlikely) updates or "refreshes" of the beta update before the final new production version is released. It is usual for the team to announce the new refresh of the beta as happened today with build 1185. If you are flagged as being in the beta program and you perform a program update then you will get the latest refresh of the beta program.
As discussed before, when the new final production release is made available and it is installed then beta program participants are automatically restored to the normal avast update stream (ie removed from the beta program).
When the avast team decides to run a new beta program then we start all over again with this process.
-
As discussed before, when the new final production release is made available and it is installed then beta program participants are automatically restored to the normal avast update stream (ie removed from the beta program).
So all I would be required to do is click on program update then?
When the avast team decides to run a new beta program then we start all over again with this process.
So in simple terms the last 4 digits are refreshes, and the next beta program could indeed be called 4.9 as an example?
I am just really trying to fathom out what I need to do when there are updates, so I am happy about refreshes but still confused on what to do when there is a complete new program update like for instance a 4.9 update.
Because of the position I find myself with 98 S.E do I just wait till there is notification of a new program update then I click on program update within Avast, as I don't want to be running aswbeta exe files or anything like that, and obviously I cannot disable any self defence modules due to me having Windows 98 S.E
I have build 4.8.1185 at the moment, so it looks like I have a beta program would you say? so when this new release becomes available for download, what is the easiest method for me to update and upgrade?
If you are flagged as being in the beta program and you perform a program update then you will get the latest refresh of the beta program.
Would you say that I have the beta program then? as I have build 4.8.1185 and it let me perform a manual update with no problems from 1178 to 1185.
Not too sure what you meant when you said if you are flagged?
-
When the beta program is over (= when the official version is released), all you have to do is make a program update (either manual, or automatic, doesn't matter) and your program is updated to the official version - and it stays like that.
If another beta is started in the future (could be just 4.8 with a higher build number, not necessarily 4.9), it will be announced on the forum. To install the beta, you always have to download a special executable (which will be included inthe announcement) and start it; without it, you'll always be on the official version. And again, when the beta program is over, all existing beta users are moved to the new official version during a program update.
-
When the beta program is over (= when the official version is released), all you have to do is make a program update (either manual, or automatic, doesn't matter) and your program is updated to the official version - and it stays like that.
If another beta is started in the future (could be just 4.8 with a higher build number, not necessarily 4.9), it will be announced on the forum. To install the beta, you always have to download a special executable (which will be included inthe announcement) and start it; without it, you'll always be on the official version. And again, when the beta program is over, all existing beta users are moved to the new official version during a program update.
So perhaps then it may be easier for me in the circumstances to just wait on final releases by just clicking on program updates when the time comes?
The build I had before I performed the upgrade to 1185 which was 1178 was downloaded from scratch from here http://public.avast.com/~vlk/4.8.1178/setupeng.exe (Home Edition, English version) ~21MB, this seemed to give me the beta right away, am I right in thinking that this would be a beta program? please confirm, because surely it wouldn't have let me perform an update within the program itself unless it was a beta version according to alanrf.
What I am really saying is that I didn't download any special executable, I just originally performed the download from the link I show above, of course I am referring to when I originally installed Avast and not this latest update to the build, although as I explained to alanrf, I didn't perform any download special executable for that either, but he said that is ok.
-
When avast decides to start a beta program then they announce it in the forum. Then avast users willing to participate normally join by downloading and running the aswbeta.exe program. This flags the user's avast configuration as now in the beta program stream and causes the beta version of avast to be installed.
What confuses me is that my original Avast download was from here http://public.avast.com/~vlk/4.8.1178/setupeng.exe (Home Edition, English version) ~21MB and I didn't download using the aswbeta.exe program, which worries me in thinking that it may not be the Beta program that I currently have at the moment.
Did I get away without downloading from the aswbeta.exe program because I didn't have a previous version installed at the time?
So I am hoping at the end of the day that I can just use the program update button all the time without the need to be running the aswbeta program as I will only be really wanting the official versions and not the beta's.
-
Ah, I didn't know that Vlk put the full installer online, too - it's not the usual way.
Anyway, it's not the usual installer - you can consider this file to include both the normal installer, downloadable from our web, and aswBeta.exe in one.
-
Ah, I didn't know that Vlk put the full installer online, too - it's not the usual way.
Anyway, it's not the usual installer - you can consider this file to include both the normal installer, downloadable from our web, and aswBeta.exe in one.
So this means I can keep my current version and just perform the manual program update when the time comes without ever having to future install the aswBeta.exe separately.
I actually preferred the way that vlk put the installer online like that as it went through with no problems, and of course it helps people like me that are unable to disable their self defence modules due to having windows 98 S.E
-
Anyone care to read my latest reply?
-
So this means I can keep my current version and just perform the manual program update when the time comes without ever having to future install the aswBeta.exe separately.
Yes. Once you're using beta, invoking program updates will update the beta (and in the future, to the official release also).
-
So this means I can keep my current version and just perform the manual program update when the time comes without ever having to future install the aswBeta.exe separately.
Yes. Once you're using beta, invoking program updates will update the beta (and in the future, to the official release also).
I understand that now, but, what happens when I need to upgrade once I have the official version?
-
I understand that now, but, what happens when I need to upgrade once I have the official version?
It will upgrade with or without the self defense module on.
The self defense only prevents the first upgrade from official version to beta, i.e., entering the beta program is only done manually disabling the self defense module.
-
It will upgrade with or without the self defense module on.
The self defense only prevents the first upgrade from official version to beta, i.e., entering the beta program is only done manually disabling the self defense module.
The only thing that worries me is when I go out of Beta to an official version, what happens if I want to go into a beta? is that when I need to download the aswbeta.exe file to enable me to enter a new beta program.
-
The only thing that worries me is when I go out of Beta to an official version, what happens if I want to go into a beta? is that when I need to download the aswbeta.exe file to enable me to enter a new beta program.
Yes, you can download it again or you can use the 'old' aswbeta.exe program too... it's very small.
-
When a new beta is announced (after a regular release) on the forums, you will be given the link for aswbeta.exe, this is required only to convert from the regular version to the beta version. If you are on the beta and there is a beta refresh you need only use the program update and you get the refreshed beta version.
When the beta is complete and that is usually indicated by a post on the forums announcing the release of a regular program update. At that point you use the program update and you will be converted to the regular release.
-
The only thing that worries me is when I go out of Beta to an official version, what happens if I want to go into a beta? is that when I need to download the aswbeta.exe file to enable me to enter a new beta program.
Yes, you can download it again or you can use the 'old' aswbeta.exe program too... it's very small.
So would it be better for me to just update to official versions and forget about future beta's? because of the fact that I am unable to disable the defense module.
I wonder how I ended up with a beta as I never downloaded the aswbeta.exe file and only first installed Avast 4.8.1178 from the home link that Vlk posted on the pre-release page.
This must have been the fulll package including the updater for the beta installation.
-
So would it be better for me to just update to official versions and forget about future beta's? because of the fact that I am unable to disable the defense module.
No, you can use beta with or without defense module, no problems.
-
Right ok, just to get all this right, I am currently using a beta free version 4.8.1185. and remember I am on 98 S.E
1. If currently on a beta and want to upgrade to a full official release?
Answer please..................................................................
2. Currently on an official release, new beta required?
Answer please...............................................................
Why I am asking all these questions is because I was a little bit confused due to the fact that I ended up with a beta when I thought i was just installing an official release.
-
1. If currently on a beta and want to upgrade to a full official release?
Just invoke program update.
2. Currently on an official release, new beta required?
Run aswbeta.exe and enter the beta program.
-
Magic, thanks for the info, and sorry for all those questions, just needed to get it right.
-
nightshade ...
it seems that you need Vlk, Tech and DavidR to tell you over again from each what I told you already and, frankly, what you have already been told before in the forum.
-
nightshade ...
it seems that you need Vlk, Tech and DavidR to tell you over again from each what I told you already and, frankly, what you have already been told before in the forum.
Now come on alanrf,
you know for sure that it's not easy to understand when posting on forums, it's all too easy to slag someone that has problems understanding all of this, especially when files are not named as Beta's but later you are told that there were infact Beta!
There have been times when I have seen you guys even question Vlk about what he has written, so lay off the sarcastic attacks on me alanrf!
I had this at the AVG forums and I certainly don't need it here!
-
These are not sarcastic comments.
You sent me a personal message asking me to enter the forum and respond to your concerns. I did so.
The discussion about how you entered this beta program has been repeated by you in the forum. You gave us same the story yet again. You effectively ask the same question in multiple threads. You got the same answers from igor, Vlk, Tech and DavidR as you got from me.
I am happy that you are participating and asking questions. I am surprised that you feel the need to get the same questions answered over again a few days after they have been given to you.
-
These are not sarcastic comments.
You sent me a personal message asking me to enter the forum and respond to your concerns. I did so.
The discussion about how you entered this beta program has been repeated by you in the forum. You gave us same the story yet again. You effectively ask the same question in multiple threads. You got the same answers from igor, Vlk, Tech and DavidR as you got from me.
I am happy that you are participating and asking questions. I am surprised that you feel the need to get the same questions answered over again a few days after they have been given to you.
Look, the answers I get are often written differently by each of you, and it's hard to determine what each of you are trying to say, I thought I made that clear, obviously you didn't understand that.
As for the multiple threads, I didnt realise there were 2 threads running and I thought it was the same one each time as I had forgotten that I had replied to the post by Vlk.
Do you personally believe that everyone understands all of this technical stuff fully, I think not.................
-
I do not want to prolong this but ... after my posts to you (that you requested me to make) I asked you (in a personal message) if they were clear to you or not. By then you were posting the same questions in a different thread and a far more knowledgeable person (igor) had already replied to you.
I cannot speak for any others in this forum but I am not inclined to play in the game of "I will get answers to the same question from as many different sources as possible and see which one I like". I am not saying that is your intent but your posts could be a bit more focused.
We are not nearly as inclined as the AVG forums to the "you will stand to attention and answer the questions or you get no answer" approach. This is a generally free and easy forum with a relaxed approach but please just try to keep your questions going wherever possible in your own thread and if the answer is not clear to you most of us are willing to try to find a way to explain that works for you.
I want to be entirely clear, I welcome you and your participation here in the avast forums. I am just suggesting that we can better help you with a bit more focus.
-
Just for people who stumbled upon this thread, the conclusive answer by Vlk is below.
nightshade, the self-defense module (as with most NEW avast features) is for Windows 2000+ only. This is why it cannot be disabled (well, in fact, it cannot be enabled ;))
rdmaloyjr, why would that be a flaw in the self-defense system? To get from 1178 to 1185 you don't even have to run aswBeta.exe. Simply invoking the program update would actually do the trick. That's because you're now using the beta stream; the beta stream is always valid for all beta refreshes, and once the product is released officially, it is merged to the release stream.
Hope this helps,
Vlk
Means, self-defense module is not working on 98 SE or Me, which is why the option is grayed out. nightshade, if you have problem with the terms, ask it in this thread but please don't repeat the same question.
-
Means, self-defense module is not working on 98 SE or Me, which is why the option is grayed out. nightshade, if you have problem with the terms, ask it in this thread but please don't repeat the same question.
If you read this thread you will know that I am already aware of this.
-
Can someone please explain how I was to know that the link I used here was a beta when it has no reference to a beta in it's title? I am no mind reader.
http://public.avast.com/~vlk/4.8.1178/setupeng.exe (Home Edition, English version) ~21MB
Thank You................
-
If you read this thread you will know that I am already aware of this.
No, I think you didn't understand me properly. Read on.
Can someone please explain how I was to know that the link I used here was a beta when it has no reference to a beta in it's title? I am no mind reader.
http://public.avast.com/~vlk/4.8.1178/setupeng.exe (Home Edition, English version) ~21MB
Thank You................
Now, yes, I have that impression. You had problem with the term. "Pre-release" means beta near to the official version but, probably, it may be suitable for Vlk to re-write it pre-release beta or next time around. Or keep any beta information to the beta board. Jut my two cent.
-
probably, it may be suitable for Vlk to re-write it pre-release beta or next time around. Or keep any beta information to the beta board. Jut my two cent.
My point exactly!
-
nightshade,
assist me please ... can you tell me just where you found this link from Vlk? I would very much like to see the context in which you fell prey to installing a beta product.
Dont' bother ... I see it ...
I am at a loss to where you do not understand that "Pre-release" means not yet in production. You do not have to be a mind reader to work that out.
-
nightshade,
assist me please ... can you tell me just where you found this link from Vlk? I would very much like to see the context in which you fell prey to installing a beta product.
Dont' bother ... I see it ...
I am at a loss to where you do not understand that "Pre-release" means not yet in production. You do not have to be a mind reader to work that out.
I am fully aware of the term pre-release.
Once I get the official stream for the official version and have it downloaded will that be me with the official version for good? unless of course I wanted to run the aswbeta.exe file for a beta.
-
Yes, that is true for all of us.