Michael Devore <[EMAIL PROTECTED]> writes: > I added enable/disable test, but the report was that it still fails, > after working for the startup test. Which either means the BIOS is > bugged and fails under stress, or there is something very weird > going on.
Like the test_a20 code failing... > The solution for second situation is to try port 92h without the MCA > check. Unfortunately there are machines reliably documented as > locking up if you goof with port 92h when they don't support that > method. If the port 92h test comes at the tail end of the test > chain, maybe it doesn't matter because you're going to fail if it > fails anyway. Perhaps this is why Linux tries 92h last. > I don't know how else to test "always on" other than to try other > methods first, The A20 gate defaults to disabled. So, assuming HIMEM64 is the first program which tries to manipulate the gate, you can make "always on" the FIRST test just by checking the state of A20. This is what the Linux setup code does. Of course, the Linux setup code is guaranteed to be running pretty early. Whether the same can be said for HIMEM64 is a design choice, I suppose. - Pat ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
