Bernd Böckmann

What exactly do you mean? Your link seems to show the whole commit diff?

> what would be the advantage of not having that feature enabled ? (and is FAT+ identical to FAT32?) FAT+ is a highly incompatible extension to FAT16/FAT32 to allow files...

> Deleting LFNs and detecting LFNs as not representing non-emptiness for RMDIR are probably useful convenience features not directly linked to FAT+. Re-enabled for the non-FAT+ build via https://github.com/SvarDOS/edrdos/commit/2c9076548ef421f151b12a35d7c6531a3113c255.

FATPLUS branch is merged into MAIN. FAT+ is disabled by default. The 64-bit SFT field extensions are not included in the non-FAT+ build.

Yes will probably be UMB. For the start I will make SHELLHIGH an alias for SHELL, so that this does not break badly if encountered in a config.sys.

> On the EDR side, I see in internals.md mentions of HIDOS, HILASTDRIVE, HIBUFFERS and HIFILES - are these the same as DOS=HIGH, LASTDRIVEHIGH, BUFFERSHIGH and FILESHIGH, respectively? Yes, these...

Regarding the whole shell and HMA thing: It seems EDR kernel does some magic by reserving some space of the HMA for command.com?!? I did not have time yet to...

Yes, I would make this an IDLEHALT config.sys command to be compatible. But it would neverthless be nice if this could be disabled / re-enabled at runtime if the user...

> > the user notices some specific slowdowns for an application. > > in my case it was the opposite - when trying out freedos in qemu (kvm), i noticed...

> > > the user notices some specific slowdowns for an application. > > > > > > in my case it was the opposite - when trying out freedos...