From:	"AndrewJ" <luminous-is AT home DOT com>
Newsgroups:	comp.os.msdos.djgpp
References:	<Pine DOT GS4 DOT 4 DOT 02A DOT 10005111505130 DOT 12531-100000 AT antares DOT cc DOT umanitoba DOT ca>
Subject:	Re: __dpmi_paddr and DJGPP pointers
Lines:	14
X-Priority:	3
X-MSMail-Priority:	Normal
X-Newsreader:	Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE:	Produced By Microsoft MimeOLE V5.00.2919.6600
Message-ID:	<DmiU4.54120$55.1104267@news2.rdc1.on.home.com>
Date:	Tue, 16 May 2000 20:40:03 GMT
NNTP-Posting-Host:	24.42.120.18
X-Complaints-To:	abuse AT home DOT net
X-Trace:	news2.rdc1.on.home.com 958509603 24.42.120.18 (Tue, 16 May 2000 13:40:03 PDT)
NNTP-Posting-Date:	Tue, 16 May 2000 13:40:03 PDT
Organization:	@Home Network Canada
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

> I used 100% flat memory model and let me tell you - it SUCKS! It might
> seem easier but it is awful since no protection exists. You write outside
> where you are suppose to and well, the best thing is that your program
> doesn't work (or does :). The worst, loosing entire DIR on a harddrive! :)

I've used Watcom for years now, and it's flat model is unprotected (the
equivalent to __djgpp_nearptr_enable() on all the time) and I've never, ever,
ever trashed anything on the harddrive.  The worst I've gotten is various page
faults and such.  Unless you were doing something wacked out to your harddrive
at the time of the crash, I don't see how that could happen.

AndrewJ

- Raw text -