public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Lemke, Michael  ST/HZA-ZIC2" <lemkemch@schaeffler.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: Setup missing installed packages
Date: Tue, 23 Oct 2018 14:44:00 -0000	[thread overview]
Message-ID: <AM6PR03MB3558D4414DDBEBEC7E063E67BEF50@AM6PR03MB3558.eurprd03.prod.outlook.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1433 bytes --]

On Tuesday, October 23, 2018 1:47 PM Houder wrote:
>On Tuesday, October 23, 2018 10:55 AM Michael Lemke wrote:
>[snip]
>
>> Thanks, I did and I can't find anything wrong. Where does setup.exe gets
>> the information from? I tried several versions, the current official one,
>> the new snapshot and something older I have lying around. They all do
>> this. They are in my distribution directory with all the Cygwin downloads
>> and all show the correct location of distribution directory
>> and installation directory. Some junk in the registry?
>
>uhm ...
>
>Data stored in the registry (Cygwin_root, local_repo):
>
>For a 32-bits instance of Cygwin,
>    see HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin
>
>For a 64-bits instance of Cygwin,
>    see HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cygwin
>

Ah, this might explain why I never had this problem in the 15+ years
of using Cygwin. I got a new PC a while ago and data was just copied
to it from the old PC. It certainly omitted registry settings. Now 
that I updated my Cygwin installation setup's amnesia is gone.

>
>.. and save you the trouble of posting to this list.

Sorry about that, I'll unsubscribe soon 😉

Michael
\x03B‹KCB”\x1c›Ø›\x19[H\x1c™\^[ܝ\x1cΈ\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÜ\x1c›Ø›\x19[\Ëš\x1d^[[\x03B‘TNˆ\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÙ˜\KÃB‘^[ØÝ[Y[\x18]\x1a[ÛŽˆ\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÙ^[ØÜËš\x1d^[[\x03B•[œÝXœØÜšX™H\x1a[™›Îˆ\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÛ[\vÈÝ[œÝXœØÜšX™K\Ú[\^[\x19CBƒB

             reply	other threads:[~2018-10-23 14:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-23 14:44 Lemke, Michael  ST/HZA-ZIC2 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-10-22 16:50 Lemke, Michael  ST/HZA-ZIC2
2018-10-22 17:57 ` Marco Atzeri
2018-10-23  8:55 ` Lemke, Michael  ST/HZA-ZIC2
2018-10-23  9:18   ` Lemke, Michael  ST/HZA-ZIC2
2018-10-23 10:24     ` Marco Atzeri
2018-10-23 17:35   ` 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=AM6PR03MB3558D4414DDBEBEC7E063E67BEF50@AM6PR03MB3558.eurprd03.prod.outlook.com \
    --to=lemkemch@schaeffler.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).