Message-ID: <5146B4FF.3090307@gmail.com>
Date: Mon, 18 Mar 2013 07:32:31 +0100
From: marco atzeri <marco.atzeri@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: problems with COM running native win32 applications through cygwin's bash
References: <CAH+_n-5pucx9OyqyLu4ZN99Z-cFjYgYiP4ZSbiXGHmD9QmeQiw@mail.gmail.com>
In-Reply-To: <CAH+_n-5pucx9OyqyLu4ZN99Z-cFjYgYiP4ZSbiXGHmD9QmeQiw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On 3/18/2013 7:26 AM, Edward Peschko wrote:

> to get a native 64 bit environment, which allows the COM calls to
> happen for diskshadow.
>
> I'm assuming that there isn't a 64 bit cygwin port? I would think that
> would solve lots of issues - the number of native 32 bit installations
> is dropping rapidly, and I think that going forward issues like the
> above will become more and more common.

not yet, it is on first infancy steps:
http://cygwin.com/ml/cygwin-apps/2013-03/msg00070.html

>
> Ed


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