home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
MediaPortal 1 Talk
the preview 1.7 is really slow for me.
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="JimCatMP" data-source="post: 1075295" data-attributes="member: 103549"><p>The issue is NOT with MePo but with MSE's interaction with MePo.</p><p></p><p>MSE's function is to protect the system so it looks at all running code, depending on code AND heuristics of the scan engine performance can suffer - the scan engine is updated regularly as are the definition files [daily], so there is nothing to 'fix' that could be considered stable, a specific operation set may be issue today and gone tomorrow:-></p><p></p><p>It's common [and accepted] practice to use whole range of exceptions covering directory, file types and/or processes in business settings, many vendors publish recommended exception lists for their products - is that 'messing up security' or 'tailoring security vs productivity'?</p><p></p><p>You say starts to lag after a day or two - can you check the SIZE of your log files when it starts to lag, if logs are file is being opened and read by MSE [or other AV tool], as they get bigger, the lag will increase, and MePo can be very verbose in logging. As a start [assuming MSE / MePo is the issue], apply an exception for the log dir in MePo datafiles directory [C:\Program Data\Team MediaPortal\MediaPortal\log if your using default - mine is softlink to D: so I have to put the real directory name into MSE]..</p><p></p><p>Cheers - JCMP.</p></blockquote><p></p>
[QUOTE="JimCatMP, post: 1075295, member: 103549"] The issue is NOT with MePo but with MSE's interaction with MePo. MSE's function is to protect the system so it looks at all running code, depending on code AND heuristics of the scan engine performance can suffer - the scan engine is updated regularly as are the definition files [daily], so there is nothing to 'fix' that could be considered stable, a specific operation set may be issue today and gone tomorrow:-> It's common [and accepted] practice to use whole range of exceptions covering directory, file types and/or processes in business settings, many vendors publish recommended exception lists for their products - is that 'messing up security' or 'tailoring security vs productivity'? You say starts to lag after a day or two - can you check the SIZE of your log files when it starts to lag, if logs are file is being opened and read by MSE [or other AV tool], as they get bigger, the lag will increase, and MePo can be very verbose in logging. As a start [assuming MSE / MePo is the issue], apply an exception for the log dir in MePo datafiles directory [C:\Program Data\Team MediaPortal\MediaPortal\log if your using default - mine is softlink to D: so I have to put the real directory name into MSE].. Cheers - JCMP. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Talk
the preview 1.7 is really slow for me.
Contact us
RSS
Top
Bottom