Readme & Known Issues in v8

Please see the full fix list and documentation update lists.

If the OmniRush v6 or v7 clients run against a v8 server, database corruption may occur. Be sure to have proper backups.

Note: As in v7, there is no support for Windows NT4 or Win9x in either the client or server.

• As in v7, the Legacy OmniRush Client is no longer part of OmniRush. Upgrading sites must manually delete the legacy client icon.

For the smoothest upgrade experience, the OmniRush Server PC and client PC's that run the OmniRush client should be checked for services that depend on the spooler. The presence of dependent services is often an indicator that the windows spooler service is probably maxed out, and may fail when OmniRush printing components are added or changed.

1. To check for such services, select Start | Run and enter: services.msc <enter>
2. Go down the list to the Print Spooler entry, right click and select Properties
3. In the Dependencies tab, check if anything other than Remote Procedure Call (RPC) and Fax services are listed.
4. If Fax service is listed, check that it is set to Manual start.
5. If additional services are listed, extreme caution is advised, as these services are often incompatible with the OmniRush installer or upgrade utility.

Additionally, the HP 1200 model printer has been found to install helper software around the spooler service that creates problems for other print drivers. If the HP 1200 is present, it must be fully uninstalled prior to installing OmniRush or upgrading the OmniRush version.

Commerce / Credit Card Processing users: Version 8 switches from using your Authorize.net password to your Authorize.net transaction key. See the Authorize.net web site for details.