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:reply-to:message-id:to:subject :in-reply-to:references:mime-version:content-type :content-transfer-encoding; q=dns; s=default; b=P1ZiXvukxMMPyfwv 7HmoJQumvJ19ZiAKcxHSTNyJW7gaJOOcyxXwB2k8v4XZS+Bb9q0aTQYeFZBaOlp5 eG8aGtUBnJaWLtqx4ymL4RJR/DYuLCIICN9qa/lTgnMaS2WBDkW/b/pDGLE4WhKQ JaDL31aL5efyYq1ngSAlzKEwS9U= 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:reply-to:message-id:to:subject :in-reply-to:references:mime-version:content-type :content-transfer-encoding; s=default; bh=ehPw7heezyG1WzfknM/0sE YstSk=; b=BRzH/tqX0zyidqOIl5uDzEi+C8PHBNYHk/bWqKAY+VdFvZoRvCeZ+W StxMRTh47tqF2lz97/xhteXdDONyVTXph5VmzJpWBWB2MWrN0phG9pTBJlMG+4K2 sEeb0bSwWD+bQkPrnW8TrIAognVtMu1JikEx4mX7y8sRMKxXOiWXo= 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-Virus-Found: No X-Spam-SWARE-Status: No, score=-4.3 required=5.0 tests=BAYES_05,FREEMAIL_FROM,GIT_PATCH_2,KAM_THEBAT,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=HX-Priority:Normal, terrible, H*F:D*yandex.ru, UD:ru X-HELO: forward103o.mail.yandex.net Authentication-Results: smtp4j.mail.yandex.net; dkim=pass header.i=@yandex.ru Date: Wed, 23 May 2018 22:56:05 +0300 From: Andrey Repin Reply-To: cygwin AT cygwin DOT com Message-ID: <1428905528.20180523225605@yandex.ru> To: L A Walsh , cygwin AT cygwin DOT com Subject: Re: normal to blue-screen windows when doing 'ls -CF' of /proc/sys/GLOBAL?? (bug? cygcheck attached) In-Reply-To: <5B030FB7.5050407@tlinx.org> References: <5B030FB7 DOT 5050407 AT tlinx DOT org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Greetings, L A Walsh! > David Conrad wrote: >> I think Michel LaBarre's suggestion of running chkdsk and sfc is a >> good one; > --- > I agree...chkdsk indicated something odd in an attribute block, > but I've yet to be able to correct it, since I'm running win7 > on a newer machine that uses USB3 and doesn't understand > that my RAID controller is a megaraid type. > So booting into recovery options (or booting from the win7 > install disk) both don't see any USB keyboard/mice > nor the system-disk which uses the megaraid controller > it just doesn't know it enough to see it... > To start with, I need to hook up a PS/2 kbd & mouse > to access those, while I could load the megaraid drivers > then, Or rebuild the Win7 disk image with related drivers. Been doing that for years myself, but YMMV. > it won't go through the discover process until > the next reboot, at which point the megaraid drivers > will be gone again...so...working on updating my > WinRE image and burning a new Win7 install disk that > can understand the missing stuff. > This is normal for me -- can't get from point 1 to 2 > without going through 3-4, where you need 5-6 as > prereqs for those...etc... > :-( -- With best regards, Andrey Repin Wednesday, May 23, 2018 22:55:06 Sorry for my terrible english... -- 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