heather@merlin.bcm.tmc.edu (03/02/90)
Does anyone know how I can get my HP Deskwriter to print from Microphone II version 2.0? Is there a patch I can get by ftp and if so from where ? Are there any fonts I can download that will work with the Deskwriter and Adobe Type Manager. Thanks!!! heather@merlin.bcm.tmc.edu
svc@well.sf.ca.us (Leonard Rosenthol) (03/06/90)
In article <256@gazette.bcm.tmc.edu> heather@merlin.bcm.tmc.edu () writes: >Does anyone know how I can get my HP Deskwriter to print from >Microphone II version 2.0? Is there a patch I can get by ftp >and if so from where ? > Unfortunately there is not 'patch' to solve this problem as this is an HP problem. The HP Deskwriter printer driver is not a full featured driver as are the Apple drivers, and most other third parties. On the Macintosh there are two different forms of printing, page based and line based. The former is how most Macintosh applications print (ie. they image a whole page all at once), on the other hand communications applications (among others) can only image one line at a time (known as streaming). HP decided that they knew printing better than Apple and as such they only support the 'Page Based' printing modal. MicroPhone II 2.0 uses the line based modal and as such won't print to the Deskwriter. Our only recommendations at this time are to a) Harrass HP into fixing their Printer Driver and b) Upgrade to MicroPhone II v3.0 which now supports the page based modal for some of its printing needs. Leonard Rosenthol Software Ventures MicroPhone II Development Team -- +--------------------------------------------------+ Leonard Rosenthol | GEnie : MACgician Lazerware, inc. | MacNet: MACgician UUCP: svc@well.UUCP | ALink : D0025
barry@primerd.prime.com (03/09/90)
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.
If you don't need immediate logging of traffic, try copying text from
the Microphone II capture buffer into a DA such as McSink that can
print using the standard driver. This should work with the DeskWriter.
------------------------------------------------------------------------
Barry Wolman | barry@s66.prime.com
Principal Technical Consultant | 500 Old Connecticut Path
Prime Computer | Framingham, MA 01701
| 508/879-2960, ext. 1100
------------------------------------------------------------------------
Nothing in this posting represents a position of Prime Computer.svc@well.sf.ca.us (Leonard Rosenthol) (03/13/90)
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. > I can not speak for other comm programs, but I can tell you that MicroPhone and MicroPhone II (2.0 and 3.0) _DO_ use the printer driver for all printing task. For print logging (print streaming, etc.), we use the 'low level interface' to the printer drivers - and this is what the HP Drivers _DO NOT_ support! Most third party (as well as the Apple Drivers) support this interface...Why can't HP!??!?! (Oh, I should also comment that when the announced new printing architecture that Apple has promised arrives that the approved method of doing 'print logging will be do 'Blast it out the serial port' (that's a quote from an Apple Engineer).... >If you don't need immediate logging of traffic, try copying text from >the Microphone II capture buffer into a DA such as McSink that can >print using the standard driver. This should work with the DeskWriter. > That will work, though for a more 'non-interactive' method we recommend that you use th the capture file commands to put all the data into a capture file on disk and the print the file later with a either some other program (like McSink, a word processor) or our Print File XCMD (in version 3.0) Leonard Rosenthol Software Ventures 'Printing Guru' MicroPhone II Development Team -- +--------------------------------------------------+ Leonard Rosenthol | GEnie : MACgician Lazerware, inc. | MacNet: MACgician UUCP: svc@well.UUCP | ALink : D0025
kaufman@Neon.Stanford.EDU (Marc T. Kaufman) (03/14/90)
Do you ever have a day where you are sure that someone is keeping secrets from you, even though you ought to know them? I write print drivers (among other things) for a living. In article <16638@well.sf.ca.us> svc@well.UUCP (Leonard Rosenthol) writes: -In article <160700096@primerd> barry@primerd.prime.com writes: - I can not speak for other comm programs, but I can tell you that -MicroPhone and MicroPhone II (2.0 and 3.0) _DO_ use the printer driver for -all printing task. For print logging (print streaming, etc.), we use the -'low level interface' to the printer drivers - and this is what the HP Drivers -_DO NOT_ support! Most third party (as well as the Apple Drivers) support -this interface...Why can't HP!??!?! -(Oh, I should also comment that when the announced new printing architecture -that Apple has promised arrives that the approved method of doing 'print -logging -will be do 'Blast it out the serial port' (that's a quote from an Apple -Engineer).... Unfortunately, no one has told me that -- so none of my drivers support low level printing calls. In fact, TN#192 (Suprises in LaserWriter 5.0 and Newer) says: "No Mo' Low: Because of the problems supporting both the high-level interfaces in the background, the low-level interface is all but removed..." In several Tech Notes (124, 192) Apple specifically recommends AGAINST using the low level calls. The preview of System 7.x at last year's developer's conference says "No pass-through (Draft) printing". DTS provides a document called "The PrintShop Mystique" to print driver writers that says: "Low-Level Calls. Low level calls are a different breed of call, currently being supported only for historical reasons. ...It is recomended that all new development, both application and driver, avoid low-level implementations if at all possible." Given this, I really can't blame HP for not supporting low-level calls. And I would have to argue your statement that "most third party drivers support this interface". If low level calls are important, then Apple should have told us so. Maybe it is MicroPhone that is out of step. Marc Kaufman (kaufman@Neon.stanford.edu)