home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!noc.near.net!hri.com!spool.mu.edu!umn.edu!news.cs.indiana.edu!babbage.ece.uc.edu!ucunix.san.uc.edu!kreinddm
- From: kreinddm@ucunix.san.uc.edu (David M Kreindler)
- Newsgroups: comp.os.os2.apps
- Subject: Re: CKermit - help! (Connects, but nothing more.)
- Message-ID: <Bz7wIp.LsL@ucunix.san.uc.edu>
- Date: 13 Dec 92 21:47:13 GMT
- References: <harriga.921212121303@lab1.duc.auburn.edu> <1992Dec12.202337.16896@ousrvr.oulu.fi> <harriga.921212210854@lab1.duc.auburn.edu>
- Sender: D. Kreindler
- Organization: University of Cincinnati
- Lines: 21
-
- In article <harriga.921212210854@lab1.duc.auburn.edu> harriga@duc.auburn.edu (Greg A. Harris) writes:
- >
- >This is exactly what happens when I do a logon. Now that you have the
- >"Call complete", you should do the "connect" command c (I do this with
- >a script). Your experience is ckermit working as advertised (at least as
- >far as I understand ckermit).
-
- I've got a slightly different problem. Kermit (V188) works fine up until
- I issue a 'C' (connect) command: it switches to terminal mode, but then
- accepts only a couple of 'ENTER''s before switching back to command-line
- mode and issuing a, "Cannot transmit to serial port." message. Does
- anyone have any idea what the problem is? (NB: I'm using exactly the
- same hardware for Kermit that's permitting me to type this; Kermit
- *does* dial, and establishes a connection. It just doesn't seems to let
- me proceed further. Further 'c' commands cause the same thing to
- re-occur. Help.)
-
- --
- kreinddm@ucunix.san.uc.edu -------------------------------------------------
-
- "Sometimes you're the windshield / Sometimes you're the bug...." - Dire Straits
-