Pharos Omega PS60:Release Notes -  1.1.4 Revision 9457

Pre-install

This document contains the release notes for this firmware release of the Pharos Omega PS60 solution. If you encounter any problems or require further assistance, contact your Pharos Authorized Reseller.

This Omega PS60 release supports version 7.2, 8.0, and 8.1 of the Pharos Uniprint Suite and versions 3.5 SP1, 3.5 R2, 4.1, and 4.2 of Pharos Blueprint Enterprise.

Install Notes

  1. IMPORTANT: Connect the site's network to the WAN port!

    Make sure that the site's network is connected to the WAN port otherwise the site's network may malfunction because a DHCP server is running on all the other ports.

  2. Adding Omega-PS-60 Terminal Types to Pharos Servers

    In Uniprint 8.0, 8.1 and Blueprint 4.1 and 4.2, the Omega-PS-60 terminal types are added automatically when the first PS60 is connected to a Pharos Uniprint EDI server or a Blueprint EDI Server. When adding terminals, create your first PS60 as type Generic 1.0.0, it will be automatically upgraded to a Omega-PS-60 type when the PS60 connects.

    In Pharos Blueprint Enterprise 3.5 SP1 and 3.5 R2, the configuration schema must be updated manually. Copy the files included in the firmware package directory \Blueprint into the Blueprint\bin directory of the Analyst server. Run the batch file InstallPS60TerminalType.bat

    In Uniprint 7.2, terminal types are added automatically when the first PS60 is connected to a Pharos Uniprint EDI Server. When adding terminals in Pharos Administrator, the Omega-PS-60 will be in the list of terminal types.

    Note: For Uniprint 7.2, you must apply Hot Fix 15 and 20 before installing a PS60. These Hot Fixes contain an update to the EDI Server and Administrator that allows the configuration schema to be installed. Hot Fixes can be downloaded from the Pharos web site.

    Note:It is always a good idea to back up the database before applying changes.

  3. Servers allowed to access the printer

    If the PS60's print server is not on the Pharos EDI Server it must be added to the Servers allowed to access the printer list in the Omega Administrator > Settings > Network > Advance Settings context.

  4. Omega requires Uniprint to run against SQL Server 2000

    While Pharos Uniprint can be installed on SQL Server 2000 or SQL Server 7, Omega installs must use SQL Server 2000 (or MSDE 2000) or later. If SQL Server 7 is used, Omega terminals may be unable to obtain their configuration information from the Pharos Database, and the error "'getutcdate' is not a recognized function name" appears at Omega terminals.

  5. Omega Administrator browser support

    The Omega Administrator web application can be viewed with Microsoft Internet Explorer 6.0, and Mozilla Firefox 2.0 or later. Other browsers, e.g. Opera or Safari, may work, but are not officially supported.

    The timing diagrams that appear in the Copier Learning wizard are displayed using the Scalable Vector Graphics (SVG) specification, which is not supported natively by Internet Explorer. In order to view timing diagrams in Internet Explorer, you must install the Adobe SVG Viewer plug-in.

    Javascript must be enabled.


What's New

  1. Enhanced Security

    A new configuration option - "Allow Any HID Reader" has been added to restrict users from plugging in non-Pharos approved USB devices to the Omega PS60. This configuration setting is set to "Yes" by default; it can be set to "No" from the Administrator. When set to "No", the Omega PS60 will not allow any non-Pharos approved USB devices to be plugged in. For more information about this setting, please refer to the "Pharos Omega PS60 Installation Guide".

  2. Print jobs released in the order they were submitted

    In previous versions, when releasing print jobs from the Omega PS60, the jobs were printed in alphabetical order. In this version, jobs are now printed in the order they were submitted - from the oldest to the most recent.

  3. Printer host name accepts up to 255 characters

    This version now accepts up to 255 characters for the printer host name. Earlier versions of PS60 accepted 128 characters only for printer host names. This is a fix for the issue where the PS60 DHCP failed to pick up Toshiba's printer host name because it contained up to 138 chars.

Known Issues

  1. Using a Billing Gateway with Omega

    If Omega terminals are being used with a Pharos Billing Gateway, and users do not have accounts in the Pharos system, a script with the following content must be created and attached to the Bank's Logon event:

    PlugIn.Result = true;

    A Billing script is also needed if you wish to use the Blackboard TIA gateway with arrears accounts - contact Pharos Support for details.

  2. Omega requires Pharos certificates for SSL

    The SSL certificates used by Omega are certified to have been generated by Pharos Systems and some other common certification authorities. If your EDI Server is using a certificate generated by another certification authority, then the Omega devices that communicate with it might not work. Contact Pharos for assistance in adding a CA certificate to your Omega devices.

  3. Server name restrictions when using SSL

    When using SSL, server names cannot contain the underscore character ( _ ).

  4. Using a Billing Gateway with Omega

    If Omega terminals are being used with a Pharos Billing Gateway, and users do not have accounts in the Pharos system, a script with the following content must be created and attached to the Bank's Logon event:

    PlugIn.Result = true;

    A Billing script is also needed if you wish to use the Blackboard TIA gateway with arrears accounts - contact Pharos Support for details.

  5. Omega requires Pharos certificates for SSL

    The SSL certificates used by Omega are certified to have been generated by Pharos Systems and some other common certification authorities. If your EDI Server is using a certificate generated by another certification authority, then the Omega devices that communicate with it might not work. Contact Pharos for assistance in adding a CA certificate to your Omega devices.

  6. Server name restrictions when using SSL

    When using SSL, server names cannot contain the underscore character ( _ ).

  7. Known Issues with Omega Administrator

    The following Known Issues exist for the Omega Administrator web application:

    • Using the web browser's Back and Forward buttons is not recommended while using Omega Administrator.
    • Using the web browser's Refresh button or F5 is not recommended while using Omega Administrator. Refresh pages by clicking menu link on left navigation panel.

  8. Number of copy lines must be a power of two

    The number of copy lines configured must be a power of two (i.e. 1, 2, 4 or 8); otherwise copying may not work, generating an error saying that copy lines are not configured correctly. Configuring copy lines using the Learn Copier wizard usually results in the correct number of copy lines.

  9. Communication timeout may be longer than configured

    Due to the fact that Omega sometimes re-tries to connect to the EDI Server if the first connection attempt is not successful, it may take longer for the communication attempt to timeout than the time configured for the Timeout property on the Pharos EDI screen of Omega Administrator.

  10. Passwords not supported

    As there is no way for a user to enter passwords on the PS60, Logon IDs with a password are not supported and protected print jobs with a password cannot be released.

  11. Omega Administrator does not show all PS60 terminals in Blueprint 3.5

    The Omega Administrator does not show all of the available PS60 terminals from the Blueprint server.The PS60 terminals have to be upgraded individually.


Need Help?

If further assistance is required, contact your Pharos Authorized Reseller.