Date: Thu, 9 Oct 2008 12:10:00 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Problem to open big selfextracting Zip files from bash - 	starting from scratch :-)
Message-ID: <20081009161000.GH13923@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <48DA7010 DOT 8000003 AT oracle DOT com> <20080924170655 DOT GB24085 AT ednor DOT casa DOT cgf DOT cx> <48DB51D2 DOT 1040909 AT oracle DOT com> <01fa01c91ef1$4875a170$9601a8c0 AT CAM DOT ARTIMI DOT COM> <48DB6E9C DOT 4050302 AT oracle DOT com> <20080925143235 DOT GD21100 AT ednor DOT casa DOT cgf DOT cx> <48EDD41B DOT 7050701 AT oracle DOT com> <20081009141610 DOT GF13923 AT ednor DOT casa DOT cgf DOT cx> <48EE19B4 DOT 5040805 AT oracle DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <48EE19B4.5040805@oracle.com>
User-Agent: Mutt/1.5.16 (2007-06-09)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On Thu, Oct 09, 2008 at 04:48:20PM +0200, Dirk Napierala wrote:
>Christopher Faylor schrieb:
>>>If I missed feedback to the thread below I have to apologize.
>>>Otherwise I would like to recall this (my last post)again
>>
>>This is getting old.  Rather than repeatedly apologize for
>>theoretically not reading a response, go back through the responses and
>>make sure of the fact yourself.
>>
>>I think that where it stands right now is that no one has a 1.5G
>>self-extracting zip file to play with to confirm or deny your findings.
>>
>>If this is vitally important, you might consider purchasing a support
>>contract with Red Hat.
>
>Thats what I did, and I did not found a reply to my findings which I
>stated in http://cygwin.com/ml/cygwin/2008-09/msg00545.html together
>with the requested files which allows trobleshooting.....

Yes.  Sometimes that happens.  People stop responding.  Maybe we have no
further insight or maybe we got tired of your inability/reluctance to
perform all of the tests that we were asking for.

>It is nailed down to the cygwin1.dll

While it is interesting that you were able to narrow it down to a DLL,
there were too many changes between the two versions that you found for
this to be a useful debugging technique.

>I assume that it should not be a big deal for someone who is a
>developer to create such a SFX file on its own for testing.

Interesting assumption.

>If it is a problem, I can provide the original file causing the problem
>to a location of your choice.  If you do not have free space avail to
>allow me put the file to, please let me know and reply to my company
>mail address.  I will than put it on our ftp server and make it avail
>for your eyes only.  You may understand that this is company
>confidential.

This is more work than I, personally, am able to take on.  That's why I
suggested investigating a support contract.

As I mentioned early on, even if this was determined to be a problem in
Cygwin 1.5.x, we're not going to release a new version of the 1.5 series
so it isn't clear how you'd proceed even if we did find a solution.

cgf

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