Talk:How Do I Determine The Amount Of RAM

OK for rewrite?

There are several typos on this page. Part of it is copied verbatim from another website. The formatting of many comments is bad. The pieces that are lifted directly out of RBIL are not as helpful as they could be.

The article belongs in Hardware/Platforms/X86 -- not in "Common Devices". It should be in two pieces. One piece would be an X86 Memory Map, including the BDA and EBDA. The other would be what remains of this current article -- I think it should be renamed "Detecting Memory (x86)". With extensions about CMOS, and including some of Brendan's commentary on the subject over the years.

Do I hear objections about me rewriting it? Bewing 08:56, 19 April 2008 (CDT)

I agree completely. As with anything, feel free as long as no information is lost. Just beware that this title is an entry in the FAQ category, and should stay that way (don't delete or move this page!). Instead, please replace it with the following snippet once you've completed the new article:

#REDIRECT [[Your New Page]]
[[Category:FAQ]]

- Combuster 16:44, 20 April 2008 (CDT)

OK, done.
Bewing 15:35, 17 May 2008 (CDT)

Volatile or ASM clobber

Unedited 'request' from TomTom: use of volatile keyword instead of asm("":::"memory"). Two reasons: it was marked as minor while it was a serious change in code, and IMO it didnt improve understandability. Apart from that, the algorithm is fundamentally flawed as it can't cope with residual bus voltages. There's a thread regarding good checking of memory whose contents would provide for a better way of checking memory - we should create a new algorithm based on the concepts there. - Combuster 15:53, 9 May 2007 (CDT)