rokicki@Navajo.ARPA (02/07/86)
*** REPLACE THIS LINE WITH YOUR MACINTOSH *** I have a printer which isn't supported by the drivers on the Workbench (it's a QMS SmartWriter), and I would like to write my own driver. I can't find the format for the printer drivers anywhere in the developer's kit; perhaps I lack something? Any pointers would be greatly appreciated; the QMS is a tremendous printer and I can't wait to get some incredible graphics going . . . -tom
bruceb@amiga.UUCP (02/07/86)
<... request for custom printer driver info...> Page 3-207 states that driver example code is included in appendix H, in fact it is included in appendix I. But it is all there. Enjoy. Til then use generic for text output. --Bruce Barrett
bruceb@amiga.UUCP (02/07/86)
That last posting of mine was real useful, gave page numbers but no manual reference, sigh. The printer info is in the "new" V1.1 ROM Kernel manual. --Bruce Barrett
papa@uscvax.UUCP (Marco Papa) (02/09/86)
> That last posting of mine was real useful, gave page numbers but no manual > reference, sigh. The printer info is in the "new" V1.1 ROM Kernel manual. > --Bruce Barrett The render.c function from the manual appendix or the prtbase.h include file have a bug that does not permit to compile correctly render.c . On of the fields in the PD structure is a function pointer that is declared VOID in the .h file, but that returns a value in the render.c file (in 4 or 5 different places). The Lattice C compiler barfs on it with "illegal void" or something like that. Also Lattice C (version 3.03) produces a warning for "incorrect value returned", since the function is declared to return a BYTE (I think) and instead it return something else. Who is wrong, the .h file or render.c? Marco Papa USC - Computer Science Dept. UUCP: ...!{decvax,ucbvax,hplabs}!sdcsvax!sdcrdcf!uscvax!papa ...!{allegra,trwrb,trwspp,ism780,cithep,oberon}!uscvax!papa CSNET: papa@usc-cse.csnet ARPA: papa%usc-cse@csnet-relay.arpa