Date:	Sat, 16 Dec 1995 14:14:38 -0800 (GMT)
From:	Orlando Andico <oandico AT gollum DOT eee DOT upd DOT edu DOT ph>
To:	DJGPP Mailing List <djgpp AT delorie DOT com>
Subject:	wattcp
Message-ID:	<Pine.SOL.3.91.951216140701.5665A-100000@gollum>
MIME-Version:	1.0

Hello again:

I was able to get a copy of a very simple HTTP daemon for Unix (the 
source code is around 7K!). Using gcc 2.6.3 on a sparc10, I was able to 
compile and use this program. I then replaced all the BSD-style socket 
calls with WATTCP-style calls (Waterloo TCP/IP implements only a subset 
of the BSD Sockets library, but this particular program didn't use any 
non-implemented features).

The program then compiled nicely under DJGPP (except for a horde of 
warnings, due to -Wall). However, when I tried to run it, the daemon
immediately crashed, taking the system down with it. That's why I can't 
use symify to obtain tracebacks -- the registers and whatever else pop up 
on screen, then two seconds later the system reboots.

Of course, I don't intend for this to be a true daemon, since MS-DOS 
isn't multitasking. My idea was to just let it run by itself (and the 
computer can't be used for anything else) so I could experiment with HTTP 
and extend the server (since it's *really* primitive).

I've never used WATTCP (or any other TCP/IP package) before so I don't 
know where this problem is coming from. I did read a TCP/IP book with the 
BSD reference, and compared all the stuff with the WATTCP source.

Many thanks,

---------------------------------------------------------------------------
Orly A. Andico                   Instrumentation, Control, and Robotics Lab
oandico AT gollum DOT eee DOT upd DOT edu DOT ph        Dept of Electrical & Electronics Eng'g
                                      University of the Philippines Diliman
---------------------------------------------------------------------------

- Raw text -