I have a HP Color Laserjet Pro 454dn printer connected to CUPS, but some of my Windows 10 computers can't print Duplex to it. Android and IOS devices have no problem printing duplex. I did notice that the driver on the working Windows 10 computer is a "Microsoft IPP driver". I cannot find this driver on the other computers. Does anyone know how to install this? I have turned the "Internet Printing Client" on, but this does not help. Also, I have tried the universal and device specific drivers from HP both with post script and PCL, some print only greyscale and others don't print duplex.
Android and iOS can print without drivers. I have looked into driverless printing for Windows, have made no progress. This would be my favourite solution.
Thank you all very much.
The IPP Driver is built into Windows 10. You might want to look at adding SAMBA to your CUPS implementation. Especially for older Windows and Android clients wanting to see your printer.
Click the 'The Printer that I want isn't listed'.
Then the radio button of "Select a shared printer by name".
Then put the printer network name in the window using this format:
http://hostname-or-ip-of-your-pi:631/printers/Printer_Name
Windows will now find the printer and ask for a print driver for it.
This link tells you all you ever wanted to know about CUPS printing but assumes your using Ubuntu to make a network printer: http://www.auxnet.org/index.php/the-news/214-installing-an-ipp-printer-in-windows-10
Related
Why? Well HP managed to ship two totally different printers, both called the 'Laserjet 6L'. One supports Postscript, the other only PCL5e. Now there is no official Windows 10 driver for the PCL5e version but the Windows NT driver supports a number of PCL5e models, including some that are supported on Windows 10. So I want to try replacing the PS version GDP file on Windows 10 with the PCL5e version and see whether this will convince Windows 10 to use the same driver it uses for the other models to run my printer in the correct manner. Except that I can't seem to get permission to write to my own hard driver - grrr!
OK, the answer to my main problem of 'my printer doesn't work' was simpler than it might have been. There were three errors working together and preventing the supplied Windows 10 drivers from working correctly:
Windows 10 has two drivers for an "HP Laserjet 6L" and chose the wrong one. It installed "HP Laserjet 6L PS", a postscript driver whereas the 6L Pro requires the "HP Laserjet 6L" driver, a PCL5e driver; from printer properties, select the correct driver by hand.
Windows 10 has a 'Legacy Plug and Play' option for LPT devices; this printer is old and seems to need this set from Administrative Tools, Component Management, Devices, Ports
Windows 10 needs to be explicitly told how much memory the printer has. I have an extra 4MB card so I needed to explicitly tell Windows the printer has 5MB total; set from printer properties again.
Having fixed all of these the printer works.
I'm manufacturing a device that connects to my computer using Bluetooth and then a desktop Java app uses the Bluetooth connection to send serial data to the device which is then displayed.
When I try to connect my device to windows 7 it successfully finds and pairs with it creating a Bluetooth link on a COM port. This link can then be used by a serial prompt (used for testing) or my Java application. It works initially however soon after windows drops the connection and the only way to reconnect is to delete the device within devices and printers and then reconnect.
This seems to be a known problem with windows bluetooth so I decieded to use a third party Bluetooth application. I downloaded and tried Toshiba's Bluetooth Stack and it was able to add a Bluetooth device and keep a stable connection which works great however this only works for Toshiba computers without getting a cracked version.
This device is commercial and can't be sold with cracked versions of software. Has anybody experienced the same problems or not in other operating systems and has any solutions of advice as that would be a tremendous help.
This is not a good idea/method to use the COM ports generated by Windows, it's not working fine and not reliable in any scenario ; you should use Bluetooth Sockets instead.
Using Toshiba or Widcomm or BleuSoleil won't help: under Win7, all dongles are now trying to use the Microsoft Stack, not their own implementation.
I have a device connected to my Windows 7 desktop pc via an Ethernet cable. My aim is to remotely view the device and control it from my pc. I have had this running on an XP computer but not on a Windows 7 machine. I have researched online to download Microsoft Windows Mobile Device Cente which I have done. I can load the ActiveSync software however the two devices are not communicating on the remote viewer. I have also entered the correct IP addresses on both my desktop computer and Windows CE device.
Thanks in advance for anyone that can help me out.
I have sorted this problem by downloading Windows Mobile Power Tools . Once I had downloaded this I ran the Active Sync Remote Display (ASRDisp.exe).
N.B I have to load Active Sync first and click ignore when the warning message appears, then I have to turn the device on.
I know, this is old, answered question.
Still, if anybody need answer for this doubt:
I have a WinCE device connected to my Windows 7 desktop pc via an Ethernet
cable. My aim is to remotely view the device and control it from my
PC.
See Remote Display of WEC7 device using Ethernet - Windows Embedded Compact 7.
I want to use my designed USB/Serial device as a printer so that the "print" action on my Linux/Windows send the data (which asked to print) to my new printer (my own designed device/printer) connected on USB/Serial port.
Could you please give me the steps to do it? I am not sure where I should start from and how to proceed with this project?
I have an option for either Windows or Linux.
We develop a custom Windows CE-based device. To connect this to the PC via ActiveSync / Mobile Device Center, we have to set up entries so that the WCE USB Serial Host (wceusbsh.sys) recognises our Vendor ID (Vid) and Product ID (Pid).
To do this, to date, we have distributed a modified version of wceusbsh.inf and wceusbsh.sys: when the user first connects the device then ActiveSync basically says it does not recognise the device, and the user is asked to identify a driver for it. If they now point at the location where they've stored our wceusbsh.* files then all is well. However this is pretty clunky.
What we really want is a slick way to do this, preferably by running an installer which just gets everything ready, so that as soon as the device is plugged in it is recognised by wceusbsh.sys.
Any clues how to do this? There seem to be a ton of registry entries which relate to WCEUSBSH, and it's not clear how these are set: just "installing" the .INF file doesn't seem to allow for setting them all, so it does look like ActiveSync reads the .INF file and then adds some more information before appending the new info to the Registry.
Thanks
Well, in case anyone else comes looking for an answer to this, we managed to do it via this link from MSDN WinUSB (Windows Driver Kit). We now have a driver install program which sets up USB / Mobile Device Center so that when you plug in the CE device it is recognised correctly.