xprintertechcom,driver xprinter xp-365b,Xprinter branded products are manufactured in the guideline of ' Quality First', which have received certain reputation in the global market. The practicability, unique design and strict quality control standards have helped obtain a steady stream of new customers. Moreover, they are offered at affordable prices with cost-efficiency thus most of the customers are willing to achieve deep cooperation.
Xprinter provides driver xprinter xp-365b products that are selling well in United States, Arabic,Turkey,Japan,German,Portuguese,polish,Korean,Spanish,India,French,Italian,Russian,etc.
Xprinter,Our company main produces xprinter xp-58iin driver,durable barcode labels,xprinter mini printer.
All variants mentioned here are probably based on more or less the same clockwork. Getting it running in Xubuntu (Ubuntu Linux plus XFCE) was a real challenge without known drivers. This page is aiming to help and should give enough clues for similar Linux environments.
It would appear the margins are coming from a setting in the Windows driver, however there is no setting anywhere in the driver to allow me to alter the margins. See the image below, the margins highlighted by the red boxes.
I use a ESC/POS Printer to print the customer ticket and as you can see in the image below, there are no excessive left / right margins added. This is of course because ESC/POS mode bypasses the Windows driver settings so the margins are set by the printer, not the driver.
This lets you tweak the page sizes (and add new ones, which just get ignored by receipt printers ). But as can be see here, there are 0cm margins set for both left and right on the paper size I am using, and if I increase the width, it just crops off the right edge of the printout and retains the same margins.
I have also tried changing the DIP switch setting on the printer from 48 characters to 42 characters, this makes the situation worse as the printer them appears to add its own additional margin on the printout.
From what I can tell, we have to start the template with a or similar tag, but the template is then being wrapped into the final document, and I guess that piece of code that wraps it has some definition for the margins (or at least, that is where we could change it). I tried creating a new wrapper inside the template, using but it just throws an error.
Yeah there is, similar as in HTML you can add a Margin="..." attribute on many elements. However I already did that on the top level , but would most likely need to apply it (or another setting) to a parent element that is not available in the template.
I just thought it was some parameter being set in the document being printed. What is frustrating is if I print to XPS either using Print to XPS or your custom document printer, then print from XPS Viewer, it is fitting to page but making it very small - but it uses the whole width. That is why I thought there might have been an easier way of doing it rather than having to set override values for page size in SambaPOS, which I agree is unnecessary. All I was hoping for was to get rid of the excessive margins.
I have software that generates pure PCL files. We have been using the standard Windows RawPrint solution (StartDocPrinter, StartDocPage, ...) to send to printers for years (like 20). We have sent files to HP, Canon, Lexamark, Kyocera, Brother, etc. We just upgraded our printers in our Demo Room to brand new M506dn (to get the duplex). Well, we have run into problems. We cannot print to the printers from our code, it goes into the print driver, we can see it being 'printed' in the Print Queue for the printer, but the printer never prints the paper. The three (3) printers are hooked up by network and USB to different PCs. I have tried the code from Serve 2008 R2, Windows XP, Windows 10 1709, and Windows 7 Enterprise. All respond the same now. I do have one printer the code still works on, a Lexmark E260d. The code works fine sending to the printer (USB port) on my machine. But the same code to any of the M506 no go. Checked the queue, the size of the file in the queue is the exact size of the file on disk.
You could try using the PRN File Print tool in the PCL Paraphernalia application (available via ) to send the content of your PCL file to the target device, to see if that also fails like your mechanism, or not; the target device can be defined in one of two ways:
The application doesn't fail, or produce any error message, but the Windows Event Viewer shows Event 1000 messages associated with "... Faulting application name: printfilterpipelinesvc.exe".
With a USB-connection, the PCL Paraphernalia application is using the same "standard Windows RawPrint solution" as you, so perhaps there is some common problem, with newer HP devices, or drivers, which causes them to no longer support this (Microsoft-documented) mechanism?
This solution worked perfectly. I tried all different tricks with the RAW and when using the XPS_PASS everything worked fine. Now trying to get the customer to let be update some old solutions to use the new format for the driver to work with.
In this driver download guide, you will get the Xprinter XP-365B driver download links for the Windows, Linux and Mac operating systems. We have taken special care to share only genuine xprinter printer drivers on this page. Therefore, all the drivers you will get from this guide are fully compatible with their respective operating systems. We have also shared below the detailed driver installation guides to help you with the printer driver installation.
All the operating systems supported by this Xprinter label printer have been mentioned in our OS list shared below. Follow the download steps given below to get the printer driver which is fully compatible with your Xprinter machine.
This thermal label printer driver must be installed by using its proper installation method if you want to avail the best performance from this printer. Therefore, for your guidance, we have provided below two driver installation guides.
The first installation guide describes the installation process for the Xprinter XP-365B driver package, while the second installation guide explains the right method of installing the Xprinter XP-365B INF driver.
Read the following driver installation guide which is related to your driver type and follow its installation instructions in the correct order to properly install the Xprinter driver on your computer.
We are an independent website and is not associated with any brand unless specified. All brand names, trademarks, images used on this website are for reference only, and they belongs to their respective owners. We disclaim any ownership, rights of such third-party products or copyright material unless otherwise specified. We also do not provide any kind of paid support. If you have any question feel free to contact us. Read our full disclaimer.
Destinations are individual printers and classes (pools) of printers. Printers use a description file with one or more driver ("filter") programs that communicate with the printer through a "backend" program. CUPS currently uses PPD (PostScript Printer Description) files to describe the printer and driver programs needed, some of which come with CUPS while others come with your operating system or Linux distribution. Backends are specified using a URI (Universal Resource Identifier) where the URI scheme is the backend name, e.g., "ipp://
11.22.33.44/ipp/print" specifies the "ipp" backend - like PPD files, some backends come with CUPS while others come with your operating system.
Classes are associated with one or more printers and are typically used to distribute print jobs amongst a group of printers or provide redundancy or high availability when printing. Print jobs sent to a class are forwarded to the next available printer in the class.
The lpadmin(8) program is used to add, modify, or delete destinations, while the lpinfo(8) command is used to list the available printer drivers and backends. The cupsctl(8) program is used to manage the printing system as a whole, including things like debug logging and printer sharing. The CUPS web interface (" :631" or " :631") can also be used, and most operating systems provide their own GUI administration tools.
The network class of backends is used for all network protocols. The Using Network Printers help document describes how to use the standard CUPS network backends. The direct class of backends is used for directly-connected printers such as USB and Bluetooth. Because these backends use a system-specific identifier, you should only use the reported device URIs.
The printing system log files track the activity of the scheduler, printer drivers, and backends. If problems occur and the log files do not provide sufficient details to diagnose the problem, you can enable debug logging using the cupsctl command:
3a8082e126