home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.protocols.tcp-ip.ibmpc
- Path: sparky!uunet!cs.utexas.edu!torn!watserv1!sail.uwaterloo.ca!eengelke
- From: eengelke@sail.uwaterloo.ca (Erick Engelke)
- Subject: Re: wattcp building troubles...
- Message-ID: <BrrspE.Kq3@watserv1.waterloo.edu>
- Keywords: tcp/ip,wattcp
- Sender: news@watserv1.waterloo.edu
- Organization: University of Waterloo
- References: <3699@svin02.info.win.tue.nl> <2864@isgtec.isgtec.com>
- Date: Wed, 22 Jul 1992 03:08:02 GMT
- Lines: 29
-
- bmw@isgtec.com (Bruce M. Walker) writes:
- >
- >I think you'll find that if you compile everything with "Turbo C" (not
- >Borland C), it will work OK.
-
- I believe BCC 3.0 will compile in Large mode (not small) or the other
- way around. I'm still using BCC 2.0 until I can upgrade to 3.1. It
- definately works with 2.0.
-
- >There is also an assumption made
- >about stack layout, which is probably necessary for the "tasking"
- >portions of the code.
-
- Actually, it's to circumvent programmers (like me) crashing their
- pc's by placing 4.2 K data structures on Borland's 4 K stack. So
- what you are looking at is a stack overflow check.
-
- >Wattcp is a pretty neat package, but it is not wriiten in C, it is
- >written in "Turbo C"!
-
- Or more accurately CI 86 C which is what I knew at that time back in
- my youth. C++ has forced a new awareness on me, but I still have to
- work with pre-ANSI C for my job.
-
- Erick
- --
- Erick Engelke Engineering Computing
- University of Waterloo
- Waterloo TCP Architect erick@development.watstar.uwaterloo.ca
-