Path: utzoo!attcan!uunet!husc6!ogccse!metheus!todd
From: todd@metheus.UUCP (Todd Stewart)
Newsgroups: comp.sys.ibm.pc
Subject: Re: using a shell within MS-Windows
Message-ID: <148@metheus.UUCP>
Date: 8 Nov 88 17:57:14 GMT
References: <75496@sun.uucp> <41898@yale-celray.yale.UUCP>
Reply-To: todd@metheus.UUCP (Todd Stewart)
Organization: Metheus Corporation, Portland Or.
Lines: 35

In article <41898@yale-celray.yale.UUCP> spolsky-joel@CS.YALE.EDU (Joel Spolsky) writes:
>In article <75496@sun.uucp> sears@sun.uucp (Daniel Sears) writes:
>| 							Are there any
>| terminal programs for MS-Windows that allow a user to invoke the DOS
>| command.com interpretor (or better yet, MKS Korn shell)?
>
>Just double click on COMMAND.COM to get a command-line interpreter in
>a window. I don't know about Ksh.
>
	Or if you want a really large command.com session so you
	can run a "real" program in the middle of a windows session,
	try the following:

	Use PIFEDIT to create a command.pif with these attributes:

		Memory Required		640K
		Memory Desired		-1K
		Modifies Screen		yes
		Modifies Memory		yes

	When you double click on this COMMAND.PIF the windows kernel
	will swap itself out to disk, and spawn a child command.com 
	with all memory available to it less about 12K.  Just type
	exit when you're through, and windows pops back up the way
	you left it.

	The only bad news is that you have to close any other windows
	apps (except MS-DOS EXEC) before you can do it.

	Yes, I know you could do the same thing by exiting windows
	and coming back in again later, but doing it this way is
	faster.

-Todd Stewart
 Metheus Corporation