Subject: RE: Problem to open big selfextracting Zip files from bash - starting from scratch :-)
From: "Dave Korn" <[email-masked]>
To: "'Dirk Napierala'" <[email-masked]>, <[email-masked]>
Cc: "'EVERS,DIRK'" <[email-masked]>, "'ZELL,VOLKER'" <[email-masked]>
Date: Thu, 25 Sep 2008 10:29:56 +0100
List-Id: <cygwin.cygwin.com>

Dirk Napierala wrote on 25 September 2008 09:55:

>  From what we understand by reading the guideline "Changing Cygwin's
> Maximum Memory" the result
> of the small program written by DJ Delorie  tests the memory allocation
> limit on your system.
> Running the program will output the maximum amount of allocatable memory
> of your system.
> Doing so on several test systems and the different cygwin versions the
> result is _always _1536.
> Trying it for example with 2500MB setting on a 4GB system also failed
> with "Cannot allocate memory".

  There is an upper limit imposed by the dividing point between kernel and
user space at the 2GB mark.  You can try adding the /3GB flag in boot.ini to
raise this by a further gig.  You might need also to make extensive use of
rebaseall to ensure your DLLs end up at the upper end of that range and don't
fragment the space, or it might not matter, depending on the patterns of
memory usage of the unpacker.

>> It probably will not make a difference but it seems like you really
>> should be trying to set the size to something noticeably larger than the
>> size of your gzip files. 
>> 
>> 
> Done, without success.

  This might then work better.

> So the SFX file itself doesn't seem to cause this problem.

  Random and wacky idea: What happens if you prepend Cygwin's
/bin/unzipsfx.exe to the existing SFX and try running that?

    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/