🚀 go-pugleaf

In article <6182@blake.acs.washington.edu>, djo7613@blake.acs.washington.edu (Dick O'Connor) writes:
> I use a Zenith Z248 AT-compatible running Zenith's MSDOS 3.3Plus to do
> a variety of things, including newsletters with First Publisher.  Finally,
> with FP Version 2.0, you can make a print file out of your publication in
> order to "sneaker-net" it over to the LaserJet in the corner!
> 
> I've noticed one odd thing that I can't explain.  The resulting HUGE print
> file (if a .PUB file is 30K, the print file can be 300K, but it's probably
> basically a bitmap) can be printed using COPY fname >PRN but not by
> using PRINT fname.  I understand that this print file is binary;  what do
> PRINT and COPY do so differently that one works in this case and one doesn't?
> (PRINT starts off OK, but hangs the printer within 4-5 lines; this tested
> on an Epson dot matrix printer as well).
> 
> "Moby" Dick O'Connor                            ** The only difference between
> Washington Department of Fisheries              ** a lazy man on a riverbank
> Olympia, Washington  98504                      ** and a fisherman is a pole
> Internet Mail: djo7613@blake.u.washington.edu   ** and a length of string.

When you PRINT a file, the print program looks for an EOF marker to designate
the end of the file, logically.  Unfortunately, this is not wanted when you are
sending bitmap files to the printer, because invariably you will encounter the
EOF code that is not meant to designate the end of the file, but rather a
particular bitmapped dot.  When you use COPY /B (the /B meaning Binary), it
ignores the EOF marker code, thereby allowing your file to transfer completely,
and without any type of ASCII translation.

Alex Cutrone
v126gfl3@ubvms.cc.buffalo.edu