Date:	Mon, 04 Nov 1996 09:14:40 +0000
From:	Bill Currie <billc AT blackmagic DOT tait DOT co DOT nz>
Subject:	Re: Sockets under DJGPP (was: need advice on djgpp vs. Turbo C)
To:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Cc:	Orlando Andico <orly AT gibson DOT eee DOT upd DOT edu DOT ph>,
	Kai Ruottu <karuottu AT freenet DOT hut DOT fi>, djgpp AT delorie DOT com
Message-id:	<327DB400.7F1E@blackmagic.tait.co.nz>
Organization:	Tait Electronics NZ
MIME-version:	1.0
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 961103111246 DOT 27986H-100000 AT is>

On Sat, 2 Nov 1996, Orlando Andico wrote:
>
> Following the build instructions, I got it to ping successfully.
>
> The ping program is apparently a trivial sort. I got it to build under
> both DJGPP 1.x and 2.0, and it pinged, yes, but according to the porter it
> can't do blocking I/O. So I tried using select() to poll the port and
> avoid use of blocking I/O, but that did not work. The level of support is
> definitely NOT at the level where you can recompile your simple Unix
> network apps under DJGPP, unfortunately.

Sorry, misunderstood your problem.

Eli Zaretskii wrote:
> 
> Without looking at the sources, I'd guess that since the port was done
> for DJGPP v1.x, it doesn't use the filesystem extensions feature
> introduced with v2.0.  I suggest to whoever is interested to check out
> the filesystem extensions and implement TCP/IP support on that level.  If
> you do this, all the rest of I/O (including `select') is taken care of
> automagically for you.  It's an incredible tool for extending DJGPP,
> believe me.  (Thank you, DJ, for including it!)

I started trying to fix all the warnings building it gives, and promply decided to rewrite the 
blasted thing.  Unfortunaly I know bugger all about tcp/ip etc, but I think using the file system 
extensions is an excelent idea (should even make porting unix tcp/ip progs easier).

If I can figure M$'s vtcp/vip vxd api's, it would even work under 'locked doors' :).

Bill

- Raw text -