This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: ncurses and terminal definitions

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                    
> RFK Partners, Inc.                      (508) 893-9779 - RFK Office
> 838 Washington Street                   (508) 893-9889 - FAX
> Holliston, MA 01746

Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]