...for some reason, this has not been delivered on Friday... (continuing a privately started debate in the mailing list) We need to start from the fact (which you have found out, and I have cofirmed) that your printer is probaby GDI based. (To me this sad fact is still surprising, or "despite all odds".)
On 23 Apr 2021 at 7:01, Bryan Kilgallin wrote: > > Hi Frank: > > > > ... so you've downloaded and installed the proprietary driver from > > Brother, for your printer? Or did Ubuntu just find and configure > > the printer automagically? > > I think that was at first Ubuntu. But I then updated from the > Brother Australia Web site. > Okay - I believe that this principally means that the CUPS printing subsystem on your Ubuntu can accept jobs formatted in PostScript and do the necessary conversion and connection to print them on your printer. The trick now is, to get PostScript jobs to the respective print queue on your Ubuntu. I'd hazard a guess that the Ubuntu PC has some listening sockets open for access via IPP, LPR and with some minimal effort we could have Samba. IPP is no use from DOS, so we have LPR or Samba left. Means to me that I have to cook a recipe for TCP/IP in MS-DOS, using the MS Network Client 3.0 for DOS, and maybe an alternative recipe using the CRYNWR packet driver API (for the mTCP tools and maybe others) - although the trick with NetCat possibly won't work, unless we can find a way for your Linux PC to accept jobs in raw format. (Hmm... maybe set up NetCat/SoCat to listen on a port and pass the job locally to LPR? Shouldn't be all that difficult.) Theoretically it should be possible to set up your own "artificial" print queue in the Linux box, employing a "filter" based on e.g. GhostScript/GhostPCL, which could accept print jobs formatted in PCL3 / PCL5. Or, raw ASCII for that matter. Convert them to PostScript and pass them to the existing CUPS queue for your physical printer. Or maybe there's a more direct way in CUPS, not sure. Again I need to sit down at my workplace with some hardware to collect the DOS drivers and "develop" a few batch files. And the Linux side of the story is yet another story :-) Frank
WPM$VXKX.PM$
Description: Mail message body
_______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
