PC's Limited

From: Ethan Dicks <erd_at_infinet.com>
Date: Sat Jan 23 00:04:18 1999

Zane Healy writes;
> However, in looking at the URL's that have been flying about I notice that
> they've apparently got the Matrix Orbital modules with the Keypads working.
> Now that's what I really want. I'd love to be able to punch a couple
> buttons on the front panel of my computer and get it to reboot, halt, or
> play my favorite MP3's!

lcdproc 0.4pre1 (and up) has a joystick driver for buttons not attached
to the LCD module. I have been frantically looking for my Gravis joypad
to no avail. :-(

> Besides I prefer the looks of the VFD's to the LCD's.

The VFD's are way cool and twice as expensive as the expensive LCD's. I
want one too, but not at $150+.

> >P.S. Any interest in LCD code for the 6502?
>
> No, but I'd love to see it for the PDP-11 :^)

Ooh! There's a challenge. To keep this on the classiccmp topic list... how
would it be best to attach one? Serial, obviously, but what OS? I could
cobble some MACRO together in a few hours to drive a serial LCD on demand
from RT-11, but I never did much more than FORTRAN on RSX.

I wouldn't guarantee most lcdproc clients would work on RT, but it might
be possible to port it to RSTS in toto. Are there any RSTS-internals
guru's out there? The default lcdproc clients give current time, uptime,
CPU usage, load (graphically) and memory stats. I'm porting the clients
to Solaris and find that I need to know the total memory, the swap size,
the swap in use, the physical mem in use, percentage of CPU in user mode,
system (kernel) mode, free and "nice"'ed, uptime and current wall time.
How much of this is accessible from RSTS? Most of it is irrelevant from
RT, ISTR.

-ethan
Received on Sat Jan 23 1999 - 00:04:18 GMT