Xref: utzoo comp.windows.ms:9026 comp.os.msdos.programmer:3161 comp.sys.ibm.pc.misc:6183
Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!clyde.concordia.ca!nstn.ns.ca!news.cs.indiana.edu!know!zaphod.mps.ohio-state.edu!maverick.ksu.ksu.edu!doc.ksu.ksu.edu!neil
From: neil@doc.ksu.ksu.edu (Neil Erdwien)
Newsgroups: comp.windows.ms,comp.os.msdos.programmer,comp.sys.ibm.pc.misc
Subject: Re: NDOSEDIT type utility that works with multiple Windows 3.0 DOS boxes??
Message-ID: <1991Feb5.221059.20123@maverick.ksu.ksu.edu>
Date: 5 Feb 91 22:10:59 GMT
References: <1991Jan31.182859.26865@imagen.com>
Sender: news@maverick.ksu.ksu.edu (The News Guru)
Organization: Kansas State University
Lines: 25

In article <1991Jan31.182859.26865@imagen.com> glenn@imagen.com (glenn boozer) writes:
>When I have two or more DOS boxes running in WINDOWS 3.0 at the same time and I
>UP-Arrow NDOSEDIT, Windows gets very upset and terminates my DOS Box(s).
>
>Is there a Dos Command Line Editor that is Windows 3.0 DOS Box compatible?
>
>THanks
>
>Glenn Boozer
>glenn@imagen.com

The problem is that the command editor is being confused because it it being used
from two separate windows.  Both CED and PC Mag's CMDEDIT have the same "problem".

The solution is to follow Microsoft's advice and not load such TSRs in the
AUTOEXEC.BAT.  Instead, create a batch file that loads the TSR and then runs
COMMAND.COM.  [I believe there is a parameter needed to make COMMAND.COM enter
its interactive mode.  /C?  I'm not at my micro, so I can't check.]  

Next, make the DOS icon in the program manager run the batch file, and you're set.
--
Neil Erdwien
Kansas State University
neil@ksuvm.ksu.edu