jantypas@hope.UUCP (John Antypas) (01/06/87)
Does anyone in netland know how to convince Microport Unix V.1.3.6
to dial a courier 2400 modem for cu and uucp access? The manuals say
1.4 will support the public domain dial, but since they're shipping
1.3.6 this isn't much help. I can't believe they'd release a Unix with
a UUCP which only works for direct connections. How have other people
done this. The courier2400 is on COM1: (Dos:)
John Antypas
uucp: ...!{sdcsvax,ucbvax!ucdavis,ucivax}!ucrmath!hope!jantypas
arpa: ucrmath!hope!jantypas@sdcsvax.ucsd.edu
ucdavis!ucrmath!hope!jantypas@{lll-crg.ARPA, ucbvax.berkeley.edu}eric@cti.UUCP (Eric Black) (01/09/87)
In article <1040@hope.UUCP> jantypas@hope.UUCP (John Antypas) writes: >Does anyone in netland know how to convince Microport Unix V.1.3.6 >to dial a courier 2400 modem for cu and uucp access? The manuals say >1.4 will support the public domain dial, but since they're shipping >1.3.6 this isn't much help. I can't believe they'd release a Unix with >a UUCP which only works for direct connections. How have other people >done this. Just put the modem dialing commands in the send/expect sequence in the L.sys entry. I'm running 1.36 and it works fine with a USR 2400. It works for dialout on an Avatex 1200 (cheap!), but not for dialin because there is no way to disable the status messages coming in from the modem (which confuses getty and login!). It's nice but not necessary to have UUCP know how to talk to a particular modem, and have the phone number(s) in a separate file. -- Eric Black "Garbage In, Gospel Out" UUCP: {sun,pyramid,hplabs,amdcad}!cti!eric
james@bigtex.uucp (James Van Artsdalen) (01/10/87)
IN article <1040@hope.UUCP>, jantypas@hope.UUCP (John Antypas) wrote: > Does anyone in netland know how to convince Microport Unix V.1.3.6 > to dial a courier 2400 modem for cu and uucp access? The manuals say > 1.4 will support the public domain dial, but since they're shipping > 1.3.6 this isn't much help. I can't believe they'd release a Unix with > a UUCP which only works for direct connections. How have other people > done this. The courier2400 is on COM1: (Dos:) There is a bug in 1.3.6 apparently. You need to call Microport and ask for the fix disk. It's a toll-free call: 1-800-PC2-UNIX. They've been fairly responsive to me thus far and calling them can actually get problems solved. bigtex is using a Courier 2400 and moves ~1.5meg of data between 4 to 5 sites per day using the Courier for both dial-outs and logins. -- James R. Van Artsdalen ...!ut-sally!utastro!bigtex!james "Live Free or Die" Voice: (512)-323-2675 Modem: (512)-323-2773 5300B McCandless, Austin TX 78756
sewilco@mecc.MECC.COM (Scot E. Wilcoxon) (01/12/87)
In article <529@cti.cti.UUCP> eric@cti.UUCP (Eric Black) writes: >Just put the modem dialing commands in the send/expect sequence in the >L.sys entry. I'm running 1.36 and it works fine with a USR 2400. >It works for dialout on an Avatex 1200 (cheap!), but not for dialin >because there is no way to disable the status messages coming in from >the modem (which confuses getty and login!). I've been keeping two binary-only sites working for a while, and others might be interested in some general tricks. Incidentally, our two Xenix machines died January 1st, and SCO's help was late and futile. Fortunately the replacement machine was being installed, so only two weeks of work was lost. Hack 1: Replace getty. It simply requires caution and a backup copy of the original getty. In this case you make a getty which ignores the modem status messages (or tells it to shut up). Also, you can have different gettys running on different ports or have getty behave differently on different ports. Want source? Site 'omen' had one several months ago, when I had to replace the one for SCO Xenix. Actually, I had already replaced getty but omen's had a few more features. (I forget omen's phone number; look in the signature of articles `fgrep "@omen" ~news/history`) Hack 2: Create logins which match the modem status messages. With no passwords and shells which do nothing, or which tell the modem to shut up, they might keep the link a little cleaner. Hack 3: Put in getty's login message a modem command which tell the modem to shut up. The reverse may be necessary in L.sys. This can be varied for different tty ports by making new 'gettydefs' entries. Hack 4: Change uucico's name and replace it with a front-end which knows how to change modem settings for uucico, and how to change them back for getty. (A front-end like this can also be used to dial out on an incoming port) -- Scot E. Wilcoxon Minn Ed Comp Corp {quest,dayton,meccts}!mecc!sewilco (612)481-3507 sewilco@MECC.COM ihnp4!meccts!mecc!sewilco National Enquirer seers: 4 Reality: 360
james@bigtex.UUCP (01/16/87)
IN article <529@cti.cti.UUCP>, eric@cti.UUCP (Eric Black) wrote: > [...] I'm running 1.36 and it works fine with a USR 2400. > It works for dialout on an Avatex 1200 (cheap!), but not for dialin > because there is no way to disable the status messages coming in from > the modem (which confuses getty and login!). The problem with the Avatex 1200 is probably *not* "disabling the status messages" (these need to be enabled for outgoing calls anyway), but instead the timing of when the Avatex prints the status message and enables carrier detect after answering the phone. My Courier, which also works great as a bidirectional modem, appears to print the "CONNECT" message and then enable the carrier detect signal. The Avatex may do this the other way around. The U.S. Robotics Password 1200 seems to do something else yet: when I tried to use it as an answer-only modem on a 3b2, I got garbage on the "login: " line. This happened with several other Passwords, so I assume it's something about the Password. Maybe the Password is re-enabling the carrier detect signal while printing the CONNECT message. In any case I doubt the status messages themselves are the problem, but instead the timing the modem uses when a connection is made. -- James R. Van Artsdalen ...!ut-sally!utastro!bigtex!james "Live Free or Die" (512)-328-0282