Contact

Contact

One address, read by the people who build the product. No form, no account, no ticket number.

Email

What to send

A useful report is short and specific. These are the pieces that make the first reply useful.

Support

The version line from CommMonitor.exe --version, your Windows build, the driver state from the Problems panel, and the steps that reproduce what you see.

Licensing

How many machines, whether they can reach the Internet, and any invoicing or purchase-order requirement.

Protocol requests

The protocol name, the device, and a capture of the traffic if you have one. A capture is worth more than a description.

Security reports

Tell us which file, which hash and what your tool reported. We would rather hear it from you than read it somewhere else.

jfyes@hotmail.com

We answer in English. Please do not send licence keys in plain text to a public address; send the fingerprint instead and we will re-issue.

Scope

What we cannot help with

Saying no early saves both sides time.

  • Device firmware internals: we can show you what a device sends, not why its firmware decided to send it.
  • Software that refuses to release a port for reasons of its own; the monitor will still capture, but it cannot make another program behave.
  • Windows 7 x64: it is not declared as supported in this release.

Before you write

The documentation covers driver install, views, filters, sessions, redirect and command-line options.