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: Fri, 25 May 2018 03:25:00 -0000 [thread overview]
Message-ID: <5B07447B.7080108@tlinx.org> (raw)
In-Reply-To: <1428905528.20180523225605@yandex.ru>
Andrey Repin wrote:
>
>> To start with, I need to hook up a PS/2 kbd & mouse
>> to access those, while I could load the megaraid drivers
>> then,
>
> Or rebuild the Win7 disk image with related drivers.
> Been doing that for years myself, but YMMV.
---
Need to learn how...just have been more busy
w/other stuff. But w/new machine, it's vital.
Trying to look at 'dism' to mount old .wim image
and update it with needed drivers, using
https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/add-and-remove-drivers-to-an-offline-windows-image
as a ref....
will have to see how that goes...
If I have any probs, maybe can get back to you?
Tnx!
-linda
--
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-24 23:02 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
2018-05-23 20:13 ` Andrey Repin
2018-05-25 3:25 ` L A Walsh [this message]
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=5B07447B.7080108@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).