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 wrote:
>
> DOSLFN might be covered using that brute-force approach, but the bug
> still exists ...
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 <
freedo
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, w
