Xref: utzoo comp.windows.ms:6146 comp.os.os2.misc:295
Path: utzoo!attcan!uunet!timbuk!cs.umn.edu!uc!tut.cis.ohio-state.edu!usenet.ins.cwru.edu!abvax!icd.ab.com!jaz
From: jaz@icd.ab.com (Jack A. Zucker)
Newsgroups: comp.windows.ms,comp.os.os2.misc
Subject: Windows 3 and OS/2 problem
Message-ID: <1913@abvax.UUCP>
Date: 11 Oct 90 12:44:25 GMT
Sender: news@abvax.UUCP
Reply-To: jaz@icd.ab.com (Jack A. Zucker)
Organization: Allen-Bradley Company, Industrial Computer Division
Lines: 27

I don't know whether this is a Windows bug or an OS/2 bug. Me thinks it's
a Windows Bug. I have OS/2 v1.2 and Windows 3 residing on my system. I use
the dual boot feature to boot into either Dos or OS/2. My config.sys for
dos uses "shell=c:\dos\command.com" and my autoexec.bat uses 
"set COMSPEC=c:\dos\command.com". Windows 3 runs fine except that when
you try to invoke a DOS window, it always uses the copy in the root directory.
Even if I specify to run \dos\command.com. The solution (kludgy) was to copy
command.com from \dos to the root directory in my autoexec.bat. The dual boot
feature of OS/2 copies (among other things) it's own version of command.com
to the root directory so it runs OK. 

The rest of system runs fine in standard DOS mode with a different version
of command.com (OS/2's) in the root directory because of my comspec and
shell command. Why doesn't MS Windows listen ?

Of course, why doesn't the "boot /dos" command from OS/2 copy command.com from
the \dos directory. I think it's two bugs !


-Jaz


| Jack A Zucker	                 {cwjcc,pyramid,decvax,uunet}!jaz@icd.ab.com |
| Allen-Bradley Company, Inc.     or                       ICCGCC::ZUCKER    |
| 747 Alpha Drive                 
| Highland Hts., OH 44143         phone: (216) 646-4668   FAX: (216)
646-4484 |