Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Thu, 15 Feb 2001 16:22:55 EST X-Mailer: Virtual Access by Atlantic Coast PLC, http://www.atlantic-coast.com/va Message-Id: To: cygwin Subject: Re: Fatal exception SYMEvent at boot time. In-Reply-To: <4.3.1.2.20010215143526.04a66128@pop.ma.ultranet.com> From: Brian Keener Reply-To: bkeener AT thesoftwaresource DOT com Larry Hall wrote: > I find it hard to believe that it could > be affecting your situation, although it depends on precisely where you get > your blue-screen I suppose. I too thought it unlikely that it could affect it but I was unsure as to whether cygwin ever ever puts anything into \windows although I felt sure it did not. I was just asking on the possibility someone might recognize SYMEvent. > What O/S are you running? I am running Win95 - but we may have found it. We are testing the theory now and as we all suspected if it is what we think it is *not* Cygwin related and my apologies for cluttering the newsgroup. I mentioned it to someone else here and they say - "gee sounds like SYMantec" and then I remembered I also installed latest patch to Norton Antivirus (because of Anna Kournikova virus) Monday - about the same time this started. I have currently disabled Norton and I have booted several times to see what affect and so far have not seen. > Perhaps a cygcheck -s -r -v would be helpful? You are correct - it would have been and I thought about but failed to follow through on my thought. My apologies. -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple