In recent versions of Uniprint, print jobs are divided into sections based on page attributes.  For example, a 6 page duplex job with three mono pages and three color pages will have two sections:

  • 3 pages, Color, Duplex
  • 3 pages, Mono, Duplex

In order to match physical expectations, if a duplex job has an odd number of pages, the last page is charged as a simplex page.  Due to prior limitations, a job with multiple sections would have each section processed individually.  This meant the last page of any section with an odd page total was charged as simplex.  As a result, the above example was actually charged as 2 mono duplex pages, plus 1 mono simplex page, plus 2 color duplex pages, plus 1 color simplex page.  When a job like this printed out on only three sheets, the charges could be difficult to explain.

This issue was addressed in Uniprint 8.2 by making the Page Counter responsible for indicating when a final page should be charged as simplex.  This now only applies to the final page of a job, rather than each section.

This change has been included as of revision 103.  However, the Page Counter adjusts its behaviour depending on which product version you are using, and the default 8.1 behaviour is not appropriate for these changes.  Therefore, applying one of these fixes means you must install a recent version of the Page Counter (any page counter more recent than the version bundled with the hot fix is fine), and create a registry value to indicate which behaviour you want.

The registry value is a DWORD called Last Page Simplex, under the appropriate key:

  • 32-bit systems: HKEY_LOCAL_MACHINE\Software\Pharos\Page Counter
  • 64-bit systems: HKEY_LOCAL_MACHINE\Software\Wow6432Node\Pharos\Page Counter

A registry file is included with the hot fix to create these values, and default to charging the last page as simplex.  The value should be set as follows:

  1. Set to 1 for the final page to be charged as simplex.
  2. Set to 2 for the final page to be charged as duplex.

Note: if this value is not set, charging may be unpredictable.