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,833 of 4,255    |
|    mutazilah@gmail.com to muta...@gmail.com    |
|    Re: visual studio 1.52 huge memory model    |
|    19 Jun 23 17:18:45    |
      From: muta...@gmail.com              On Sunday, June 18, 2023 at 3:02:43 PM UTC+8, muta...@gmail.com wrote:              > > where I said that I needed two values - a divide value        > > (of the amount being added) and a multiply (of how        > > to manipulate the segment), but that both of these        > > could potentially be shifts instead.              > Actually, it's unclear to me why I thought I needed two        > values, and indeed, Microsoft has two as well (but I've        > only seen one used).        >        > It seems to me that I just need that one value returned        > by DosGetHugeShift.               I think it is because the selectors are not necessarily       spaced 64k apart. They may only be 8k apart for example,       for better granularity. It would change depending on how       much memory is available (and designed to max out the       available selectors).              Therefore I would be dividing the offset by 8 to find out how       many selectors I need to advance.              Although this would only be relevant if I needed the pointers       normalized, which Visual C++ doesn't appear to be doing.              BFN. Paul.              --- 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