George R. Kasica wrote:
I've dropped back to 3.1.5 last evening about 2200 CDT and no problems since. I'm also running FuzzyOCR 2.3b here and did not see the problem until I got to 3.1.7 I'll cc this to the FuzzyOCR list and see if anyone there is seeing this....
If someone(s) can definitively confirm whether this problem only happens under 3.1.6/3.1.7 and not 3.1.5 or earlier, please make sure we hear about it.
IIRC, it's possible that the fix for bug 5081 (3.1.6) could be affecting this.
Daryl
