<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>userbinator</author><text>My experience has always been that &amp;quot;not supported&amp;quot; means anywhere from &amp;quot;physically impossible&amp;quot; (e.g. because there just isn&amp;#x27;t that many address bits) to &amp;quot;we won&amp;#x27;t help you because we haven&amp;#x27;t tested it&amp;quot;.&lt;p&gt;Some quick searching shows that others have managed to get that CPU to use 32GB of RAM:&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;forums.overclockers.com.au&amp;#x2F;threads&amp;#x2F;p55-chipset-i5-750-takes-32gb-ram.1083529&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;forums.overclockers.com.au&amp;#x2F;threads&amp;#x2F;p55-chipset-i5-75...&lt;/a&gt;&lt;p&gt;I thought he would go as far as patching the BIOS itself, which would make it a &amp;quot;permanent&amp;quot; fix. In fact one of the projects I haven&amp;#x27;t gotten around to finishing is to patch the memory init code for an old Atom processor embedded motherboard to make it recognise more combinations of RAM modules; analysis of the BIOS and leaked sources shows that it was stupidly written as &amp;quot;if(512MB in slot 1 and 512MB in slot 2) ... else if(1GB in slot 1 and empty slot 2) else if(1GB in slot 1 and 1GB in slot 2) ...&amp;quot;, when the memory controller can actually be set up generally to work with many more different configurations.</text><parent_chain></parent_chain></comment><story><title>Adventures of putting 16 GB RAM in a motherboard that doesn’t support it (2019)</title><url>https://www.downtowndougbrown.com/2019/04/adventures-of-putting-16-gb-of-ram-in-a-motherboard-that-doesnt-support-it/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>benjaminpv</author><text>I was looking to Hackintosh an older Dell desktop I had squirreled away and in the process of gathering all the hardware every piece of documentation I found &lt;i&gt;insisted&lt;/i&gt; that it topped out at 4GB. This was a late-era Core 2 so that seemed completely nonsensical to me (I don&amp;#x27;t think I ever owned a Core 2 that had less than 8) and, wouldn&amp;#x27;t you know it, 8GB worked perfectly fine.&lt;p&gt;Funnily enough, like the article&amp;#x27;s author I also encountered a DSDT-related problem on that same system: if you were to dump the tables and recompile them with the standard Intel utility it straight up wouldn&amp;#x27;t work. Came to find out that there are apparently two compilers, one from Intel and another from MS and the MS one is super-lenient about accepting garbage. Eventually worked out that the logic in the stock tables was such that several features (HPET and sleep, iirc) just straight up don&amp;#x27;t work unless the OS identifies itself to ACPI as Vista (and not like Vista+, Vista exclusively). Such a pain.</text><parent_chain></parent_chain></comment><story><title>Adventures of putting 16 GB RAM in a motherboard that doesn’t support it (2019)</title><url>https://www.downtowndougbrown.com/2019/04/adventures-of-putting-16-gb-of-ram-in-a-motherboard-that-doesnt-support-it/</url></story>