From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,5f05fd52c45de56c
X-Google-Attributes: gid103376,public
From: radke@dsdl.ee.iastate.edu (Kevin Radke)
Subject: Re: ObjectAda and ANSI.SYS
Date: 1998/06/19
Message-ID: <6medqi$t78$1@news.iastate.edu>#1/1
X-Deja-AN: 364282744
References: <35879521.65EE@ddre.dk>
 <1998061820484300.QAA03489@ladder03.news.aol.com>
Organization: Iowa State University, Ames, IA  USA
Newsgroups: comp.lang.ada
Date: 1998-06-19T00:00:00+00:00
List-Id: <comp.lang.ada>


In article <1998061820484300.QAA03489@ladder03.news.aol.com>,
John Herro <johnherro@aol.com> wrote:
>Hans Marqvardsen <hm@ddre.dk>
>is having trouble running a program
>that requires ANSI.SYS under Windows NT.
>
>Running a program that needs ANSI.SYS under Windows NT is a hassle, but it can
>be done.  My AdaTutor program is one such program, and, while it's easy to
>install ANSI.SYS for Windows 95, several customers called me because of
>difficulty running the program under Windows NT.  (BTW, we're working on a
>Windows version, to be called AdaEase, which of course won't need ANSI.SYS). 
>Here are the steps to follow:
>
>1.  Make a subdirectory and copy your executable and all related files to it.
>2.  Copy CONFIG.NT to this directory from C:\WINNT\SYSTEM32\CONFIG.NT.
>3.  Edit the copy of CONFIG.NT in this directory, adding the line
>         device=C:\WINNT\SYSTEM32\ANSI.SYS
>4.  Right click on the icon for the executable file.
>5.  Click Properties, then click the Program tab.
>6.  Click the button at the bottom that says Windows NT ...
>7.  Change the Config filename to the CONFIG.NT file in this directory.  For
>example, if this directory is C:\TEMP, change the Config filename to
>C:\TEMP\CONFIG.NT.
>8.  Double click the icon for the executable file to run the program.
>
>It's a mess compared to doing the same thing with Windows 95, but it can be
>done.

This doesn't work with 32bit windows "console" applications, which
is what OA is producing.  I.E. 32bit programs do not have a "program"
tab in properties...

Kevin