Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!casbah.acns.nwu.edu!nucsrl!igloo!ddsw1!ddsw1!akcs.dgy
From: akcs.dgy@ddsw1.MCS.COM (Donald Yuniskis)
Newsgroups: comp.sys.next
Subject: getty eating all the CPU time.
Keywords: getty,terminal
Message-ID: <27ffc8b4-174e.1comp.next-1@ddsw1.MCS.COM>
Date: 8 Apr 91 02:00:04 GMT
References: <1193@nikhefh.nikhef.nl>
Lines: 12

Drive the modem control lines (DSR, DTR, etc.) to a solid level.
Problem is most probably the getty seeing a signal bouncing up
and down ("floating") and alternately seeing it as asserted -- time
to post a "login:" prompt -- and then released -- oops... he disconnected.
First make _sure_ these lines required by the system are actually being
driven _even when the Atari is ON!_.  You could have an input on the NeXT
connected to an input on the Atari.  Assuming this is OK, and you don't
want to leave the Atari on, try placing a resistive load between the signal
in question and GND (3K should be OK for the Atari to "overdrive" when it
has to).  You could also get nasty and disable the signal by tying it to
another signal available from the NeXT.  Sorry can't help any further -- I
don't own a NeXT to be able to dig much deeper.