DOSLFN might be covered using that brute-force approach, but the bug still exists ... INT 25 and 26 need some sort of integration with the existing buffer cache, otherwise every other user of INT 25 and INT 26 are still exposed.
On Mon, Aug 18, 2025 at 3:08 PM Jim Hall via Freedos-devel < freedos-devel@lists.sourceforge.net> wrote: > I don't know if everyone saw this, so I'll repeat the news item here. > I saw that Jason Hood posted an update to DOSLFN that seems to fix > this issue. Here's the news item I posted on the website earlier > today: > > > >> > Thanks to Jason Hood for version 0.42 that fixes disk corruption > issues on FreeDOS, which can happen when using FDNPKG on some > packages. This fix resets the drive before creating the LFN. Also in > this release: removed -l, uses LANG instead, messages are read from > files in an NLS directory. See the release notes for other changes. > Download it from Jason's [DOSLFN](http://adoxa.altervista.org/doslfn/) > website. We've also mirrored it in the FreeDOS Files Archive at > ibiblio, under [/files/util/system/doslfn]( > https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/util/system/doslfn/0.42/ > ) > << > > > _______________________________________________ > Freedos-devel mailing list > Freedos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-devel >
_______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
