Hi, about UMB problems in FreeDOS 2034: I noticed that since I updated MEM (!), it displays an UMB corruption error (without any explanation of where and how, and it even prevents MEM /? from working) IFF the UMBs are created by UMBPCI. The problem does NOT happen with e.g. DR DOS EMM386. And this happens with FreeDOS kernel 2033 / FAT32. To my surprise I found that I do not seem to have an EBDA at all (e.g. it is not displayed in low RAM, nor does MEM show less than 640k RAM, both with and without switches=/e). So I can probably exclude EBDA problems.
But that would mean that my "UPXing (= read-modify-writing, with size change) a program can corrupt file contents or filesystem" spurious error of a while ago on THIS computer could NOT have been caused by EBDA problems!? On ANOTHER computer, I was able to fix the UPX troubles with switches=/e, and THAT computer did have an EBDA (and I tested with 2034 THERE). All quite strange. Will update to 2034 FAT32 and newest HIMEM / EMM386. And please modify MEM so that it displays a more useful UMB corruption message and maybe even tries to make the best of the situation and display information for at least the uncorrupted parts. As you already know, my HARDWARE should not be the problem: UMBPCI UMBs on this board are excluded from L1 and L2 caches and slow, but not broken as far as I can tell. Eric. ------------------------------------------------------- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click _______________________________________________ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
