From: Mike McCarty <mcmccarty@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Corrupt Cygwin64 install?
Date: Tue, 27 Sep 2016 18:06:00 -0000 [thread overview]
Message-ID: <CACt7iwnpDJfXq+MhVn_kgJSBS1BKYNp9qVE98=3ahBYFb2caVQ@mail.gmail.com> (raw)
In-Reply-To: <87a8etxnon.fsf@Rainer.invalid>
Ooo... You still have that script lying around? ;^)
On Tue, Sep 27, 2016 at 12:22 PM, Achim Gratz <Stromeko@nexgo.de> wrote:
> Mike McCarty writes:
>> 0x000007fefcb07497 in TmmonDestoryAddonObject () from
>> /cygdrive/c/windows/system32/tmumh/20019/AddOn/6.80.0.1007/TmUmEvt64.dll
>
> It always instills much confidence in the abilities of the programmers
> and the usefulness of the program when you see such typos…
>
>> tmmon64.dll is a TrendMicro OfficeScan dll. After talking my sysadmin
>> into disabling OfficeScan on my machine temporarily, the crash goes
>> away. Adding cygwin to the exclusion list doesn't help here (I tried
>> it) I think because this is a "real-time monitor", not the file scan
>> that the exclusion list generally applies to.
>
> The real-time monitor has it's own exclusion list (last I looked). And
> no, you won't be able to run Cygwin or anything of similar complexity
> with that stupid DLL injection that TrendMicro is doing.
>
>> Has anybody else had a similar experience with TrendMicro AV software?
>> My IT dept. will not allow me to disable it entirely...
>
> I've had a .reg file on my desktop that re-instated the realtime
> exclusion for the Cygwin install path since generally each time the
> computer loaded the Group policy or updated the signatures it would
> forget about it (the UI to add to that list was locked down with a
> password, but the registry key was open to write to). Fortunately we no
> longer use Trend Micro (I guess the fact it produced the major part of
> all end user support requests was a too big hint to ignore for IT).
>
>
> Regards,
> Achim.
> --
> +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
>
> SD adaptation for Waldorf microQ V2.22R2:
> http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
>
> --
> 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
>
--
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-09-27 17:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 22:35 Mike McCarty
2016-09-22 14:18 ` Ken Brown
2016-09-26 21:09 ` Mike McCarty
2016-09-27 2:00 ` Ken Brown
2016-09-27 2:18 ` Brian Inglis
2016-09-27 15:05 ` Mike McCarty
2016-09-27 17:59 ` Achim Gratz
2016-09-27 18:06 ` Mike McCarty [this message]
2016-09-27 18:12 ` Achim Gratz
2016-09-27 18:29 ` Achim Gratz
2016-09-27 20:15 ` Mike McCarty
2016-09-28 0:06 ` Brian Inglis
-- strict thread matches above, loose matches on Subject: below --
2016-09-21 22:04 Mike McCarty
2016-09-21 22:09 ` Ken Brown
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='CACt7iwnpDJfXq+MhVn_kgJSBS1BKYNp9qVE98=3ahBYFb2caVQ@mail.gmail.com' \
--to=mcmccarty@gmail.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).