Ifyou're running on Windows 10, at least, you can soon purge that memory. command.com doesn't exist (may never have existed on Win2k, XP, Vista, 7, 8, 8.1 or 10). If I try and run either "command" or "command.com" from Win10, both say command cannot be found.
IIRC, command.com was a relic of Win9x running on top of DOS and was a 16-bit executable, so inherently crippled (and probably never support by the NT kernel). Whereby cmd.exe coexisted but ran in a 32-bit context. On Mon, Dec 5, 2016 at 8:44 PM, Steve D'Aprano <steve+pyt...@pearwood.info> wrote: > On Tue, 6 Dec 2016 10:09 am, eryk sun wrote: > > > On Mon, Dec 5, 2016 at 4:49 PM, Steve D'Aprano > > <steve+pyt...@pearwood.info> wrote: > >> > >> You've never used cmd.com or command.exe? "The DOS prompt"? > > > > The default Windows shell is "cmd.exe", and it's informally called the > > "Command Prompt", > > Thanks for the correction, I always mix up cmd/command . exe/com. I fear > this won't be the last time either -- I wish there was a good mnemonic for > which is which. > > > > -- > Steve > “Cheer up,” they said, “things could be worse.” So I cheered up, and sure > enough, things got worse. > > -- > https://mail.python.org/mailman/listinfo/python-list > -- https://mail.python.org/mailman/listinfo/python-list
