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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=UGSqRXHCl9Fe+Yj9qcKXdegijcCLc4TmWKtIA/pqieA
	Qnt8l97iC60iOUt+bPEaFqbEMOmV+QclWTYAC45eO4/F16p6LWqJoxesvtVcpicn
	xQRvmgKACzntwKDOB9VenrR9lnip94nvu7Y5LUKrYf37dpz0Yw7K/PIqVIY78oWg
	=
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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 s=default; bh=WEeiZqyePJbJtiLQttpTHG+qVEc=; b=M/pcLIR+gSXXWkXnk
	U1qYVb9tF06eEJTfmY5eT8Q/5GFLJbWFz+SiquOV6zRIJH9TW1ZqyKkdwOlgHo/q
	B71PrZFCh2oqrSnitPfMjVw97o46G21gB2QAJH+LPvhul3hYopCy0oZ3VHaqSl4O
	W2PXAzMCrKaaq2AfytN8I0ABmI=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-5.0 required=5.0 tests=BAYES_20,GIT_PATCH_2 autolearn=ham version=3.3.2 spammy=indicated, keyboard, drivers, mouse
X-HELO: Ishtar.sc.tlinx.org
Message-ID: <5B030FB7.5050407@tlinx.org>
Date: Mon, 21 May 2018 11:28:07 -0700
From: L A Walsh <cygwin AT tlinx DOT org>
User-Agent: Thunderbird
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: normal to blue-screen windows when doing 'ls -CF' of /proc/sys/GLOBAL?? (bug? cygcheck attached)
References: <CAEotdwnTihdr7AdRFNWyvPvtxP57YjZXfgWy__X2JSpfkiwB8Q AT mail DOT gmail DOT com>
In-Reply-To: <CAEotdwnTihdr7AdRFNWyvPvtxP57YjZXfgWy__X2JSpfkiwB8Q@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

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, 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...
:-(


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