I run a small college print shop with two older Xerox machines, a 4112 and a Docucolor 252, both using Fiery servers. My computer recently got upgraded from Windows 7 to Windows 10. The 252 seems to be working smoothly using a Windows 8 driver, but we're having trouble with the 4112. Since we couldn't find any 4112 drivers for Windows 10, or even Windows 8, our IT guy downloaded a global driver.
He started with a PCL driver, but that didn't work. Jobs were showing up in the hold queue without any options--the Job Properties brought up only the Quick Access, Job Info and Summary tabs, and virtually all of the printing options were missing. So I made him track down a postscript driver, but it's been super buggy. Sometimes jobs show up in the hold queue labeled with a PS, other times they show up labeled PCL with no real rhyme or reason (and still the PCL ones are missing all the options). Every time a PS job is sent successfully, it is accompanied by a ghost PCL file labeled "Uknown" that has no pages and no data. Perhaps the strangest quirk is that every time a job does successfully show up with a PS label, and I print it, it automatically changes the quantity to 13 as soon as it processes. I keep getting 13 copies of little things like emails and invoices.
Our IT guy is baffled and I'm not really much of an under-the-hood person, so I was just wondering if anyone else has experienced similar issues and/or is able to recommend the correct driver for this setup, because the ones we've tried don't seem to cut it.
The 4112 will work fine with the 4112 PCL driver for Windows 7, or Windows 7 x64.
It must be installed manually, and the port should be set as RAW with port 9100 and SNMP set on with the default settings.
The Xerox GPD doesn't work well at all with FujiXerox products, if the 4112 has a PS kit (Shows on the config page as I believe PS v3012.104 then go with the PS driver not PCL with the same port settings listed here.
If windows won't allow install (you choose the driver and it just re-asks but gives no error) then you would need to disable Driver Signing, install the driver and re-enable driver signing