Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!uwm.edu!rutgers!netnews.upenn.edu!eniac.seas.upenn.edu!hodas
From: hodas@eniac.seas.upenn.edu (Josh Hodas)
Newsgroups: comp.sys.mac
Subject: Re: Deskwriter usage [For logging from Comm programs]
Message-ID: <21585@netnews.upenn.edu>
Date: 10 Mar 90 05:34:16 GMT
References: <256@gazette.bcm.tmc.edu> <160700096@primerd>
Sender: news@netnews.upenn.edu
Reply-To: hodas@eniac.seas.upenn.edu.UUCP (Josh Hodas)
Organization: University of Pennsylvania
Lines: 29

In article <160700096@primerd> barry@primerd.prime.com writes:
>
>Most comms programs that log traffic do so by dumping characters onto
>the printer port, bypassing the printer driver completely.  The HP
>DeskWriter does not have any builtin fonts and cannot be used in this
>fashion.  Pushing HP to "fix" the DeskWriter is likely to be useless
>since we're talking about a basic design decision.  Anyone who needs to
>log traffic on the printer port would be better served by the DeskJet
>Plus. 
>
Note,

Versterm 4.0 (and I believe earlier versions) will work perfectly 
in conjunction with the deskwriter. The page setup dialog has an option
whether you want the logging (and other printing functions) should
drive the printer directly, or use the installed printer driver.

I have had no problems. It is yet another example of why I love versaterm.


Josh Hodas
-------------------------

Josh Hodas    (hodas@eniac.seas.upenn.edu)
4223 Pine Street
Philadelphia, PA 19104

(215) 222-7112   (home)
(215) 898-5423   (school office)