A problem in a third party communications control component used by IntoxNet, “SaxComm8.ocx”, has been identified as the source of this problem. This comunications control component supports a developmental diagnotic communcations logging capability, which IntoxNet turns on only when spefically instructed to do so via command line arguments supplied to IntoxNet.
It has been determined that a bug exists in the different versions of the SaxComm8 control included in all IntoxNet releases between 3.1.0 and 3.3.5. If you have an earlier or a later version of IntoxNet, you are not affected by this issue. The problem is that the control logs communications events regardless of whether it has been configured to do so, or not.
An updated version of the SaxComm8 control has been made available subsequent to our reporting of this situation to the manufacturer, which corrects the problem behavior in its entirety.
To correct this situation, download the updated SaxComm8.ocx control using the link at the end of this article, and “Save” it to your c:windowssystem32 (c:winntsystem32 directory on Windows NT and 2000 computers), replacing the existing file of the same name.
Once you have done this, delete any “commspy.txt” file which may exist in your c:windows directory (“c:winnt directory on NT and 2000 PCs) to recover the disk space. The logging activity to this file will now be discontinued, and the communications issues resolved.