ISTech Support Forum

ISTech Support Forum
http://www.istechforum.com/YaBB.pl
Evo-ERP and DBA Classic >> Problem Reports - Repeatable >> Anti virus software has large effect on EVO
http://www.istechforum.com/YaBB.pl?num=1175021945

Message started by Reid on 03/27/07 at 11:59:04

Title: Anti virus software has large effect on EVO
Post by Reid on 03/27/07 at 11:59:04

As I evaluate EVO and consider whether to implement it company-wide, one of the things I notice is how long it takes (about 5 seconds) to load EVO screens (DBA screens load instantly).

I have discovered that the load time is reduced by half if I disable the auto-protect function of Symantec AntiVirus. In initial conversations with my network consultant, we're wondering why DBA and EVO are so different in this regard. Is the application infrastructure dramatically different?

Can anyone offer support in this regard? Are there settings within SAV to make it co-exist better with EVO?

Thanks,
Reid

Title: Re: Anti virus software has large effect on EVO
Post by JNAPIER on 03/27/07 at 12:12:23

It will help to configure your exclusions in Norton to exclude the following.

*.rwn
*.run
tp7runtime.exe
*.rtm
evoerp.exe

That is all I can remember, their might be more.

John

Title: Re: Anti virus software has large effect on EVO
Post by David Waldmann on 08/26/09 at 06:11:21

We just switched from AVG to Kaspersky and am having real trouble with DBA/Evo. We are still using all the old (non-GUI) screens and everything is like molasses. It takes 5-10 seconds to open a window. Even moving from one field to the next in some cases (seems to be mostly fields that have a lookup in them) can take 2-3 seconds.

I've excluded the following directories:
C:\ISTS\*.*
P:\DBAMFG\*.* (program files)
S:\DBA\*.* (data)

I have not seen any difference in performance as I added the various directories.

Have I missed something, or is there something that should be done with Pervasive?

Title: Re: Anti virus software has large effect on EVO
Post by David Waldmann on 08/27/09 at 08:58:38

NM, there was one other setting - whether or not to scan all network traffic - that took care of it.