#Papercut ng known issues driver
In all honesty, if you can recreate the issue on your setup using the latest code, then send us the driver download link, and we will do the rest. Using a driver like the PaperCut PS driver, is also another good idea, does that work? If so, you know it should work (if it works on one driver, why not your one?). In fact, try a completely different driver – you don’t need to waste paper, get it held by PaperCut using a Nul port and see if PaperCut detects everything correctly once printed to the Nul port. This way, you can see if one of the new options prints as expected and PaperCut detects everything correctly. However, if the existing driver has specific functionality that the other drives are missing (we know you like your finishing options), then consider installing 2-3 test queues with different drivers.
Life is short, maybe an older/newer/universal driver will work, and we can all move on. Is the driver causing your PaperCut Print Analysis issue? We mention this because a B&W document detected as being in colour comes up a lot, and it’s because the image contains some form of colour and is not actually greyscale. Now, you could “re-colour” your proper image in Word and set it to grayscale – that may help. If you check the properties, you will see the low bit depth. …add that to a new Word document and print it, we bet that it’s detected as greyscale. You can go further to test this by grabbing a sample greyscale Tiff file from here. Did PaperCut detect the job correctly? If it did, that means the image you were using is causing the issue.
Do you have a document that is being detected as colour yet it all looks B&W to you? Does it have an image (perhaps in the letterhead)?Ĭolour is a tricky thing – a solid test is to ignore that image for now and create a two-page Microsoft Word document with one word on each page, the text on page one should be in the default blank font colour, and then the text on page two should be changed to be a colour (go for red).
0 kommentar(er)
