I note that in 2.0.36, you no longer need the append mem= trick.
In fact, I just tested this, booting the latest version of Tom's RTBT
on a 128M machine, and voila!
Now, 'twas my understanding that detection of memory beyond 64M was
chip dependent, and that in order to do it, required intimate
knowledge of and cooperation from specific chip sets. That is,
Microsoft can do it in NT, because they are willing to "work with" (in
the MS sense of the phrase (*)) the chip manufacturers to make it
work, but that it just isn't worth it in Linux.
My question is: How did they do it, in 2.0.36? Was there some
heretofore undiscovered BIOS call or something, or did they
essentially do the same thing as NT does? I'm looking for an
explanation in "semi-layman's terms" - I'm not a layman, but not
exactly a kernel hacker either. Also, is there any particular reason
why you couldn't just probe memory (write a byte, read a byte) until
(*) One is reminded of the line from the book "The Microsoft Files" -
"Doing business with Bill Gates is like having a date with Mike Tyson
- you expect to get*d."