Newsgroups: comp.os.msdos.djgpp
Subject: Re: RSXNTDJ and export libs...
From: frenchc AT cadvision DOT com (Calvin French)
References: <34befb68 DOT 0 AT news DOT cadvision DOT com> <69np1a$g3m$3 AT news DOT ox DOT ac DOT uk>
MIME-Version: 1.0
Content-Type: Text/Plain; charset=US-ASCII
NNTP-Posting-Host: ts6ip220.cadvision.com
Message-ID: <34c12724.0@news.cadvision.com>
Date: 17 Jan 98 21:48:20 GMT
Organization: CADVision Development Corporation (http://www.cadvision.com/)
Lines: 65
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

In article <69np1a$g3m$3 AT news DOT ox DOT ac DOT uk>, mert0407 AT sable DOT ox DOT ac DOT uk says...

>Stability isn't really a problem with some Winsock libraries I've
>seen; I've never had any trouble with my own (but that's probably
>because I know exactly how to use it and what it can and cannot do).
>Dan's library in version 0.93b seemed quite stable to me, but I didn't
>use it much (C++ isn't my forte).  I haven't looked at Indrek's yet,
>but he's implemented more functions than I have.

Well, Dan's lib just hasn't done it for me, I don't know why. I can get 
chat1/2 working just fine, but if I try something like:

SocketInit();
Socket* s = new Socket(...etc...);

it will hang right then and there.

>Last I heard, some people are trying to figure out how the VxD for
>Winsock 2.0 works.  This was a few months ago now though...

Yes, I suppose it's always a possibility that somebody (else :) will figure 
this out in time...

>Another option I think they were trying was to use a third party VxD
>which as far as I understand allows a DOS application to call pretty
>much any DLL function (by making it the VxD that calls the function,
>not the DOS app).

That's an interesting idea as well. Sort of a Win<->Dos layer.

>Alfons Hoogervorst and others have created a portable library
>originally called SockThing but now called Dossock95, among other
>names.  It works under Watcom, Borland and Symantec in DOS and
>Windows, and also with RSXNTDJ in Windows IIRC (but I haven't tested
>this).  A message was posted to this mailing list around July 1997 --
>try searching the archives at http://www.delorie.com/djgpp/.  I'm
>working on a straight djgpp port of this at the moment; it's nearly
>done :).

Well, I will definitely hold out for this one... I have decided just to use 
dummy network code for now, since even if I could get sockets working 
correctly it's doubtful that would make my program any easier to debug.

>One interesting thing about this library is that it can get all its
>information about IP address and nameservers from the registry (or at
>least the next version will be able to).  I have ported the registry
>reader to djgpp already; I've also separated the registry reader
>completely from the rest of SockThing and made a djgpp library
>(libreg.a) from it.  I'll probably upload this somewhere shortly.  It
>basically offers standard registry reading functions.  There's another
>module by Alfons which automates the reading of IP and nameserver data
>from the registry that you can look at when he releases it to see
>where to get the data from in the registry for various types of
>connection.

This would be very useful for many other things as well...

>In addition, libnet's winsock driver will (hopefully) have this
>functionality soon, so anyone who wants minimal code just to read IP
>data from the registry will be free to `steal' it from libnet.

What is libnet?

- Calvin -