![]() |
|
#1
|
|||
|
|||
|
i'm using the trial of ess 3.0.551 and most of the time windows reports that eset is off even though it's not, i used to get this the odd few times with 2.7 regged version but it seems to happen way too often with ess
am i gonna get this when i reg it i'm tempted to just go back to 2.7 and find another firewall ![]() |
|
#2
|
|||
|
|||
|
so am i'm the only one having this problem
or is it considered too minor for a response from eset ![]() |
|
#3
|
||||
|
||||
|
I was having this as well with the trial version but it's fixed in 3.0.563 only avilable to registered users which I think is crazy but there ya go...
|
|
#4
|
|||
|
|||
|
ok thanks very much, i'm not using that version
maybe it's time for a change ![]() |
|
#5
|
|||
|
|||
|
|
|
#6
|
|||
|
|||
|
thanks all that replied all working fine now
(fingers crossed) |
|
#7
|
|||
|
|||
|
It was simple , right
|
| « Previous Thread | Next Thread » |
| Thread Tools | Search this Thread |
|
|