Hi... > Except he didn't find out saving registers would fix things. He dug into > it, got some debugging information and then flatly decided _without_ > verification that register usage definitely _was_ the problem...
So I gave exact information on how this could be tested, and Jeremy, who already has the compile environment set up, tested and verified things. > Is discovering a possible fix so exciting it has to be sent out Right That > Very Second? Is verification, testing, and reading documentation... Things started when I found that Jeremy still RECOMMENDS the 386-optimized kernel on http://fdos.org/kernel/ ... So instead of writing him about poor 386-kernel still being incompatible and asking him to place a warning "please do not use the 386 kernel with EMM386", I decided to spend the rest of the night (until 7am) to FIND the bug, allowing it to be SOLVED. Better a solved bug than having to keep people over and over again what they have to do for the workaround. And yes, I had ruled out several other possible bug sources first, even though I did neither compile a fixed EMM386 nor an immunized kernel. Was a bit late at the morning to do so, and luckily Jeremy did the immunized kernel test and reported success until I got up the next day :-). Eric ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Freedos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-devel
