I have the exact same problem with TCC V22. This is a paid-for installation. As a long-time user of 4DOS/4OS2/4NT/TCC I can confidently say that this is not how it usually works.
Fixed yesterday; see the announcement in another message.
For as-yet-unknown reasons, yesterday afternoon the Symantec/ Comodo code signing certificates used in all JP Software products was nolonger considered valid by Windows. I am still investigating the cause;in the meantime I have uploaded patched versions of v21 and v22 to ourwebsite. You will need to download & install the updated build.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.