By the way, it's long since I last watched the EMM sources, but I've always thought that implementing RAM=/I=/X= couldn't be very difficult with current sources, by just modifying a bit ScanSystemMemory(), the current search range is fixed (at least it was in 2003):
for (mem = 0xc000; mem < 0xf000;) /* This is the range that should be IMHO modified with RAM= */
so you'd process the I's first, the X's next, and lastly the previous loop, so that if the entry is empty (hasn't been filled by the I/X processing) then you scan.
Well, the fact that it might not have been done like that by current EMM386 developers gives a clue that it must be something more difficult behind... or am I wrong?
Most standard options aren't all that horrible to implement, they just take modest chunks of time one by one, with debug and verification/field testing usually taking a lot more time than actually coding them.
Now we have active RAM and HIGHSCAN requests, no big deal for either, really. But I'd like to see what the timeline for 1.0 FreeDOS release is first. The ever-receding goal line is getting me down.
------------------------------------------------------- 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
