From: Bruce Horrocks via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Bruce Horrocks <ntg@scorecrow.com>
Subject: Re: lmtx installation paths not working
Date: Wed, 15 Jun 2022 22:22:57 +0100 [thread overview]
Message-ID: <C8FF1500-DA00-4FFA-9B66-B662939B5BE6@scorecrow.com> (raw)
In-Reply-To: <CAPefzZ0V1gJCV5HGk362PJfV2Bq2cCiRsVhzPxxjePTJn+KuWQ@mail.gmail.com>
> On 14 Jun 2022, at 12:20, Jano Kula via ntg-context <ntg-context@ntg.nl> wrote:
>
> Do you have an idea how to fix problem?
> I will be thankful for an advice, it is quite urgent (everything was working yesterday).
Do you have an anti-virus product installed?
In the past I've noticed that Symantec sometimes gives a false positive on some of the ConTeXt files as they are installed and silently deletes them thinking they contain malware.
The result is a broken ConTeXt because files are missing but you have no idea which files are missing. :-(
Try temporarily disabling AV and then do a complete re-install into an empty C:/data/context directory.
—
Bruce Horrocks
Hampshire, UK
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2022-06-15 21:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 11:20 Jano Kula via ntg-context
2022-06-14 13:47 ` Jano Kula via ntg-context
2022-06-14 16:26 ` Aditya Mahajan via ntg-context
2022-06-14 20:56 ` Alain Delmotte via ntg-context
2022-06-15 21:22 ` Bruce Horrocks via ntg-context [this message]
2022-06-17 14:18 ` Jano Kula via ntg-context
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=C8FF1500-DA00-4FFA-9B66-B662939B5BE6@scorecrow.com \
--to=ntg-context@ntg.nl \
--cc=ntg@scorecrow.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 NNTP newsgroup(s).