Hello Michael,
> Should EMM386 remove its current code which changes returned upper memory > block start addresses from A000 to A001? Is it safe? Is it sane? Is it > The Right Thing To Do or not?
when I wrote that 'return a001 instead of a000', I saw a lot of problems, that would arise, if lower memory MCB's will ever be joined to a000 UMB memory. so I decided to intentionally return a001.
IMO this might be feasable, if the kernel knew about a000, and immediately merged completely into lower memory arena, and start UMB at c800; else strange things *will* happen.
neither KE2035 nor toms KE2035+ kernel care about a000, and will probably behave somewhat different from specification.
Alright, I'm a bottom-line kind of guy. Do you think we should
A. remove the A000 -> A001 code (Arkady preferred) or
B. not remove the A000-> A001 code (status quo) or
C. don't care?
I'm neutral unless more than one other person supports removing the code.
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Freedos-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-devel
