Converts a USB printer into a standalone network printer over a 10/100 Ethernet network Windows based set-up program and web-management Share a standard USB printer with multiple users over an Ethernet network. GeForce® GTX 1080 Ti is the fastest gaming GPU that delivers 35% faster performance than the GeForce GTX 1080.
What I need is to send a PDF document directly to the remote network printer, without any changes, as it is
, using Print
button.
In Ubuntu I just use Generic / Raw Queue
driver, and all is OK.
Problem with Windows 10 is that I can't find a Generic / Raw Queue
driver, it's only a Generic / Text only
driver here, and it fails to print PDF.
I tried to use Microsoft / PDF to file
driver, but it changes PDF (changes PDF structure, it replaces all with 1 image, that I don't need).
Any advices? Or maybe someone could send me a driver that wouldn't change the file and just resend it?
If your printer understands PDF directly (most printers require some utility), you can try sending it to the printer using the following command:
LPR -S printer_IP_address -P queue_name filename.PDF
The queue_name parameter is printer specific. You could try PDF or RAW. If those don't work, you'll need to look up the printer's documentation.
Here's a user-friendly solution if you don't want to type commands. Use Notepad to create a file containing the command
LPR -S printer_IP_address -P queue_name %1%
Name this file PrintPDF.bat and place it (or a link to it) on the desktop. From Windows Explorer you can now drag a PDF onto this icon, and it will be sent to the printer.
hdhondthdhondtWhat I need is to send a PDF document directly to the remote network printer, without any changes, as it is, using Print button.
For most apps, this isn't possible using the 'Print' button because the application you're using is trying to talk to a non-raw printer driver whereas you explicitely want to bypass those capabilities. Instead, you should send the raw stream to the printer directly. To achieve this in Windows (WITHOUT the use of a print button)
cmd
(or PowerShell, etc): echo sample.pdf > computerprinter
Or from a programming language such as JScript:
Getting an application to behave this way is not going to be common. Most applications capable of opening and rendering a PDF wouldn't have the ability to bypass the driver. This is by convention only. The underlying languages (e.g. C++, Java) do have techniques for raw data flavors, it's just not something that's commonly associated with the 'Print' button you are describing.
In Ubuntu I just use Generic / Raw Queue driver
, and all is OK.
Which application inside the Ubuntu operating system allows this? Generally speaking CUPS will use Ghostscript and and will suffer a similar translation as the Microsoft PDF driver. I would challenge the claim that the PDF data being sent is 'unmodified' on Ubuntu. It is more likely that is IS modified, but that the modified version is simply more desirable. If you're right and the byte stream is unmodified, this seems more like a hidden feature of CUPS rather than a problem with WinSpool.
Here is how to set up an LPR/LPD Printer on Windows 10.
Install the Windows Components
Create the printer
SOLVED Check edit
Hi all,
Through a series of unfortunate events, I have a set of computers that have updated to the Windows 10 Anniversary patch. Post-patch everything seemed okay. However, my users started informing me that they could no longer print on those computers. We use an instance of Print Manager Plus as our print server. Prior to the patch, all the computers were configured with the correct LPR ports. However, post patch, those ports are no longer listed in the print management snap in. But, if I try to re-add those ports, I receive an error saying that an identical port already exists. I'm currently combing through the registry to see if there's some obscure place where its still being referenced. I'll take any advise if anyone has experience with a problem like this.
*Edit: Okay I am now slamming my head against my desk. These workstations were being used immediately after the windows 10 anniversary patch was installed. After just performing a restart, the ports are recognized again and everything works. I did not perform the first rule of windows troubleshooting. Goddamnit