Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: YLAP on April 30, 2007, 09:06:53 PM
-
Hello everyone!
I know this time it is stupid question, but... What will be next? avast 4.8 or well see beta to test v.5 ? ;D
-
Maybe 4.7.1005
-
Funny ;D I can't remember if avast has had 4.*.**** version number ;D
-
alanrf pretty much guessed it, the build number goes on sequentially (i.e. after 999 comes 1000).
But frankly, we don't expect to have more new versions in the near future. We hope that build 997 will last for some time :)
-
We hope that build 997 will last for some time
Except when that hope needs to be changed a few hours later.
(Sorry I was wrong about 1005 ... it was just 1001 ... I bet they skip 1005 just to prove me wrong).
-
:-[
-
Oh... Now I see what's next ;D (interesting I was not asked to restart pc after update, but i did it without asking) :)
-
We hope that build 997 will last for some time
Except when that hope needs to be changed a few hours later.
Sod's Law in action ;D
If you say it won't happen it will, if you say it will happen it doesn't.
-
A only once BSOD episode after updating to 4.7.997
0x00000050 (0xe132b000, 0x00000000, 0x80509b92, 0x00000001)
Memory dump to C:\WINDOWS\MEMORY.DMP
Thanks God, next boot, everything fine.
I'm trying to update to 4.7.1001 now...
-
Oh... Now I see what's next ;D (interesting I was not asked to restart pc after update, but i did it without asking) :)
Odd, 1001 did ask me to restart, as the vast majority of avast program upgrades have done. Maybe it depends on what OS?
-
Odd, 1001 did ask me to restart, as the vast majority of avast program upgrades have done. Maybe it depends on what OS?
For me it asked as usual... the problem was a lonely BSOD after it... strange...
-
Stop 50 sometimes means, 'incompatible software'. Strange ???
- Stop 0x00000050 or PAGE_FAULT_IN_NONPAGED_AREA - The Stop 0x50 message indicates that requested data was not in memory. The system generates an exception error when using a reference to an invalid system memory address. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause Stop 0x50 messages.
-
Tech, you always advise people to send me the minidump - now you have a bluescreen yourself and don't send me anything...? ;D :P
-
Tech, you always advise people to send me the minidump - now you have a bluescreen yourself and don't send me anything...? ;D :P
It was a lonely one... how can I be sure it's avast related.
Ok, I've tryed but I can't find the file C:\WINDOWS\MEMORY.DMP that Windows says that was saved.
I can't find nothing into C:\WINDOWS\Minidump folder either.
My settings are for saving here %SystemRoot%\MEMORY.DMP
It's strange, do you have any solution for that Vlk? Thanks.
-
Tech, make a search in your computer for: *.dmp
-
A programmer once told me that if you 'send a report to Microsoft' (after an error) that your mem-dump is deleted. I've never been able to verify this -- and in fact -- doesn't make sense to me. ???
-
A programmer once told me that if you 'send a report to Microsoft' (after an error) that your mem-dump is deleted. I've never been able to verify this -- and in fact -- doesn't make sense to me. ???
I never send any file dump to Microsoft... for what? Do they give me support when I need it? I've payed for Windows and Office, and what? When I need, nothing, caput, zero... support. I hate this kind of costumer relationship. I hate lack of support.
I'll try to find any *.dmp file now...
-
The dumps submitted to Microsoft are processed by a sophisticated automated system, the faulting module is (attempted to be) detected, and if there is a higher count of identical problems, the related module vendor is notified about it (that's what Vlk told me some time ago, at least.)
So, it actually might be useful sometimes (but I have no idea if the dump is deleted or not during the submission).
-
The dumps submitted to Microsoft are processed by a sophisticated automated system, the faulting module is (attempted to be) detected, and if there is a higher count of identical problems, the related module vendor is notified about it (that's what Vlk told me some time ago, at least.)
I believe in Vlk.
I don't believe (all the times) on Microsoft.
Anyway, no dump file to send to Vlk, strange...