On Fri, 16 Apr 2004, tom ehlert wrote: > one thing I don't understand: > MEM /F will show a 1K dataarea, between 2 FILES drivers, at ~2a6:0 > > this existed also in ke2033, and possibly before. > > as it *seems* to be unused, what is it?
That would be the relocated EBDA. I should improve MEM to detect that one properly. > BTW: I fullheartily disagree with your efforts to move share_check() > into assembly, and I will never like #pragma aux, even if that saves a > few byte. IMO this is dos-C, and should be coded in C (which is > possible mostly) you'd have to be consistent. Most of the remote functions use assembly. So why have just one using intr()? Either use intr() for all of them or use external asm files for all of them. Since the resident code had only 4 or so intr() users it was easier to go for the external assembler. I left all the intr()s in the init code as is though -- since it's the predominant technique there. As to #pragma aux, this helps the Watcom optimizer quite a bit (about 350 bytes for the asmsupt.asm interfaces) -- without it even a "memcpy" in C would make a smaller kernel (but in the past you argued to do memcpy in assembly). Ironically as soon as you throw a "normal" __cdecl or pascal assembly function into the equation (whether intr() itself or anything else) the whole optimizer chain collapses. Bart ------------------------------------------------------- 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-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
