Author Topic: 98 S.E problems on previous 4.7 build  (Read 18126 times)

0 Members and 1 Guest are viewing this topic.

Offline nightshade

  • Avast Evangelist
  • Advanced Poster
  • ***
  • Posts: 682
Re: 98 S.E problems on previous 4.7 build
« Reply #30 on: April 11, 2008, 01:08:00 AM »
Can you try if the latest beta version solves this?
Download the updater (http://files.avast.com/files/beta/aswbeta.exe) and run it or go here for more information.

Dear Tech,

Can I wait and do this later as I don't have Avast installed as yet, as I am waiting until the support for AVG drops in August, then I am installing Avast.

I am kind of confused a little, is the beta the same as the 4.8?

Also when you asked to run the updater is that to be used when someone has version 4.7? what is it actually updating?
« Last Edit: April 11, 2008, 01:18:43 AM by nightshade »
Free Avast 19.8.2393 (build 19.8.4793.535)
Windows 7, Google Chrome Version for android
77.0.3.865.92 (Official Build) (32-bit)

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 82696
  • No support PMs thanks
Re: 98 S.E problems on previous 4.7 build
« Reply #31 on: April 11, 2008, 01:26:22 AM »
I don't know why you are waiting, avast is far better ;D

I haven't looked back since I jumped the AVG ship 4 years ago.
WinXP ProSP3/ Core2Duo E8300/ 4GB Ram/ avast! free 18.5.2342/ Firefox ESR, uBlock Origin, uMatrix/ MailWasher Pro7.11.0/ DropMyRights/ WinPatrol+/ Drive Image 7.1/ SnagIt 10.0/ avast! mobile security
Windows 10 Home 1909 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 20.1.2397 (build 20.1.5069.558) UI-1.0.460/ WinPatrol+/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro

Offline oldman

  • Avast Evangelist
  • Massive Poster
  • ***
  • Posts: 4143
  • Some days..... MOS...this bug's for you
Re: 98 S.E problems on previous 4.7 build
« Reply #32 on: April 11, 2008, 01:34:51 AM »
As mentioned, I haven't seen that happen lately. Perhaps something in avast has changed.

Can I ask which version you currently use when you say you haven't seen it happen lately?


4.7.1043

Offline nightshade

  • Avast Evangelist
  • Advanced Poster
  • ***
  • Posts: 682
Re: 98 S.E problems on previous 4.7 build
« Reply #33 on: April 11, 2008, 01:44:13 AM »
I don't know why you are waiting, avast is far better ;D

I did install it last year, but the icon problem put me off, but of course that was before I learned that AVG were discontinuing support for my system, now I am being forced to change, ah well.

I am waiting for Tech to answer a couple of questions in a reply to his message as I am a little confused to say the least.
Free Avast 19.8.2393 (build 19.8.4793.535)
Windows 7, Google Chrome Version for android
77.0.3.865.92 (Official Build) (32-bit)

Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67275
Re: 98 S.E problems on previous 4.7 build
« Reply #34 on: April 11, 2008, 03:11:31 AM »
I am kind of confused a little, is the beta the same as the 4.8?
The current version is 4.8.1169. The beta is 4.8.1178.

Also when you asked to run the updater is that to be used when someone has version 4.7? what is it actually updating?
You'll update from any version (4.7 or 4.8 versions) to 4.8.1178.
The best things in life are free.

Offline alanrf

  • Avast Evangelist
  • Massive Poster
  • ***
  • Posts: 3867
  • Just an avast user
Re: 98 S.E problems on previous 4.7 build
« Reply #35 on: April 11, 2008, 04:03:54 AM »
A beta is always with avast the chance for users to test a release of avast that is not currently delivered to the main user population.  avast is seeking help from those of us willing to take some risk to test out the new release of avast before it becomes the release which all users get offered.

Please be aware that though the avast team does their best to ensure the quality of beta releases before starting a beta program there are always some risks with testing beta releases.  Anyone testing with a beta release is well advised to have a backup of their system or alternative recovery strategy before starting to test with the beta release.

Offline Vladimyr

  • Avast Evangelist
  • Super Poster
  • ***
  • Posts: 1640
  • Super(massive black hole) Poster
Re: 98 S.E problems on previous 4.7 build
« Reply #36 on: April 11, 2008, 04:27:07 AM »
I actually tried to add another 256 of ram but for some reason when I turned on the PC and hit the internet explorer icon I went into a loop with a message saying that explorer could not connect and to restart, but as I say this went into a loop so I took out the RAM and the problem went away.

One other thing I would like to add is when the new RAM was in it showed up as a total of 511 instead of 512.

Sorry I didn't notice this earlier. Does the m/board have an Intel chipset with integrated graphics?
Some Intel chips have an on-demand GPU memory allocation whereby a nominal 1MB is assigned to graphics but the actual amount being used is constantly adjusted on-the-fly as demanded by running programs. This can lead to display anomalies but I don't really know if your disappearing icons is one of them.
There is a way that seems right to a man,
       but in the end it leads to death
.” - Proverbs 16:25

Offline nightshade

  • Avast Evangelist
  • Advanced Poster
  • ***
  • Posts: 682
Re: 98 S.E problems on previous 4.7 build
« Reply #37 on: April 11, 2008, 09:59:44 AM »
I actually tried to add another 256 of ram but for some reason when I turned on the PC and hit the internet explorer icon I went into a loop with a message saying that explorer could not connect and to restart, but as I say this went into a loop so I took out the RAM and the problem went away.

One other thing I would like to add is when the new RAM was in it showed up as a total of 511 instead of 512.

Sorry I didn't notice this earlier. Does the m/board have an Intel chipset with integrated graphics?
Some Intel chips have an on-demand GPU memory allocation whereby a nominal 1MB is assigned to graphics but the actual amount being used is constantly adjusted on-the-fly as demanded by running programs. This can lead to display anomalies but I don't really know if your disappearing icons is one of them.

I have the following.

NVIDIA GeForce2 GTS
BUS Type : AGP
Bios Version: 3.15.00.12
On Board Memory: 64MB
IRQ 11:
TV Encoder Type: Conexant Bt869
Free Avast 19.8.2393 (build 19.8.4793.535)
Windows 7, Google Chrome Version for android
77.0.3.865.92 (Official Build) (32-bit)

Offline nightshade

  • Avast Evangelist
  • Advanced Poster
  • ***
  • Posts: 682
Re: 98 S.E problems on previous 4.7 build
« Reply #38 on: April 11, 2008, 10:37:31 AM »
I will more than likely be downloading version 4.8.1169.

Is this when I use the updater if I want to try the beta which is  4.8.1178.
Free Avast 19.8.2393 (build 19.8.4793.535)
Windows 7, Google Chrome Version for android
77.0.3.865.92 (Official Build) (32-bit)

Offline nightshade

  • Avast Evangelist
  • Advanced Poster
  • ***
  • Posts: 682
Re: 98 S.E problems on previous 4.7 build
« Reply #39 on: April 11, 2008, 12:26:37 PM »
I am kind of confused a little, is the beta the same as the 4.8?
The current version is 4.8.1169. The beta is 4.8.1178.

Also when you asked to run the updater is that to be used when someone has version 4.7? what is it actually updating?
You'll update from any version (4.7 or 4.8 versions) to 4.8.1178.

I have now installed version 4.8.1178.

And I am unable to click on the self defence module as it is greyed out.

Any ideas?
Free Avast 19.8.2393 (build 19.8.4793.535)
Windows 7, Google Chrome Version for android
77.0.3.865.92 (Official Build) (32-bit)

Offline alanrf

  • Avast Evangelist
  • Massive Poster
  • ***
  • Posts: 3867
  • Just an avast user
Re: 98 S.E problems on previous 4.7 build
« Reply #40 on: April 11, 2008, 12:49:12 PM »
The newer functions of avast including the self-defense module are not supported or available in the Windows 9x operating systems.

Offline nightshade

  • Avast Evangelist
  • Advanced Poster
  • ***
  • Posts: 682
Re: 98 S.E problems on previous 4.7 build
« Reply #41 on: April 11, 2008, 01:10:46 PM »
The newer functions of avast including the self-defense module are not supported or available in the Windows 9x operating systems.
Does this then mean I will not be able to test the beta, and will just need to wait on a new program update?
Free Avast 19.8.2393 (build 19.8.4793.535)
Windows 7, Google Chrome Version for android
77.0.3.865.92 (Official Build) (32-bit)

Offline alanrf

  • Avast Evangelist
  • Massive Poster
  • ***
  • Posts: 3867
  • Just an avast user
Re: 98 S.E problems on previous 4.7 build
« Reply #42 on: April 11, 2008, 01:28:42 PM »
It means that wait until doomsday you will never have support of the newer functions of avast, in any release of avast - beta or production, while you continue to use the Windows 9x operating systems.

Offline nightshade

  • Avast Evangelist
  • Advanced Poster
  • ***
  • Posts: 682
Re: 98 S.E problems on previous 4.7 build
« Reply #43 on: April 11, 2008, 01:31:20 PM »
It means that wait until doomsday you will never have support of the newer functions of avast, in any release of avast - beta or production, while you continue to use the Windows 9x operating systems.

So why did Tech ask me to try the beta?

Its not the functions I am on about, it's what Tech asked to do so that I could install the Beta.
« Last Edit: April 11, 2008, 01:33:16 PM by nightshade »
Free Avast 19.8.2393 (build 19.8.4793.535)
Windows 7, Google Chrome Version for android
77.0.3.865.92 (Official Build) (32-bit)

Offline alanrf

  • Avast Evangelist
  • Massive Poster
  • ***
  • Posts: 3867
  • Just an avast user
Re: 98 S.E problems on previous 4.7 build
« Reply #44 on: April 11, 2008, 01:43:55 PM »
I must not try to speak for Tech but I think that perhaps Tech was hoping that the problem (this thread is now so long and messy that I think this issue may have become lost) would be fixed in the new 4.8 beta release.

I thought that this (and your concern) was about the loss of the quick launch icons - which has existed with previous versions of avast.  If so then I have to say that I think the suggestion that this might be fixed in the new beta release of avast 4.8 is stretching hope a very long way.