public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Michel LaBarre" <michel.labarre@rogers.com>
To: "'L A Walsh'" <cygwin@tlinx.org>,	<cygwin@cygwin.com>
Subject: RE: normal to blue-screen windows when doing 'ls -CF' of /proc/sys/GLOBAL?? (bug? cygcheck attached)
Date: Tue, 22 May 2018 02:07:00 -0000	[thread overview]
Message-ID: <000001d3f156$e6312be0$b29383a0$@rogers.com> (raw)
In-Reply-To: <5B030FB7.5050407@tlinx.org>

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@cygwin.com [mailto:cygwin-owner@cygwin.com] On
> Behalf Of L A Walsh
> Sent: May 21, 2018 2:28 PM
> To: cygwin@cygwin.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

  reply	other threads:[~2018-05-21 22:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-20 11:37 David Conrad
2018-05-21 20:18 ` L A Walsh
2018-05-22  2:07   ` Michel LaBarre [this message]
2018-05-22 10:48     ` L A Walsh
2018-05-23 20:13   ` Andrey Repin
2018-05-25  3:25     ` L A Walsh
2018-05-25 14:56       ` Andrey Repin
  -- strict thread matches above, loose matches on Subject: below --
2018-05-15 12:58 L A Walsh
     [not found] ` <000a01d3ec54$a2bb2ca0$e83185e0$@rogers.com>
2018-05-15 16:51   ` L A Walsh
2018-05-15 17:18     ` James Darnley
     [not found]     ` <2b3cf1ed-1a3f-d8ff-136b-0ee533ae9e59@wagner.is>
2018-05-15 19:54       ` L A Walsh
2018-05-16 17:26 ` Andrey Repin
2018-05-17 13:22   ` L A Walsh
2018-05-17 19:41     ` Brian Inglis
2018-05-17 20:38       ` L A Walsh
2018-05-17 22:09       ` Michel LaBarre
2018-05-18  4:49         ` L A Walsh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000001d3f156$e6312be0$b29383a0$@rogers.com' \
    --to=michel.labarre@rogers.com \
    --cc=cygwin@cygwin.com \
    --cc=cygwin@tlinx.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).