home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.os2.apps
- Path: sparky!uunet!cs.utexas.edu!uwm.edu!linac!mp.cs.niu.edu!rickert
- From: rickert@mp.cs.niu.edu (Neil Rickert)
- Subject: Re: CKermit - help!
- Message-ID: <1992Dec13.051302.21757@mp.cs.niu.edu>
- Organization: Northern Illinois University
- References: <1992Dec12.202337.16896@ousrvr.oulu.fi> <harriga.921212210854@lab1.duc.auburn.edu> <harriga.921212220925@lab1.duc.auburn.edu>
- Date: Sun, 13 Dec 1992 05:13:02 GMT
- Lines: 28
-
- In article <harriga.921212220925@lab1.duc.auburn.edu> harriga@duc.auburn.edu (Greg A. Harris) writes:
- >
- >In looking over this again, it appears that your carrier detect must not
- >be correct. I do not think you should be able to "connect" until there
- >is a carrier (I can't). Do you have your modem set to always show the
- >carrier on (this can be done with the &C0 command in hayes, or with a
- >dip switch on some modems)? My carrier detect follows the carrier signal.
-
- Those comments are somewhat confused, or at least confusing.
-
- Here is the situation:
-
- If the modem is properly set up, then there is no carrier line before
- the connections is established. In this case, you should use
-
- dial number
- connect
-
- If the modem is configured to always supply carrier detect, then you
- can just connect and manually dial yourself.
-
- If the modem never supplies the carrier detect line, then use
-
- set carrier off
-
- This will allow you to connect regardless of the status of the carrier
- detect line.
-
-