Hi :-) Forwarding a post from Rugxulo on BTTR about NASM, plus, in unrelated news: If CHKDSK reports a pile of CHK files (you would have to check all contents and rename them to their old name) then one or more directory listings might be lost. On FAT32, even the root dir can be affected. It might be worth trying DOSFSCK instead of CHKDSK, but when the CHK files already are there, it is probably too late. DOSFSCK also supports simulating changes before applying.
If harddisks are in a bad state and you have space: Make a full disk image and work on copies of it. Then you can always revert changes until the best repair is reached. But back to the original topic: A new NASM version is there and Rugxulo writes the following about that via BTTR forum: On 29 November 2017, the NASM developers released 2.13.02. Home page: http://www.nasm.us/ Download: http://www.nasm.us/pub/nasm/releasebuilds/2.13.02/dos/ Changelog: http://www.nasm.us/doc/nasmdocc.html Partial list of recent changes: * Fix false positive in testing of numeric overflows * Fix generation of PEXTRW instruction * Fix smartalign package which could trigger an error during optimization if the alignment code expanded too much due to optimization of the previous code * Fix a case where negative value in TIMES directive causes panic instead of an error * Always finalize .debug_abbrev section with a null in dwarf output format * Fix missing update of global BITS setting if SECTION directive specified a bit size using output format- specific extensions (e.g. USE32 for the obj output format) * Fix the incorrect generation of VEX-encoded instruction when static mode decorators are specified on scalar instructions, losing the decorators as they require EVEX encoding * Option -MW to quote dependency outputs according to Watcom Make conventions instead of POSIX Make conventions. [...] * The obj output format now contains embedded dependency file information, unless disabled with %pragma obj nodepend [...] * Fix generation of dependency lists * Fix [...] null pointer reference and memory allocation errors ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
