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-Authentication-Warning:	slinky.cs.nyu.edu: pechtcha owned process doing -bs
Date:	Sun, 12 Jan 2003 10:32:20 -0500 (EST)
From:	Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To:	cygwin AT cygwin DOT com
To:	Bhiksha Raj <bhiksha AT cs DOT cmu DOT edu>
cc:	cygwin AT cygwin DOT com
Subject:	Re: BSOD on cygwin
In-Reply-To:	<20030111230404.A9110@CS.CMU.EDU>
Message-ID:	<Pine.GSO.4.44.0301121024370.10883-100000@slinky.cs.nyu.edu>
Importance:	Normal
MIME-Version:	1.0

On Sat, 11 Jan 2003, Bhiksha Raj wrote:

> Hi All,
>
> I hope this is not the wrong forum for this:
>
> Im trying to install TeXmacs on my win98+cygwin laptop.
> First I installed the binaries for guile from the cygwin setup
> (I have XFree and Tex and all associated libs already)
> downloaded TeXmacs sources, ran ./configure and then
> gave a "make".
> I got  the blue screen of death (BSD).
> After iterating through several BSDs, I hunted on the web
> and found a site that said that static linkages were a problem with
> the latest guile and that I must install guile 1.4.1. So I uninstalled
> guile,
> downloaded the sources for guile 1.4.1, untarred them and
> ran
> ./configure --disable-shared
>
> It runs through several checks, but never completes - insted it
> gives me at some point it simply gives me the blue screen of death.
> This time around Im not even getting past configure.
>
> Im not sure what to do now.
> Any advice at all would be greatly appreciated.
>
> Much thanks
> Bhiksha
> bhiksha AT merl DOT com

Bhiksha,

This is a forum for all problems with Cygwin, so your question fits in
nicely.  To answer it, Cygwin never *causes* a BSOD.  It may expose or
trigger a bug in Windows or some process running with system privileges
(antivirus programs have been blamed a lot), but Cygwin itself doesn't
have enough access to the low-level OS to be able to cause a BSOD.

Try turning off your antivirus program(s) and see if it makes the BSOD go
away.  Another possibility is firewall or VPN software.  The output of
'cygcheck -s -v -r' as a non-inline uncompressed text *attachment*
wouldn't hurt, either (as indicated in <http://cygwin.com/bugs/>).
	Igor
P.S. I'm sure you'll get more and better responses on Monday.
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

Oh, boy, virtual memory! Now I'm gonna make myself a really *big* RAMdisk!
  -- /usr/games/fortune


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