Ihre Kommentare
Fixed in 1.8.1
>Did use 1.7.1 and updated to 1.8.1 >Error does no more occur. >Sorry! >Next time I will give better description. |
It's ok! Great to know it's working now. So I'm closing this issue.
fixed in 1.8.1
Yes, we have upgraded to latest version of the protector. I think this problem comes from this. We are currently working on the solution.
Probably around 15 Oct we'll release 1.8.2 that should fix this.
Probably around 15 Oct we'll release 1.8.2 that should fix this.
Is the problem still present with version 1.8.1?
Is the problem still present with version 1.8.1?
Customer support service by UserEcho
Jeff, the problem occurs because of the software protector we are using to prevent cracking CN. I've already contacted the software's vendor, and they are preparing a fixed version. As soon as they deliver a fix, I'll release an update that should fix this problem, so please stay put! Thanks for your patience.