<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Why are the rules for &lt;CODE&gt;GetWindowText&lt;/CODE&gt; so weird?</title><link>http://blogs.msdn.com/oldnewthing/archive/2003/09/04/54794.aspx</link><description>Set the wayback machine to 1983.</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>RE: Why are the rules for &lt;CODE&gt;GetWindowText&lt;/CODE&gt; so weird?</title><link>http://blogs.msdn.com/oldnewthing/archive/2003/09/04/54794.aspx#54795</link><pubDate>Thu, 04 Sep 2003 18:25:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:54795</guid><dc:creator>Joe Beda</dc:creator><description>Hey Raymond,

256MB?  Do you mean KB?</description></item><item><title>RE: Why are the rules for &lt;CODE&gt;GetWindowText&lt;/CODE&gt; so weird?</title><link>http://blogs.msdn.com/oldnewthing/archive/2003/09/04/54794.aspx#54796</link><pubDate>Thu, 04 Sep 2003 19:31:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:54796</guid><dc:creator>Damit</dc:creator><description>Even 256KB would be quite a lot... how much memory could the 8086 support anyway? (I recall it was somewhere near 1MB, but you couldn't use that much)</description></item><item><title>RE: Why are the rules for &lt;CODE&gt;GetWindowText&lt;/CODE&gt; so weird?</title><link>http://blogs.msdn.com/oldnewthing/archive/2003/09/04/54794.aspx#54797</link><pubDate>Thu, 04 Sep 2003 19:38:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:54797</guid><dc:creator>MartinJ</dc:creator><description>An 80x86 can handle 640KB in real mode (that's 16 bit).  Even though addresses were handled in 32 bits, the system addressing was overlapped (multiply the upper 16 bits by 16 and add the lower 16 bits).</description></item><item><title>RE: Why are the rules for &lt;CODE&gt;GetWindowText&lt;/CODE&gt; so weird?</title><link>http://blogs.msdn.com/oldnewthing/archive/2003/09/04/54794.aspx#54798</link><pubDate>Thu, 04 Sep 2003 21:44:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:54798</guid><dc:creator>Blake</dc:creator><description>Martin:  It's more complicated than that.  The 8086 which is what's Damit was asking about had 20 address pins.  2^20 results in 1MB of address space.  The IBM PC developers decided that of that 1MB, 384K should be reserved for mapping in devices and 640K should be available to address main memory.  The 640K limitation is a PC thing, not a x86 thing.  And of course then it gets even more complicated, if you look at the 286 and 386 (and perhaps 186 but I can't remember) where there were more than 20 address pins you could actually address that extra 64K beyond 1MB that became known as the High Memory Area and was used by DOS 5 and QEMM and such.</description></item><item><title>RE: Why are the rules for &lt;CODE&gt;GetWindowText&lt;/CODE&gt; so weird?</title><link>http://blogs.msdn.com/oldnewthing/archive/2003/09/04/54794.aspx#54799</link><pubDate>Fri, 05 Sep 2003 18:07:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:54799</guid><dc:creator>w.h.</dc:creator><description>I always loved how the 65816 (the 16 bit version of the 6502) went from 16 bit addresses to 24-bit addresses without really obnoxious segment registers.  The segment register was 8 bits slapped on the side without any of the usual funkieness.

Although, the segment registers like that did prevent a few tricks that were useful when you were doing graphics, i.e. setting the segment register to the beginning of a bitmap and using the 16 bit addresses.

I love the history of computing. ;)</description></item><item><title>RE: Why are the rules for &lt;CODE&gt;GetWindowText&lt;/CODE&gt; so weird?</title><link>http://blogs.msdn.com/oldnewthing/archive/2003/09/04/54794.aspx#54800</link><pubDate>Sat, 06 Sep 2003 20:01:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:54800</guid><dc:creator>dz</dc:creator><description>&amp;quot;co&amp;#246;peratively.&amp;quot;  &amp;quot;pre&amp;#235;mptive.&amp;quot;  I thought only The New Yorker rose to that level of pr&amp;#235;t&amp;#235;ns&amp;#239;&amp;#246;n.</description></item><item><title>RE: Why are the rules for &lt;CODE&gt;GetWindowText&lt;/CODE&gt; so weird?</title><link>http://blogs.msdn.com/oldnewthing/archive/2003/09/04/54794.aspx#54801</link><pubDate>Thu, 25 Sep 2003 02:51:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:54801</guid><dc:creator>Peter Lund</dc:creator><description>That would be 8088 and 4.77 MHz, wouldn't it?</description></item><item><title>The Old New Thing : What's the difference between EM_UNDO and WM_UNDO?</title><link>http://blogs.msdn.com/oldnewthing/archive/2003/09/04/54794.aspx#4866695</link><pubDate>Tue, 11 Sep 2007 18:07:53 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:4866695</guid><dc:creator>The Old New Thing : What's the difference between EM_UNDO and WM_UNDO?</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://blogs.msdn.com/oldnewthing/archive/2007/09/11/4857870.aspx"&gt;http://blogs.msdn.com/oldnewthing/archive/2007/09/11/4857870.aspx&lt;/a&gt;&lt;/p&gt;</description></item></channel></rss>