Hi there,
I have started reading EMM386.ASM (not the latest "hot" version, but the previous one, not many changes I assume), and although I haven't yet finished, I think I'd need a couple of hints on some things there. BTW quite an interesting pierce of work! :-)
I suppose some of them are related to TASM rather than EMM, I'm best used to NASM, and don't even know all of it. Anyway here we go. Thanks to all that can give a hint.
(1) Constant EXT and variable _MONITOR_ADDR EXT is a measure of "something" in KBs, and _MONITOR_ADDR is in MBs. In
EXT is moldy code leftovers, EMM386C.C sets the actual address. Be aware the comments in code can be out-of-date due to a 12-year EMM386 lifespan and can be in German, English, or a weird amalgam of Germglish. "Fade", for one example, seems to be used as a synonym for "map".
You might try locating TASM and/or MASM documentation, since several questions touch upon specific behaviors of those assemblers.
There ought to be, but apparently aren't, community projects to write a utility, or utilities, which convert differing ASM source file versions to each other. It is a sorely needed solution for many programmers, infinitely preferable to independently hand-modifying individual source files.
As it is currently a quite active development project, any nontrivial changes to EMM386 unrelated to fixing a verified bug should be sync'ed through me or Tom. Unannounced code changes to EMM386 could make Michael cry and misbehave.
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
