Xref: news-dnh.mv.net comp.os.msdos.djgpp:3389
Path: news-dnh.mv.net!mv!news.sprintlink.net!howland.reston.ans.net!newsfeed.internetmci.com!solaris.cc.vt.edu!hp.fciencias.unam.mx!usenet
From: quartic AT polloux DOT sun DOT soe DOT clarkson DOT edu (Mena Quintero Federico)
Newsgroups: comp.os.msdos.djgpp
Subject: Extender performance...
Date: 22 Nov 1995 13:45:23 -0600
Organization: UNAM
Lines: 25
Sender: quartic AT polloux DOT sun DOT soe DOT clarkson DOT edu
Reply-To: quartic AT polloux DOT fciencias DOT unam DOT mx
Nntp-Posting-Host: polloux.fciencias.unam.mx
To: djgpp AT sun DOT soe DOT clarkson DOT edu
Dj-Gateway: from newsgroup comp.os.msdos.djgpp

Hello, all!

I've been playing with DJGPP for about two weeks now, and I just
*love* it.  Much better than BC++!!!

So yesterday I compiled POV-Ray using DJGPP, to take some dirty
benchmarks against a Watcom compile of POV (the POVFAST one)... 
and the Watcom compile beat the DJGPP one by about 30%.  So, my 
question is... is this really due to the different DOS extenders?  
How does GO32 compare to DOS4GW?

I don't think the issue comes to optimizations... I used -O3 for
compiling, anyway (and my experience with different POV compilations
is that the DOS extender *really* matters).

And another question, perhaps a very stupid one... I am writing a
small hypertext browser for an electronic magazine, and I am using
libgrx.  Is there a way to have libgrx autodetect the video card and
use the appropriate driver, instead of having to set the GO32
variable?  My problem is that *very* naive users will be using this
browser, and they won't have the slightest clue about which video card
they have... much less about how to set environment variables :)

Here, with my stupid questions... :)
  Quartic