[comp.sys.apollo] 4500, 10.3, BSD, 2400 modem?

daniel@world.std.com (Daniel Smith - you know, that West Coast one...) (03/08/91)

	This is my second request for help in trying to get a modem
going on a 4500 running 10.3.  I'm not seeing clear documentation (at least
not from the BSD System manual...) on what device I'm supposed to use,
/dev/sio* or /dev/tty0*.  I don't see a makedev entry for cua0, is it
supposed to be a symlink to another dev entry?  Would someone please send
me a sample /etc/remote that works for a hayes compatible modem?  I'd
really appreciate it.  thanks,


				Daniel

-- 
daniel@island.com  .....Daniel Smith, Island Graphics, (415) 491 0765 x 250(w)
daniel@world.std.com ...4000 CivicCenterDrive SanRafael MarinCounty CA 94903
dansmith@well.sf.ca.us .I must write this, or Island will take away my coffee.
Could we continue with the petty bickering? I find it most intriguing-Data:TNG

hdtodd@eagle.wesleyan.edu (03/08/91)

In article <1991Mar8.073658.12083@world.std.com>, daniel@world.std.com (Daniel Smith - you know, that West Coast one...) writes:
> 
> 	This is my second request for help in trying to get a modem
> going on a 4500 running 10.3.  I'm not seeing clear documentation (at least
		...

	This may be a related question.  I would like to purchase an 
inexpensive PC modem and install it in my 3500 backplane to access the system
from home.  
	a.  Is it possible to do this (is there some known reason it 
	    won't work) and if someone has done it could I get some hints
	b.  If it isn't known to not be feasible, is there a standard
	    device driver for that modem that I would activate (and how)?

Thanks for any advice.

						David Todd

goldfish@CONCOUR.CS.CONCORDIA.CA (03/09/91)

After spending two years and logging at least twenty calls to the
hotline number over serial port use, I can say with complete
conviction:

            **************************************
            *   APOLLO SERIAL PORTS DON'T WORK   *
            **************************************

Experience says they don't work   . . .   Apollo says they don't work
   . . .   yourMODEM will tell you they don't work.

Some of the things that don't work:

	1)  handshaking:  the DSR-DTR interaction is broken.  HP knows
	    it is broken, Apollo knew it was broken before the merger.

	1a) The computer will drop the DTR occasionally and hang up
	    your MODEM.

	1b) Upon hanging up the MODEM, it will not terminate the
	    session so the next caller gets your session already
	    logged in.  (caution boys and girls, don't try this
	    without parental supervision) (and to think all the work
	    HP did to ship an insecure system when all you needed was
	    a MODEM and POOF, you're as safe as a long-tailed cat in a
	    rocking chair factory :-()

	2)  BAUD switching: The word I got from HP (semi-official) was
	    that BAUD switching was not supported in the Domain-OS.
	    (the fact that the termcap entries to do BAUD switching
	    are unchanged from the Berkeley release not-withstanding;
	    that the documentation says nothing about this and the
	    hotline folk think it is supposed to.)

	3)  The SIO and TTY drivers do NOT maintain consistent
	    internal structures.  (can you say "probably written in
	    unstructured COBOL" everyone?) 

The Apollo serial ports will:

	1)  drive a printer

	2)  handle a local terminal

	3)  talk to a single speed MODEM if you are careful

Remember the logic:  one man -- one machine ... (Apollo had hoped to
sell you that machine,) Better spend your money on a terminal server;
at least TELNET works. Or even better still: remember how well HP
supports their products and tell your friends ...

Have a nice Day ... :-)

--	  Paul Goldsmith
<goldfish@concour.cs.concordia.ca>				 (514) 848-3031
	(Shirley Maclaine told me there would be LIFETIMES like this)

Ps: It's Friday, I am taking a week's leave and I'll probably be a lot
nicer in nine days.

