Ewido 4.0 beta bug

Grammar and a missing word...Disallow scripts to 'be' executed.
Delete the word 'to' as it's not needed in this sentence.

 

All in all a great bit of work from ewido.
I really like the new look and all the additional tools and options.

Well done people.

 

I think it should be:

If the resident shield is not active this is a security risk. It will not block and clean threats trying to run on your system.

Gerard

 

Geez, I'm not getting any of these probs (except for the grammar errors, of course).. it's working perfectly smoothly on my machine, which is an absolute miracle :X

 

I think this should be...You should keep automatic updates active to always be up to date and protected against the latest threats.

 

Me neither, so far so good.

 

Apart from the cpu issue (will be fixed) it's running ok here to!
After a complete sys scan it found one (low risk) issue: NetworkActivePIAFCTM, but this app. was installed on my machine by myself

Gerard

 

Here is an omitted word:
http://img260.imageshack.us/img260/5363/ewidopic30qp.jpg

 

This doesn't sound right to me..
http://img284.imageshack.us/img284/1669/ewidopic43cw.jpg

I think you should take out the word "be" and put it after the word "always"..

 

My suggestion:

You should always keep automatic update active in order to get the most updated protection against the latest threats.

 

My suggestion:

If the resident shield is not active, it will not be able to block and clean threats trying to run on your system. This is a security risk.

"This is a security risk", IMHO, is not necessary and optional. The title "Your computer is at risk" is already the result of not having the resident shield active.

 

I checked the backup I took before installing the 4.0 beta; nothing like uninstall* in there.

Anyway, it's not a big deal - I just wanted to let you know that with the current version there is no upgrade occurring. This should be addressed before the final release of version 4.

Thanks for a great product!

 

May I suggest that we create a new topic for spelling/grammar issues (since there seem to be so many [small ones, I admit]) ?

 

Well this is a good idea since those grammar mistakes are many (most of them are minor) and they are not really bugs.I suggest the next tester that will find a mistake should create a new topic with the appropriate title.

 

The wording bugs are listed here, are fixed in 4.0.0.151

Also the number displaying but ",00" _should_ be fixed.
BR

 

I just downloaded the 1.51 and ALL ,00 bugs that I described are gone.
Congratulations!
But this build still crashes when I cancel a fast system scan midway as described in one of my previous posts.

 

I tried to reproduce it but i can't

BR

 

Well Vinzenz there are more bugs ...
Firstly today I tested the Complete Scan and the program still crashes when cancelling the scan midway.
But lets forget this problem for a moment since there are also other bugs.
If I start any scan and then cancel the scan before it is completed the following things happen.
The progress bar reaches at once at the end and it reports that the scan has being completed.
Take a look at the three following screen captures.
You can clearly see in the first picture that we are in the middle of the scan.
But in the second picture right after cancelling the scan the progress bar is full and it says that the scan
is completed though you can see that the number of files scanned and the time elapsed are exactly the same.
In the third picture you can see that the main screen reports that the last scan was performed today (27/4/2006).
But today I didnt let on purpose none of the scans I started to complete!
So we have these problems ...
If someone starts a scan and then cancels it the program reports that scan is completed while its not.
Also the date of the last scan is set to reflect when this not-completed scan happened.
My opinion is that when it says Last scan it should report the last not-cancelled scan because when someone
checks the date of the last scan he cannot be sure whether the whole system was scanned or
not.A cancelled system scan does not ensure a malware free computer.So when a scan is cancelled instead
of reporting it as completed it should report it as stopped (or cancelled).

 

2nd picture

 

3rd picture

 

I have two more computers in my home with windows XP.
I will try to reproduce the crashing problem on them and I will tell you what heppened...

P.S
Can anyone else confirm the problem that occurs when cancelling a fast sytem scan or a complete scan midway?
I have described the problem in detail in the previous page.

 

Agreed

 

It is reproducable that the last scan date will be updated although it was aborted.

The crash is still not reproducable

 

In the ewido exit message substitute "is not" with "will not be".

 

now as long as this crashing bug is concerned i think it should be wiser to just leave it for now and to try to solve it later if it insists since it happens only to my pc.
But if you think that there is any file which i can provide to you in order to help you trace the root of the problem I would be happy to give it to you.
In fact below I am attaching the txt file generated by windows drwtsn32.exe.
Also I noticed that after the crash only ewido.exe is terminated while guard.exe still runs in the background properly.

P.S
I suspect it may a windows XP sp2 bug and a problem from your side but I am not sure.