Massive problems with Cygwin (fixed)

[Berki]

Hi!

I have Outpost Firewall 4.0 RC3.1 (4.0.954.6918 (582)) installed and unfortunately this causes massive problems with my CygWin installation I am really dependend on. When I start CygWin an "unhandled win32 excpetion" occours in bash.exe.

Please fix this problem in the next release canditate because a lot of users need Cygwin. If there is a workaround, please tell me (disabling the firewall didn't help)!

I would really appreciate any help!

Daniel

[hayc59]

Daniel, Welcome to the forum
Please send problems to:
Bug Submit Form

[GwenDragon]

Problem not solved in Outpost 4 Final!

[jcc3]

Unistalling Outpost solves the problem. Apparently, outpost hooks on ntdll.dll and/or kernel32.dll kill cygwin. Is there another solution?

[BZwart]

Same problem here, uninstalling OP 4.0 final and going back to 3.5 solves the problem.

PS. I have send in a bug report

[Fazion]

Cygwin based products such as Avi2DVD does not work either.

Hmm, seems to be a rather new phenomenon - RC3 does not have this problem.

I have already submitted a bug report. Hopefully this will get fixed soon.

[Pokinpo]

Guys,
I do not currently use Cygwin products, but have in the past and know that lots of people do. Please report this bug - otherwise, Agnitum may never become aware of the issue.

[jcc3]

I filed a bug report and then sent support the information they requested. We'll see what happens . . .

[ronaiml]

Hi,

I install the new outpost 4.0 and my cygwin was block.
I disable outpost and new functions and nothing!
I put bash as trust applicantion and nothing!
Why ?

In attachments we show dr.watson log:

portuguese !!!

Exceção de aplicativo:
Aplicativo: C:\cygwin\bin\bash.exe (pid=3008)
Data e hora: 29/9/2006 às 22:05:38.406
Número da exceção: c0000005 (violação de acesso)

[john5]

I can also confirm this issue. Any news on a fix yet?

[don@as]

Confirm this problem too. Cygwin is totally blocked.

[jcc3]

According to tech support, "The information was sent to developers. We'll continue the investigation of the problem."

MSYS ( http://www.mingw.org/ ) seems to work.

[GwenDragon]

Originally Posted by jcc3

MSYS ( http://www.mingw.org/ ) seems to work.

Well, MSYS is NOT the same as cygwin.
I use the Cygwin-X-Server for connections from Windows to Linux and other cygwin tools like unter Unix.

[thecon]

This has also been reported in the past, but I would like to refresh it.

As a beta tester, I noticed that when I installed cwRsync Server, it crashed upon receive an incoming connection and posted a cwRsync Server specific bug.

However, I only today needed to use rsync.exe as well to check a remote machine's files, but it also crashed. It turns out that not only rsync.exe has a problem with Outpost Firewall 4.0, but many (perhaps ALL) cygwin applications (rsync.exe needs cygwin1.dll in order to work).

The strange thing is that cygwin applications seem to work on Outpost Firewall 3.51, so this crash might be a new feature's bug.

Unfortunately this cannot be solved by configuration changes. I devoted more than a day on that, and it seems that this must be fixed only by the development Gods

The closest thing to a fix I was able to find was
http://outpostfirewall.com/forum/showthread.php?t=12472

but this hack refers to an older version of Outpost Firewall. Seems that cygwin is a bit of a headache for Agnitum since Outpost Firewall's birth

Oh well, let's hope it gets fixed.

Cheers
Themistoklis Economou

[andy_kim]

Hi guys,

after upgrading OP to version 4 (downloaded yesterday) on a Win XP-SP2 system with all the latest patches cygwin shell and tools do not work anymore, because of not being able to access their stacks. No configuration in OP helped.
As the cygwin tools a essencial on the systems I needed to downgrade to 3.51 again. But after restarting OP kept itself busy with consuming 80-90% cpu time.
No remove/reinstall helped. Only restoring a backup-image solved the problem to go back to version 3.51.

On a second fresh installed system with SP2 and all patches and OP4 the install of cygwin produced that error in the postinstall phase, when all the postinstal scripts need to be run by the shell, which terminates with the described error. Cygwin fresh downloaded - so newest version. Same procedure with the downgrade.

Anyone seen this before? Anyone with a solution?

Cheers, Andreas