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:	<200205300824.g4U8OQQ05854@mail020.syd.optusnet.com.au>
Mime-Version:	1.0
From:	Mitch Davis <mjd AT alphalink DOT com DOT au>
To:	"Larry Hall (RFK Partners, Inc)" <lhall AT rfk DOT com>
Cc:	cygwin AT cygwin DOT com, mjd AT alphalink DOT com DOT au
Date:	Thu, 30 May 2002 18:24:26 +1000
Subject:	RE: 1.3.10: SendMessage(WM_COPYDATA) in a Win32 program fails
	within Cygwin

> -----Original Message-----
> From: Larry Hall (RFK Partners, Inc) [mailto:lhall AT rfk DOT com]
> 
> At 12:50 PM 5/29/2002, Mitch Davis wrote:
> >
> >I would like to use plink (a command-line 
> >SSH program from the "PuTTY" suite) to 
> >connect my W2K PC to a Linux host, using the 
> >ssh v2 protocol, and RSA keys, via the 
> >"pageant" key agent. 
> >
> >I would also like to be able to invoke plink (a 
> >conventional "console" Win32 app) both from a 
> >W2K cmd.exe window, and from a bash window. 
> >
> >My problem is, plink works under cmd.exe, but doesn't 
> >work under bash.  It also doesn't work if I invoke 
> >cmd.exe inside bash, then invoke plink from the cmd.exe. 
> >By "doesn't work", I mean plink is unable to fetch any 
> >keys from "pageant", the SSH key agent. 

[lots deleted]

> >My questions: 
> >
> >  - Do you know what the problem might be? 
> 
> Perhaps.
> 
> >  - Do you know what might be causing SendMessage to 
> >    fail?  (I'm not a Windows programmer). 
> 
> Yes.  I expect it's that send message expects there is a 
> window to process this message, with its own message loop.
> cmd.exe may provide one.  Cygwin does not.  

That's a good hypothesis; I've sent it to the PuTTY people.

As I mentioned yesterday, if I invoke bash, then cmd.exe,
then plink, the problem still happens.  But this might be
because a secondary cmd.exe is somehow different to a primary
cmd.exe.

So today I invoked cmd.exe, then bash, then plink.  Same
problem.  Then I invoked cmd.exe, then bash, then cmd.exe
then plink.  Also the same problem.

Do you know how I can further test your hypothesis?

Regards,

Mitch.
---
mailto:mjd AT alphalink DOT com DOT au

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

- Raw text -