Quote:
Originally Posted by gmw
Seems to me you're making a mountain out of a vernacular molehill. Lots of people use "dos prompt" and "command prompt" and "console" somewhat interchangeably…
|
It mostly doesn't matter, except it won't run actual DOS programs (NTVDM or the better DOSBox will) and the commands with the same name don't always exactly behave the same.
Windows NT family is very very different to non-NT Windows (which ended with Win9x/WinME).
If you really think it's a DOS or MS Command Prompt eventually that will bite you.
I remember teaching trainee secretaries in 1991-1993 the difference between the PC box, a screen, an actual hard disk, and a floppy. Some thought the system box was the HDD. Some thought the 3.5" floppy was the HDD.
The easiest to teach were ones from poorer schools with NO PCs. I advised UK Education authorities in early 1980s that it was madness putting the mix of Apples, RM 380Z, Acorns, BBC and later IBM PCs into classrooms without training the teacher and giving the teacher a PC first.
Children in schools in many cases taught nonsense in UK & Ireland.
Concentration on marketing designed courses teaching features of applications (menus) rather than how to use a PC, how to do tasks. So today we still have most malware disasters are caused by user irrespective of patches, updates and AV.
People using wordprocessors like glass typewriters (ignoring styles and headings). People misusing spreadsheets, powerpoint etc. Managers insisting a program only ever used locally with local data should be a web app.
The console on all real operating systems is sometimes needed. People need to know what it is and not think of it as a "bundled" or legacy C:\ prompt or DOS or MS Command.
There is no "net" command on DOS. The CLI or Console net command lets you still do stuff removed from GUI of cheaper versions of windows, like create user accounts without a Microsoft online account and internet.