Michael Devore schreef:
It necessary, RAM can be completely emulated within the command line parser via internal mapping to I= and X= options. It wouldn't take a lot of time to implement.
hello Michael,
please do so if you are willing to do that.
and your comment about it is correct: it's better to make the emm386-line machine-specific in order to fully take advantage of UMB space.
but implementing the RAM keyword (it means allocate UMBs + pageframe in the specified UMB-area ???) allows a MSDOS config.sys
to be transferred 1-on-1 to FreeDOS (more specific: FreeDos emm386).
any idea if the HIGHSCAN option should be accepted (preferably as a dummy parameter)?
device=himem.exe device=emm386.exe RAM HIGHSCAN dos=high,umb
last but not least, is it possible to access the UMB-scanning engine from the commandline, so it would indicate if 4KB blocks are
filled with all zeroes, all FF's, or something else (code). Upper memory block testing code for when no EMM386 is loaded :)
just when you guys have done a wonderful job, people keep asking to implement wishes :)
and to save myself from typing another message: any chance of Tom taking the time to release emm386r2 as a final EMM386 1.12/1.13 package?
any word from Erwin?
Bernd
-------------------------------------------------------
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
