Here are more specific details on the Borland bug. If and ONLY if BOTH of the following are true:
1) Kernel was built for 80386 with Borland C 3.1 to 5.2 (tried 3.1, 4.0, 4.52, 5.2), AND 2) INSTALLHIGH commands are executed while UMBs are available (I use UMBPCI as UMB driver),
then the kernel crashes with an "invalid opcode" message after executing INSTALLHIGH commands.
I will continue investigating the problem. By the way, MSVC-compiled kernels don't even start up, but I don't care about that, as I don't see any advantages of building the kernel with MSVC 1.52.
Lucho
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
