Ultimately Pharos is correct that if it uses a proprietary driver, it would not be supported by Pharos (Which printer drivers are supported by Pharos products?). There are two things I would do if I were in your shoes.
First, I would see if there is any Epson driver that uses a language on Pharos' list (pay attention to footnote #2 regarding Epson's in case it is applicable in your case, though I suspect it would not be if Epson and Pharos have already gone over this with you).
Second, I would investigate the possibilities of recreating the pieces of the system prior to the upgrade. For example, was a different print driver used on the Mac computers? If so, is there any reason that could not be redeployed? Depending on the version of Pharos that you were using, perhaps the older page counter could be used if it somehow counted the jobs correctly.
Another piece to the server side of the puzzle would be the potential to manipulate the page counter registry files to try to force the system to use the Windows page count. I am not sure if that is possible, but it could be explored. It would likely mean that you would need a dedicated print server just for those devices though as the page counter keys affect all jobs on the server. This third section would really just be a temporary Band-Aid, but depending on how desperate you are it may be worth it. Using devices that accept drivers on the relatively extensive list of support print driver languages is your best bet.
1 of 1 people found this helpful
I have ready access to a Macintosh, so I downloaded the latest EPSON Stylus Pro 4800 driver for my Windows 8.1 machine and MacOS Mavericks workstations and printed some documents to FILE from MS Word 2016, Acrobat Standard 9.5, and Firefox. The Windows side of the operation was easy, and it handily printed to file, read as ESC/P2, and then analyzed them with our Page Counting software, and they each counted correctly (I am using PCounter.exe 10.0.8953).
On the Mac side (using the 9.33 version of the "EPSON SPro 4800 driver" driver), it was a bit more difficult, because the driver installs some filters and they appear to want a real connection a device, so the job fails to leave the Mac. However, the PDF file that gets stowed in /private/var/spool/cups awaiting the resolution of the filter problem does analyze correctly. I cracked open the PPD that gets built when I create the queue using the EPSON driver, and there are two job language filters that convert either "raster" (bitmap graphics) or "PDF" data to "ESCP"...which I assume (or hope) is actually creating ESC/P2. If it is actually ESC/P2 hitting the Uniprint server, and it is the same ESC/P2 created by the Windows version of the driver, they would page count similarly (and, in my case, correctly).
I know that this isn't really helping your immediate situation, but my observations are that it should work.
Thanks for the suggestions. We were using older popup client and older printer driver, and that did not work. I also asked Epson if I could
do something to edit the ppd file and they have no suggestion. I did open the .ppd file and I saw those lines. I assume that the students are
printing from photoshop psd files, so maybe those 'filters' you mention are for raster and for pdf, and there is not one for psd.
Maybe as an experiment, if the users print only PDF files, then the filters would work to make it into the ESCP that the Pharos server needs.
To change the print driver on the Mac to use the ESC/P2, can only be changed in the printer System Preferences,
but only in Epson models which have that ability/feature. Unfortunately the 4800 and 4900 do not have that feature, so I cannot change
it in the System Preferences. The tech support tole me it was something like 'Process job by printer' whatever that is.
I will also ask our IT department if they could do something like you suggested and go back to the old counter
I am going to mark this as answered, since it is not possible to get Pharos to work with the Epson printers. The Uniprint
is not compatible because Epson uses a proprietary ESCP printer language and that will not change. We are going to try
using another print queue manager called Paper Cut, which is known to work with Epsons. Thanks for your responses.