Hi! > Uploaded to ftp://ftp.devoresoftware.com/downloads are the files > emmx13b.zip, EMM386 mostly executable package, and emms13b.zip, EMM386 > mostly source package.
> These versions follow the latest EMM386 fileset template directory and > naming conventions. Thanks for the template directory part, but I think trying to keep the URL in 8.3 naming convention will only have the result that people who look for emm386 will no longer imagine that emmx could be what they want. You could upload as emm386x-13b.zip and people can save the downloaded file to emm386x.zip, then everybody should be happy. It is good to have /MAX back. The /MEMCHECK should be enabled by default. Once upon a time, I suggested a very crude variant of this: If the size or pointer values of the int 15 block move request have un-plausible high bits set, skip the move (instead of segfaulting yourself - the exception handler had problems with stack layout of protected mode exceptions at that time). Good to hear that you now have a proper implementation of this (my kludge never got accepted, as it was too kludgy). I think even emm386-vm-to-pm communication with itself can conceivably be a victiom of wrong block move parameters, if e.g. DMA related variables get messed up (you never know) in vm86 before the protected mode actual block move call is triggered. Using 386SWAT, I saw that EMM386 of MS does A20 simulation by having two page dirs for the first 4 MB, flipping between them (one wraps HMA to 0:0, the other has "A20 open"). If you combine that with some way of spoiling port 60/64/92 direct A20 access, you can probably get more stability... And the "flip the map" is probably even faster than port 92 A20 control!? Eric ------------------------------------------------------- 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
