Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <3F29629E.23CEFFE7@staktek.com>
Date: Thu, 31 Jul 2003 13:40:30 -0500
From: Terry Dabbs <tdabbs AT staktek DOT com>
X-Accept-Language: en
MIME-Version: 1.0
To: "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject: ncurses and terminal definitions
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


I've been using gcc to compile some simple applications for NT win98 and
win95 for automating machinery. I have a problem on one screen where you
can't read the command.com screen (windows98) clearly, so I loaded
ncurses, redid the application so it the text is very bright and
colorful even on the poor screen. Very nice.
The problem is, I was up to now only needing to place the cygwin1.dll on
each machine I put a program on, and that's all, with the exception of
the executable and miscellaneous setup files. I thought I would only
have to place the cygncurses7.dll on the machines as well.
I moved the executable and placed cygncurses7.dll on a machine, tried
it, and got "Error opening terminal: cygwin". I read references to this
in the mailing lists, which say do an "install" on each machine with
multiple packages using setup.
For a number of reasons I wish to avoid this, the least of which is they
are not on the net.
What is the least amount of files I need, and where should I put them
for ncurses to identify the terminal on the machines I need to put my
executable? Can you help?

Thanks

Terry Dabbs


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/