<?xml version="1.0" encoding="UTF-8"?> <rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:wfw="http://wellformedweb.org/CommentAPI/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
> <channel><title>Autarchy of the Private Cave &#187; myth</title> <atom:link href="https://bogdan.org.ua/tags/myth/feed" rel="self" type="application/rss+xml" /><link>https://bogdan.org.ua</link> <description>Tiny bits of bioinformatics, [web-]programming etc</description> <lastBuildDate>Wed, 28 Dec 2022 16:09:04 +0000</lastBuildDate> <language>en-US</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>https://wordpress.org/?v=3.8.27</generator> <item><title>Debunking the widespread myth of 2^32=4GB being the architectural limit</title><link>https://bogdan.org.ua/2011/04/10/debunking-widespread-myth-of-2-32-4gb-architectural-limit.html</link> <comments>https://bogdan.org.ua/2011/04/10/debunking-widespread-myth-of-2-32-4gb-architectural-limit.html#comments</comments> <pubDate>Sun, 10 Apr 2011 13:10:54 +0000</pubDate> <dc:creator><![CDATA[Bogdan]]></dc:creator> <category><![CDATA[Hardware]]></category> <category><![CDATA[Links]]></category> <category><![CDATA[Misc]]></category> <category><![CDATA[Software]]></category> <category><![CDATA[32bit]]></category> <category><![CDATA[4GB]]></category> <category><![CDATA[myth]]></category> <category><![CDATA[PAE]]></category> <category><![CDATA[windows]]></category> <guid
isPermaLink="false">http://bogdan.org.ua/?p=1555</guid> <description><![CDATA[Quite a number of people are aware of the PAE which can extend the addressable space from 32bit up to 36-48-52bit (depending on the implementation; as I understand, Windows PAE extends to 36 bits, or 64GB of addressable space). However, overwhelming numbers of internet pages continue insisting that a not-more-than-4GB limit for the 32bit Windows [&#8230;]]]></description> <content:encoded><![CDATA[<p>Quite a number of people are aware of the <abbr
title="Page Address Extension">PAE</abbr> which can extend the addressable space from 32bit up to 36-48-52bit (depending on the implementation; as I understand, Windows PAE extends to 36 bits, or 64GB of addressable space). However, overwhelming numbers of internet pages continue insisting that a not-more-than-4GB limit for the 32bit Windows is the consequence of <em>2^32 = 4GB architectural limit</em>.</p><p>There is an <a
href="http://www.geoffchappell.com/viewer.htm?doc=notes/windows/license/memory.htm">excellent, in-depth, well-argumented article by Geoff Chappell</a> on the issue. Highly recommended in its entirety to those who want a complete understanding (additional side-reading and facts verification might be necessary).</p><p>A single citation to get you started:</p><blockquote><p>There is already on the Internet and elsewhere an awful lot of rubbish to read about this question. Hardly any of it would be worth citing even if I didnâ€™t want to spare the authors the embarrassment. A surprising number of people who claim some sort of attention as expert commentators would have you believe that using more than 4GB of memory is mathematically impossible for any 32-bit operating system because 2 to the power of 32 is 4G and a 32-bit register canâ€™t form an address above 4GB. If nothing else, these experts donâ€™t know enough history: 2 to the 16 is only 64K and yet the wealth of Microsoft is founded on a 16-bit operating system that from its very first version was designed to use 640KB of RAM plus other memory in a physical address space of 1MB. Some remember this history and add seemingly plausible qualifications that exceeding 4GB is possible only at the price of nasty hacks that require everyoneâ€”well, all programmersâ€”to jump through hoops. Fortunately, Intelâ€™s processors are a lot more advanced than the 8086 from all those years ago.</p></blockquote><p>P.S. Unfortunately, patching the kernel won&#8217;t help make Windows XP see more than 4GB RAM: even though the kernel itself does support more RAM (with PAE), starting with SP2 the <abbr
title="Hardware Abstraction Layer">HAL</abbr> was modified in a way prohibiting access to any RAM beyond 4GB. Patching may only be suggested to devoted geeks with Vista&#8217;s and 7&#8242;s.</p><p><a
class="a2a_button_citeulike" href="https://www.addtoany.com/add_to/citeulike?linkurl=https%3A%2F%2Fbogdan.org.ua%2F2011%2F04%2F10%2Fdebunking-widespread-myth-of-2-32-4gb-architectural-limit.html&amp;linkname=Debunking%20the%20widespread%20myth%20of%202%5E32%3D4GB%20being%20the%20architectural%20limit" title="CiteULike" rel="nofollow noopener" target="_blank"></a><a
class="a2a_button_pocket" href="https://www.addtoany.com/add_to/pocket?linkurl=https%3A%2F%2Fbogdan.org.ua%2F2011%2F04%2F10%2Fdebunking-widespread-myth-of-2-32-4gb-architectural-limit.html&amp;linkname=Debunking%20the%20widespread%20myth%20of%202%5E32%3D4GB%20being%20the%20architectural%20limit" title="Pocket" rel="nofollow noopener" target="_blank"></a><a
class="a2a_button_kindle_it" href="https://www.addtoany.com/add_to/kindle_it?linkurl=https%3A%2F%2Fbogdan.org.ua%2F2011%2F04%2F10%2Fdebunking-widespread-myth-of-2-32-4gb-architectural-limit.html&amp;linkname=Debunking%20the%20widespread%20myth%20of%202%5E32%3D4GB%20being%20the%20architectural%20limit" title="Kindle It" rel="nofollow noopener" target="_blank"></a><a
class="a2a_button_evernote" href="https://www.addtoany.com/add_to/evernote?linkurl=https%3A%2F%2Fbogdan.org.ua%2F2011%2F04%2F10%2Fdebunking-widespread-myth-of-2-32-4gb-architectural-limit.html&amp;linkname=Debunking%20the%20widespread%20myth%20of%202%5E32%3D4GB%20being%20the%20architectural%20limit" title="Evernote" rel="nofollow noopener" target="_blank"></a><a
class="a2a_button_pinterest" href="https://www.addtoany.com/add_to/pinterest?linkurl=https%3A%2F%2Fbogdan.org.ua%2F2011%2F04%2F10%2Fdebunking-widespread-myth-of-2-32-4gb-architectural-limit.html&amp;linkname=Debunking%20the%20widespread%20myth%20of%202%5E32%3D4GB%20being%20the%20architectural%20limit" title="Pinterest" rel="nofollow noopener" target="_blank"></a><a
class="a2a_dd addtoany_share_save addtoany_share" href="https://www.addtoany.com/share#url=https%3A%2F%2Fbogdan.org.ua%2F2011%2F04%2F10%2Fdebunking-widespread-myth-of-2-32-4gb-architectural-limit.html&#038;title=Debunking%20the%20widespread%20myth%20of%202%5E32%3D4GB%20being%20the%20architectural%20limit" data-a2a-url="https://bogdan.org.ua/2011/04/10/debunking-widespread-myth-of-2-32-4gb-architectural-limit.html" data-a2a-title="Debunking the widespread myth of 2^32=4GB being the architectural limit"><img
src="https://static.addtoany.com/buttons/share_save_120_16.png" alt="Share"></a></p>]]></content:encoded> <wfw:commentRss>https://bogdan.org.ua/2011/04/10/debunking-widespread-myth-of-2-32-4gb-architectural-limit.html/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> </channel> </rss>