Forums before death by AOL, social media and spammers... "We can't have nice things"
|    alt.os.development    |    Operating system development chatter    |    4,255 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 3,327 of 4,255    |
|    Joe Monk to All    |
|    Re: segmentation    |
|    20 Oct 22 02:41:26    |
      From: joemonk64@gmail.com              > Far pointers are just segment and offset, and are restricted to 64k.        >               Far pointers are 32-bit. They are not restricted to 64k. They are generally       written as segmentoffset. So if the segment is B000 and the offset is 8000       (i.e. video memory), then the far pointer is 0xB0008000. Far simply means, in       pointers, that the memory        is not near (i.e. within the current segment).              The problem with far pointers is that segments overlap, so they are not       normalized.              >Huge pointers manipulate the segment every time you try to change        >the pointer, keeping the offset to under 16 and changing the segment        >so that the entire 1 MB is addressable.              A huge pointer is just a far pointer, but normalized.              Joe              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca