Article View: comp.sys.atari.st
Article #37189Re: MX2 and DC-Port
From: Michael B. Vederman
Date: Fri, 17 Mar 1989 15:01
Date: Fri, 17 Mar 1989 15:01
58 lines
3006 bytes
3006 bytes
In article <8903161551.AA25783@ucbvax.Berkeley.EDU> MCCABE@MTUS5.BITNET writes:
>Date: 16 March 89, 10:46:54 EST
>From: Jim McCabe MCCABE at MTUS5
>To: INFO-ATARI16 at SCORE.STANFORD.EDU
>Subject: MX2 and DC-Port
>
>Wowzers -- I just read the docs for MX2 and I'm extremely
>impressed!! Fred sure added a lot since his earlier versions.
>
>Anyway, one of the niftiest features is MX2's ability to
>use custom device drivers for each process. Fortunately,
>there are four extra device drivers that are available --
>isn't that the number of extra serial ports available on
>DC-Port?
>
>My question is this: Are any device drivers available
>for DC-Port under MX2? Will DC-Port even work with MX2?
>
>Finally, I've got one more question that doesn't relate
>to MX2 necessarily. How easy is it to poll the carrier
>on each port? Also, how easy is it to control the DTR lines?
>
>Thanks in advance!
>
> Jim McCabe
> MCCABE @ MTUS5.BITNET
Jim,
DC-PORT offers 2 extra lines, for a total of three serial ports.
We have a prototype of the 5 port version (four additional ports) which
we just sent to MichTron so Tim Purves can adapt the BBS for 5 lines.
That prototype will then go to ATARI so they can get ATARI BASE up and running
with MichTron 3.0 and DC-PORT.
Anyway, the real question concerns DC-PORTs functionality.
1) Device drivers - we include a disk which has an AUTO folder program that
wedges itself in the TRAP vector to intercept Bconin, Cconin, Cauxstat, etc.
calls and redirect them to DC-PORT if the proper device handle is specified.
2) How easy is it to poll carrier? Very easy. That interrupt is monitored
just as DTR is. In fact MichTron BBS uses both of these. Sample code is
provided on the disk which comes with DC-PORT, so you (or anyone) will know
exactly how you can perform these functions.
We do not have plans to release the source to our driver, but are always
glad to work with someone who wants to add support to their software, and
may find the driver not acceptable.
Thanks for your interest!
- mike
--
for (;;) : Use ATARINET, send an interactive
do_it(c_programmers); : message such as:
: Tell UH-INFO at UHUPVM1 ATARINET HELP
University Atari Computer Enthusiasts : University of Houston UACE
Technical Details
Message-ID:
<726@uhnix2.uh.edu>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cwjcc!hal!nic.MR.NET!umn-d-ub!rutgers!bellcore!texbell!uhnix1!uhnix2!uace0References:
<8903161551.AA25783@ucbvax.Berkeley.EDU>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cwjcc!hal!nic.MR.NET!umn-d-ub!rutgers!bellcore!texbell!uhnix1!uhnix2!uace0 From: uace0@uhnix2.uh.edu (Michael B. Vederman) Newsgroups: comp.sys.atari.st Subject: Re: MX2 and DC-Port Message-ID: <726@uhnix2.uh.edu> Date: 17 Mar 89 15:01:02 GMT References: <8903161551.AA25783@ucbvax.Berkeley.EDU> Reply-To: uace0@uhnix2.UUCP Organization: University of Houston Lines: 58