At 04:58 PM 4/8/2004 -0400, Patrick J. LoPresti wrote:
>Michael Devore <[EMAIL PROTECTED]> writes:
>
>> Although the new A20 test code should work, as it does fine in many
>> machines and the logic is sound.
>
>I still think instruction reordering is a potential issue.

It might be, it's hard to be definitive without an Intel/BIOS engineer backing us up.  
But it turns out the reversion to original A20 test code didn't clear up any reported 
problems and I'm not sure I'm ready to change to a third A20 test when it won't help 
with known problems.

We're still running into a shortage of testers and I think the best approach may be to 
soon release a cleaned-up version of the HIMEM we have into the wild, then modify as 
necessary afterwards.  Too many people apparently see "test" version and decide they 
don't have the time or energy to fool with it, and I'm in sympathy with that viewpoint 
to a certain extent.

What I'll do is keep the MEMDSK A20 test code at the ready, and swap it in for testing 
with anyone reporting problems that correlate to A20 testing.  Additionally, if any 
port 92h related lockups happen, I'll move "always-on" to top the A20 test list, see 
if they go away.  We may wind up mirroring Linux test methods almost exactly that way, 
or perhaps not if everybody comes out happy in a modestly different configuration.

Oh, a final question for you:  do you know if any of the Linux code listed is even 
remotely tied up with all that SCO garbage?  Obviously SCO's case is utterly bogus, 
but as you know, unlike IBM we cannot afford to play chicken with their lawyers.




-------------------------------------------------------
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

Reply via email to