Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!asuvax!ncar!boulder!wallwey
From: wallwey@boulder.Colorado.EDU (WALLWEY DEAN WILLIAM)
Newsgroups: comp.windows.ms
Subject: Re: Windows term
Message-ID: <17915@boulder.Colorado.EDU>
Date: 8 Mar 90 00:08:26 GMT
References: <4362@cvl.umd.edu> <16557@orstcs.CS.ORST.EDU>
Sender: news@boulder.Colorado.EDU
Reply-To: wallwey@boulder.Colorado.EDU (WALLWEY DEAN WILLIAM)
Organization: University of Colorado, Boulder
Lines: 40

In article <16557@orstcs.CS.ORST.EDU> larsen@mist.CS.ORST.EDU (Scott Larsen) writes:
>Is there such a thing as a dos shell under ms windows?  I am a user of
>X windows and am used to doing stuff in a "normal" shell like structure
>like xterm.
>
>Is there anything out there or is this just a pipe dream?
>
>-Scott Larsen
>larsen@cs.orst.edu                       UUCP: hplabs!hp-pcd!orstcs!larsen
>--------------------------------------------------------------------------
>"Open the pod bay doors, Hal."
>		- David Bowman

	If I am understanding your question right, you basically want to
run DOS's COMMMAND.COM in a window.  I do this all the time.  All you need
to do, is create a COMMAND.PIF file for COMMAND.COM.  Use the
PIFEDIT.EXE program that came with windows.  The nice thing about COMMAND.COM
is that it actually comforms to all of window's requirements for running
in a window (at least as far as I know). You can use the PIFEDIT's
defaults (of course after filling the in the balnks at the top), and then
make sure you UNCHECK "Directly writes to SCREEN [ ]". After you save
the COMMAND.PIF file with the other *.PIF files you have, you can
just start up command.com from either the MS-DOS Executive, or on the 
command line when starting windows like "WIN COMMAND", or even modify
part of your WIN.INI file so command starts up when windows does.

The neat thing about doing this is, you can run several "DOS windows
at once".

Some helpful hints:
1) The COMMAND.PIF needs to be in the directory where windows looks for 
   PIF files when not running "Windows applications".

2) You should also make .PIF files for non resident commands.

3) Command.com runs slowly "in a window".

4) Experiment!!!!

		Dean