X-Spam-Check-By: sourceware.org From: "Gary R. Van Sickle" To: Subject: RE: cygwin bsod using make after configure on gcc Date: Thu, 9 Feb 2006 23:12:56 -0600 Message-ID: <003601c62e00$a7a194e0$020aa8c0@DFW5RB41> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <20060209235016.3984.qmail@web26304.mail.ukl.yahoo.com> X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk 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 > From: cygwin-owner AT cygwin DOT com > [mailto:cygwin-owner AT cygwin DOT com] On Behalf Of c c > Sent: Thursday, February 09, 2006 5:50 PM > To: cygwin AT cygwin DOT com > Subject: cygwin bsod using make after configure on gcc > > i've recently installed cygwin - i'm new to this so excuse me > if i'm in error > > after using configure on gcc-4.0.2, run make and my pc bsod's > > i'm using windows xp sp2 Windows XP BSODs for a number of reasons, none of them Cygwin-specific. I list them here in decreasing order of liklihood: 1. An uninstalled "Windows Update". 2. A faulty driver. 3. A defect in XP for which Microsoft offers no patch at the present time. 4. Faulty hardware. 99% of the time its 1 or 2, 1% of the time 3 or 4. The only other help anybody can offer is to look at the BSOD info. It used to tell you what kernel mode component was BSODing on you, but to tell you the truth it's been so long since I've seen one I don't know if it does anymore. If it does, it will probably be a driver, and then you're 99% of the way towards a solution. Hey, this would make a reasonably good Not-Entirely-Infrequently-Asked-Question. -- Gary R. Van Sickle -- 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/