Message-ID:	<3630BD4D.E39265BF@clover.c2d.fedex.com>
Date:	Fri, 23 Oct 1998 12:30:53 -0500
From:	Walter Moore <walter AT clover DOT c2d DOT fedex DOT com>
Organization:	Federal Express
X-Sender:	"Walter Moore" <walter AT clover DOT c2d DOT fedex DOT com> (Unverified)
X-Mailer:	Mozilla 4.04 [en]C-FedExIntl (Win95; I)
MIME-Version:	1.0
To:	djgpp AT delorie DOT com
Subject:	Re: RSXNTDJ and Winsock
References:	<Pine DOT OSF DOT 4 DOT 05 DOT 9810222037160 DOT 17406-100000 AT sable DOT ox DOT ac DOT uk>
Reply-To:	djgpp AT delorie DOT com

George Foot wrote:
> 
> Hello
> 
> I recently ported a sockets application (the Libnet library, in
> fact) to RSXNTDJ, using the Winsock.  I have it working at the
> moment, but I had to make some changes to the supplied headers.
> If anybody else has used Winsock from RSXNTDJ successfully, I'd
> like to know whether they had to do what I have done, or whether
> there's an easier (read: cleaner) way.

I have not been able to get my application to write to a socket
successfully. Actually, it looks like the client just THINKS its
connecting, but the server never sees any such connection.
Nor am I using any of the select functions, though I probably 
should. But I did use the winsock.h from the MSSDK,
with the newest patch applied in the include/mssdk directory.

This client and server work on a unix machine, so I just need
to figure out how to make it all work in the PC world.


> Firstly, RSXNTDJ's supplied winsock.h file does not seem to work
> properly.  It doesn't define any of the `select'-related types
> and macros properly.  I tried also including <sys/select.h> to
> no avail -- that clashed with the winsock.h header.  To resolve
> all these problems, I copied another winsock.h file from a
> documentation pack I have about the Winsock.
> 
> It seems dangerous to me to pass to the DLL socket lists
> (fd_set) which are not what the DLL expects to receive.
> RSXNTDJ's headers seemed to be doing this (if I was in fact
> correct in including <sys/select.h>).
> 
> Secondly, I created the import library from wsock32.dll (which
> was in my Windows `system' directory), not winsock.dll (which my
> documentation pack was written for -- it's old documentation, I
> know).  Is this likely to cause any problems?  I don't need any
> of the fancy Winsock 2 features at the moment. 

I think wsock32.dll supplies the winsock 1.0 functions also,
so should not create problems there. 

> My last concern is that maybe Winsock 2 support is part of the
> MSSDK.  I have downloaded it, along with Doug Gale's patches,
> but have not yet installed it.  Since RSXNTDJ already had a
> winsock.h file I assumed it was meant to support Winsock
> programming without needing the MSSDK.  Please correct me if I'm
> wrong.

according to the Bugs and missing features of RSXNTDJ 1.31,
"* socket functions not implemented (alpha status), use WinSockets"

So I'd guess you'd have to use the mssdk include files at least.
That SHOULD clear up problems with winsock.h include file.

Of course, this is all hypothetical, as I do not yet have my
own application writing to a socket successfully. I may have to 
start smaller and work my way up. The client seems to think
its connecting, but the server is never actually being connected
to.
-- 
Walter Moore                Sr. Programmer Analyst
Federal Express             wbmoore AT fedex DOT com
2813 Business Park          Memphis TN 38118 USA
work: 901-369-2640          fax: 901-369-3634

- Raw text -