Grounded0

I agree that anything that imposes a permanent conventional memory reduction should stay outside of COMMAND. Fixing DOSBox KEYB might make sense on that basis.

Seems more like 2 KB of conventional and 1 KB of high memory but should still be avoided if possible.

FreeDOS COMMAND does not interfere with reported DOS version as its queried from DOS 30H function which can be set in dosbox-staging.conf: 

Does DOSBox Staging support loading external screen fonts? If not we're kinda forced to try to fix that mess (around 620 KB free conventional memory should suffice for everybody otherwise).

If the backend code is there i try to load FreeDOS CPI/CPX with FreeDOS KEYB if its more stable.

Looking at it we should fix KEYB, poach all the newest CPI files from FreeDOS and save everyone a 10 KB+ of conventional memory. What a mess.

Since KEYB can be loaded into high memory i think it should also be replaced by FreeDOS equivalent. Closes #1506:

Problem is that DOSBox userland probably will never be fixed because most people annoyed by it install a more feature complete and robust DOS userland anyway. So there's no value...

> how many tools would you replace, or just add all available? Replacing COMMAND and all that is in Z: drive while keeping IMGMOUNT and any other DOSBox specific commands....

I have been doing "Z drive customisation" for years by setting Z: drive as the lowest order directory in my PATH. Problem is that it doesn't fix the userland for...