Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs
Date: Thu, 29 Apr 2004 16:03:59 -0400 (EDT)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: Jim Gelasakis <gelasakis AT Pulse DOT com DOT au>
cc: cygwin AT cygwin DOT com
Subject: Re: System Beep using Cygwin
In-Reply-To: <007601c42db7$fcdd6790$830100c0@plsp002>
Message-ID: <Pine.GSO.4.56.0404291601130.6532@slinky.cs.nyu.edu>
References: <007601c42db7$fcdd6790$830100c0 AT plsp002>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Scanned-By: MIMEDefang 2.39

On Thu, 29 Apr 2004, Jim Gelasakis wrote:

> Hi there,
>
> Let me try this again as I think I have confused some.
>
> We have telnet sessions which we need to beep on some logic error.
>
> Previously, we have made them beep by simply outputing a ^G to make the
> bell sound.
>
> This now fails to make a sound under a Cygwin session.
>
> The following can reproduce the symptom.
>
> Telnet into a cygwin session, and run a unix script that contains the
> one line:
>
> echo "^G"
>
> We'd expect this to beep - a system bell not a wav file.
>
> We are working on a client (a device or a PC from which we telnet into
> the server which is running cygwin).
>
> It may be that the server beeps, thinking it is a console session, when
> in fact we have remote session.  Yet we are
> echoing the ^G out to the display device, the terminal, so would expect
> the terminal to beep.
>
> Perhaps significant is a third-party product is used here.  SL-Net
> allows us to telnet into our windows server, to login and
> run a cygwin shell, all done so that our software can run in an
> environment similar to how we use Unix, even though the server is
> Windows 2000.
>
> Kind Regards
> Jim Gelasakis

As I said before, the remote end doesn't actually do anything with '^G' --
it passes it to the *local* terminal (in this case, the telnet client).
Cygwin's telnet will simply pass it along to the window it's running in
(which will invoke the console handler for a console window).  Since you
mentioned that you're using a different telnet client, perhaps you should
take it up with the authors of that client.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

--
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/