From: L A Walsh <cygwin@tlinx.org>
To: 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 10:48:00 -0000 [thread overview]
Message-ID: <5B03DF98.2000400@tlinx.org> (raw)
In-Reply-To: <000001d3f156$e6312be0$b29383a0$@rogers.com>
Michel LaBarre wrote:
> If you need a boot environment that knows your hardware, try downloading the backup program Reflect from Macrium - there is a free version.
----
Wouldn't it be more prudent in the long run to make sure the repair-environment
builtin to windows and your install disk knows about the new HW?
I've had problems relying on 3rd party tools that I had trouble getting
to work some number of years later.
I'm able to backup the machine with the ms-backup tools, (crappy though they are),
and have those tools create an image backup every week.
I don't keep "data" on my winbox. just on my linux box.
I try to only put programs on the winbox as I haven't found windows
to be very reliable over the long term.
Had system restore wipe files more than once....no fun.
--
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
next prev parent reply other threads:[~2018-05-22 9:16 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
2018-05-22 10:48 ` L A Walsh [this message]
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=5B03DF98.2000400@tlinx.org \
--to=cygwin@tlinx.org \
--cc=cygwin@cygwin.com \
/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).