|
PureBytes Links
Trading Reference Links
|
see below
Regards,
Ton Maas
ms-irb@xxxxxxxxxxxxxxxx
Dismiss the ".nospam" bit (including the dot) when replying and
note the new address change. Also for my Homepage
http://home.planet.nl/~anthmaas
----- Original Message -----
From: UG
To: Metastock-List <metastock@xxxxxxxxxxxxx>
Sent: zaterdag 8 januari 2000 20:04
Subject: Re: how to improve generalization in system optimization
> A.J. Maas writes:
>
> > -Your Windows clock (protected mode) can be accessed via the Window's Control Panel,
> > via the Window's RUN box(Win Prompt) and via the Window's VDOS box(VDOS Prompt).
> > It gets its information from the real PC clock(above), and presents this as though it is
> > the PC clock(eg a VPC clock, a virtual clock), now on your DeskTop (eg thus in Windows).
> >
> > -Your DOS clock (real mode) can be accesed via the DOS prompt, eg with the DATE and
> > TIME commands.
The latest available DOS commander Command.com was the 6.22 version.
The v6.22 of Command.com isn't constructed in a way that it can be run within
the Win9.x environments.
Its successor is the Windows VDOS commander Command.com version 7.0.
This v7.0 of the Command.com can be used:
1.- by PC at start up, to boot directly to DOS
(the DOS's ">" DOS prompt, see below).
2.- by Windows commander Win.com to execute RUN commands
(the Windows' RUNbox "blanc" RUN command line).
3.- by Windows commander Win.com's multiple VDOSbox boxes
(the Windows' MS-DOS prompt ">", see below).
All this can be achieved since the 7.0 version of Command.com for base is build up
with most of the older -now discontinued- single DOS v6.22 operating system commands.
Another difference between both versions of the Command.com is that some functions
from the 6.22 version are not available in the 7.0 version, and some new functions were
added.
> I'm not sure I understand the difference here, but when I issue a
> "date" or "time" command at a command prompt, the clock on the taskbar
> changes to match.
Issueing the DATE or TIME command at a command prompt
a. Running DOS and at command prompt, will envoke the DOS commander (base functions
of the Command.com)
(that's build-in in the DOSv7.0 program in Windows 9.x, an integrated subprogram).
b. Running Windows and in the RUNbox, will envoke the Windows commander(Win.com), which
on its turn will envoke the Windows VDOS commander (build-in in the Command.com)
c. Running Windows and in the MS-DOS promptbox, will envoke the Windows VDOS commander
(build-in in the Command.com) since Win.com already has actived the DOSbox.
Since the multi-usable commander Command.com is build-in in Windows' Win9.x operating
system, than having a separte DOS version of Command.com (single usable for true DOS only)
on disk is not required.
>
> Is that what you meant by the Windows VDOS box?
>
Window's VDOS is only a simulated (Virtual) DOS machine (thus not a real DOS machine)
that is only to be run within the Windows environment (the Windows operating system).
Therefore too, you can have as many (simulated) DOS machines running (eg windows open, a
standard feature of Windows), limited to as many windows(instances) as your PC MEM at
that time can handle.
Thus meaning too that you can open as many VDOSbox boxes as you like, and advanced,
work with all machines (boxes) simulantainously at the same time
(like having 10+ PC's in your room) .
DOS on the other hand was a single one(1) machine operating system. In the old days, when
you started your PC (and DOS was installed), you would than "automatically" arrive at the
single lined Dos prompt, eg
>
C:>
A:>
(C if you were pointing to your hard disk drive and A to your floppy disk drive)
More instances of the DOS prompt (eg having more machines running) could not be
achieved, eg it (DOS) was a one command lined very limited operating system.
|