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/
