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
X-Info: This message was accepted for relay by
	smtp03.mrf.mail.rcn.net as the sender used SMTP authentication
X-Trace: UmFuZG9tSVaLxNYt+MvCfwYBtkXKE9E1bUT9Pfv+z4p+orIf5tV3WtxVsGDmxcZn
Message-ID: <3F2A89E9.9050508@cygwin.com>
Date: Fri, 01 Aug 2003 11:40:25 -0400
From: Larry Hall <cygwin-lh AT cygwin DOT com>
Reply-To: cygwin AT cygwin DOT com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Terry Dabbs <tdabbs AT staktek DOT com>
CC: cygwin AT cygwin DOT com
Subject: Re: ncurses and terminal definitions
References: <3F29629E DOT 23CEFFE7 AT staktek DOT com> <3F296B2F DOT 3030309 AT cygwin DOT com> <3F29711D DOT 68FD15FD AT staktek DOT com> <3F298051 DOT 2010809 AT cygwin DOT com> <20030731210249 DOT GB12450 AT redhat DOT com> <3F2988BB DOT 2040806 AT cygwin DOT com> <3F299238 DOT 8D601F23 AT staktek DOT com> <3F2995C6 DOT 8030106 AT cygwin DOT com> <3F2A6C2C DOT 9B0C8F85 AT staktek DOT com>
In-Reply-To: <3F2A6C2C.9B0C8F85@staktek.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

OK, as long as you're aware of the restrictions and adhere to them, it
should work for you without mounting or creating a wrapper batch file.

Larry


Terry Dabbs wrote:

> Thanks for the clarification. These are pretty standard MS workstations regardless of
> the task we are using them for (wish it was linux...), so I can't help but use the
> default drive. So, although it may be something to be aware of, it does appear it is
> hard to screw it up.
> 
> Terry Dabbs
> 
> 
> Larry Hall wrote:
> 
> 
>>Terry Dabbs wrote:
>>
>>
>>>Thanks for the help. Since your advice kept me from having to "install" cygwin
>>>on the machines I'm going to run this on, the mounting, I suppose defaults to
>>>what it was on my compiling machine, which is the C drive for cygwin in my case.
>>>
>>
>>Actually, no.  I guess I wasn't clear.  Whether the file is found or not
>>depends on the current drive.  If the user's current drive is C: and you've
>>installed the file on the C drive, then the path will work.  Otherwise,
>>it will complain that the file isn't found.  If you want to avoid this,
>>you need to create the mount point I suggested or otherwise wrap your
>>application to make sure that C: is always the current drive when it
>>runs.
>>
>>--
>>Larry Hall                              http://www.rfk.com
>>RFK Partners, Inc.                      (508) 893-9779 - RFK Office
>>838 Washington Street                   (508) 893-9889 - FAX
>>Holliston, MA 01746


-- 
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
838 Washington Street                   (508) 893-9889 - FAX
Holliston, MA 01746


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