Message-ID: <3630DC74.17365F76@clover.c2d.fedex.com>
Date: Fri, 23 Oct 1998 14:43:48 -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 9810231912220 DOT 15122-100000 AT sable DOT ox DOT ac DOT uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp AT delorie DOT com

George Foot wrote:
> 
> On Fri, 23 Oct 1998, Walter Moore wrote:
> 
[SNIP about needing to port from Unix to PC world]

> Note that the Winsock needs special initialisation before you
> can use it.  Other than that (and a few compatibility defines)
> your standard Berkeley sockets code should work reasonably well.

Well, the sample I had been working with had a
WSAStartup(0x0101, &wsaData)
I changed it to WSAStartup(MAKEWORD(1,1),&wsaData)
and it now connects to the server. but the write() to the
server dies a horrible death. I'm trying to figure it out now.
I can't figure out the debnt that comes with rsxntdj as it
seems to need a *SYM file, and my make is not creating one (and I
am definitely using '-g' as an option to gcc).

Anything else I need to be aware of?

> > > 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.
> 
> Oh, hmm.  I wonder whether it was actually talking about Winsock
> when it said `socket functions'.

hmm. good question. dunno. 
This is what I did to patch the MSSDK headers for use with RSXNTDJ:
get http://webhome.idirect.com/~eschunk/mssdk/rsxpatch.zip
unzip rsxpatch.zip (assume to \tmp)
get
http://mssjus.www.conxion.com/msdownload/platformsdk/i386/iBLDENV.Exe
run iBLDENV.Exe (assume to c:\MSSDK)
copy c:\MSSDK\include\*.* \rsxntdj\include\mssdk 
copy c:\tmp\patch.exe c:\djgpp\contrib\rsxntdj\include\mssdk
copy c:\tmp\sdkpatch.dif c:\djgpp\contrib\rsxntdj\include\mssdk
cd c:\djgpp\contrib\rsxntdj\include\mssdk
patch<sdkpatch.dif

If you are having difficulty linking, 
then there is a *dif file included in rsxpatch.zip that will 
patch the original specs file of rsxntdj.

> I'll be uploading my source code shortly, so you could take a
> look at that and try it out yourself.

I can't wait to see it! thanks. 

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