There are a lot of them and they're either noise (should be turned off) or indicate potential issues. Focus is on files matching ck[on]*.[ch] as these are specific to Windows and OS/2 support so there is little risk of a change breaking, for example, C-Kermit on OpenVMS.
Any changes to ck[cu]*.[cwh] should be coordinated with FdC, especially if they're not #ifdefd for NT, to ensure the change doesn't break C-Kermit on some other platform or with some other compiler which is perhaps less standards compliant than modern versions of Visual C++ or GCC.
There are a lot of them and they're either noise (should be turned off) or indicate potential issues. Focus is on files matching ck[on]*.[ch] as these are specific to Windows and OS/2 support so there is little risk of a change breaking, for example, C-Kermit on OpenVMS.
Any changes to ck[cu]*.[cwh] should be coordinated with FdC, especially if they're not #ifdefd for NT, to ensure the change doesn't break C-Kermit on some other platform or with some other compiler which is perhaps less standards compliant than modern versions of Visual C++ or GCC.