Jan Brittenson: >>Blinky [& friends]; 48-internals; spritzing your screen
In article <kbE7C1u00WBM83dksI@andrew.cmu.edu> 
   dj1l+@andrew.cmu.edu (Demian A. Johnston) writes:

 > Subject: Re: Blinky, A CHIP-48 PacMan & Chipper,
 >          A PC based CHIP-48 assembler

   I haven't received anything about the items mentioned in the
subject. In fact, I haven't received anything on this newsgroup the
last couple of days. So something is probably broken at my end. Could
some kind soul mail me the address of an ftp site that carries them?
(nic.funet.fi, like Demian mentioned, doesn't seem to.)

   Also, this makes me wonder whether my announcement of the
48-internals list a couple of weeks ago ended up in the bitbucket.
It's still an informal list open for requests, for non HP (Corvallis)
employees and contractors; send me your 48's serial #, date and place
of purchase, your name and a working e-mail address, and I will add
you to the list. The list's purpose is for a group of 48 owners to
nonpublicly be able to discuss the software and hardware of their
HP-48SX calculators, where similar activities if done in public would
infringe upon HP's copyright.

   Finally, I have written a simple but fast sprite drawer in ML. The
current version is stack-based for debugging purposes, but will become
an integral part of a sprite animation system I'm working on and then
inaccessible stackwise. If there is enough interest in the stack-based
version, I can type up a short description and post it on the net. It
supports sprite drawing at 16 angles, rotation, collision detection (a
fairly stupid one, but fast and adequate for my purposes), drawing
with BIS (bit set - OR), XOR, BIC (bit clear), and that's about all it
does. It doesn't do any boundary checking, or clipping, for speed's
sake, and so will merrily trash your innocent little 48's memory
without the slightest notion of wrong-doing, if given improper
arguments. (Don't tell me you weren't warned.) I realize calling it
from user code is virtually useless (unless you have an object that
will take considerably less space as a spritzel than it does as a
GROB, which might be the case if you had, say, a world contour map
:-)), but the enlightened reader of course recognizes the hacking
potential. Minor lobotomization can work wonders.

That's about it for now.
                                                -- Jan Brittenson
                                                   bson@ai.mit.edu