19 Mar
2020
19 Mar
'20
8:27 p.m.
On Thursday 19 March 2020 02:21:32 pm Michael Howard via trinity-users wrote:
Ah, a GDI printer. GDI is a microsoft system and the printer expects
most of the processing to be done from within Windows, so in this case,
it's really not the fault of CUPS but that of the printer really.
Ah, but it use to print fine from CentOS 6 up to about 2016/2017. It wasn't
even that hard to setup, extract some file(s) from the Win software, drop
them into Linux, and CUPS just worked. Now CUPS flips you the bird and will
no longer print to it.
Cool!
Thanks,
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On 19/03/2020 17:40, Michael wrote:
> On Thursday 19 March 2020 11:40:28 am Michael Howard via trinity-users
wrote:
On 19/03/2020 16:27, Michael wrote:
i-don't-know, make me walk to the printer closet to look will ya!
Panasonic KX-MB2030 (Multi-Function Laser) There’s nothing wrong with my 7 year old printer
(which I now have to
send files to a windows box to print...).
Which printer is it? Eventually I
want to try installing the Panasonic Windows print utility
in a Windows VM. Would seem to be a complete waste, but *shrug* if it
works, so be it...
Anyone ever tried that (printing from a Windows VM on a Linux box)?
If you have windows already, or with a new installation (either real or
virtual) just share the printer and let Windows do the processing.