From: elliottm@csulb.edu (Mike Elliott)
Subject: Trying to get dial in on COM2
Organization: Cal State Long Beach
Date: Fri, 1 Jan 1993 00:18:52 GMT

I continue to be astounded at the difficulty in using modems with SCO
version 3.2.2.  Having a 2400 baud Hayes compatible modem on COM2 seems
like the most common possible setup.  However, the ODT manuals only give
hints as to minimum requirements -- they don't just state what has to be in
existence.  However, since others have undoubtedly solved this problem, I
appeal to the informed to endow me with the mystical arcania required to
complete the job.  I have done the following:

1) As per page 216 in Administering ODT-NET:
   Changed owner and group of /dev/tty2a and /dev/tty2A to uucp.  
   ls -l now shows:

      crw-r-----   1 uucp     uucp       5,136 Dec 28 12:41 /dev/tty2A
      crw-r-----   1 uucp     uucp       5,  8 Dec 28 12:40 /dev/tty2a

2) As per page 216 in Administering ODT-NET:
   Modified the last two lines in /etc/inittab to read:

      t2a:2:off:/usr/lib/uucp/uugetty -t60 tty2a 2
      t2A:2:off:/usr/lib/uucp/uugetty -t60 tty2A 3

3) As per page 217 in Administering ODT-NET:
   Modified /usr/lib/uucp/Devices to read

      # Standard modem line also used for dialin
      Direct tty2a - 1200-2400 direct
      ACU tty2A - 1200-2400 /usr/lib/uucp/dialHA24

4) As suggested by a knowledgeable user:
   Modified the setuid of kermit to allow arbitrary users to dial out:

      chmod u+s /usr/local/bin/kermit

   I was able to confirm at that point that users could use kermit to dial
   out.

6) As per step 15, page 221 in Administering ODT-NET:
       
       enable tty2A

    which responded:
         enable: tty2A not enabled : already enabled

7) Attempted to dial in from another computer.  The modem did not answer.

8) I verified that the electrical connections were correct, by rebooting the
   computer to MS-DOS and running Procomm+ in host mode.  Procomm+ was able
   to make the modem answer without any intervention, and upon answering, 
   Procomm+ displayed its login prompt.

9) Rebooted to Unix, and used cu to set the Procomm modem initialization
   string in two steps:

      cu -ltty2a dir
      ATE1V1X4Q0&C1&D2 S7=255 S0=0

      cu -ltty2a dir
      ATS0=1
   
10) Redialed from another computer.  The modem answered, eventually lighting
    the MR TR -- -- OH CD AA HS lights.  No prompt was displayed.  When the 
    remote computer sent a character, the RD light flashed.  The SD light
    never displayed any activity.

11) As per page 98, TIPS section of the User's Guide, under the heading
   
       Modem Answers, But No Login Prompt

       . . . use the AT&C1 command

   which was interpreted to mean

      cu -ltty2a
      AT&C1

   This caused the TR light to go off briefly, then return.  The modem 
   still answered, and no login prompt appeared.  No change in behavior.

12) Continuing from page 98, 

      enable /dev/tty2A

    responded with 
      
      enable: tty2A not enabled : already enabled

13) The manual then suggests veriifying that the modem is using the
    correct /etc/gettydefs entry and is selecting the proper baud rate.  It
    suggests that the modem port device line in /etc/inittab should look like
   
      t2A:2:off:/usr/lib/uucp/uugetty -t60 tty2A 3

    which is what it was set to in step (2).  However, the line now reads:

      t2A:2:respawn:/usr/lib/uucp/uugetty -t60 tty2A 3

    which I assume is a harmless difference (since Unix made the change).

14) Finally, the last bit of advice is to verify that entry 3 in 
    /etc/gettydefs is the 2400 baud entry.  The _fourth_ entry is the
    2400 baud entry (after 19200 9600 and 4800) which looks like

2400# B2400 OPOST ONLCR TAB3 BRKINT IGNPAR IXON IXANY PARENB ISTRIP\
      ECHO ECHOE ECHOK ICANON ISIG CS7 CREAD # B2400 OPOST ONLCR\
      TAB3 BRKINT IGNPAR IXON IXANY PARENB ISTRIP ECHO ECHOE ECHOK\
      ICANON ISIG CS7 CREAD #login: #1200

So, at this point, I ran out of manuals to look in.  However, this is such
a common situation that lots of folks must have solved it, so ... could 
some kind soul give me a clue as to what to do next?

Thanks,
Mike Elliott
elliottm@csulb.edu







-- 


                                           Mike Elliott
                                           elliottm@beach.csulb.edu
Xref: sparky biz.sco.general:4866 comp.unix.xenix.sco:3554