Xref: utzoo comp.windows.ms.programmer:1108 comp.windows.ms:9854
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!udel!sbcs!sbstaff2!altman
From: altman@sbstaff2.cs.sunysb.edu (Jeff Altman)
Newsgroups: comp.windows.ms.programmer,comp.windows.ms
Subject: Re: Installation Problem
Message-ID: <1991Mar2.212712.17415@sbcs.sunysb.edu>
Date: 2 Mar 91 21:27:12 GMT
References: <1388@ssp18.idca.tds.philips.nl>
Sender: usenet@sbcs.sunysb.edu (Usenet poster)
Organization: State University of New York at Stony Brook
Lines: 23

In article <1388@ssp18.idca.tds.philips.nl> mm@idca.tds.PHILIPS.nl (M. Molenaar) writes:
>
>Well, I have found that the problem arises if the environment
>variable COMSPEC specifies that the COMMAND.COM is present in
>a SUBdirectory of the root, e.g. SET COMSPEC=c:\dos\command.com.
>So COMMAND.COM MUST be specified in the root. If not, the dos-
>prompt within Windows cannot start too and reports "Cannot find
>command.com".

MArco:
	The problem you are having is that the so called "DOS Prompt
in Windows" is really just an Icon in the Program Manager.  If you
use the properties command in the ProgMan you will find that the
File NAme is specified as C:\COMMAND.COM.  Therfore, if Command.com
is not in the specified location it will report that it cannot find
Command.com.  
	This has absolutely nothing to do with the specification 
of the COMSPEC variable.
	To fix it just change the file name to include the proper
path to your Command.com.

--
- Jeff (jaltman@ccmail.sunysb.edu)