Prev: Bootstrapping DOS boot disk
Next: what ascii symbol stands for EOF in windows based systems?
From: J de Boyne Pollard on 1 Nov 2007 08:52
T> As indicated, you can access SOME hardware under the two
T> DOS emulators (COMMAND.COM and CMD.EXE).

Neither of those are emulators, DOS or otherwise. They are command
interpreters. The former is a 16-bit DOS program, and the latter is
an ordinary Win32 program, that has _nothing whatsoever_ to do with
DOS. The _single_ "DOS emulator" is NTVDM, the Windows NT Virtual DOS
Machine.

<URL:http://homepages.tesco.net./~J.deBoynePollard/FGA/a-cli-is-not-a-
dos-prompt.html>

From: santosh on 1 Nov 2007 09:24
J de Boyne Pollard wrote:

> s> BTW, what wrong in using a DOS bootdisk. I really don't see
> s> why you should go "off-campus" just for a simple thing like this.
>
> My educated guess is that the university's IT services department
> doesn't allow the machines to be booted from floppy disc, in order to
> prevent students from installing viruses or corrupting the installed
> operating system and application softwares.

And my educated response is that the professors can set up the system
using their floppies. No one was speaking about allowing students to
upload software.

Anyway if the use Bochs+FreeDOS they are assured of security and a
workable real-mode environment. No need to go off-campus for this.

From: Phil Carmody on 1 Nov 2007 09:24
J de Boyne Pollard <j.deboynepollard(a)tesco.net> writes:
> T> As indicated, you can access SOME hardware under the two
> T> DOS emulators (COMMAND.COM and CMD.EXE).
>
> Neither of those are emulators, DOS or otherwise. They are command
> interpreters. The former is a 16-bit DOS program, and the latter is
> an ordinary Win32 program, that has _nothing whatsoever_ to do with
> DOS. The _single_ "DOS emulator" is NTVDM, the Windows NT Virtual DOS
> Machine.
>
> <URL:http://homepages.tesco.net./~J.deBoynePollard/FGA/a-cli-is-not-a-
> dos-prompt.html>

You seem to be confusing the filename "COMMAND", with the name
of the program, "MS-DOS". Only Microsoft have the right to dictate
what the name of their program is, and if they say that the CLI
is called "MS-DOS", and that the commands you type into it
are called "MS-DOS commands", then the CLI is called "MS-DOS",
and the commands you type into it are called "MS-DOS commands"
whether you like it or not. And they do. Sure, they use the same
name for the CLI that's part of the OS as they do for the whole
OS, which is a poor choice, but it's a choice that they had the
right to make, as it's their product, not yours.

Phil
--
Dear aunt, let's set so double the killer delete select all.
-- Microsoft voice recognition live demonstration
From: Ted Davis on 1 Nov 2007 20:09
On Thu, 01 Nov 2007 23:04:02 +0200, Phil Carmody wrote:

> ""Your CONFIG.SYS file contains commands that are not valid MS-DOS
> commands,""

CONFIG.SYS is processed before the command processor loads. It is in fact
processed by the OS loader or the OS itself.

--
T.E.D. (tdavis(a)umr.edu)


From: H. Peter Anvin on 1 Nov 2007 20:15
Ted Davis wrote:
> On Thu, 01 Nov 2007 23:04:02 +0200, Phil Carmody wrote:
>
>> ""Your CONFIG.SYS file contains commands that are not valid MS-DOS
>> commands,""
>
> CONFIG.SYS is processed before the command processor loads. It is in fact
> processed by the OS loader or the OS itself.
>

Yes, and in the latest versions of DOS (Win95/DOS 7 or higher, I
believe) MSDOS.SYS is also a text file with configuration commands.

-hpa
 |  Next  |  Last
Pages: 1 2 3 4 5
Prev: Bootstrapping DOS boot disk
Next: what ascii symbol stands for EOF in windows based systems?