Message-ID: <37B20CB2.FC6242D9@geocities.com>
From: Sahab Yazdani <beyonder69 AT geocities DOT com>
X-Mailer: Mozilla 4.51 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
Newsgroups: comp.os.msdos.djgpp
Subject: Re: How to convert a selector into a pointer?
References: <37b19b34 DOT 33491353 AT NotesXnt> <37B16C34 DOT 10FE AT mitre DOT org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 16
Date: Wed, 11 Aug 1999 19:52:19 -0400
NNTP-Posting-Host: 209.5.17.165
X-Complaints-To: abuse AT sprint DOT ca
X-Trace: newscontent-01.sprint.ca 934415549 209.5.17.165 (Wed, 11 Aug 1999 19:52:29 EDT)
NNTP-Posting-Date: Wed, 11 Aug 1999 19:52:29 EDT
Organization: Sprint Canada Inc.
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

[SNIPPY-TY-SNIP]
> > This technique is highly unportable and is the way to do the stuff that
> Watcom lets you do with pointers in 32-bit DOS mode that wouldn't be
> prudent in a gcc-based compiler. It effectively changes the segment
> limit of your program to 0xFFFFFFFF, so that all memory becomes
> addressable. It also lets you accidentally take down the computer if
What do you mean *take down*, like totally destroy it or just make it
hang??
> you're not careful, because you can corrupt any memory that would
> normally be protected from your program. So if your computer resets, its
> not my fault.
> 
> Oh yeah, and do a __djgpp_nearptr_disable() at the end of your program
> to clean up.
> 
> moogla