Xref: utzoo unix-pc.general:7447 comp.sys.att:11635
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!att!westmark!hico2!kak
From: kak@hico2.UUCP (Kris A. Kugel)
Newsgroups: unix-pc.general,comp.sys.att
Subject: Re: 3B1 Device Driver Dev. Guide update and ordering info
Summary: Another Volunteer
Message-ID: <924@hico2.UUCP>
Date: 28 Jan 91 15:58:32 GMT
References: <38457@cup.portal.com> <1991Jan26.042946.17465@dms3b1.uucp> <38507@cup.portal.com>
Followup-To: unix-pc.general,comp.sys.3b1
Organization: High Country Software
Lines: 26

In article <38507@cup.portal.com>, thad@cup.portal.com (Thad P Floryan) writes:
> dave@dms3b1.uucp (Dave Hanna) in <1991Jan26.042946.17465@dms3b1.uucp> writes:
> 
> Regarding the UNIXPC Device Driver Development Guide and my suggestion that
> a team type it into the computer:

> The Guide's print quality is readable by humans, but I do not believe there's
> any scanner capable of reliably processing it today; the time required to make
> corrections would (probably) be greater than the time required to type in the
> document assisted by human optical scanning!  :-)
> 
> What's annoying (to me) is that the ORIGINAL document must have been in a file
> for troff or TeX, but no-one I've called claims any knowledge of that.
> 
> Thad Floryan [ thad@cup.portal.com ]

I'm willing to type it in, or, as an alternate, re-add the nroff
constructs for the document.  I've recently done this for a major
document on the 3b1 posted to this group.
I'm also willing to co-ordinate a combination of the pieces,
and that will be completed quicker.
                               Kris A. Kugel
                             ( 908 ) 842-2707
                      uunet!tsdiag.ccur.com!hico2!kak
                        {daver,ditka,zorch}!hico2!kak
                      internet: kak@hico2.westmark.com