appear to be a current problem. Can anyone reproduce with the current
kernel? Did anyone already fix this or are we possibly still corrupting
memory, just a different location now?
Thanks, Jeremy
...
version 1.1.35w (Build 2035w-UNSTABLE, Nov 28 2004) also saved a wrong BIOS interrupt vector table, so GRUB.EXE does not run. Details:
FreeDOS build 2035w-UNSTABLE destroyed two hardware interrupt vectors. FreeDOS build 2035w-UNSTABLE tried to save the original BIOS int 0x08 - int 0x0F vectors at 0000:0710, but the FreeDOS startup code overwrote the region. On my QEMU virtual machine, this destroyed region is dumped here:
...
(53 FF 04 1A) corresponds to int 0x0B; (1C 9E 00 F0) corresponds to int 0x0C.
...
Hope this bug in the FreeDOS Kernel will be fixed soon!
Wengier
------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Freedos-kernel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
