From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: setup-x86_64.exe does not start in win10 20H2
Date: Tue, 14 Dec 2021 01:09:05 -0700 [thread overview]
Message-ID: <a715ef99-1316-464e-ca46-94254dc83100@SystematicSw.ab.ca> (raw)
In-Reply-To: <1e70d715-5e22-8cd1-1f68-5b5e66045361@gmail.com>
On 2021-12-13 23:31, Marco Atzeri wrote:
> On 14.12.2021 07:17, Brian Inglis wrote:
>> On 2021-12-13 16:26, Kutty, Rejeesh wrote:
>>> I uninstalled Beyond Trust with our IT help, rebooted, same behavior.
>>> I then came upon another thread that talks about the compression.
>>> I didn't build it, I just decompressed it and now setup-64bit works
>>> fine.
>>> For some reason, 32bit doesn't have any of this problem.
>>> If it is not too much of trouble, I would request that you provide an
>>> uncompressed version too.
>>> The file size is not that bad, It came to be about 5MB only.
>>> Perhaps, suggest in the installation instructions to try in case it
>>> doesn't launch?
If you have that problem, you have an app in the BLODA.
Are you still running BeyondTrust or another AV?
You need to get Cygwin setup exes using upx bypassed or whitelisted by
your support or the vendor.
>> What was the URL of the thread about compression?
>> Which file did you download about 5MB, from which URL, how did you
>> download and decompress it: using which tools, commands, options, and
>> what were the before and after sizes?
>> There appear to be no Cygwin setup files about 5MB:
> he means 5MB after decompressing the 1.3Mb setup-x86_64.exe
> If I remember right upx is used for setup compression
Why would anyone want or need to do that manually: that implies a badly
written app in the BLODA interfering with decompression, and that hasn't
had any mentions as a problem for a couple of years!
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2021-12-14 8:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 14:39 Kutty, Rejeesh
2021-12-10 14:55 ` Marco Atzeri
2021-12-10 16:45 ` Ken Brown
2021-12-10 17:12 ` Kutty, Rejeesh
2021-12-10 18:28 ` Ken Brown
2021-12-10 18:38 ` Kutty, Rejeesh
2021-12-10 20:17 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2021-12-10 20:19 ` Kutty, Rejeesh
2021-12-11 5:38 ` Brian Inglis
2021-12-13 23:26 ` Kutty, Rejeesh
2021-12-14 6:17 ` Brian Inglis
2021-12-14 6:31 ` Marco Atzeri
2021-12-14 8:09 ` Brian Inglis [this message]
2021-12-10 15:19 Kutty, Rejeesh
2021-12-10 15:30 ` Marco Atzeri
2021-12-10 15:39 ` Kutty, Rejeesh
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=a715ef99-1316-464e-ca46-94254dc83100@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).