X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:subject:in-reply-to:message-id :references:mime-version:content-type; q=dns; s=default; b=DrXs/ 6K+kFDT5zlHBg+S9u6S4PeoK/fA9Kz2hLuInMYoUvb7dO7vpctzjZqa7+u6Bn/iy yLIpA/b96CI8Tam+ltZEyytm/0TJeFYAIy3f+GDssAiJmT9ghwl2J8JM4mdYHubt xLNd8zFmQjQVLfp+mtQcg4VS9WJdBhhvxQt+rg= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:subject:in-reply-to:message-id :references:mime-version:content-type; s=default; bh=ux0IgVQwAQb CiRX1OGC8TJdHrMc=; b=KQrgiKHL4IPBthwsTjTLRGSUcBAaAGQSQhsIK6q9xYC vGY+ioXBp9i7vb+fJQPUmk9onZa+MHXX16Nm77asnVF1HIqSZslAfHZ4X4oeBPB6 N0ia2XnrRJcZ5F8GYdC8eP137Pm/Ykc0y8vTih0y+QwsXKPA4h+fwQzzoV/k/J0E = Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=1.5 required=5.0 tests=AWL,BAYES_50 autolearn=ham version=3.3.2 X-HELO: mail.sciencetools.com Date: Wed, 5 Feb 2014 09:39:49 -0800 (PST) From: Richard AT KarmannGhia DOT org To: cygwin AT cygwin DOT com Subject: A device driver as BLODA? In-Reply-To: <52F26065.1070306@cygwin.com> Message-ID: References: <52E6C814 DOT 1060009 AT cygwin DOT com> <52F0F834 DOT 1070300 AT cygwin DOT com> <52F26065 DOT 1070306 AT cygwin DOT com> User-Agent: Alpine 2.03 (LFD 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-IsSubscribed: yes Hello All, For weeks I've been pondering all the troubles I've had with setup, spurred by all the conversations that have happened recently about packaging, etc, and the occasional comments about BLODA. I have sometimes figured Cygwin's setup program is a member of BLODA - it certainly has been anything but reliable in my personal experience. And all too often it's between me and my enjoyment of Cygwin. (I maintain a fleet of Windows boxes with Cygwin, no two of which are identical.) I've forgotten who wrote it, but I especially appreciated the email in my in-box this morning about how to tell when Cygwin installation scripts go wrong, where the list of scripts is, etc, because, frankly, when a Cygwin installation goes wrong (and when doesn't it?) I seldom have time to track down exactly why - I just try, try again, with different versions until it works or I give up and try another day. (One MAJOR headache here is the download process, no fixed starting point to know you got everything.) ...And so it was this morning I decided to re-convince myself I didn't have any BLODA problems... MAYBE all those issues "weren't Cygwin's fault?" I was surprised to find "ATI Catalyst", and even MORE surprised to find "NVIDIA GeForce" on the list, both as "some versions". I haven't any idea why the Catalyst product would want to hook into things that would interfere with Cygwin, but I did have problems with it - it would crash the machine sometimes! - so I deleted it. But the description, "NVIDIA GeForce" has me a bit confused because I thought that was the maker's name for a series of video cards (hardware) and possibly the device drivers that enable them to do magic things, like provide a display consisting of six monitors as my "desktop." ...I use this hardware! And, certainly, I use the NVIDIA drivers for it. This raises two primary questions (and a few related ones): 1) How can I confirm I do or don't have an NVIDIA GeForce BLODA issue? (Is there really a device driver level issue?) And; 2) Might "we, the community" develop a BLODA-checker to help the installation process? I'm thinking that whenever a new item is discovered to put on the BLODA list, a small "here's how you know you have this software" script is written that could become a part of the Cygwin install process. There's already a script walker for scripts in a directory - maybe it could be harnessed to run a list of BLODA-checkers. Sure, there's a back-log of already known BLODA, most of which I have never even heard of before (probably not alone on that!), but if we can have scripts created on an on-going basis - say, when new BLODA are discovered and put on the list - eventually the backlog would get caught up... Given all the complaints out there about the installation / setup process, I have to believe that I'm far from alone in thinking that there's likely a strong link between installation troubles and BLODA..... Regards, Richard -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple