Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-ID:	<39FA05F6.8FB14008@redhat.com>
Date:	Sat, 28 Oct 2000 00:47:18 +0200
From:	Corinna Vinschen <vinschen AT redhat DOT com>
Reply-To:	cygwin AT sources DOT redhat DOT com
X-Mailer:	Mozilla 4.75 [en] (X11; U; Linux 2.2.14-SMP i686)
X-Accept-Language:	de, en
MIME-Version:	1.0
To:	cygwin <cygwin AT sources DOT redhat DOT com>
Subject:	Re: Bug report: with CVS
References:	<20001023142004 DOT 17298 DOT qmail AT web122 DOT yahoomail DOT com> <39F454C8 DOT 14003F89 AT techspan DOT com> <39F71352 DOT 5847F251 AT ece DOT gatech DOT edu> <39F75794 DOT 5185485D AT techspan DOT com> <39F8595A DOT B37B03F4 AT ece DOT gatech DOT edu> <39F9F802 DOT 5C5CAF14 AT techspan DOT com> <39F9FC54 DOT 23A6F989 AT ece DOT gatech DOT edu>

"Charles S. Wilson" wrote:
> Mark Swanson wrote:
> > > cvs update -d
> > DuplicateHandle failed Win32 error 6 268015 [main] cvs 835187
> > fhandler_base::fork_fixup: /dev/tcp - Win32 error 6, handle io_handle<0x2784>
> 
> Corinna, does this error message indicate that a program is tripping
> over the WinSock problems you addressed Thursday?  If so, then would you
> expect to still see this error message using the new cygwin1.dll -- from
> calling the "bad" functions before switching over to the WinSock2
> versions?  I'm a little confused...

The above error message is a hint that the system doesn't use
the Winsock2 method but the old one. fork_fixup wouldn't be called
otherwise. I didn't read that thread so I just took a look back and
Mark (Hi, Mark!) has a Win95 system. Win95 doesn't have Winsock2
by default.

Mark's system seems to be one of the strange behaving 9x systems
which aren't able to deal correctly with duplicated sockets.

FYI: I'm desperately trying to get some info about that problem
in a Microsoft networking newsgroup. I got a hint that 9x systems
might not treat sockets as normal handles dependent of the installed
underlying drivers but nothing really convincing... rather gossip.

Mark, you should try to download Winsock2 for Win95 as I mentioned
in my related mail "descriptor is a file, not a socket" which I sent
yesterday:

http://www.microsoft.com/windows95/downloads/contents/wuadmintools/s_wunetworkingtools/w95sockets2/default.asp


Hope, that helps,
Corinna

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

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -