public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
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: Thu, 17 May 2018 20:38:00 -0000	[thread overview]
Message-ID: <5AFDDAF0.5070208@tlinx.org> (raw)
In-Reply-To: <4310b729-b8b1-03aa-1c59-7a9c902edfef@SystematicSw.ab.ca>

Brian Inglis wrote:
> Run "cygcheck ls" to see if any Windows installs added to your path pick up
> api-ms-win-core-... intercept dlls e.g. Firefox, Tortoise, etc.
---
	Nope. I set my path in my login profile:
reorder path, filter out dups and empty dirs and
use abbreviated paths for some common names.and filter out weird things in my
login profile.


> Tried running same command under strace?
> BLODA possibly messing up net access to AD?
---
Not running AD...using older NT4-style Dom on my home
lnx box.

Doubt it is BLODA, though not impossible given the growing number
if things that are incompat w/something.

BTW, is Win10 on the BLODA list?  seems to cause
alot of new incompats w/every release.

though in the same vein, MS updates for win7 seem to be
more likely to create problems as much as solve them since
they started trying to get people to switch away from pre-win10
OS's.  

Even had MS-forum-support people tell me that the fix for
some issue or another that they couldn't solve or fix 
was to move to Win10 (not that it was known to fix the 
problem -- just as a shotgun approach).


--
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-17 19:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2018-05-17 22:09       ` Michel LaBarre
2018-05-18  4:49         ` L A Walsh
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
2018-05-25 14:56       ` Andrey Repin

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=5AFDDAF0.5070208@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).