Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!ucsd!ucbvax!ziploc!eps
From: eps@toaster.SFSU.EDU (Eric P. Scott)
Newsgroups: comp.sys.next
Subject: Re: Direct access to screen pixels
Message-ID: <245@toaster.SFSU.EDU>
Date: 9 Jan 90 22:44:56 GMT
References: <5963@cps3xx.UUCP>
Reply-To: eps@cs.SFSU.EDU (Eric P. Scott)
Organization: San Francisco State University
Lines: 16

In article <5963@cps3xx.UUCP> flynn@pixel.cps.msu.edu (Patrick J. Flynn) writes:
>Now that the faint-hearted are scared away...

Eek.  I'm surprised you can do this at all--I wouldn't expect
screen pixels to be writeable by a user process unless they were
explicitly mapped into a task's address space via an ioctl that
insisted on w access to its device--or is this a side-effect of
DKIOCGADDR?

"So much for turning off PublicWindowServer"

While we're on the subject, has anyone figured out exactly what
/usr/bin/blit does, and why it doesn't seem to work once the
system is up and running?  (Which is arguably a good thing.)

					-=EPS=-