Michael Devore schreef:
Uploaded to ftp://ftp.devoresoftware.com/downloads/emm386 are the
files emmx208.zip, EMM386/HIMEM mostly executable package (EXEs
compressed via mutant UPX), and emms208.zip, EMM386/HIMEM mostly
source package. Nomyso version 2.0 was uploaded to
ftp://ftp.devoresoftware.com/downloads/nomyso named nomyso20.zip.
nomyso is the newly chosen subdirectory for all Nomyso versions.
Great work again, Michael.
So the Nomyso perl-script changes requirements from TASM/TurboC to
NASM/TurboC?
Perhaps Blair's TCC2WAT helper library could even turn that into
NASM/Openwatcom.
This library does not seem available yet, but the link is
http://wiki.fdos.org/Main/TCC2WAT
Version 2.08 of EMM386 is strictly a compatibility release to help
ease transition for Microsoft EMM386 setups, increasing the number of
identical options allowed in both EMM386 versions. Specifically,
EMM386 will now accept NOHI and NOMOVEXBDA without complaint, although
these two options are
I think HIGHSCAN was the most used exotic option, but I have no idea
what *exact* function it performed. Probably something like X=TEST or
I=TEST, and I=C800-EFFF (or F7FF, Bios area). Still, it's very nice to
see programs behaving as "drop-in replacements" instead of only
"FreeDOS-only equivalent for MS program 'XYZ'. SHSUCDX is a nice
example, and now also the memory drivers you've expanded greatly (for
any DOS usage except loading up Windows)
So, a big thanks.
I anticipate that Version 2.08 of EMM386 is the final non-bugfix
release I will create (bugfix versions will continue, as necessary).
I've done all the new design and enhancements I want to do, or think
are necessary. The ability to assemble and test with NASM may expand
the pool of potential developers, although any such changes should
still be discussed with -- and need be approved by -- the HIMEM/EMM386
maintainer(s).
I can only think about non-driver behaviour functions as an add-on (like
XMSTEST.EXE inside HIMEM). For example implement commandline mode of
which UMBs might be suitable for inclusion. UMBPCI has an UMBCHK program
which does this. Drawback is that it increases the size of the binary,
often not desired for things like bootdisks.
For my part, on the FreeDOS-related front, I will likely continue work
on Nomyso. There is even a faint chance I will someday document
advanced HIMEM and EMM386 options and behavior, or heck, maybe clean
up that really lame Wikipedia Encyclopedia entry for FreeDOS.
Even my name is on Wikipedia (written in a wrong matter), but I can't
remember doing anything significant to justify that.
Note that NASM is slightly less efficient than TASM when generating
object code so there will be a slight increase in the EMM386 binary
size, although the increase was well under 1%. In fact, NASM is
better than TASM at one type of optimization, but not enough to
overcome other misses.
your NOMYSO page already points to Perl website, so I guess it's
pointless to ask for converted sourcecode.
More information on Nomyso is available at
www.devoresoftware.com/nomyso . If any of you have suggestions for an
open source application written in MASM or TASM which could use an
automatic conversion to NASM, let me know and I'll consider making it
the test case for Nomyso version 2.5 or 3.0.
http://www.darklogic.org/fdos/projects/atapicdd/atapicdd.0.2.14.zip
I have no clue about in which condition the TASM(MASM?) and NASM
sourcecode is. Having sourcecode that compiles with NASM might actually
encourage people other than Jeremy to work on it. Always not enough
hours in a day, I guess.
if HIMEM compiles now with NASM, does FDXMS/FDXXMS/FDXDM286 also (as
HIMEM was based on it, looooooong time ago)?
Can't think of any other programs, right now.
Bernd
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Freedos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-devel
