Xref: utzoo comp.windows.ms.programmer:1061 comp.windows.ms:9755
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!samsung!uunet!mcsun!hp4nl!philapd!ssp18!mm
From: mm@idca.tds.PHILIPS.nl (M. Molenaar)
Newsgroups: comp.windows.ms.programmer,comp.windows.ms
Subject: Installation Problem
Message-ID: <1388@ssp18.idca.tds.philips.nl>
Date: 28 Feb 91 13:48:39 GMT
Organization: Philips Information Systems, Apeldoorn, The Netherlands
Lines: 23


Yesterday (27 febr 91) I wrote an article about an installation
problem were I had problems with changing diskettes within
Windows 3.0. Windows generated a system message "Cannot read from
drive A:".
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".

Can anyone tell me if this is really a solution or only a bypass?
If a DOS application runs under Windows, apparently the
environment settings are (re)set to default. 
So COMSPEC will be set to C:\COMMAND.COM.

How can I tell to Windows to use the environment variables
specified in config.sys and autoexec.bat ?

Kind regards,

Marco