Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!samsung!munnari.oz.au!uniwa!vaxa.cc.uwa.oz.au!d_volaric
From: d_volaric@vaxa.cc.uwa.oz.au
Newsgroups: comp.sys.mac.programmer,aus.mac
Subject: Re: Writing a Printer/Device Driver. - Help
Message-ID: <1990Jul31.175346.2019@vaxa.cc.uwa.oz.au>
Date: 31 Jul 90 09:53:46 GMT
References: <10418@wehi.dn.mu.oz>
Organization: University of Western Australia
Lines: 30

In article <10418@wehi.dn.mu.oz>, JON@wehi.dn.mu.oz (Jon Eaves) writes:
> G'day Net,
> 	I have been asked to write a device driver for a new printing task.

> The daemon is not my problem, so all I need to know is what is involved with
> writing the device driver (if that is the correct term).
> Is there any skeleton code available?

"MacTech Quarterly" Vol 1 No. 2; Summer 1989, page 44 "The Great Printer
Conspiracy". Aptly named. You may have to sell your soul to The Devil to make 
it all work.

The article lists source in 68000 and goes into depth about printer drivers
and their evils. It does not tell ALL the secrets of the way the Mac currently 
performs its printing, but it should be fine for what you're doing.

Also, it just so happens that a friend of mine has typed in the source or
a translation in pascal or something. He may give you what he's done for
your firstborn, pound of flesh or maybe just a disk :-).

> I'd appreciate ANY comments because this whole style of programming is new
> to me.

Get a copy of Inside Macintosh Vols 1-5 (and a draft of Vol 6 if you can get it)
before you even look sideways at programming a Mac. Make sure you've got a good
debugger (Macsbug, TMON), you'll need it.

>   Jon Eaves 
        
Darko Volaric.