rees@pisa.citi.umich.edu (Jim Rees) (03/09/91)

In article <9103081115.aa05182@concour.cs.concordia.ca>, goldfish@CONCOUR.CS.CONCORDIA.CA writes:

              **************************************
              *   APOLLO SERIAL PORTS DON'T WORK   *
              **************************************

It's almost as if someone started a complete overhaul, then took a vacation
in France or something.

  Better spend your money on a terminal server;
  at least TELNET works.

What?  Did someone finally fix ptys?

Actually, I've never had any trouble with the serial port on my Apollo.
Maybe that's because I don't use it.  RS232 is for people who can't afford
real communications.

nazgul@alphalpha.com (Kee Hinckley) (03/09/91)

In article <9103081115.aa05182@concour.cs.concordia.ca> goldfish@CONCOUR.CS.CONCORDIA.CA writes:
>            *   APOLLO SERIAL PORTS DON'T WORK   *
If anyone cares, it's because the person doing the SR10 work for them
left in the middle and noone ever finished it.  Did you care?  I thought not.

>	1)  handshaking:  the DSR-DTR interaction is broken.  HP knows
>	    it is broken, Apollo knew it was broken before the merger.
For what it's worth, I think CTS works but RTS doesn't, or some such.

>	1a) The computer will drop the DTR occasionally and hang up
>	    your MODEM.
Ah.  That explains a lot.

>	1b) Upon hanging up the MODEM, it will not terminate the
>	    session so the next caller gets your session already
>	    logged in.  (caution boys and girls, don't try this
See my source below.

>	2)  BAUD switching: The word I got from HP (semi-official) was
>	    that BAUD switching was not supported in the Domain-OS.
Ditto.

>	3)  The SIO and TTY drivers do NOT maintain consistent
>	    internal structures.  (can you say "probably written in
>	    unstructured COBOL" everyone?) 
No, that's almost certainly due to having it dropped in the middle.

>	3)  talk to a single speed MODEM if you are careful
We drive a Telebit T2500 succesfully, although we do so by having
the following entry in /etc/ttys:

tty02   "/etc/fakegetty std.9600"       dialin

It all seems to work pretty well, although of course none of it
should be necessary.  Apollo proper does actually have dialin
lines, and they were constantly screwing up until they got a
terminal concentrator - but they aren't heavily used, so things
never got fixed.  Terminals are obsolete, you see...

Here's fakegetty.c:


#include <sys/file.h>
#include <sgtty.h>

main(argc,argv)
int argc;
char **argv;
{
	int fd;
	char dpn[100];
	struct sgttyb sgbuf;

	strcpy(dpn, "/dev/");
	strcat(dpn, argv[2]);

	fd = open(dpn, O_RDWR|O_NDELAY);
	if (fd < 0) {
		perror("dpn");
		exit(1);
	}

	if (ioctl(fd, TIOCGETP, &sgbuf) < 0) {
		perror("getp");
		exit(1);
	}
	
	sgbuf.sg_flags &= ~ECHO;
	sgbuf.sg_ispeed = B2400;
	sgbuf.sg_ospeed = B2400;

	if (ioctl(fd, TIOCSETN, &sgbuf) < 0) {
		perror("setn");
		exit(1);
	}

	sleep(2);
	write(fd, "+++", 3);
	sleep(2);
	write(fd, "ATZ\r", 4);
	sleep(2);
	if (ioctl(fd, TIOCNOTTY, 0) < 0) {
		perror("notty");
		exit(1);
	}
	close(fd);

	execv("/etc/uugetty", argv);
}

-- 
Alfalfa Software, Inc.          |       Poste:  The EMail for Unix
nazgul@alfalfa.com              |       Send Anything... Anywhere
617/646-7703 (voice/fax)        |       info@alfalfa.com

I'm not sure which upsets me more: that people are so unwilling to accept
responsibility for their own actions, or that they are so eager to regulate
everyone else's.