From:	"Stephen Howe" <SPAMGUARDstephen DOT howe AT teamsybase DOT com>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Why did ID choose DJGPP for Quake?
Date:	Thu, 6 Jan 2000 18:14:34 -0000
Organization:	UUNET WorldCom server (post doesn't reflect views of UUNET WorldCom
Lines:	57
Message-ID:	<852m1p$1bi$1@soap.pipex.net>
References:	<94711738901 AT out DOT newmail DOT net>
NNTP-Posting-Host:	tnagbgate76.tnagb.com
X-Trace:	soap.pipex.net 947182457 1394 194.202.213.76 (6 Jan 2000 18:14:17 GMT)
X-Complaints-To:	abuse AT uk DOT uu DOT net
NNTP-Posting-Date:	6 Jan 2000 18:14:17 GMT
X-Newsreader:	Microsoft Outlook Express 4.72.2106.4
X-MimeOLE:	Produced By Microsoft MimeOLE V4.72.2106.4
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Kalum Somaratna aka Grendel wrote in message
<94711738901 AT out DOT newmail DOT net>...

>>>
If you have or know of any  testing/benchmark program please
consider posting it. I'm sure many of the members of this group
would be interested in the results from compiling the programs with
full optimisations with watcom and djgpp.
>>>

I will come back to this later.

>>Could you please tell me where you got DOS4GW 2.01. I myself
>>have been on the look out for a newer version than 1.97.

From Tenberry. See

http://www.tenberry.com/dos4g/watcom/index.htm

and release notes

http://www.tenberry.com/dos4g/watcom/rn4gw.htm

2.01 fixes some _very_ obscure bugs in 1.97. It is slightly faster on some
benchmarked tests. You can also get a manual (I have) which I find answers
some questions on what DOS4GW does and raises questions on others. It is
useful but I have reservations.

I do not rate DOS4GW anymore because I think Tenberry have given up
development of it. I would go for Causeway. Part of the reason for this is
that I filed two simple bugs on DOS4GW 1.97 (and 2.01) at the beginning of
1999 with Tenberry and it is now 11 months later. The two bugs were

(i) If you have a PATH that is longer than 256 characters, DOS4GW will fail
to load giving some type of load error message. Your application never gets
started. People who applied SP4 to NT4.0 picked this up.

(ii) If you have an enviroment where you have more than approx 3.5K of env
variables, DOS4GW fails to load giving out a message like
"R6009: Enviroment too big" which is a Microsoft error message.

(iii) I also raised a third bug with Tenberry where in a pure DOS
environment (not Windows  nor any other DPMI server running) with DOS4GW is
its own DPMI host, the timer interrupt int 8H (IRQ 0) should be reflected
first in protected mode according to the DPMI 0.9 standard. I proved it is
not.

From the fact that Tenberry have not fixed these for 11 months, I rate
Causeway because I know that Micheal Devore is _very_ responsive to his
customers.

Hope this helps

Stephen Howe

- Raw text -