These are things that might be observed when you run C-Master, or impose additional requirements on the computer(s) you may use. This list will be updated as circumstances warrant.

• Program size: The C-Master main, configuration, repair, and SQL programs may require over 1 GB of memory when they run.
• Log strip generation (JPG images): The utility that produces the JPG image files has an issue with image complexity. Usually, the problem manifests itself when the resolution is set high (i.e. 120 DPI or higher) and the image is large (lots of log strips and very “long”). The program may crash with an error box displayed.
  A different utility is being developed and tested to prevent this from occurring. If this becomes an issue for you, you can adjust your options to lower the resolution of the resulting image. Generally, 100 DPI is plenty. Symbologies and annotations assume the line width is equal to the DPI resolution.
  As an alternative, you can generate the image as a PDF, then convert the PDF to a JPG using a PDF utility (not included).
• Program “stalls”: This can happen on computers with slower processors and/or limited memory when some system dialogs are to be displayed. An example  is:
  • Click/Make a selection that will ask for a file name;
  • After a few to several seconds, the file dialog is shown and an input is asked for

Other than these specific items, C-Master runs very fast, processing up to hundreds of logs per minute in a variety of scenarios. As an example, on the development system, I have generated 18,000 PDF logs strips of a public-domain data set of logs, one log per output file, in about 2 hours. In a similar experiment, I allowed up to three columns of logs and 200 inches of length for the same set of logs and it took about 20 minutes.