Path: utzoo!attcan!uunet!ncrlnk!ncr-sd!crash!pnet01!fgbrooks
From: fgbrooks@pnet01.cts.com (Fred Brooks)
Newsgroups: comp.sys.atari.st
Subject: Re: MX2 and DC-Port
Message-ID: <3917@crash.cts.com>
Date: 18 Mar 89 01:16:11 GMT
Sender: news@crash.cts.com
Organization: People-Net [pnet01], El Cajon CA
Lines: 37

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


I don't know if MX2 will work with that rs232 port device. I haven't really
checked out the device driver functions. it should word tho. I am working on a
version that uses threads and process, but is still don't have my ST yet
I'm still waiting for the NAVY to ship it from Subic Bay phillipines where I
was working for the last 6 1/2 months.

UUCP: {nosc ucsd hplabs!hp-sdd}!crash!pnet01!fgbrooks
ARPA: crash!pnet01!fgbrooks@nosc.mil
INET: fgbrooks@pnet01.cts.com