Here is some useful links you might like to use:

• Pharos Knowledge Base
• Pharos 7.2 New Features Document
• Pharos Downloads

Pharos Technical Support is always happy to help. And, we would welcome any questions you might have.

Merry Christmas and Happy New Year!

Matthew Bull
Global Support Manager
Pharos Systems International

Color Cost Controls Propel Uniprint 7.2 Release from Pharos Systems
Rochester, New York (PRWEB) November 15, 2006 - Pharos Systems International, the leading provider of Enterprise Print Asset Management software solutions, announces the release of Uniprint ® 7.2, which includes several key enhancements designed to help better manage the costs associated with color print and copy devices.

Uniprint 7.2 empowers both higher education institutions and corporations to maintain control of color printing and copying, while also providing users information about their print jobs, encouraging them to make responsible choices about a costly school and business expense.

Pharos iMFP for Hewlett-Packard
Hewlett-Packard and Pharos Systems have partnered to take MFPs to a new level of integration. The HP integrated MultiFunction Printer (iMFP) with its large touch-screen panel, programmable interface, and internal development platform combined with the job accounting, color access control features, and authentication capabilities of Pharos Uniprint® create a single integrated solution unrivaled in the industry. With Uniprint’s user-level job accounting, departmental chargeback, Secure ReleaseHere functionality, and state-of-the-art color access control built directly inside the iMFP. Pharos and HP together offer an uncompromising solution designed exclusively for the higher education marketplace.

Service Packs, Hot Fixes and Firmware

Pharos 7.1 Hot Fix 8 for the Pharos Station
This Hot Fix addresses the following issues:

• The application of this Hot Fix ensures that the Pharos Station works correctly when using a Bank that has "Monitor System" as the Source of Payment and either "Express Logon" or "ID & Password Dialog Box" as the Source of Identification.
• The application of this Hot Fix prevents "Pharos Cardreader Helper Not Responding" error messages from appearing when the Pharos Station starts up.

Pharos 7.1 Hot Fix 7 for the Pharos EDI
This Hot Fix addresses the following issues:

• The Hot Fix adds additional features to the Pharos EDI to support a wider range of applications. This allows greater flexibility when adding users to the Pharos Database, including the ability to add guest users. If you are a Pharos EDI developer, please contact Pharos Systems for more information.
• The application of this Hot Fix prevents errors when using the UpdatePharosStation function.
• GetJobCostMethod was returning 'unknown verb'. This has been fixed to return a correct response.

Pharos 7.0 Hot Fix 6 for Pharos Reports
This Hot Fix affects the Pharos Reports application, and must be applied to all PCs running Pharos Reports.

Pharos 7.0 Hot Fix 5 for the Pharos Station
This Hot Fix contains the following fixes and enhancements:

• The Pharos Station now supports registry values, which prevent users from exceeding their quota by selecting print jobs individually, then printing them all at once. These values must be manually created after the application of this Hot Fix.
• In certain situations, when a user cancelled a reservation at the Pharos Station a new reservation was immediately made again. The application of this Hot Fix ensures that reservations are cancelled successfully at the Pharos Station.
• The application of this Hot Fix prevents "Pharos Cardreader Helper Not Responding" error messages from appearing when the Pharos Station starts up.

Pharos Blueprint Enterprise 3.1 Hot Fix 7 for the Tracker
This Hot Fix addresses the following issues:

• Slow processing of print jobs on a server or client machine with the Tracker installed. The problem is caused where there is restricted permissions to %Program Files% \ PharosSystems \ OutputManagement \ PrintTracker \ Spool or temporary directories on the machine. The problem can be identified by a large number of zero length psp*.spl files collecting in one of these directories.
• The ComTaskMaster service consuming high CPU and memory resources within minutes of starting up. The problem was caused by the way that older Blueprint 3.0 jobs were processed and sent to the server. This issue only applies to sites which have upgraded from Blueprint 3.0.
• When using NDPS printers in a Novell environment where the printers have been pushed to client workstations and have port names such as \\NDPS01, \\NDPS02 etc, the printers were reported in Blueprint using their port names instead of the printer name. The application of this Hot Fix ensures that the Tracker will report the printer name as seen by the user in the Printers window on the client workstation.
• In the presence of certain printer drivers, the Blueprint Diagnostic Tool would fail with an error message when run on Tracker workstations. The application of this Hot Fix ensures that the Diagnostic Tool runs correctly on Tracker workstations.
• The Blueprint Diagnostic Tool would fail with an error message when run on Tracker workstations using a French locale. The application of this Hot Fix ensures that the Diagnostic Tool runs correctly on Tracker workstations.
• Previously, the Tracker could pagecount jobs incorrectly when printing PDF documents to certain printers. The application of this Hot Fix ensures that such jobs are counted correctly.
• This Hot Fix includes enhancements that increase support for Novell environments. It ensures that the Tracker correctly retrieves Novell printer driver names and other Novell information correctly, and fixes problems when other software unhooks the Tracker, e.g. Novell client update.
• If a Tracker was unable to contact its Collector for a long time, it would attempt to send all stored print jobs in a single, potentially very large batch file when contact was re-established. Application of this Hot Fix ensures that Trackers will never send a batch larger than the Maximum Batch Size property (configured on the Tracker > Settings screen in Blueprint Administrator). Jobs will be grouped into multiple batches smaller than this size if necessary.
• If the Blueprint Diagnostic Tool was left running, or the process stopped unexpectedly, diagnostic gathering would not be turned off, which used up system resources. This Hot Fix ensures that diagnostic gathering will be stopped after 2 hours. The Hot Fix includes stability improvements to the Diagnostic Tool.

• This Hot Fix adds a command line option was added to Tracker installer, so that you can specify an install directory:

  InstallPackage.exe /dir="c:\install\directory"

  (Note the quote marks, and no space between the /dir= option and the install directory path.)

• The application of this Hot Fix improves error handling, error reporting and robustness of the Tracker when the server is under load.
• The Tracker now supports Lexmark C770 and C772 printer drivers.
• This Hot Fix improves the Tracker installer's detection of the Windows operating system.
• This Hot Fix removes the AlwaysSpoolToRaw, FilterDataTypes and GetJobAnalysis settings, as they are no longer necessary
• The Hot Fix addes the ability to define the location of the Print Tracker spool directory should it be necessary. Contact Pharos for more details.