IBM 5160
forsure.dev
forsure.dev
IIRC, there’s some limited command line editing support using the function keys. You can also get command line history using https://en.wikipedia.org/wiki/DOSKEY (if your DOS has it)
“So figuring out the available commands is using a lot of DIR .EXE's and DIR .COM's.”
Try
C:\> DIR | MORE
(Alternatively, redirect the output to a file and use an editor. I think your DOS has edit.exe, but EDLIN is the true way)In order to mitigate the toxic effects of "screen time", I've always felt that a young child's first computer should be an old-style one, like a Commodore 64 or even a DOS PC. Current-era machines designed in the same vein, like the Commander X16, would do just as well. Modern devices come with lots of mind-numbing distractions (YouTube videos, addictive pay-to-win "games") and no means to program them. Back in the day, a computer was for programming as a pencil is for writing with: it was the unique thing the machine was built for. The sooner a child comes to grips with programming and instructing a computer (beyond clicking things or selecting from menus), the more savvy they will be about its use; after all, pay-to-win "games" and YouTube and social media are all just programs also. The genie will do good or evil only according to whomever is rubbing the lamp, and understanding early that you can rub the lamp and command the genie, and the responsibility that entails is even more important now than it was back in the 80s.
... haul out the Simh is my only option for now.
It takes text input from the terminal quite literally. No backspacing, no editing. You'll just get control characters in the resulting file.
Type it right the first time or start over. Brutal.
But it works from a disk that has only IO.SYS, MSDOS.SYS, and COMMAND.COM.
Somewhat true. IIRC, DOS changes all path input to uppercase and tries to find a file/directory which is labelled in uppercase. If some program manages to create a file which has a lowercase character in its name (for example FOo.TXT), you can't touch it with for example DEL, because DEL FOo.TXT would be converted to DEL FOO.TXT, and DOS would complain there is no FOO.TXT...
Also, installing dos stuff in C:\DOS is what people generally did. I'm pretty sure it could be anywhere in the path.
Something else neat, the manual for these have the BIOS source listed.