Mail Archives: djgpp/2000/04/09/23:14:54
On Sun, 9 Apr 2000 08:36:03 +0200 (IST), Eli Zaretskii
<eliz AT is DOT elta DOT co DOT il> wrote:
>On Fri, 7 Apr 2000, batchex wrote:
>
>> Umm, I just looking for a compromise, between memory protection
>> and near pointers. Because I'll do much ASM in the project,
>> using far pointers can cause much pain for me, all that pushing
>> & popping segment pointers.
>
>Sorry, I don't understand: what pushing and popping? All you need to
>access a far pointer in assembly is to load FS with the _dos_ds
>selector (once) and then use the fs: segment override.
What are the names of those segments?
SS = stack
CS = code
DS = data
ES = extra
(DS = ES = SS references the same memory as CS, right?)
FS = farptr
GS = ?
>> And I think I left that behind when moving from real mode to
>> protected mode programming....
>
>You can leave that behind if you access the ``normal'' memory mapped
>into your address space. Accessing devices mapped into specific
>absolute addresses is not something ``normal'' programs do.
If you leave far memory access to libraries (Allegro, etc.),
your program can remain a ``normal'' program, right?
--
Damian Yerrick
"I refuse to listen to those who refuse to listen to reason."
See the whole sig: http://www.rose-hulman.edu/~yerricde/sig.html
This is McAfee VirusScan. Add these two lines to your signature to
prevent the spread of signature viruses. http://www.mcafee.com/
- Raw text -