From eScan Wiki
(Difference between revisions)
Revision as of 07:13, 15 June 2009 WikiSysop (Talk | contribs) ← Previous diff |
Revision as of 06:08, 21 June 2009 WikiSysop (Talk | contribs) Next diff → |
||
Line 4: | Line 4: | ||
| style="width:56%; color:#000;" | | | style="width:56%; color:#000;" | | ||
{| style="width:280px; border:none; background:none;" | {| style="width:280px; border:none; background:none;" | ||
- | | [[Image:mwti_logo.gif|frame|left|100px|<!--We add confidence to computing-->]] | + | | [[Image:mwti_logo.gif|left]] |
|} | |} | ||
|width="1000pt" style="width:11%; font-size:95%;" white-space:nowrap;| | |width="1000pt" style="width:11%; font-size:95%;" white-space:nowrap;| |
Revision as of 06:08, 21 June 2009
|
General |
Knowledgebase |
Support |
Q. Will eScan cause instability & performance hit?
A. Since eScan works well above the "raw-packet" layer, MS-MWL - on its own - should not cause any instability and/or performance hit.
Please note however that the anti-virus & any Content-Check components of eScan do use CPU resources & RAM.
Email us your feedback to solutions@mwti.net