Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com To: cygwin Subject: Re: Can't run Macro Express from within Cygwin bash shell References: <86hedtdxiz DOT fsf AT ls-jtwilley DOT brightmail DOT com> From: Jack Twilley X-Attribution: Jack Date: Wed, 04 Dec 2002 19:09:25 -0800 In-Reply-To: (Michael A Chase's message of "Wed, 4 Dec 2002 18:44:19 -0800 (PST)") Message-ID: <86el8xduvu.fsf@ls-jtwilley.brightmail.com> User-Agent: Gnus/5.090008 (Oort Gnus v0.08) XEmacs/21.1 (Cuyahoga Valley, i386--freebsd) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii >>>>> "Michael" == Michael A Chase writes: [...] Michael> If it's a MSDOS/Windows executable, it won't know anything Michael> about Cygwin paths. Getting backslashes (\) right can be Michael> rather tricky in a shell environment, so what I'd suggest is Michael> something like this: Michael> # A DOS program won't understand Cygwin file specifications Michael> mex=$(cygpath -w -a Michael> /cygdrive/j/diesel/scripts/PerfmonMacros.mex) Michael> # Use a Cygwin path for the shell to find the program Michael> "/cygdrive/c/Program Files/MacroExe/meproc" /F$mex Michael> /APerfMonInit Your solution works with a local bash shell but not a remote one. Any idea why? While logged in remotely, I can ls both the binary and the macro file, so it's not a permissions thing, or I don't think it is anyway. Jack. (never the easy questions) -- Jack Twilley // Tier 2 Support Engineer // Brightmail Inc. jtwilley at brightmail dot com -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/