Re: //c and Linux

[Christopher Dalton <cd27+@andrew.cmu.edu>]

In message <2lg72g$2fa@usenet.INS.CWRU.Edu>, 
 nhill@b61649.student.cwru.edu (Nathan A. Hill) writes:
>	I want to connect my //c to my Linux box through a null modem, has
>anyone done this yet?  any advice?

I just recently did this.  I'm using an imagewriter I cable with a gender
changer (just what I had lying around).  The normal thing would be to use
a //c modem cable and a null modem adapter.  Or just build your own.  
2<-->3, 3<-->2, 7<-->7 and it should work.

I just followed the serial-howto to set getty up.  Said howto tells you 
to replace the standard getty with some other one ... I didn't bother.
On the apple side I use kermit-65.  My kermit init file sets the term to
vt100 and then goes on line.  I'm running at 9600 but I understand some
people are doing better with newer versions of the //c.

I use the //c in one of two ways.  Sometimes I log on from it in the usual
way and dial or telnet out (kermit or slip) to some other machine.  It's nice
to be able to download directly to the //c even though I don't have a modem
attached to it.  

The other thing I do is use it as an extra display while I'm in X.  I start
up a tiny xterm ('unreadable' font ... about 1" square) and echo everything
to the serial port device.  That way when I put the mouse pointer in the 
small window I can type onto the //c screen with the linux keyboard.  The
command is 
	xterm -vb -l -lf /dev/ttyS1 -fn nil2 -geometry 80x24+0+0 &

Email me if you have any questions.

>	First I gotta get my //c fixed.  It's 80-column chip is burnt out and
>when I turn it on, it just starts running random characters across the screen,
>totally ignoring everything else, like the disk drive.  Does anyone know what
>exactly is wrong with it?

I dunno.

--Chris
dalton+@cmu.edu
I don't have a sig.  But if I did have one it would say something about how
ms-dos and mac are evil, and people should use unix, amiga and apple ][.