X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
From:	"Dave Korn" <dave DOT korn AT artimi DOT com>
To:	"'Dirk Napierala'" <Dirk DOT Napierala AT oracle DOT com>
Cc:	<cygwin AT cygwin DOT com>, "'EVERS,DIRK'" <DIRK DOT EVERS AT oracle DOT com>,
	"'ZELL,VOLKER'" <DR DOT VOLKER DOT ZELL AT oracle 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>
Subject:	RE: Problem to open big selfextracting Zip files from bash - starting from scratch :-)
Date:	Thu, 25 Sep 2008 13:29:05 +0100
Message-ID:	<022201c91f0a$4cd102f0$9601a8c0@CAM.ARTIMI.COM>
MIME-Version:	1.0
X-Mailer:	Microsoft Office Outlook 11
In-Reply-To:	<48DB6E9C.4050302@oracle.com>
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

Dirk Napierala wrote on 25 September 2008 11:58:

> it is more the fact that settings
> like /3GB flag in boot.ini are out of our control (you know huge
> company's and internal politic restrictions

  Yeh, gotcha.

> Anyway even if this would help, it doesn't explain, why on the same
> system, without any other change than
> switching the cygwin versions, it works with the old one and doesn't
> work with the current one.

  Yeh, there must be some kind of different memory layout going on.  Have you
run the rebaseall procedure on either/both of the installations?

>>   Random and wacky idea: What happens if you prepend Cygwin's
>> /bin/unzipsfx.exe to the existing SFX and try running that?
>> 
> 
> If we test it try to do it using unzip or cmd /c for example it is
> working fine.
> But also at this point would not help us as a workaround due to the fact
> that
> the SFX file is called withing cygwin bash by a another (out of our
> control) programm that we can not change ourself.

  Yes, but can you not preprocess the sfx files before handing them over to
that other program?  You don't need to worry about stripping off the native
sfx header either, it should just work to prefix the cygwin one.

    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


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

- Raw text -