J
Jeff Barnett
I recently upgraded to ESET NOD32 version 3 and am having a problem. I
am hoping that some one out there has found a solution. (Before asking
here, I have tried ESET support but I think that they are not informed
about their products.) What I want to do is schedule an in-depth scan
during off hours. Please note that my computer is in S3 suspend state
during off hours. The ESET scheduler is incompetent to wake a sleeping
computer. Therefore, I wrote a BAT to run the scan. The BAT wakes the
computer, runs the scan, and allows the computer to reenter S3.
Unfortunately, there is no way to stash the log of that scan where ESET
tools can access and display it. The BAT is scheduled under an
administrative account but I normal work under a limited account, hence
the desire to be able to access the log through ESET tools.
Has anyone of you solved this problem using either the XP (Pro SP2 using
simple file sharing and welcome screen) or ESET scheduler? If so, please
share.
-- Jeff Barnett
PS There was no problem using version 2.7 - I will roll back if I cannot
find a solution to this problem.
am hoping that some one out there has found a solution. (Before asking
here, I have tried ESET support but I think that they are not informed
about their products.) What I want to do is schedule an in-depth scan
during off hours. Please note that my computer is in S3 suspend state
during off hours. The ESET scheduler is incompetent to wake a sleeping
computer. Therefore, I wrote a BAT to run the scan. The BAT wakes the
computer, runs the scan, and allows the computer to reenter S3.
Unfortunately, there is no way to stash the log of that scan where ESET
tools can access and display it. The BAT is scheduled under an
administrative account but I normal work under a limited account, hence
the desire to be able to access the log through ESET tools.
Has anyone of you solved this problem using either the XP (Pro SP2 using
simple file sharing and welcome screen) or ESET scheduler? If so, please
share.
-- Jeff Barnett
PS There was no problem using version 2.7 - I will roll back if I cannot
find a solution to this problem.