Path: utzoo!utgpu!watserv1!watmath!att!pacbell!pacbell.com!ucsd!swrinde!cs.utexas.edu!sun-barr!apple!snorkelwacker!ai-lab!rice-chex!bson
From: bson@rice-chex.ai.mit.edu (Jan Brittenson)
Newsgroups: comp.sys.handhelds
Subject: 48 ML: real-time clock, keyboard
Message-ID: <10469@life.ai.mit.edu>
Date: 6 Sep 90 20:12:53 GMT
Sender: news@ai.mit.edu
Organization: nil
Lines: 14


   Does anyone know how/where to access/find the 48's real-time clock,
presumably in ticks? I found some value similar to what TICKS returns
at #70488h (give or take 8h).

   How about the keyboard, how are the scan codes stored in the buffer
(#704EAh), and what is expected from code that reads a key - is it a
ring buffer, or a shift buffer, and is decoding press-release
sequences necessary?  Will the buffer keep filling with scan codes
while a key is depressed or will there merely be two separate entries
for press/release? I just can't make anything useful out of the info
I've got without tons of thin-air assumptions or (too many) hours of
experimentation. I read somewhere that "it works just like the 28" -
so, how is that?