${memory}?

I got the

${memory} error opening [4]

When doing a scan of memory, I never had this problem before, why is a part of the memory locked?

 

I think its part of the memory bug i reported to them. they are aware of it and filed a bug report. dunno when its gonna be fixed tho. **shrug**

 

This must have been fixed with an automatic update because I no longer see it - Eset Antivirus Home edition 3.0.566 on Windows XP SP2

 

still does it on my machine... and the can operating memory still unchecks itself so it hasnt been fixed yet so i dunno when they are going to fix it =( bug was reported 11/17 =( maybe in next release but who knows when thst is going to be they wont tell you over the phone =(


Scan Log
Version of virus signature database: 2707 (20071206)
Date: 12/6/2007 Time: 5:32:05 PM
Scanned disks, folders and files: Operating memory;Operating memory;Operating memory;Operating memory;Operating memory;Operating memory
${Memory} - error opening [4]
${Memory} - error opening [4]
${Memory} - error opening [4]
${Memory} - error opening [4]
${Memory} - error opening [4]
Number of scanned objects: 390
Number of threats found: 0
Time of completion: 17:32:19 Total scanning time: 14 sec (00:00:14)
Notes:
[4] Object cannot be opened. It may be in use by another application or operating system.

 

Please fill in the integrated technical support query form and submit it so that we have more information about your EAV and system configuration.

 

Send information for Eset - Here

 

Marcos,
I already did and have an email from a tech support guy from Eset on 11/17 and he said that he filed it as a bug report. **shrug**

 

i donot know eset and marcos forget it
please see this thread
https://www.wilderssecurity.com/showthread.php?t=191689&highlight=memory

 

i have win2000 sp4 with 2.80mhz dual core

 

same problem here:

http://img156.imageshack.us/img156/8531/nodkd3.jpg
Shot at 2007-12-07

 

Why on Earth I am not seeing this ... "bug" on any of my computers nor at the office ?

 

do you install ess or eav on win2000 sp4?

 

I don't have Win 2000 machines - just XP

 

the problem is on win2000 sp4 not on winxpsp4
install win2000sp4 and see it by you own eyes
are you with us or eset
we are the users
and eset have to make ess and eav compatible with win 2000 sp4

 

SP2 is the latest genuie one for XP

It is impossible.

Of course .


I asked because I remember an ex-thread where not only 2000 machines had the problem

 

if you install win200 sp4
you can see many bugs like
memory bug
bsod
network disable bug
multi thread warning bug
install and see with you eyes

 

be happy

well i am using winxp sp2 with latest patches so its not only a win2000 prob. could u say what $(Memory) error means. i see no negative behaviour on my machine.

 

HiTech_boy
you have to think like a nod user
we are not reporting false bugs
we see it and tell it

 

winxp sp2 with all patches here and got the bug **shrug** my license expires on 12/30 hope they have it sorted out by then

 

Which profile are you using to scan? Whenever I go into "Custom Scan", the "Scan profile" defaults to "My profile". If I then check "Operating memory" and scan, I get the "bug".

OTOH, if I change the scan profile from "My profile" to either "In-depth scan" OR "Smart scan", I do not see the "error".

 

No , don't get me wrong . I am not saying you report false bugs , NO .
It just seems it is something speficic on your computers that makes the program do act like that (since it doesn't happen here)

Doing the same and :




https://www.wilderssecurity.com/showpost.php?p=1119386&postcount=30