Date: Sun, 21 Sep 1997 00:13:07 -0400 (EDT) Message-Id: <1.5.4.16.19970921094535.392f7f90@giasbga.vsnl.net.in> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: djgpp AT delorie DOT com From: Chirayu Krishnappa Subject: far pointers Precedence: bulk Hi, The FAQ sez that we have to wary of the base address changing after a malloc(), system(), spawn...() etc. call. My question is that when the base address changes, dont all pointers go haywire (including near pointers, etc). Could somebody point me to a good online introduction or tutorial describing prot. mode mem. management (and everything else if possible). And one other thing. My friend uses a Watcom compiler and guess how he uses video mem. char *p=(char *)0xA0000; *(p+something)=color. thats it. No farptr functions or anything. how does watcom manage this. I thought maybe watcom was always in nearptr mode, but if so, wont the base address need to e recalculated or something? Bye, Chirayu Krishnappa: ------------------ e-mail: chirayu AT radiolink DOT net or ruby AT radiolink DOT net Phone: 91 080 3332616.