At 11:17 AM 3/9/2004 +0000,Bart Oldeman wrote: >Looks very promising! -- it looks like the programs work. But I see one >problem now with both dos4gw 1.97 and causeway. > >fd kernel 2033, freecom 0.82pl3 >config.sys: >dos=umb,high >lastdrive=z >device=himem64.exe >device=emm38664.exe >shellhigh=command.com /e:2048 /p > >nothing loaded in autoexec.bat > >running *any* dos4gw or causeway program I tested I got a "dos mem corrupt >message". > >simplest case: > >d:\watcom\binw>cwstub >Causeway error 11: DOS reported an error or corrupt file found. >dos mem corrupt, first_mcb=02c2 >prev cf42:0000|4d 00 00 3c 10 06 .... (crap) >notMZdf7f:0000|00 00 00 00 00 00 (all zeros here) > >no idea why -- perhaps there was an MCB here (possibly freecom as it puts >various things at the top of the UMBs) and it was wiped out by something >... I'll try to narrow down and have a look later. > >The MCB chain corrupted message doesn't occur when using umbpci instead of >emm386. > >And will also have a look at DJGPP programs later (using cwsdpmi).
I'm a bit confused on the programs working part of your message. Does EMM386 work for you under some circumstances with the extenders or does it always fail under all circumstances? If you exclude (X=<addr> parameter in EMM386) the problematic ranges for any PROMs -- which it looks like needs work in the original EMM386 code based on other messages -- does it help any? ------------------------------------------------------- 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
