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
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Mon, 17 Dec 2001 10:34:24 +0100
From:	Corinna Vinschen <cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Re Re: Re: UNIX Sockets - Broadcast address
Message-ID:	<20011217103424.B25400@cygbert.vinschen.de>
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<F871TlbRRu6arJfkprZ000060a4 AT hotmail DOT com>
Mime-Version:	1.0
User-Agent:	Mutt/1.2.5i
In-Reply-To:	<F871TlbRRu6arJfkprZ000060a4@hotmail.com>; from passhark@hotmail.com on Mon, Dec 17, 2001 at 03:37:13AM +0000

On Mon, Dec 17, 2001 at 03:37:13AM +0000, Kay M wrote:
> So what the bottom line, no broadcasting ?.
> 
> Question: Has any one ever written a program on cygwin that uses A broadcast 
> address ?. A client program to be more specific.

What about actually debugging the problem?  Or did you try using
WinSock functions directly instead of the Cygwin wrapper functions
just for debugging purposes?  Anything which tracks down the cause?

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -