X-Spam-Check-By: sourceware.org Date: Mon, 27 Nov 2006 13:01:29 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: 1.5.22: Error from anything using the cygwin dll Message-ID: <20061127180129.GA5404@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <666554 DOT 84409 DOT qm AT web52102 DOT mail DOT yahoo DOT com> <009701c71231$76e0a600$a501a8c0 AT CAM DOT ARTIMI DOT COM> <20061127153238 DOT GB32354 AT trixie DOT casa DOT cgf DOT cx> <456B17E7 DOT 9070802 AT cygwin DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <456B17E7.9070802@cygwin.com> User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Mon, Nov 27, 2006 at 11:52:55AM -0500, Larry Hall (Cygwin) wrote: >Christopher Faylor wrote: >>On Mon, Nov 27, 2006 at 02:36:45PM -0000, Dave Korn wrote: >>>On 27 November 2006 14:06, Mikkel Erup wrote: >>> >>> >>>>Making sh.exe a copy of bash.exe and running the installer to >>>>reinstall produces the same error for bash.exe, ash.exe, sed.exe, >>>>sh.exe, rm.exe, cmp.exe and a some others (The instruction at >>>>"0x6100365f" referenced memory at "0x006ada90". The memory could >>>>not be "written"). Will try booting to safe and install from >>>>the hdd to see if it lets the installer complete. >>>>I am also wondering why cygwin works if I boot to safe mode >>>>without network. As I said it doesn't work if I boot to safe >>>>mode with network. >>> You wouldn't by any chance be using any kind of firewall or internet >>>security packages, would you? Something by Norton/McAffee, perhaps? >> >>And, this wouldn't be a situation of multiple cygwins on the machine, >>would it? >> >>And, as has been previously requested, cygcheck output would be useful. > > >Actually, Mikkel was good enough to provide the 'cygcheck' output with his >original message. :-) > > Huh! Well, it's hardly *my* fault that I have to scroll down in the archives to see the attachment. Ok, well, maybe it is my fault, but they really should improve the archives so that it is clear that there is an attachment. Ok, well, maybe I'm responsible for the format of the archives but... . . . I got nothin'. Sorry for missing this. I would still do a check for other copies of cygwin1.dll however. >There's no other cygwin1.dll found, though that was my first thought too. > >I'm with Dave and Mikkel in believing that the difference between safe mode >and not is significant. I'm betting on virus scanners/firewalls or some >network driver. The address in question is in cygwin's cygthread handling code. Historically, this has been affected by things like scanners/firewalls and special drivers, so this is a good thought. I have seen something like this myself in the past but it was so sporadic that I was never able to track it down and I haven't seen it in months. cgf -- 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/