TIP: Click on subject to list as thread! ANSI
echo: cis.os9.6809.coco
to: 70415,421
from: Lee Veal 74726,1752
date: 1991-04-06 12:33:49
subject: SmartWatch and SC-II

#: 10134 S10/OS9/6809 (CoCo)
    06-Apr-91  12:33:49
Sb: SmartWatch and SC-II
Fm: Lee Veal 74726,1752
To:  70415,421

     There's a fellow in our local club that uses a
  SuperController II, and has a SmartWatch installed in its ROM
  socket.  He has a question concerning the dri.ers found in
  SWCLOC.AR in Lib 10 her on CI$.  All of the drivers and programs
  in the ARchive are slot-specific which seems to mean that they
  assume that an MPI is plugged into the system.  However, since
  he doesn't use an MPI (the SCII handles his HD, FD, and RS-232),
  he's wondering if it even matters which SWClock driver, SetClk,
  GetClk program he uses in his system.
       The only differences that I've been able to find among the
  like modules contained in the ARchive (besides the CRCs) are the
  slot select codes.  For instance, the module SWCLOCK4 has,
  starting at 1EB, an 8633 (LDA immediate) followed by a B7FF7F
  (STA), and SWCLOCK3 has an 8622 followed by the POKE (STA) that
  actually does the slot select.
       Since the B7FF7F is addressing the Slot Select byte that
  only means something if an MPI is plugged in, would it be
  necessary to NOP the 86xxB7FF7F instruction sequence with
  1212121212, if no MPI is plugged into the CoCo?

  Lee

SOURCE: compuserve via textfiles.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.