: >How can you allocate memory at a given PHYSICAL ABSOLUTE
: >NON-program-memory-address-space location?
: But! Note that the kernel itself occupies some 1MB of memory, and if you
: write bit patterns there you're likely to crash your machine.
: Memory testing is a job for a standalone program, i.e. running
: without an OS kernel. Moreover, the code should be position independent
: so that it can reposition itself and test the memory occupied by it
: Note that you can use DOS to load a standalone program, because DOS
: doesn't control anything your code does (e.g. changing descriptor tables
: or such things)
: Perhaps someone could turn that memtest.c into a standalone program
: (to be loaded by lilo or by DOS)?
My personal opinion is that it is unlikely that there are socalled
"CELL errors". Those are the ones that are specifically related to a
single memory cell. These are usually found by the BIOS memory test.
The harder ones are the ones that are caused by specific address
changes. For instance when the address changes from 10101010 to
10101010 the chips might have extra trouble with that, and require a
few ns extra time. If you have your chipset configured for a critical
number of waitstates, this just might mean that the memory delivers
the requested data "too late".
These are rarely detected by simple memory tests, as they tend to
access memory sequentially.
something that is really good :-) . Untill then you might use the
*** War doesn't determine who's right ****** War determines who's left. ***
*** <a href="http://einstein.et.tudelft.nl/~wolff/">my own homepage</a> ***