Conference hydra::amiga_v1

1545.0. "1.3<==>1.2 print compatibility" by VTHRAX::KIP (No Dukes.) Fri Jul 15 1988 18:31

    Wondering if anyone can shed some light on this:
    
    I have an old clunker Star Gemini-15 printer.  It is supposed to
    be "Epson-compatible" but of course isn't completely.  So I used
    PRTDRVGEN V2.2 to generate a driver for it, which works well with
    the 1.2 printer device.
    
    With ProWrite 2.0, I received the 1.3 printer.device, with the
    additional printer setup screens.  Now, when I use DeluxePaint II
    with the 1.3 device and my driver, everything works ok.  This includes
    the different density and print size options in 1.3 Preferences.
    
    BUT, when I try to use these same two modules (1.3 device and my
    driver) with ProWrite, all I get for output in ProWrite's "standard"
    mode is hieroglyphics; if I try to use "draft" mode, I get normal
    characters, but control codes are all messed up (each line is
    underlined for half of a page, some words bolded, some not, etc.)
    
    I'm curious as to why the device/driver combination I'm trying to
    use works with DPaint, but not with ProWrite.  Could ProWrite be
    trying to use functions in the printer.device that DPaint isn't
    touching?
    
    Thanks for any advice/help.

Re: .0

>    I'm curious as to why the device/driver combination I'm trying to
>    use works with DPaint, but not with ProWrite.  Could ProWrite be
>    trying to use functions in the printer.device that DPaint isn't
>    touching?

Quite likely.   DPaint only uses the bitmap dump features of a printer
driver.  In addition to those, a driver supports all sorts of text
related features like "turn on bolding,"  "turn off underline," etc.
I could easily believe that a word processor is using such features.