Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
X-Injected-Via-Gmane:	http://gmane.org/
To:	cygwin AT cygwin DOT com
Path:	not-for-mail
From:	Danilo Turina <danilo DOT turina AT alcatel DOT it>
Subject:	Re: xinted rsync bluescreen
Date:	Thu, 16 Jan 2003 14:27:06 +0100
Lines:	38
Message-ID:	<3E26B32A.4090806@alcatel.it>
References:	<5 DOT 2 DOT 0 DOT 9 DOT 2 DOT 20030113102404 DOT 029296d0 AT pop3 DOT cris DOT com> <000401c2b846$48882a60$0201a8c0 AT sos> <59A835EDCDDBEB46BC75402F4604D5528F75CC AT elmer> <005001c2b841$b3f55520$4d1f1cac AT THEODOLITE> <000401c2b846$48882a60$0201a8c0 AT sos> <5 DOT 2 DOT 0 DOT 9 DOT 2 DOT 20030113102404 DOT 029296d0 AT pop3 DOT cris DOT com> <5 DOT 2 DOT 0 DOT 9 DOT 2 DOT 20030113105240 DOT 01e1f660 AT pop3 DOT cris DOT com> <20030113185823 DOT GA180863 AT WORLDNET> <avva35$1sl$1 AT main DOT gmane DOT org> <b03r0e$3nv$1 AT main DOT gmane DOT org> <3E2660BC DOT 1080709 AT alcatel DOT it> <b069a2$jol$1 AT main DOT gmane DOT org>
Mime-Version:	1.0
X-Complaints-To:	usenet AT main DOT gmane DOT org
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130
X-Accept-Language:	it, en-us, en
In-Reply-To:	<b069a2$jol$1@main.gmane.org>

Dan Holmsand wrote:
> Danilo,
> 
> Danilo Turina wrote:
> 
>> I also have a very similar problem (writing in /etc when X is running, 
>> always cause a BSOD, regardless of antivirus packages), if I can have 
>> that hacked cygwin1.dll I can try it on my systems and tell if it's 
>> the same problem.
> 
> 
> Sure. I'll send you one in private mail.
> 
> /dan

Thank you. I tried the patched cygwin1.dll and BSOD not occurred (even 
with McAfee enabled).

After replacing the original cygwin1.dll BSOD not occurred anymore.
But note that this happened to me also in the past, i.e. in some cases 
(e.g. entirely disabling antivirus or with other tries) I was able to 
avoid BSOD.

When this happened to me, restoring the original conditions did not 
immediately cause BSOD to reappear immediately, but only after a while.

Unfortunately I'm unable to understand what made the BSOD reappear (or 
what delayed it). I only had the sensation that once avoided the BSOD 
the first time, the system does not BSOD anymore even if the previous 
situation is restored (I think until a reboot). It is somewhat like the 
first time an handle must be requested or some resource must be 
allocated if this succeeds, the next time the system does not need 
anymore to perform that operation.

Ciao,

			Danilo



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -