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
Message-Id: <5.1.0.14.2.20020815085006.01fa35d8@pop3.cris.com>
X-Sender: rrschulz AT pop3 DOT cris DOT com
Date: Thu, 15 Aug 2002 08:58:17 -0700
To: cygwin AT cygwin DOT com, crossgcc AT sources DOT redhat DOT com
From: Randall R Schulz <rrschulz AT cris DOT com>
Subject: RE: Cygwin takes *forever* to run gcc's configure!
In-Reply-To: <4A798B3E3B58794FB40A47DFCE728BA8485453@STR1VEXC002.CTHES.C
 OM>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

Hi,

The Norton AntiVirus controls offer you a direct and "sanctioned" way to 
disable or suspend virus checking without resort to subterfuge such as 
invoking the debugger (assuming you have it installed, that is--is that 
option even available if you don't have a debugger installed on your 
system? I don't think so, but I'm not going to uninstall Visual C++ just to 
find out...).

Personally, I don't enable my Norton Anti-Virus for continual monitoring. I 
only use it on demand, either to make a full sweep (on rare occasions) or 
when I receive a file that I find suspicious. I've never had an active 
infection and only rarely have I ever discovered a virus in the first 
place. Discounting the obvious ones, I could (if my memory were perfect) 
almost certainly count on one hand the number of times I found a virus when 
I wasn't already expecting one.

Randall Schulz
Mountain View, CA USA


At 08:26 2002-08-15, Jimm Burk wrote:
>Dan,
>
>Are you using win2K?  if so start the task manager and switch to
>processes:
>
>If you are using Norton Antivirus you will find a process NOPDB.EXE which 
>has something to with Norton.  Check the process time of all the running 
>processes and you may find the culprit.  In my case it has always been the 
>NOPDB.  Which, by the way you CANNOT kill directly. :( Right click the 
>process and say debug.  You can then stop the process and low and behold 
>cygwin will start moving again.  This seems to appear more on the 
>non-Intel processors, I have no idea why.
>
>Regards,
>Jimm Burk


--
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/