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:from:to:references:in-reply-to:subject:date
	:message-id:mime-version:content-type:content-transfer-encoding;
	 q=dns; s=default; b=yfcy/LPzOeBiFTVdCVVHObuGq18Jk8TakYbALpw+yJQ
	IDw/dXuQyHAzhGJDa91wHCifkE4ZMz812AHWJvfm61VVPXFYejyoZ0L5s154VxOA
	9mDARHP25I7lm3y/AyeWpapek0iZfIPoKHPnXrAYe5NtzkX/WYfKUhNXlsb14iIo
	=
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:from:to:references:in-reply-to:subject:date
	:message-id:mime-version:content-type:content-transfer-encoding;
	 s=default; bh=xRbGi/3OJtchtesTjeHdm664o0o=; b=rn07jZfE9zPA8bwER
	vlBr4MQeZieZGwhFFIxledTgzEi5NKiLRzDIFWWqNtOuozh64o4+ElLZYgBh2VeY
	uIo2MRxse/3nqOL4ursxHu8Z3cq/Hc0LcUJPHRTpqvvL+6cf3xqXqvMINXf4naer
	kFkDgA8RrQbfaffo8J6kNql510=
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=-2.8 required=5.0 tests=AWL,BAYES_00,CYGWIN_OWNER_BODY,GIT_PATCH_2,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 spammy=bonus, facilities, H*UA:14.0, H*x:14.0
X-HELO: sonic312-25.consmr.mail.ne1.yahoo.com
From: "Michel LaBarre" <michel DOT labarre AT rogers DOT com>
To: "'L A Walsh'" <cygwin AT tlinx DOT org>, <cygwin AT cygwin DOT com>
References: <CAEotdwnTihdr7AdRFNWyvPvtxP57YjZXfgWy__X2JSpfkiwB8Q AT mail DOT gmail DOT com> <5B030FB7 DOT 5050407 AT tlinx DOT org>
In-Reply-To: <5B030FB7.5050407@tlinx.org>
Subject: RE: normal to blue-screen windows when doing 'ls -CF' of /proc/sys/GLOBAL?? (bug? cygcheck attached)
Date: Mon, 21 May 2018 18:56:04 -0400
Message-ID: <000001d3f156$e6312be0$b29383a0$@rogers.com>
MIME-Version: 1.0
Content-Type: text/plain;	charset="UTF-8"
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id w4LMuLDn011978

If you need a boot environment that knows your hardware, try downloading the backup program Reflect from Macrium - there is a free version.
(I use it for backup/recovery of my Win 10 and Win 7 systems.  So far it has been 100% solid.)

You can then use it to build a boot USB with all your drivers. 
I have not explored their recovery environment except to initiate a full system drive restore but at minimum, I expect it will include all the Windows facilities.

As an incidental bonus, you can create backups in case your remediation measures go south - restore and try again.  You can repeat steps 3-4 until you get it right... ;-)

Michel

> -----Original Message-----
> From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com] On
> Behalf Of L A Walsh
> Sent: May 21, 2018 2:28 PM
> To: cygwin AT cygwin DOT com
> Subject: Re: normal to blue-screen windows when doing 'ls -CF' of
> /proc/sys/GLOBAL?? (bug? cygcheck attached)
> 
> 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


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