From: "Nellis, Kenneth" <Kenneth.Nellis@conduent.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: open IE from command line
Date: Wed, 21 Dec 2016 17:01:00 -0000 [thread overview]
Message-ID: <0D835E9B9CD07F40A48423F80D3B5A704BBD5C5A@USA7109MB022.na.xerox.net> (raw)
In-Reply-To: <0D835E9B9CD07F40A48423F80D3B5A704BBD5B0F@USA7109MB022.na.xerox.net>
[-- Attachment #1: Type: text/plain, Size: 568 bytes --]
From: Nellis, Kenneth
> I suspect the issue is that some required DLLs are not in
> my PATH. Indeed, my Cygwin PATH is a pruned version of my
> Windows PATH.
Actually, that's not the case and is irrelevant as Lee demon-
strates in https://cygwin.com/ml/cygwin/2016-12/msg00220.html.
Comparing the output from
Windows: C:/>path
and
cygwin/bash: $ cmd /c path
shows only new paths added to support Cygwin.
I'm on Microsoft Windows 7 Enterprise Edition, 64-bit Service Pack 1 (build 7601)
FWIW, output from "cygcheck -svr" attached.
--Ken Nellis
[-- Attachment #2: cygcheck.out --]
[-- Type: application/octet-stream, Size: 42458 bytes --]
[-- Attachment #3: Type: text/plain, Size: 219 bytes --]
--
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:[~2016-12-21 17:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-20 16:15 Nellis, Kenneth
2016-12-20 17:20 ` Lee
2016-12-20 22:10 ` cyg Simple
2016-12-20 22:51 ` Andrey Repin
2016-12-20 23:32 ` Eliot Moss
2016-12-21 0:50 ` Lee
2016-12-21 14:11 ` Nellis, Kenneth
2016-12-21 14:46 ` Buchbinder, Barry (NIH/NIAID) [E]
2016-12-21 16:14 ` Lee
2016-12-21 17:01 ` Nellis, Kenneth [this message]
2016-12-22 1:04 ` Doug Henderson
2016-12-22 1:25 ` Doug Henderson
2016-12-22 13:43 ` Nellis, Kenneth
2016-12-22 13:54 ` cyg Simple
2016-12-22 13:51 ` cyg Simple
2016-12-22 14:26 ` Nellis, Kenneth
2016-12-22 15:51 ` Andrey Repin
2016-12-22 20:56 ` Nellis, Kenneth
2016-12-22 18:14 ` Brian Inglis
2016-12-21 7:30 ` Brian Inglis
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=0D835E9B9CD07F40A48423F80D3B5A704BBD5C5A@USA7109MB022.na.xerox.net \
--to=kenneth.nellis@conduent.com \
--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).