From: "Kelly Harrelson" <ksharrel@!nospam!mindspring.com>
Newsgroups: comp.os.msdos.programmer,comp.os.msdos.djgpp,comp.os.ms-windows.programmer.misc
Subject: Re: 16-bit Apps under Windows NT
Date: Wed, 17 Feb 1999 14:25:09 -0500
Lines: 32
Message-ID: <7af508$jk$1@news0-alterdial.uu.net>
References: <7acb6p$9fk$1 AT news0-alterdial DOT uu DOT net> <7acv11$ef0$1 AT remarQ DOT com> <7adgtb$h94$1 AT samsara0 DOT mindspring DOT com> <7adnhs$42n$1 AT news DOT itis DOT com>
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

Tried both suggestions below, no luck.  Also, the Metaware High-C 16-bit
v1.6 compiler is no longer supported. Any more ideas?
-Shane

Joe Hagen wrote in message <7adnhs$42n$1 AT news DOT itis DOT com>...
>I've had this occur when using older 16-bit apps in NT also.
>
>There are two things you could try:
>
>    1.  Ensure the PATH is less than 128 characters.  You
>
>    2.  Eliminate excess environment variables, or ensure that no single
>         environment  variable exceeds 128 characters.  I recently
installed a package


>>>>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
>
>
>