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
- From: "Michel LaBarre" <michel.labarre@xxxxxxxxxx>
- Subject: RE: normal to blue-screen windows when doing 'ls -CF' of /proc/sys/GLOBAL?? (bug? cygcheck attached)
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... ;-)
> -----Original Message-----
> From: cygwin-owner@xxxxxxxxxx [mailto:cygwin-owner@xxxxxxxxxx] On
> Behalf Of L A Walsh
> Sent: May 21, 2018 2:28 PM
> To: cygwin@xxxxxxxxxx
> 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
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple