Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Direct Connect PostScript Printer Driver - Official Release
516 views
Skip to first unread message
Hugh Hood
Feb 18, 2021, 10:58:42 PM2/18/21
to
================================================================
Direct Connect PostScript Printer Driver
- For the Apple IIgs running GS/OS -
Official Release - February, 2021
================================================================
Direct Connect PostScript Printer Driver - What is It?
---------------------------------------------------------
The Direct Connect PostScript Printer Driver [DCPPD] is a moderately
patched version of Apple's GS/OS System 6.0.1 LaserWriter Printer Driver
that allows a user of Apple IIgs GS/OS Desktop software to print
directly to any PostScript-capable printer, and unlike Apple's Driver,
requires NONE of the following:
(i) that the IIgs have AppleTalk networking installed and enabled;
(ii) that the PostScript-capable printer understand the AppleTalk
protocol;
(iii) that the PostScript-capable printer have an AppleTalk /
EtherTalk speaking networking port and be attached to an
AppleTalk network that is connected to the LocalTalk port
on the IIgs;
(iv) that the PostScript-capable printer be recognized and selected
in the Net Printer Control Panel; and,
(v) that the connection path between the IIgs and the printer
support bi-directional communications.
A PostScript printer can now be connected to the Apple IIgs via either
built-in serial port (Printer or Modem), via a parallel printer card, or
via an Uthernet TCP/IP card. The latter is important because while not
many modern printers still include a serial or parallel interface,
almost all modern network printers have an Ethernet TCP/IP connection.
In addition, the patches include changes to the generated PostScript
code to provide better compatibility with Level 1, Level 2 and Level 3
PostScript printers, with printers utilizing automatic emulation
switching (e.g. receiving and discriminating between both PostScript and
PCL jobs), and with printers from manufacturers other than Apple, whose
variant or emulation of the PostScript language may differ from Apple's.
************************
For complete details, including full documentation and screen shots of
the Direct Connect PostScript Printer Driver in operation please visit:
<http://www.apple2works.com/directconnectpostscriptdriver>
Hugh Hood
Direct Connect PostScript Printer Driver
- For the Apple IIgs running GS/OS -
Official Release - February, 2021
================================================================
Direct Connect PostScript Printer Driver - What is It?
---------------------------------------------------------
The Direct Connect PostScript Printer Driver [DCPPD] is a moderately
patched version of Apple's GS/OS System 6.0.1 LaserWriter Printer Driver
that allows a user of Apple IIgs GS/OS Desktop software to print
directly to any PostScript-capable printer, and unlike Apple's Driver,
requires NONE of the following:
(i) that the IIgs have AppleTalk networking installed and enabled;
(ii) that the PostScript-capable printer understand the AppleTalk
protocol;
(iii) that the PostScript-capable printer have an AppleTalk /
EtherTalk speaking networking port and be attached to an
AppleTalk network that is connected to the LocalTalk port
on the IIgs;
(iv) that the PostScript-capable printer be recognized and selected
in the Net Printer Control Panel; and,
(v) that the connection path between the IIgs and the printer
support bi-directional communications.
A PostScript printer can now be connected to the Apple IIgs via either
built-in serial port (Printer or Modem), via a parallel printer card, or
via an Uthernet TCP/IP card. The latter is important because while not
many modern printers still include a serial or parallel interface,
almost all modern network printers have an Ethernet TCP/IP connection.
In addition, the patches include changes to the generated PostScript
code to provide better compatibility with Level 1, Level 2 and Level 3
PostScript printers, with printers utilizing automatic emulation
switching (e.g. receiving and discriminating between both PostScript and
PCL jobs), and with printers from manufacturers other than Apple, whose
variant or emulation of the PostScript language may differ from Apple's.
************************
For complete details, including full documentation and screen shots of
the Direct Connect PostScript Printer Driver in operation please visit:
<http://www.apple2works.com/directconnectpostscriptdriver>
Hugh Hood
Ewen
Feb 19, 2021, 2:33:44 AM2/19/21
to
Hugh,
This is great news, as it enhances the IIgs yet again.
Keep up the good work...
Ewen (Speccie)
This is great news, as it enhances the IIgs yet again.
Keep up the good work...
Ewen (Speccie)
Todd Holcomb
Feb 20, 2021, 11:09:53 PM2/20/21
to
Thank you for this! I've already got network printing working with Treehugger. Would there be any advantage of using this over Treehugger?
Hugh Hood
Feb 21, 2021, 2:00:16 AM2/21/21
to
Todd,
Actually, you would still use TreeHugger as your selected port driver.
The advantage here is that you can select a *PostScript* printer driver
rather than the PCL/Epson/ImageWriter/Dot Matrix-type drivers (e.g.
Harmonie/Independence) you're probably now using.
Of course, you'll need a printer with either real or emulated PostScript
language support to take advantage of that.
In general, the PostScript driver, which directly translates QuickDraw
commands contained in the documents into PostScript code and sends them
immediately to the printer to render, prints much more rapidly (no
internal image rendering on the IIgs and no spooling) and with higher
quality than do the non-PostScript drivers.
The only disadvantage of the PostScript driver that I can think of is
that it is Black and White only. I know some of the other drivers (for
color printers) don't have that limitation.
{If you don't have a PostScript printer but are on a network with a
machine that supports CUPS, perhaps one could configure TreeHugger to
print to that CUPS server, which would then translate the PostScript job
and send it on to your network printer in the form it is needed. This is
offered untested, but it sounds plausible, I think}.
I'm curious, which network printer are you now using?
Hugh Hood
Actually, you would still use TreeHugger as your selected port driver.
The advantage here is that you can select a *PostScript* printer driver
rather than the PCL/Epson/ImageWriter/Dot Matrix-type drivers (e.g.
Harmonie/Independence) you're probably now using.
Of course, you'll need a printer with either real or emulated PostScript
language support to take advantage of that.
In general, the PostScript driver, which directly translates QuickDraw
commands contained in the documents into PostScript code and sends them
immediately to the printer to render, prints much more rapidly (no
internal image rendering on the IIgs and no spooling) and with higher
quality than do the non-PostScript drivers.
The only disadvantage of the PostScript driver that I can think of is
that it is Black and White only. I know some of the other drivers (for
color printers) don't have that limitation.
{If you don't have a PostScript printer but are on a network with a
machine that supports CUPS, perhaps one could configure TreeHugger to
print to that CUPS server, which would then translate the PostScript job
and send it on to your network printer in the form it is needed. This is
offered untested, but it sounds plausible, I think}.
I'm curious, which network printer are you now using?
Hugh Hood
Todd Holcomb
Feb 21, 2021, 9:24:34 AM2/21/21
to
On Sunday, February 21, 2021 at 1:00:16 AM UTC-6, Hugh Hood wrote:
> {If you don't have a PostScript printer but are on a network with a
> machine that supports CUPS, perhaps one could configure TreeHugger to
> print to that CUPS server, which would then translate the PostScript job
> and send it on to your network printer in the form it is needed. This is
> offered untested, but it sounds plausible, I think}.
>
> I'm curious, which network printer are you now using?
Thanks for the explanation! I'm using a Brother DCP-L2550DW, which is a modern B&W laser printer, for my networked vintage Macs and IIgs. It's been awhile since I set it up, but I believe I'm using the Independence LaserJet driver. I do remember not being able to get CUPS to work. I was never satisfied with the output from Print Shop GS, so I will definitely give this a try.
> {If you don't have a PostScript printer but are on a network with a
> machine that supports CUPS, perhaps one could configure TreeHugger to
> print to that CUPS server, which would then translate the PostScript job
> and send it on to your network printer in the form it is needed. This is
> offered untested, but it sounds plausible, I think}.
>
> I'm curious, which network printer are you now using?
Todd Holcomb
Feb 21, 2021, 9:29:37 AM2/21/21
to
On Sunday, February 21, 2021 at 8:24:34 AM UTC-6, Todd Holcomb wrote:
> Thanks for the explanation! I'm using a Brother DCP-L2550DW, which is a modern B&W laser printer, for my networked vintage Macs and IIgs. It's been awhile since I set it up, but I believe I'm using the Independence LaserJet driver. I do remember not being able to get CUPS to work. I was never satisfied with the output from Print Shop GS, so I will definitely give this a try.
And now I see from your site that Print Shop has issues because it uses its own printer drivers, so disregard that!
> Thanks for the explanation! I'm using a Brother DCP-L2550DW, which is a modern B&W laser printer, for my networked vintage Macs and IIgs. It's been awhile since I set it up, but I believe I'm using the Independence LaserJet driver. I do remember not being able to get CUPS to work. I was never satisfied with the output from Print Shop GS, so I will definitely give this a try.
Hugh Hood
Feb 21, 2021, 9:56:00 AM2/21/21
to
On 2/21/2021 8:24 AM, Todd Holcomb wrote:
> On Sunday, February 21, 2021 at 1:00:16 AM UTC-6, Hugh Hood wrote:
>>
>> I'm curious, which network printer are you now using?
>>
>
> Thanks for the explanation! I'm using a Brother DCP-L2550DW, which
> is a modern B&W laser printer, for my networked vintage Macs and
> IIgs. It's been awhile since I set it up, but I believe I'm using
> the Independence LaserJet driver.
>
Todd,
> On Sunday, February 21, 2021 at 1:00:16 AM UTC-6, Hugh Hood wrote:
>>
>> I'm curious, which network printer are you now using?
>>
>
> Thanks for the explanation! I'm using a Brother DCP-L2550DW, which
> is a modern B&W laser printer, for my networked vintage Macs and
> IIgs. It's been awhile since I set it up, but I believe I'm using
> the Independence LaserJet driver.
>
You should be good-to-go trying the PostScript driver in place of the
Independence driver with your printer. I think you'll find it an
improvement.
According to the Brother website, the printer supports the following
languages:
PCL6, BR-Script3, PDF Version 1.7
BR-Script3 is Brother's emulated PostScript 3, and includes 66 built-in
scalable fonts. Plus, your printer is 1200 dpi x 1200 dpi, which is very
sharp.
I'm glad you saw the caveat about Print Shop GS.
Hugh Hood
Hugh Hood
Feb 21, 2021, 12:54:21 PM2/21/21
to
On 2/21/2021 8:24 AM, Todd Holcomb wrote:
>
>
> I was never satisfied with the output from Print
> Shop GS ...
>
Yeah, and it's not because some of our best Apple II programmers haven't
tried to get it going with 'modern' laser and inkjet printers either.
I got this from the late Joe Kohn's ShareWare Solutions II newsletter,
which Ewen has archived on his site:
>
> I [Joe Kohn] commissioned the Apple II programming master Bill
> [Becky] Heineman to create a set of HP printer drivers for the IIGS
> version of Print Shop. Over the past year, Bill [Becky] Heineman has
> spent literally hundreds of hours trying to patch Print Shop GS so
> that it would recognize HP printers. Bill [Becky] ended up modifying
> 17 different Print Shop GS files, yet in the end, was unable to
> achieve satisfactory printed output.
>
If a consummate pro like Heineman threw in the towel on this project,
this duffer isn't even going to think about trying it. ;-)
Hugh Hood
Antoine Vignau
Feb 21, 2021, 3:01:03 PM2/21/21
to
Hi Hugh,
Great work!
Could you send me your source code to add it to the genuine source code, please?
Thank you,
Antoine
Great work!
Could you send me your source code to add it to the genuine source code, please?
Thank you,
Antoine
Hugh Hood
Feb 22, 2021, 11:38:07 PM2/22/21
to
Antoine,
I assure you that I would be more than happy to share with you any and
all of the work I did on the DCPPD.
That said, the only LaserWriter driver source code that I had access to
was in MPW/ORCA format and rather than spend the time to learn a new
assembler (I'm a Merlin32 guy) and purchase the tools to use it, I opted
instead directly to modify the LaserWriter driver by using Ewen's
ChewBagger byte editor, with assistance from his BrkDown disassembler.
I did, in fact, study and use the source code in order to determine what
to patch. It was invaluable, actually, because it was well commented.
Without it, I would not have attempted this project.
My method involved semi-organized trial and error, patch and unpatch,
and cryptic notes that I made to myself throughout the source code while
I functioned in a bit of a manic state in the late night and early
morning hours back in the late spring and early summer of last year.
There were over 12,000 lines of source code to examine and I placed
patches throughout.
My intent, now that I've released the DCPPD, is to gather all my notes
in order to document everything I did and assuming I complete that task,
I may be able to provide the modified source for someone else to build.
My preference would be to build it from source myself, so as to ensure
that I didn't overlook anything, but ...
Hugh Hood
I assure you that I would be more than happy to share with you any and
all of the work I did on the DCPPD.
That said, the only LaserWriter driver source code that I had access to
was in MPW/ORCA format and rather than spend the time to learn a new
assembler (I'm a Merlin32 guy) and purchase the tools to use it, I opted
instead directly to modify the LaserWriter driver by using Ewen's
ChewBagger byte editor, with assistance from his BrkDown disassembler.
I did, in fact, study and use the source code in order to determine what
to patch. It was invaluable, actually, because it was well commented.
Without it, I would not have attempted this project.
My method involved semi-organized trial and error, patch and unpatch,
and cryptic notes that I made to myself throughout the source code while
I functioned in a bit of a manic state in the late night and early
morning hours back in the late spring and early summer of last year.
There were over 12,000 lines of source code to examine and I placed
patches throughout.
My intent, now that I've released the DCPPD, is to gather all my notes
in order to document everything I did and assuming I complete that task,
I may be able to provide the modified source for someone else to build.
My preference would be to build it from source myself, so as to ensure
that I didn't overlook anything, but ...
Hugh Hood
Antoine Vignau
Feb 23, 2021, 2:43:53 AM2/23/21
to
Hi Hugh,
Ouch, what a tremendous work you did by patching the file directly!
Antoine
Ouch, what a tremendous work you did by patching the file directly!
Antoine
Antoine Vignau
Feb 23, 2021, 4:25:02 AM2/23/21
to
Hi again Hugh,
I did the job for you... http://www.brutaldeluxe.fr/public/postscript/postscript.zip
Find for "HH 202102" for all changes in the asm files.
The makefile is updated as well.
Assembly is not tested yet.
Cheers,
Antoine
I did the job for you... http://www.brutaldeluxe.fr/public/postscript/postscript.zip
Find for "HH 202102" for all changes in the asm files.
The makefile is updated as well.
Assembly is not tested yet.
Cheers,
Antoine
Hugh Hood
Feb 23, 2021, 10:00:04 PM2/23/21
to
Antoine,
You sir, astonish me. Bravo!
Thank you so much for saving me time and frustration.
As a side note: Some of my patches are inelegant. Since the driver was a
multi-segment OMF file I could not count on fixed addresses, so most of
the patches, other than in the GSDict PostScript dictionary, were to
branch opcodes.
Thanks again, and feel free to improve on it.
BTW, as people use this driver, I would appreciate their letting me know
with which PostScript printer model(s) they've had success so I can
compile a list.
Hugh Hood
You sir, astonish me. Bravo!
Thank you so much for saving me time and frustration.
As a side note: Some of my patches are inelegant. Since the driver was a
multi-segment OMF file I could not count on fixed addresses, so most of
the patches, other than in the GSDict PostScript dictionary, were to
branch opcodes.
Thanks again, and feel free to improve on it.
BTW, as people use this driver, I would appreciate their letting me know
with which PostScript printer model(s) they've had success so I can
compile a list.
Hugh Hood
Hugh Hood
Feb 23, 2021, 11:54:28 PM2/23/21
to
On 2/23/2021 3:25 AM, Antoine Vignau wrote:
>
>
> Assembly is not tested yet.
>
Antoine,
>
I was going to test the driver called 'postscript' that you included
with source code (assuming that it was built from the patched source),
but it appears that this is the driver from the original LaserWriter
(rather than the patched) source code.
Perhaps I misunderstood, thinking that it was the driver that was
untested, rather than the build process?
Thank you.
Hugh Hood
Antoine Vignau
Feb 24, 2021, 9:25:37 PM2/24/21
to
Hi Hugh,
The build process was untested. So, I just tested it by adding a PS folder within the printer drivers of gstoolbox. Now, "my" system builds it and adds it to System tools disk #1, the script is not made yet (too early).
You can get the disk image at http://www.brutaldeluxe.fr/public/postscript/
Antoine
The build process was untested. So, I just tested it by adding a PS folder within the printer drivers of gstoolbox. Now, "my" system builds it and adds it to System tools disk #1, the script is not made yet (too early).
You can get the disk image at http://www.brutaldeluxe.fr/public/postscript/
Antoine
Hugh Hood
Feb 25, 2021, 9:45:12 PM2/25/21
to
Antoine,
Thank you for taking the time to build that driver with the changes.
I tested it and it printed well to my PostScript printer with the
TreeHugger TCP/IP port driver, although I noticed that the Print dialog
still displayed the older 'No network-not supported' message rather than
the patched 'DirectConnect PostScript' message.
What's strange is that you most definitely made the change in the source
in dialogdata.asm as follows:
*NoNetworkStr str 'No networkÑnot supported' HH 202102
NoNetworkStr str 'DirectConnect PostScript'
I'll let you sort that out, of course.
And, may I ask a technical question of you? I noticed in the release
notes for 6.0.4 that 'packing' was used on some of the system files, as
apparently was last done in 6.0.1.
What is 'packing' and how is it done? I noticed that the same source
code can generate ostensibly identical drivers, but the 'packed' one is
slightly shorter. Thanks for educating me on that, as I've been unable
to locate any explanation.
Hugh Hood
Thank you for taking the time to build that driver with the changes.
I tested it and it printed well to my PostScript printer with the
TreeHugger TCP/IP port driver, although I noticed that the Print dialog
still displayed the older 'No network-not supported' message rather than
the patched 'DirectConnect PostScript' message.
What's strange is that you most definitely made the change in the source
in dialogdata.asm as follows:
*NoNetworkStr str 'No networkÑnot supported' HH 202102
NoNetworkStr str 'DirectConnect PostScript'
I'll let you sort that out, of course.
And, may I ask a technical question of you? I noticed in the release
notes for 6.0.4 that 'packing' was used on some of the system files, as
apparently was last done in 6.0.1.
What is 'packing' and how is it done? I noticed that the same source
code can generate ostensibly identical drivers, but the 'packed' one is
slightly shorter. Thanks for educating me on that, as I've been unable
to locate any explanation.
Hugh Hood
Antoine Vignau
Feb 26, 2021, 3:53:41 AM2/26/21
to
Oops,
I copied/pasted all source files but I hand modified the dialog source file and I forgot to update the NoNetworkStr. I will change that and, as it seems to run, I will remove the unnecessary code as well. I believe version should be set to v1.0 now :-)
What is called packing on 6.0.4? Frankly, I do not know, I do not use it, I will read the notes. The option I see is the one that crunches OMF files. Why? To save place on disk. For instance, if a file has a direct page segment of $1000 zero bytes, it can take (worst case scenario) $1000 bytes on disk. By crunching and by using the right OMF commands, it can take < 10 bytes on disk.
I will come back here once the driver is updated.
Cheers,
Antoine
I copied/pasted all source files but I hand modified the dialog source file and I forgot to update the NoNetworkStr. I will change that and, as it seems to run, I will remove the unnecessary code as well. I believe version should be set to v1.0 now :-)
What is called packing on 6.0.4? Frankly, I do not know, I do not use it, I will read the notes. The option I see is the one that crunches OMF files. Why? To save place on disk. For instance, if a file has a direct page segment of $1000 zero bytes, it can take (worst case scenario) $1000 bytes on disk. By crunching and by using the right OMF commands, it can take < 10 bytes on disk.
I will come back here once the driver is updated.
Cheers,
Antoine
Antoine Vignau
Feb 26, 2021, 6:21:18 AM2/26/21
to
Georg Basse
Feb 27, 2021, 7:48:29 AM2/27/21
to
Dear Hugh
Thank you for this piece of software! The driver works fine together
with GS/OS 6.0.4 and my Uthernet 1 card. I use a postscript printer (OKI
C332) as output device.
Greetings- Georg B.
Am 19.02.21 um 04:58 schrieb Hugh Hood:
Thank you for this piece of software! The driver works fine together
with GS/OS 6.0.4 and my Uthernet 1 card. I use a postscript printer (OKI
C332) as output device.
Greetings- Georg B.
Am 19.02.21 um 04:58 schrieb Hugh Hood:
Hugh Hood
Feb 27, 2021, 12:29:23 PM2/27/21
to
On 2/26/2021 2:53 AM, Antoine Vignau wrote:
>
> I copied/pasted all source files but I hand modified the dialog
> source file and I forgot to update the NoNetworkStr. I will change
> that and, as it seems to run, I will remove the unnecessary code as
> well. I believe version should be set to v1.0 now :-)
>
Antoine,
>
> I copied/pasted all source files but I hand modified the dialog
> source file and I forgot to update the NoNetworkStr. I will change
> that and, as it seems to run, I will remove the unnecessary code as
> well. I believe version should be set to v1.0 now :-)
>
Yes, setting the version to v1.0 is a good thing, because, combined with
your modified source, it may encourage others to improve upon the
driver. The addition of color support, for example, would be welcomed by
many, I believe.
One other thing I noticed in your latest driver build, although it is so
very minor -- In the dialog source file one string reads 'Postscript',
whereas it should be 'PostScript'. This appears in the Print dialog, BTW.
Thanks again.
Hugh Hood
Hugh Hood
Feb 27, 2021, 12:59:38 PM2/27/21
to
Georg,
You are most welcome.
I thank you for taking the time to provide your feedback, and I have
added the OKI C332 to my list of PostScript-capable printers confirmed
as working with the driver.
That list is useful in that it gives us both a range of ages and
manufacturers for confirmed working models.
Regards,
Hugh Hood
You are most welcome.
I thank you for taking the time to provide your feedback, and I have
added the OKI C332 to my list of PostScript-capable printers confirmed
as working with the driver.
That list is useful in that it gives us both a range of ages and
manufacturers for confirmed working models.
Regards,
Hugh Hood
Antoine Vignau
Feb 27, 2021, 4:13:13 PM2/27/21
to
> One other thing I noticed in your latest driver build, although it is so
> very minor -- In the dialog source file one string reads 'Postscript',
> whereas it should be 'PostScript'. This appears in the Print dialog, BTW.
>
> Thanks again.
>
Hi Hugh,
> very minor -- In the dialog source file one string reads 'Postscript',
> whereas it should be 'PostScript'. This appears in the Print dialog, BTW.
>
> Thanks again.
>
oops, sorry, typo corrected.
New disk image available at http://www.brutaldeluxe.fr/public/postscript/ (in lower case chars)
Antoine
duhas...@gmail.com
Feb 28, 2021, 10:20:45 PM2/28/21
to
On Tuesday, February 23, 2021 at 10:00:04 PM UTC-5, Hugh Hood wrote:
>
> BTW, as people use this driver, I would appreciate their letting me know
> with which PostScript printer model(s) they've had success so I can
> compile a list.
>
I have downloaded and installed the new driver. ROM 01 GS with 8mhz Zip, 4 MB RAM. System 6.0.1. I attempted to print things from Appleworks GS, older files to a Laserjet 4200. The printer printed, although the output was not optimal. Spacing off, some things were not drawn correctly. I printed approximately 5 pages worth of stuff, then attempted to quit back to the Finder to launch another program to test printing. I got an Error stating that I need either System 6.0.1 or at least 300k of free memory. ($0410). Does this eat memory and not give it back?
>
> BTW, as people use this driver, I would appreciate their letting me know
> with which PostScript printer model(s) they've had success so I can
> compile a list.
>
Hugh Hood
Mar 1, 2021, 12:48:32 AM3/1/21
to
Du,
Thanks for the report. I did test the DCPPD with a document on
AppleWorks GS v1.1 and experienced no issues.
Is it possible for you to send me the file that gave you problems?
Nothing was changed in the LaserWriter Quickdraw to PostScript routines
so I really can't explain the quality issues you are seeing, but I'd
like to try it myself to see if I get the same results as you did.
As far as memory issues -- the driver doesn't spool, but rather sends
each page to the printer immediately. Another test for you to try would
be to select the original LaserWriter driver and <OA-F> to save it to a
file and see if you have any memory issues after the file generates.
Thanks, and feel free to send the file (preferable in .shk form) to my
comp.sys.apple2 address shown above.
Hugh Hood
Thanks for the report. I did test the DCPPD with a document on
AppleWorks GS v1.1 and experienced no issues.
Is it possible for you to send me the file that gave you problems?
Nothing was changed in the LaserWriter Quickdraw to PostScript routines
so I really can't explain the quality issues you are seeing, but I'd
like to try it myself to see if I get the same results as you did.
As far as memory issues -- the driver doesn't spool, but rather sends
each page to the printer immediately. Another test for you to try would
be to select the original LaserWriter driver and <OA-F> to save it to a
file and see if you have any memory issues after the file generates.
Thanks, and feel free to send the file (preferable in .shk form) to my
comp.sys.apple2 address shown above.
Hugh Hood
Hugh Hood
Mar 1, 2021, 1:33:35 AM3/1/21
to
> The printer printed, although the output was not optimal. Spacing
> off, some things were not drawn correctly.
>
Du,
> off, some things were not drawn correctly.
>
I had another thought on this issue. If the document is using fonts that
are not resident in the printer, the DCPPD driver will NOT download them
as to the printer as IIgs bitmaps, but rather will specify them by font
name. Since the printer does not contain that font, it will substitute
the monospaced Courier font in its place, which will most certainly will
affect the layout.
Can you let me know which fonts are used on those pages?
Thanks.
Hugh Hood
Todd Holcomb
Mar 8, 2021, 3:48:40 PM3/8/21
to
On Sunday, February 21, 2021 at 8:56:00 AM UTC-6, Hugh Hood wrote:
> Todd,
>
> You should be good-to-go trying the PostScript driver in place of the
> Independence driver with your printer. I think you'll find it an
> improvement.
>
> According to the Brother website, the printer supports the following
> languages:
>
> PCL6, BR-Script3, PDF Version 1.7
>
> BR-Script3 is Brother's emulated PostScript 3, and includes 66 built-in
> scalable fonts. Plus, your printer is 1200 dpi x 1200 dpi, which is very
> sharp.
I finally got around to trying this out but unfortunately I'm not having any luck getting it to work. Printing works fine with Treehugger and LaserJetIII.HAR printer driver but when I select the DC.PostScript printer driver (and keeping Treehugger as the port), the GS looks like it sends everything ok but the printer does nothing. I'm using GS/OS 6.0.3 with an Uthernet II card and the latest Uthernet II link layer. I'm unable to change the MTU to 320 as suggested because I get an "invalid value entered" error, so I've tried it at the default of 1460 and the lowest value that I could enter at 600 but no dice...
> Todd,
>
> You should be good-to-go trying the PostScript driver in place of the
> Independence driver with your printer. I think you'll find it an
> improvement.
>
> According to the Brother website, the printer supports the following
> languages:
>
> PCL6, BR-Script3, PDF Version 1.7
>
> BR-Script3 is Brother's emulated PostScript 3, and includes 66 built-in
> scalable fonts. Plus, your printer is 1200 dpi x 1200 dpi, which is very
> sharp.
Todd Holcomb
Mar 8, 2021, 4:27:51 PM3/8/21
to
On Monday, March 8, 2021 at 2:48:40 PM UTC-6, Todd Holcomb wrote:
> I finally got around to trying this out but unfortunately I'm not having any luck getting it to work. Printing works fine with Treehugger and
> LaserJetIII.HAR printer driver but when I select the DC.PostScript printer driver (and keeping Treehugger as the port), the GS looks like it
> sends everything ok but the printer does nothing. I'm using GS/OS 6.0.3 with an Uthernet II card and the latest Uthernet II link layer. I'm
> unable to change the MTU to 320 as suggested because I get an "invalid value entered" error, so I've tried it at the default of 1460 and the
> lowest value that I could enter at 600 but no dice...
And after turning the printer off and back on again it works! I really didn't do anything else to get it to work. Now to do more testing...
> I finally got around to trying this out but unfortunately I'm not having any luck getting it to work. Printing works fine with Treehugger and
> LaserJetIII.HAR printer driver but when I select the DC.PostScript printer driver (and keeping Treehugger as the port), the GS looks like it
> sends everything ok but the printer does nothing. I'm using GS/OS 6.0.3 with an Uthernet II card and the latest Uthernet II link layer. I'm
> unable to change the MTU to 320 as suggested because I get an "invalid value entered" error, so I've tried it at the default of 1460 and the
> lowest value that I could enter at 600 but no dice...
Todd Holcomb
Mar 8, 2021, 4:51:18 PM3/8/21
to
Wow, what an improvement over the LaserJetIII driver! I printed out your readme.txt file with Teach and it printed out in less than 30 seconds with the DC.PostScript driver, but it took well over 3 minutes with the LaserJetIII driver. In addition, the DC.PostScript driver printed a nice smooth font, rather than the bitmapped-appearing font that you get with the LaserJetIII driver.
Nice job!!
Nice job!!
Hugh Hood
Mar 8, 2021, 9:24:47 PM3/8/21
to
Todd,
Thank you for your valued feedback, and for giving the DCPPD a shot.
I'll add your Brother DCP-L2550DW printer to the list of
PostScript-capable printers that have been reported to work with the
driver.
Regarding the Uthernet Link Layer MTU -- I really think this issue is
isolated to the emulated Uthernet (I) in the GSPort emulator, or perhaps
just to my vintage JetDirect TCP/IP print server in my laser printer.
Ewen was kind enough to update the original Uthernet LL (v.1.0.4) for us
to accept values that low. I suspect that on 'real' Apple IIgs hardware
that may not be necessary, but I'm not yet certain.
Regards,
Hugh Hood
Thank you for your valued feedback, and for giving the DCPPD a shot.
I'll add your Brother DCP-L2550DW printer to the list of
PostScript-capable printers that have been reported to work with the
driver.
Regarding the Uthernet Link Layer MTU -- I really think this issue is
isolated to the emulated Uthernet (I) in the GSPort emulator, or perhaps
just to my vintage JetDirect TCP/IP print server in my laser printer.
Ewen was kind enough to update the original Uthernet LL (v.1.0.4) for us
to accept values that low. I suspect that on 'real' Apple IIgs hardware
that may not be necessary, but I'm not yet certain.
Regards,
Hugh Hood
Jeremy Rand
Mar 9, 2021, 2:24:10 PM3/9/21
to
I just tried your driver to print to my Brother MFC-8710DW using TreeHugger
for the connection and it also worked flawlessly for me. I also printed
the read me from the driver to test it. Great work!
This is from a real GS with an Uthernet II card and I am using the default
1500 MTU so that is another datapoint about the MTU.
If there is anything you would like me to test in this configuration, let
me know.
--
Jeremy Rand
for the connection and it also worked flawlessly for me. I also printed
the read me from the driver to test it. Great work!
This is from a real GS with an Uthernet II card and I am using the default
1500 MTU so that is another datapoint about the MTU.
If there is anything you would like me to test in this configuration, let
me know.
Jeremy Rand
Hugh Hood
Mar 10, 2021, 12:26:22 AM3/10/21
to
Jeremy,
Thanks so much for trying the DCPPD and letting me know your results.
I have added your Brother MFC-8710DW to the list of printers with which
the driver is working, a list that I hope continues to grow.
Thanks also for passing on that the default 1500 MTU works well with the
driver and Uthernet II card.
Please do continue to throw things at the driver.
I hope next to play with whether there is a procedure whereby the
TrueType font names passed by Pointless to the DCPPD can be made to
match exactly the names of the various PostScript fonts that are
resident in (or separately downloaded to) the PostScript printer.
It may involve editing a resource in the TT font in advance of using it
with Pointless, though I haven't spent enough time yet to know for
certain. That way, we could have the nice-looking Pointless generated
fonts on the screen that correspond to those on the printer. Feel free
to experiment if that type of thing interests you.
BTW, I'm a big fan. Thanks for your contributions to the Apple II community.
Regards,
Hugh Hood
Thanks so much for trying the DCPPD and letting me know your results.
I have added your Brother MFC-8710DW to the list of printers with which
the driver is working, a list that I hope continues to grow.
Thanks also for passing on that the default 1500 MTU works well with the
driver and Uthernet II card.
Please do continue to throw things at the driver.
I hope next to play with whether there is a procedure whereby the
TrueType font names passed by Pointless to the DCPPD can be made to
match exactly the names of the various PostScript fonts that are
resident in (or separately downloaded to) the PostScript printer.
It may involve editing a resource in the TT font in advance of using it
with Pointless, though I haven't spent enough time yet to know for
certain. That way, we could have the nice-looking Pointless generated
fonts on the screen that correspond to those on the printer. Feel free
to experiment if that type of thing interests you.
BTW, I'm a big fan. Thanks for your contributions to the Apple II community.
Regards,
Hugh Hood
Jeremy Rand
Mar 10, 2021, 1:21:54 AM3/10/21
to
No problem at all. As another test, I tried to print out an old AWGS
drawing made by one of my housemates back in my first year of university.
Traveling Riverside Blues had just been released by Led Zeppelin and he
drew the four symbols for the band members in AWGS. Because it is a vector
drawing program, I figured it would print well to my laser printer.
And it did. It looks very good when printed. I think I printed that on my
ImageWriter II back in the day posted it on my wall. Maybe I will post
this even better looking version from the laser printer. I did change the
vertical scaling to match the screen so that the circles looked like
circles and not ellipses when printed.
Thanks so much Hugh. You should be proud of your contribution here to the
Apple II community.
--
Jeremy Rand
drawing made by one of my housemates back in my first year of university.
Traveling Riverside Blues had just been released by Led Zeppelin and he
drew the four symbols for the band members in AWGS. Because it is a vector
drawing program, I figured it would print well to my laser printer.
And it did. It looks very good when printed. I think I printed that on my
ImageWriter II back in the day posted it on my wall. Maybe I will post
this even better looking version from the laser printer. I did change the
vertical scaling to match the screen so that the circles looked like
circles and not ellipses when printed.
Thanks so much Hugh. You should be proud of your contribution here to the
Apple II community.
Jeremy Rand
I am Rob
Mar 10, 2021, 10:34:14 AM3/10/21
to
Hugh,
I have been following this with great interest.
I am waiting for the day you announce you can print from Appleworks. :)
It's a long shot, but since you and I are both big Appleworks users, any chance this can be converted to a Prodos8 driver?
Or are there just too many dependencies on other drivers? Uthernet card, Link Layer ... etc.
I have been following this with great interest.
I am waiting for the day you announce you can print from Appleworks. :)
It's a long shot, but since you and I are both big Appleworks users, any chance this can be converted to a Prodos8 driver?
Or are there just too many dependencies on other drivers? Uthernet card, Link Layer ... etc.
Christopher G. Mason
Mar 10, 2021, 12:55:52 PM3/10/21
to
officially supported it with AppleTalk using the Remote Print Manager
and the ImageWriter emulator loaded into the LaserWriter. The RPM was a
bit of software and firmware trickery that made the Workstation Card (or
virtual IIgs slot) appear as a Super Serial card that one could print to.
Directly connected via a serial or parallel port is doable though. You
can still use the ImageWriter emulator in many PostScript printers or
directly use HP PCL escape codes.
Oliver Schmidt
Mar 10, 2021, 5:38:35 PM3/10/21
to
Hi,
> The RPM was a
> bit of software and firmware trickery that made the Workstation Card (or
> virtual IIgs slot) appear as a Super Serial card that one could print to.
Likely I'm just too naive, but at least conceptually one should be able to
route the data coming from the virtual IIgs slot containing the pseudo
Super Serial card (intended for the AppleTalk stack) to the TCP/IP stack...
Just some thought,
Oliver
> The RPM was a
> bit of software and firmware trickery that made the Workstation Card (or
> virtual IIgs slot) appear as a Super Serial card that one could print to.
route the data coming from the virtual IIgs slot containing the pseudo
Super Serial card (intended for the AppleTalk stack) to the TCP/IP stack...
Just some thought,
Oliver
Hugh Hood
Mar 13, 2021, 12:17:13 PM3/13/21
to
Rob,
Yes, I'm an unabashed AppleWorks nut. Guilty as you charged. ;-)
Funny you should ask about 8-bit TCP printing ...
There are talented people [not me, obviously] working on a couple of
different solutions for this. But, those are not my projects and thus
it's not my place to say anything about them at this point. Maybe that
will change. Sorry.
I am very optimistic, though.
Hugh Hood
Yes, I'm an unabashed AppleWorks nut. Guilty as you charged. ;-)
Funny you should ask about 8-bit TCP printing ...
There are talented people [not me, obviously] working on a couple of
different solutions for this. But, those are not my projects and thus
it's not my place to say anything about them at this point. Maybe that
will change. Sorry.
I am very optimistic, though.
Hugh Hood
Hugh Hood
Mar 13, 2021, 12:39:15 PM3/13/21
to
{Somewhat long - apologies}
Du sent me the AWGS Page Layout file with which he was experiencing
missing content issues when using the DCPPD. FWIW, the issue is also
present with the v3.3 LaserWriter driver from the GS/OS System 6.0.1
release and with the v3.0 LaserWriter driver from the AWGS install
disks. So, at least it's not something the DCPPD 'added'.
In addition to text, Du's AWGS page layout file contains some images
from the AWGS graphics module containing both bit-mapped and vector
elements.
I spent some time researching this particular issue by going back 25
years to the old GEnie Apple II Bulletin Board Archives.
I found this discussion, which appears to be exactly what Du and I
experienced with his AWGS document -- Page Layout module importing
combined draw and bit-mapped objects. I afraid there's not a solution to
this particular problem, other than his using the bit-mapped Harmonie
driver, which is less satisfying, because even at 300 dpi, it's still
not PostScript quality.
Here's that GEnie BB discussion:
> Q: Here is another thing I have wondered about with AWGS. I have
> created graphics with the paint module, where a draw object is
> combined with a paint object. In the paint module you can do this
> and everything seems to work fine. However, when I have tried to
> print using a LaserWriter, graphics created in the paint module and
> printed from the page layout module do not print correctly. The draw
> portion of the graphic appears but the rest of the graphic
> disappears. Any explanation why? Thanks.
>
> A: The problem with printing on LaserWriters is very well
> documented...it's a limitation of Apple's printer driver, and it's
> always been there. The driver simply cannot handle a thing called a
> "region". When QuickDraw II (The tool the GS uses to draw pictures)
> is drawing, it can draw several kinds of shapes. Lines, rectangles,
> ovals, arcs, and rounded rectangles all print fine on LaserWriters,
> these are simple shapes. QuickDraw also has "polygon" commands.
> These commands allow a program to define any shaped polygon, by
> drawing a series of lines. Luckily, even these more complex shapes
> print fine on a LaserWriter. The region is the most complex thing
> in all of QuickDraw, and the most useful. A region is defined by
> =any= collection of lines, ovals, rectangles, etc., even polygons.
> But they don't print on LaserWriters.
>
> I have a feeling AWGS is using regions for some of it's stuff, this
> would actually be pretty good, because regions are very versatile;
> you can reshape them, and perform complex operations on them, and QD
> handles it without any problem. But I don't know if PostScript
> handles them... even if it does, it may not be easy for QuickDraw
> regions to be translated into something the LaserWriter would
> understand. In any case, the driver just doesn't handle them, so you
> get a blank sheet of paper if you try to print one. The ImageWriter
> driver is fine, because it has to convert everything to a bitmap,
> anyway. And a bitmap is basically what you see on the screen.
Whether the analysis given on GEnie is correct I can't say.
FWIW, Du is experimenting with importing his graphics from another
graphics program instead of the AWGS graphics module.
Also, I've been unable to replicate the memory/crash issue that Du
mentioned. GS/OS can be a complex world, can't it?
Hugh Hood
Du sent me the AWGS Page Layout file with which he was experiencing
missing content issues when using the DCPPD. FWIW, the issue is also
present with the v3.3 LaserWriter driver from the GS/OS System 6.0.1
release and with the v3.0 LaserWriter driver from the AWGS install
disks. So, at least it's not something the DCPPD 'added'.
In addition to text, Du's AWGS page layout file contains some images
from the AWGS graphics module containing both bit-mapped and vector
elements.
I spent some time researching this particular issue by going back 25
years to the old GEnie Apple II Bulletin Board Archives.
I found this discussion, which appears to be exactly what Du and I
experienced with his AWGS document -- Page Layout module importing
combined draw and bit-mapped objects. I afraid there's not a solution to
this particular problem, other than his using the bit-mapped Harmonie
driver, which is less satisfying, because even at 300 dpi, it's still
not PostScript quality.
Here's that GEnie BB discussion:
> Q: Here is another thing I have wondered about with AWGS. I have
> created graphics with the paint module, where a draw object is
> combined with a paint object. In the paint module you can do this
> and everything seems to work fine. However, when I have tried to
> print using a LaserWriter, graphics created in the paint module and
> printed from the page layout module do not print correctly. The draw
> portion of the graphic appears but the rest of the graphic
> disappears. Any explanation why? Thanks.
>
> A: The problem with printing on LaserWriters is very well
> documented...it's a limitation of Apple's printer driver, and it's
> always been there. The driver simply cannot handle a thing called a
> "region". When QuickDraw II (The tool the GS uses to draw pictures)
> is drawing, it can draw several kinds of shapes. Lines, rectangles,
> ovals, arcs, and rounded rectangles all print fine on LaserWriters,
> these are simple shapes. QuickDraw also has "polygon" commands.
> These commands allow a program to define any shaped polygon, by
> drawing a series of lines. Luckily, even these more complex shapes
> print fine on a LaserWriter. The region is the most complex thing
> in all of QuickDraw, and the most useful. A region is defined by
> =any= collection of lines, ovals, rectangles, etc., even polygons.
> But they don't print on LaserWriters.
>
> I have a feeling AWGS is using regions for some of it's stuff, this
> would actually be pretty good, because regions are very versatile;
> you can reshape them, and perform complex operations on them, and QD
> handles it without any problem. But I don't know if PostScript
> handles them... even if it does, it may not be easy for QuickDraw
> regions to be translated into something the LaserWriter would
> understand. In any case, the driver just doesn't handle them, so you
> get a blank sheet of paper if you try to print one. The ImageWriter
> driver is fine, because it has to convert everything to a bitmap,
> anyway. And a bitmap is basically what you see on the screen.
Whether the analysis given on GEnie is correct I can't say.
FWIW, Du is experimenting with importing his graphics from another
graphics program instead of the AWGS graphics module.
Also, I've been unable to replicate the memory/crash issue that Du
mentioned. GS/OS can be a complex world, can't it?
Hugh Hood
Todd Holcomb
Mar 13, 2021, 5:12:59 PM3/13/21
to
A user on Captain's Quarters II BBS reports that the HP LaserJet HPLJ4050N printer works well with the Direct Connect PostScript Printer Driver too.
Hugh Hood
Mar 13, 2021, 10:32:13 PM3/13/21
to
Excellent. I've added it to the list.
Thanks.
Hugh Hood
Thanks.
Hugh Hood
Antoine Vignau
Mar 14, 2021, 5:59:30 PM3/14/21
to
Hi Hugh,
Antoine
"GS/OS can be a complex world, can't it?"
We're dealing with the System toolbox world, it is not related to GS/OS at all.
Antoine
Steven Nelson
Mar 19, 2021, 4:50:40 PM3/19/21
to
Thanks for a superb work.
--Steven
Antoine Vignau
Mar 20, 2021, 11:27:16 AM3/20/21
to
Hi Hugh,
Your printer driver + Treehugger running on a Sweet16 ROM 3 IIgs connected to a HP OfficeJet Pro 9022 by wifi.
Only garbage is printed.
Antoine
Your printer driver + Treehugger running on a Sweet16 ROM 3 IIgs connected to a HP OfficeJet Pro 9022 by wifi.
Only garbage is printed.
Antoine
Hugh Hood
Mar 20, 2021, 5:59:19 PM3/20/21
to
Antoine,
Thank you for the report. Unfortunately, this behavior is the expected
one on the HP OfficeJet Pro 9022.
I went to HP's site and pulled the specifications on that particular model.
The only printer language supported in that model is that which they
term 'HP PCL3 GUI'. It neither supports HP PCL 5/PCL 6, nor PostScript.
PCL3 GUI is common in many of the inkjet printer models these days, and
relies on the host computer to do all the graphics and text image
processing before sending all the data as an image to the printer.
Generally, a PCL3 GUI printer contains no built-in fonts nor high-level
text or graphics routines.
Since I've been asked off-list about the various printer languages in
today's printers, here is a small chart:
1. HP PCL3 GUI - graphics only from host printer driver; contains no
built-in fonts nor high-level text or graphics
routines / common in modern ink-jet printers
- these type printers will NOT support 8-bit text
output from programs such as AppleWorks or BASIC
- these do NOT understand PostScript
2. HP PCL 5 / HP PCL 6 - intelligent languages with built-in fonts and
that support numerous high-level text and
graphics commands
- these WILL support 8-bit text output from
programs such as AppleWorks and BASIC,
and also from GS/OS desktop programs that
use the Harmonie or Independence printer
drivers
- these do NOT understand PostScript
3. PostScript emulation - intelligent language that supports output from
a PostScript Printer driver
- these support GS/OS Desktop output from the
Direct Connect PostScript Printer Driver and
also from 8-bit programs such as PublishIt! 4
Many of the printers that support #2 will also support #3 and will be
able to auto-switch between the two. Virtually all modern printers that
support #3 will also contain #2.
The surprising thing (to me) is that since HP owns the rights to PCL 5 /
PCL 6, it would cost them nothing to include it with any of their
printers OTHER than the additional memory and processing power required,
which wouldn't amount to much. Strangely, HP never asked for my opinion. ;-)
Hugh Hood
Thank you for the report. Unfortunately, this behavior is the expected
one on the HP OfficeJet Pro 9022.
I went to HP's site and pulled the specifications on that particular model.
The only printer language supported in that model is that which they
term 'HP PCL3 GUI'. It neither supports HP PCL 5/PCL 6, nor PostScript.
PCL3 GUI is common in many of the inkjet printer models these days, and
relies on the host computer to do all the graphics and text image
processing before sending all the data as an image to the printer.
Generally, a PCL3 GUI printer contains no built-in fonts nor high-level
text or graphics routines.
Since I've been asked off-list about the various printer languages in
today's printers, here is a small chart:
1. HP PCL3 GUI - graphics only from host printer driver; contains no
built-in fonts nor high-level text or graphics
routines / common in modern ink-jet printers
- these type printers will NOT support 8-bit text
output from programs such as AppleWorks or BASIC
- these do NOT understand PostScript
2. HP PCL 5 / HP PCL 6 - intelligent languages with built-in fonts and
that support numerous high-level text and
graphics commands
- these WILL support 8-bit text output from
programs such as AppleWorks and BASIC,
and also from GS/OS desktop programs that
use the Harmonie or Independence printer
drivers
- these do NOT understand PostScript
3. PostScript emulation - intelligent language that supports output from
a PostScript Printer driver
- these support GS/OS Desktop output from the
Direct Connect PostScript Printer Driver and
also from 8-bit programs such as PublishIt! 4
Many of the printers that support #2 will also support #3 and will be
able to auto-switch between the two. Virtually all modern printers that
support #3 will also contain #2.
The surprising thing (to me) is that since HP owns the rights to PCL 5 /
PCL 6, it would cost them nothing to include it with any of their
printers OTHER than the additional memory and processing power required,
which wouldn't amount to much. Strangely, HP never asked for my opinion. ;-)
Hugh Hood
Hugh Hood
Mar 20, 2021, 6:11:32 PM3/20/21
to
Steven,
Thank you for taking the time to test the DCPPD and to report back.
I'm tickled that it works with the LaserJet M402dn because that printer
is an HP laser in relatively recent production. I'll gratefully add it
to the list!
I'll make a note about the IP and port # too.
BTW, we all should be glad that Daniel Krue released his TreeHugger
TCP/IP printer port driver. Without it, the DCPDD would have a VERY
limited audience, I'm afraid. I've tried twice to email Daniel and thank
him for TreeHugger and to let him know about the DCPDD, but have yet to
receive a response. I do hope he's OK these days.
Please know also that I appreciate the past testing you've done with my
other Apple II efforts.
Hugh Hood
Thank you for taking the time to test the DCPPD and to report back.
I'm tickled that it works with the LaserJet M402dn because that printer
is an HP laser in relatively recent production. I'll gratefully add it
to the list!
I'll make a note about the IP and port # too.
BTW, we all should be glad that Daniel Krue released his TreeHugger
TCP/IP printer port driver. Without it, the DCPDD would have a VERY
limited audience, I'm afraid. I've tried twice to email Daniel and thank
him for TreeHugger and to let him know about the DCPDD, but have yet to
receive a response. I do hope he's OK these days.
Please know also that I appreciate the past testing you've done with my
other Apple II efforts.
Hugh Hood
Scott Alfter
Mar 22, 2021, 1:55:05 PM3/22/21
to
In article <Upidncbrv5mt7cv9...@earthlink.com>,
I had a LaserJet 1020 on my desk at work that was like that. For a good
long time, though, all their printers supported at least proper PCL (5 or
later), and many (like the LaserJet 1320 at home) did PostScript as well.
Oh, well...after HP's other recent shenanigans, my last printer purchase was
an Epson ET-3760. I have no idea if it speaks PostScript, but I think it at
least handles something descended from what used to run their dot-matrix
printers. Before trying to get that working with my IIGS, though, I need to
put the LaserJet 1320 back on the LAN (I have a JetDirect box for that
purpose) and see if your driver will print to it.
_/_
/ v \ Scott Alfter (remove the obvious to send mail)
(IIGS( https://alfter.us/ Top-posting!
\_^_/ >What's the most annoying thing on Usenet?
Hugh Hood <hugh...@earthlink.net> wrote:
>1. HP PCL3 GUI - graphics only from host printer driver; contains no
> built-in fonts nor high-level text or graphics
> routines / common in modern ink-jet printers
> - these type printers will NOT support 8-bit text
> output from programs such as AppleWorks or BASIC
> - these do NOT understand PostScript
Sounds like a return to the bad old days of "WinPrinters." Until recently,
>1. HP PCL3 GUI - graphics only from host printer driver; contains no
> built-in fonts nor high-level text or graphics
> routines / common in modern ink-jet printers
> - these type printers will NOT support 8-bit text
> output from programs such as AppleWorks or BASIC
> - these do NOT understand PostScript
I had a LaserJet 1020 on my desk at work that was like that. For a good
long time, though, all their printers supported at least proper PCL (5 or
later), and many (like the LaserJet 1320 at home) did PostScript as well.
Oh, well...after HP's other recent shenanigans, my last printer purchase was
an Epson ET-3760. I have no idea if it speaks PostScript, but I think it at
least handles something descended from what used to run their dot-matrix
printers. Before trying to get that working with my IIGS, though, I need to
put the LaserJet 1320 back on the LAN (I have a JetDirect box for that
purpose) and see if your driver will print to it.
_/_
/ v \ Scott Alfter (remove the obvious to send mail)
(IIGS( https://alfter.us/ Top-posting!
\_^_/ >What's the most annoying thing on Usenet?
Hugh Hood
Mar 24, 2021, 12:41:52 AM3/24/21
to
Scott,
I pulled the specs and that Epson EcoTank inkjet you have only speaks
ESC/P-R, which is, as you mentioned, Epson's latest incarnation of their
original language for dot-matrix printers. Although it doesn't speak
PostScript, I suspect that the Vitesse Harmonie Epson printer drivers
would work fine with it from GS/OS, and you could drive it with Krue's
TreeHugger TCP/IP port driver provided you have an Uthernet card.
The LaserJet 1320, on the other hand, speaks both PCL 5 / PCL 6 and
PostScript, so I imagine the DCPPD will work just fine with it.
It you do get around to testing it, though, please let us know as I'm
putting together a list of printers that work with the DCPPD.
Thanks.
Hugh Hood
I pulled the specs and that Epson EcoTank inkjet you have only speaks
ESC/P-R, which is, as you mentioned, Epson's latest incarnation of their
original language for dot-matrix printers. Although it doesn't speak
PostScript, I suspect that the Vitesse Harmonie Epson printer drivers
would work fine with it from GS/OS, and you could drive it with Krue's
TreeHugger TCP/IP port driver provided you have an Uthernet card.
The LaserJet 1320, on the other hand, speaks both PCL 5 / PCL 6 and
PostScript, so I imagine the DCPPD will work just fine with it.
It you do get around to testing it, though, please let us know as I'm
putting together a list of printers that work with the DCPPD.
Thanks.
Hugh Hood
0 new messages