From: Petr Andrs <xtonda-konf@quick.cz>
To: cygwin@cygwin.com
Subject: Re: Trouble running agetty
Date: Wed, 30 Apr 2003 03:24:00 -0000 [thread overview]
Message-ID: <3EAEE766.5020201@quick.cz> (raw)
In-Reply-To: <00d601c30e91$53f29740$4bf886d9@ellixia>
Of course I did prior bothering people here, but I haven't found answer
there.
pa
On 4/29/2003 10:52 PM, Elfyn McBratney wrote :
>>Really nobody knows how to connect serial terminal into cygwin?
>
>
> Personally, no. Perhaps you might find help in the archives
> (<http://cygwin.com/ml/cygwin/>) or the documentation (in /usr/doc and
> /usr/doc/Cygwin).
>
>
>>>Hi all,
>>>
>>>I want to use old PC with DOS as a terminal connected via serial null
>>>modem cable to Win2K machine with cygwin. But when I launch agetty in
>>>Cygwin and terminal emulator on DOS box I don't see anything in the
>>>terminal and agetty quits after short while being completely silent. I
>>>don't know what to do since there is no indication of problem, just
>>>nothing happens.
>>>
>>>I tried following agetty configurations.
>>>
>>>/sbin/agetty /dev/ttyS0 9600
>>>/sbin/agetty /dev/ttyS0 9600
>>>/sbin/agetty -L /dev/ttyS0 9600
>>>/sbin/agetty -L -T vt100 /dev/ttyS0 9600
>>>/sbin/agetty -L -T vt100 -8 -1 -N /dev/ttyS0 9600
>>>
>>>COM1 port in both WIN and DOS box is set to 8N1 9600, when running
>>>terminal emulators on both ends (Hyperterminal on Win and comit on DOS)
>>>letters go through, so wiring is OK.
>
> [...snippage...]
>
> Elfyn
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2003-04-29 20:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-28 8:32 Petr Andrs
2003-04-30 2:58 ` Petr Andrs
2003-04-30 3:15 ` Elfyn McBratney
2003-04-30 3:24 ` Petr Andrs [this message]
2003-04-30 3:18 ` sos
2003-04-30 3:25 ` Petr Andrs
2003-04-30 3:46 ` sos
2003-04-30 4:29 ` Petr Andrs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3EAEE766.5020201@quick.cz \
--to=xtonda-konf@quick.cz \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).