TIP: Click on subject to list as thread! ANSI
echo: cis.os9.6809.coco
to: thomas aubin 70540,1666 (X)
from: Pete Lyall 76703,4230
date: 1991-05-17 23:22:56
subject: #10720-#os9/telecomm

#: 10727 S10/OS9/6809 (CoCo)
    17-May-91  23:22:56
Sb: #10720-#os9/telecomm
Fm: Pete Lyall 76703,4230
To: thomas aubin 70540,1666 (X)

Tom -

I'm no longer a coco'er, so some of this is a stretch for me memory wise... I'm
not sure where/when the /M1 module was first distributed.

Is there any possibility that it exists in the bootfile on the 2.00.00 disk?
Try this:

   Ident -s    Ident -s /d0/OS9boot

And see what drivers and descriptors are there....

Something else just occurred to me. Because of the inadequate handling of the
IRQ's for devices in the multi-pak, we developed something called an IRQ hack
that tied to the RS232 pak. This allowed it to receive serial interrupts. In
the case of the modem pak, this wasn't necessary because they (Tandy/Microware)
included a _virtual_ IRQ driver (VIRQ) that would issue interrupts every so
often. They'd use this to act as sort of a baby sitting timer for checking the
modem pak. This all boils down to the fact that if you use /M1, you may also
need to unearth VIRQ. I believe that VIRQ wasn't implemented until 2.00.00.

Again - see what's in the 2.00.00 bootfile. In fact, omit the -s option and get
the full poop on all the modules. We're mainly interested in finding M1, it's
driver (the descriptor will list which driver it is affiliated with), and
whether or not you have VIRQ.

Pete

There is 1 Reply.

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™.