elric@mabelode.imrryr.org said:
> Wscons does support multiple virtual terminals on the alpha, just not
> on the TGA framebuffer that the multia uses.  I was thinking about
> throwing it in, but it certainly begs a number of questions, since a
> copy of the framebuffer memory would be a meg.  So, would one just
> store the characters that are on the screen?

Yes, why not? You can't use the rcons stuff directly in this case,
but it should be possible.
For color support, rcons is somehow in the way and should be
replaced.

> In which
> case X probably wouldn't be too happy.  Or the fact that one can
> combine graphics and text on a non-X screen if one writes the
> appropriate app.

It would need a switching protocol so that the X server
can claim a screen and disallow wscons access until it gives
it up.

> For that matter, does anybody have any ideas as to why I can't get the
> keyboard bell to work on my multia?  I've fixed the drq line for wss
> in my config file, for what that's worth.  And dmesg claims that it
> attaches a device named isabeep0; shouldn't that do the right thing?

It should work then - isabeep() is called from pckbd.c since
rev. 1.11 (1998/08/07).
Does it beep at all, eg with the spkr (/dev/speaker) device?

best regards
Matthias