From:	"Kelly Harrelson" <ksharrel@!nospam!mindspring.com>
Newsgroups:	comp.os.msdos.djgpp
Subject:	16-bit Apps under Windows NT
Date:	Tue, 16 Feb 1999 16:51:24 -0500
Lines:	27
Message-ID:	<7acp66$ig3$1@news0-alterdial.uu.net>
NNTP-Posting-Host:	208.218.107.9
X-Newsreader:	Microsoft Outlook Express 4.72.3155.0
X-MimeOLE:	Produced By Microsoft MimeOLE V4.72.3155.0
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

I have an *old* 16-bit cross compiler that runs under DOS and generates
.OBJs for a proprietary platform.  The compiler worked fine under DOS,
Windows 3.11, and Windows 95.  When we moved to Windows NT, we ran into
problems.  Running it under the default shell, cmd.exe
(\winnt\system32\cmd.exe), would cause the entire shell to exit, instantly,
with no error messages or anything.  One of our developers noticed however
that it ran fine under the command.com shell (\winnt\system32\command.com).
So, we happily continued using it under the alternate shell.  Now, with
Windows NT Service Pack 4 installed (as well as Developer Studio 97 Service
Pack 3, although I don't know if that could effect it), it has stopped
working, but not in the same way as before.  When calling the compiler from
a batch file, the batch file just exits and the shell stays intact.  Calling
the compiler from NMAKE just causes NMAKE to hang.

Has anyone else noticed any problems with older 16-bit apps?  Anyone have
any ideas? Does anyone know why it worked for a while under command.com but
not cmd.exe?

If there is another group I should post this to, please let me know.  This
problem is quite frustrating and I would really like to get it solved.  Any
help would be appreciated.

Thanks in advance.
-Shane

- Raw text -