From:	adalee AT sendit DOT sendit DOT nodak DOT edu (Adam W Lee)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: a few questions...
Date:	13 Sep 1997 06:43:25 GMT
Organization:	SENDIT - North Dakota's Educational Network
Lines:	27
Distribution:	world
Message-ID:	<5vdcmd$gq5$1@news.sendit.nodak.edu>
References:	<5v87rt$2j4$1 AT kurica DOT wt DOT com DOT au> <JLodrCAf1TG0EwIC AT jenkinsdavid DOT demon DOT co DOT uk>
NNTP-Posting-Host:	sendit-2.sendit.nodak.edu
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

: I know, I got it muddled the first time.
: When I said "Win95 handles the illegal calls better than Dos."
: Either it was before I read Sinans post in another thread of mine or it
: just hadn't sunk in.

: So, why does Dos handle catch SIGSEGV errors and Win95 doesn't??
: Is Win95 just ignoring them to avoid crashes or something??

Actually, CWSDPMI is just a killer DPMI server (Thank you, Mr. Sandman! :)

If you are having troubles with this you could always use PMODE/DJ, it's
about as unpicky about null pointer dereferrences as you can get...  My
friend wrote a 3D engine for Watcom that DOS4G/W handled fine.  Then he
gave it to me and CWSDPMI spewed out Page Faults and Sig Segs up the
wazoo...  I re-stubbed it with PMODE/DJ and all is (not really) well...

It seems DOS4G/W, PMODE/DJ and the Win95 DPMI are really lazy... :)

--
  
  +--- --  --   -     -
  | [pHiXx/VorteX]
  : phixx AT usa DOT net

  :

  .

- Raw text -