Timeline for Memory limits in 16, 32 and 64 bit systems
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 6, 2014 at 17:29 | comment | added | supercat | @OCDtech: The 8086 segmented model would allow an object-oriented language to use 2-byte object references to identify objects aligned on 16-byte boundaries, but languages were not well-equipped to use segments effectively. The 80286 model imposes monstrously-greater overhead to such programs, and the way it was extended on the 80386 would make a segment-per-object scheme totally useless. | |
| Mar 7, 2013 at 15:51 | comment | added | Ramhound | Its my view that answers should stand alone. Your comment adds enough information to resolve my problems with your answer. | |
| Mar 7, 2013 at 15:08 | comment | added | OCDtech | You're Feb 22 comment, and Scott Chamberlin's explanation pretty much cover what I was driving at. They do leave out descriptions of why extensible segmented pagination was used in DOS/Win16, but not in later Windows. I didn't include that, because it would not contribute directly to answering the OP's question. | |
| Feb 22, 2013 at 23:26 | comment | added | Ramhound | This really does not have enough information to backup your statements. Windows 3.1 is a 16-bit operating system. One must remember that in 1992 2MB of memory was over $300. | |
| Feb 22, 2013 at 21:46 | history | answered | OCDtech | CC BY-SA 3.0 |