Message-ID: <104901bdfe38$8b8031e0$ea023ace@alpha> From: "Brian Bacon" To: Subject: Re: RSXNTDJ and Winsock Date: Thu, 22 Oct 1998 20:52:18 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Reply-To: djgpp AT delorie DOT com Well, a week or two back I posted that I had successfully ported Winsock2.2 to work. I got microsoft's distro of the winsock headers (including QOS.H and QOS.h, I have never used WinSock before, so I wrote s very simple test program to open a socket and close it, and check for errors, and it worked. You can get the Zip file from my webpage - http://trr.home.ml.org or straight http://trr.home.ml.org/ws22-rsx.zip I have Winsock2.2 on my computer so I don't worry about it not working, and you can check which version the end user has to make sure their DLL supports the features you are using. -Brian -----Original Message----- From: George Foot To: djgpp AT delorie DOT com Date: Thursday, October 22, 1998 11:47 AM Subject: RSXNTDJ and Winsock >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. > >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 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 ). > >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. > >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. > >Thanks in advance for any information. > >-- >george DOT foot AT merton DOT oxford DOT ac DOT uk > >xu do tavla fo la lojban -- http://xiron.pc.helsinki.fi/lojban/lojban.html >