Please note that this is the first of two issues referred to in my previous response to your original posting. This addresses only the matter of the message received in regard to HPZipm12.exe. In order to solve the problem, I believe it is appropriate to gain a basic understanding of the issue that is creating the problem itself. This is as opposed to giving you a solution that simply directs you to go to this page, click here, and click there... Further, with an understanding of the primary problem, it becomes a little less difficult to dig through the mounds of material available on any given internet site that may not be as accurate as we may hope.
HP multi-function printers, such as your PSC2110, utilize a PML driver service. PML ("Printing Industry Markup Language") was a markup language designed for the printing industry (printers, publishers, paper distributors, and ink/consumable suppliers, for instance. This is similar to the XML language to be used primarily in the grahic industry (at the time of development).
The PML service basically handles bidirectional communication between the PC and the printer, therefore being required for such functions as scanning, card reader functions, certain copy tasks, usage of the HP Director software, and updating of printer item status in the related system tray tracking icons, etc. Unfortunately, certain versions of the driver have been associated with nearly constant problems, and specifically with specific software applications, such as Sage Accounting, or with "unable to start driver"
errors at startup.
Based on my extensive research, there is one potential fix for this problem, with the second being to disable it. (Note that this assumes you are signed in and working as an administrator.) The first is to ensure that your firewall alows the task to communicate external to the PC. In other words, if the firewall does not allow the HP function to communicate through the firewall as an exception, it will be blocked, and will not function, thereby creating the result you see. Please review your firewall in detail, and HP recommends that all HP software be permitted to communicate as exceptions to the firewall.
The second manner of addressing this problem is primarily to disable the function at startup, changing the type of startup to manual. Per HP, most ("if not all") of the functions will continue to work as they should without the PML driver. Therefore, HP recommends that, should changing of the firewall/security software not achieve the desired result, that the driver be set to manual startup. This will have the effect of disabling it at startup, and will require that (should you attempt a function requiring its support) you manually start the service as necessary. (See HP reference: http://h10025.www1.hp.com/ewfrf/wc/document?docname=c01179939&lc=en&dlc=en&cc=us&product=79488&rule=14279&lang=en
There are a number of other references, should you desire same, but this was the most comprehensive and relevant to the problem at hand.
If this information assists you in resolving the problem, please take a moment to rate the solution at a "FixYa" level. If you do not feel that you can rate at a "FixYa", please post back with more information regarding what has occurred and/or more details regarding the situation, and I will gladly help you until we have reached a definitive solution. Thank you for using and rating FixYa!