Borland 32RTM 1.5 fails to work in FreeDOS but works in MS-DOS.Forgot the message: Unhandled exception 000D at 0020 034B ErrCode 0000. This happens without EMM386. I haven't tried it with EMM386 in FreeDOS.
Well, I can tell you where it's happening and the problematic DOS call, but I'm not a kernel developer, so I can't suggest a fix or detail on what causes the function to fail.
Anyway, the problem appears to occur when 32RTM is running in protected mode and issues an INT 31h function 300h (simulate real mode interrupt) to emulate INT 21h function 34h, aka get InDOS flag. The INT 31h function is set to use the internal DPMI stack which RBIL warns may be as small as 30 words and that it should not be messed about from its entry state. RBIL also warns about not calling the 34h DOS function when another DOS function may be executing.
Some way or another, it looks 32RTM is unhappy with what is going on with the stack on the call to function 34h. I don't think the InDOS pointer itself is what causes the failure because the exception can occur during or immediately after return from the Get InDOS simulate call.
Using the -X option bypasses the InDOS function call, so you don't see a problem when you use that 32RTM option.
Incidentally, this occurs with only HIMEM loaded, DOS loaded low, and no XMS swapping command shell present , so EMM386 and the rest of the motley crew isn't getting in the way here.
------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
