From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_0027_01C33D52.CFD548E0
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   When COMMAND.COM runs it is in a VDM.  It's not necessary when you =
run an MS-DOS.

Rich

  "Tony Ingenoso"  wrote in message =
news:3efd0871{at}w3.nls.net...
  Does COMMAND.COM run as V86 task (the answer better be yes or a whole =
bunch'o shit is broken)?  If so, then running it starts a V86 session =
(i.e. a DOS box)
    "Rich"  wrote in message news:3efcb8ce$1{at}w3.nls.net...
       COMMAND.COM is really a compat thing.  CMD.EXE is used to run all =
applications, Win32, Win64, Windows 3.x, Posix, MS-DOS, and OS/2.  Not =
all versions of Windows support all these targets but whatever are =
supported are handled by CMD.EXE.

    Rich

      "Tony Ingenoso"  wrote in message =
news:3efc494a{at}w3.nls.net...
      The stock NT/W2K command line is protected mode Win32.  Running a =
COMMAND.COM within that will fire up a DOS box.

      "Paul Ranson"  wrote in message =
news:3efc3404$1{at}w3.nls.net...
      > I missed the subtlety...
      >
      > But an idle command line window requires no idle detection. The =
cleverness
      > is in detecting that a DOS app is idle while busy polling all =
its inputs.
      >
      > Paul
      >
      > "Robert Comer"  wrote in message
      > news:3efb3466$1{at}w3.nls.net...
      > > > Check the 'misc' tab of the properties of a DOS app on an NT =
machine.
      > >
      > > I knew it could do that, but that's something different than =
just a
      > command
      > > line window.
      > >
      > > Of course, if you create a new shortcut to command.com, you =
can change
      > those
      > > settings for it, so I'll shut up . 
      > >
      > > - Bob Comer
      > >
      > >
      > >
      > > "Paul Ranson"  wrote in message
      > > news:3efb2fda$1{at}w3.nls.net...
      > > > Check the 'misc' tab of the properties of a DOS app on an NT =
machine.
      > > >
      > > > Paul
      > > >
      > > > "Robert Comer"
 wrote in message
      > > > news:3efb1e2c$1{at}w3.nls.net...
      > > > > I think he's getting OS/2 mixed in there -- it had the =
ability to
      > adjust
      > > > > idle detection in a DOS command line window.  If
NT can do =
that too I
      > > > > haven't run across it.
      > > > >
      > > > > DOS box is just shorthand for a DOS command line
window in =
either OS/2
      > > or
      > > > > NT.
      > > > >
      > > > > - Bob Comer
      > > > >
      > > >
      > >
      > >
      >


------=_NextPart_000_0027_01C33D52.CFD548E0
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   When
COMMAND.COM runs it =
is in a=20
VDM.  It's not necessary when you run an MS-DOS.
 
Rich
 

  "Tony Ingenoso" <tonyiNOSPAM{at}attglobal.net&g=">mailto:tonyiNOSPAM{at}attglobal.net">tonyiNOSPAM{at}attglobal.net&g=
t;=20
  wrote in message news:3efd0871{at}w3.nls.net...
  Does COMMAND.COM run as V86
task (the =
answer=20
  better be yes or a whole bunch'o shit is broken)?  If so, then =
running it=20
  starts a V86 session (i.e. a DOS box)
  

    "Rich" <{at}> wrote in message news:3efcb8ce$1{at}w3.nls.net...
      
COMMAND.COM is really =
a compat=20
    thing.  CMD.EXE is used to run all applications, Win32, Win64, =
Windows=20
    3.x, Posix, MS-DOS, and OS/2.  Not all versions of Windows =
support all=20
    these targets but whatever are supported are handled by=20
CMD.EXE.
     
    Rich
     
    
      "Tony Ingenoso" <tonyiNOSPAM{at}attglobal.net&g=">mailto:tonyiNOSPAM{at}attglobal.net">tonyiNOSPAM{at}attglobal.net&g=
t;=20
      wrote in message news:3efc494a{at}w3.nls.net...Th=
e=20
      stock NT/W2K command line is protected mode Win32.  Running a =

      COMMAND.COM within that will fire up a DOS box."Paul =
Ranson"=20
      <paul{at}barkto.com>">mailto:paul{at}barkto.com">paul{at}barkto.com>
=
wrote in=20
      message news:3efc3404$1{at}w3.nls.net...=
>=20
      I missed the subtlety...>> But an
idle command line =
window=20
      requires no idle detection. The cleverness> is in detecting =
that a=20
      DOS app is idle while busy polling all its
inputs.>> =

      Paul>> "Robert Comer"
<bobcomer{at}mindspring.com>=20">mailto:bobcomer{at}mindspring.com">bobcomer{at}mindspring.com>=20
      wrote in message> news:3efb3466$1{at}w3.nls.net...=
>=20
      > > Check the 'misc' tab of the properties of a DOS app on =
an NT=20
      machine.> >> > I knew
it could do that, but =
that's=20
      something different than just a>
command> > line=20
      window.> >> > Of
course, if you create a new =
shortcut=20
      to command.com, you can change>
those> > settings =
for it,=20
      so I'll shut up . <g>>
>> > - Bob =
Comer>=20
      >> >>
>> > "Paul Ranson"
<paul{at}barkto.com>">mailto:paul{at}barkto.com">paul{at}barkto.com>
wrote in=20
      message> > news:3efb2fda$1{at}w3.nls.net...=
>=20
      > > Check the 'misc' tab of the properties of a DOS app on =
an NT=20
      machine.> > >>
> > Paul> >=20
      >> > > "Robert Comer"
<bobcomer{at}mindspring.com>=20">mailto:bobcomer{at}mindspring.com">bobcomer{at}mindspring.com>=20
      wrote in message> > > news:3efb1e2c$1{at}w3.nls.net...=
>=20
      > > > I think he's getting OS/2 mixed in there -- it had =
the=20
      ability to> adjust> >
> > idle detection in =
a DOS=20
      command line window.  If NT can do that too
I> > =
> >=20
      haven't run across it.> > >
>> > > =
> DOS=20
      box is just shorthand for a DOS command line window in either =
OS/2>=20
      > or> > > >
NT.> > > >> =
>=20
      > > - Bob Comer> > >
>> > =
>>=20
      >>=20
>>=


------=_NextPart_000_0027_01C33D52.CFD548E0--

--- BBBS/NT v4.01 Flag-4