[comp.unix.microport] Couple of Questions

mludwig@lehi3b15.UUCP (Mitchell Ludwig ) (08/31/88)

Ok, I am a relatively new user of Microport's Unix, so please bear
with a few *VERY* childish questions regarding its use...

	1.  I am using the machine on a 386 with 2 meg of ram and
	    a 60 meg drive.  The machine has two com ports.  Herin
	    lies my first and second problem.
	    
	    The com 1 port has a hayes compatable modem up on it running
	    at 2400 baud.  I would like to use it for bi-directional
	    communications.  I used the ttyM00 in the inittab and that
	    sets my modem correctly.  All works fine until I attempt
	    to use kermit.  I set to /dev/ttyM00 and I get a protection
	    violation.  If I use root to change the protection I can call
	    out.  Unfortunately, after completing my communication, the
	    modem does not reset.  Any ideas as to what I am doing wrong?
	    
	2.  My com2 port is wired with a null modem to an AT&T 7300 running
	    UN*X.  How can I get bi-directional communications between the
	    two?  I tried using a uugetty and that allows me to communicate
	    with the 7300.  When the 7300 tries to talk to me, the first time
	    it works ok.  After that, however, my machine isn't killing off
	    the lockfile and the 7300 cannot communicate again.
	    
	3.  (My, don't these go on forever)  I own a 3com lan board and
	    want to use TCPIP with it.  The lan is wired via ethernet to
	    a machine with internet access.  How (if I can) can I get the
	    inittab to spawn me a getty for the 3com board?
	    
	
			I appreciate the help, any and all replies will
			be appreciated.  
			
		
Mitchel Ludwig					KMLFUDW@vax1.cc.lehigh.edu
309 East 4th Street				MFL1@Lehigh.bitnet
Bethlehem, PA 18015				mludwig! (wherever here is!)

plocher@uport.UUCP (John Plocher) (09/02/88)

In article <412@lehi3b15.UUCP> mludwig@lehi3b15.UUCP (Mitchell Ludwig ) writes:
>	    communications.  I used the ttyM00 in the inittab and that
>	    sets my modem correctly.  All works fine until I attempt
>	    to use kermit.  I set to /dev/ttyM00 and I get a protection
>	    violation.

You should use ttyM00 for gettys and tty00 (no 'M') for kermit and uucp.

>	2.  My com2 port is wired with a null modem to an AT&T 7300 running
>	    UN*X.  How can I get bi-directional communications between the
>	    two?

Use ttyM01 for the getty and make sure that DTR from the 386 is wired to
CD on the 7300, and that DTR from the 7300 is wired to CD on the 386.
Use tty01 for kermit and uucp (set line /dev/tty00 -or- tty00 in your
Devices file for uucp)

Do not use uugetty, it is not needed if you use the ttyMxx/ttyxx scheme.

>	3.  (My, don't these go on forever)  I own a 3com lan board and
>	    want to use TCPIP with it.

You could port the KA9Q TCP code... :-)
(Microport does not currently have drivers for the 3com board)

     -John Plocher

nelson@sun.soe.clarkson.edu (Russ Nelson) (09/02/88)

In article <452@uport.UUCP> plocher@uport.UUCP (John Plocher) writes:

   In article <412@lehi3b15.UUCP> mludwig@lehi3b15.UUCP (Mitchell Ludwig ) writes:
   >	3.  (My, don't these go on forever)  I own a 3com lan board and
   >	    want to use TCPIP with it.

   You could port the KA9Q TCP code... :-)
   (Microport does not currently have drivers for the 3com board)

Well, my boss has charged me with porting KA9Q to Microport V/286 using
the 3c501 (ack) and the NI5210 (!!).  When this get done, of course,
depends upon the number of twits who call me up with questions of the
form "Now where is that power switch again?  I used to know where it
was, but they must have moved it on me ...."
--
--russ (nelson@clutx [.bitnet | .clarkson.edu])
Shuzan held out his short staff and said, "If you call this a short staff,
you oppose its reality.  If you do not call it a short staff, you ignore the
facts.  Now, what do you wish to call it?"