True, but at least it's a workaround for those who use DOSLFN. (I should have described it as a workaround, not a 'fix.' I'll update the news item.)
On Mon, Aug 18, 2025 at 5:16 PM Michael Brutman <mbbrut...@brutman.com> wrote: > > 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: [..] _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
