On 7/13/25 00:32, Bruce Horrocks wrote:
On 11 Jul 2025, at 15:42, Pablo Rodriguez via ntg-context wrote: […] I knew, but I was downloading a Win64 distribution (with its binaries) on a Linux64 OS (afaIk, `$HOME` is a Unix variable, `%USERPROFILE%` in Windows).
Well I did wonder why you were using Unix syntax but saying the problem was with your Windows machine.
Also `$USERPROFILE` is a MSYS2 (https://msys2.org) extended variable to have a Windows variable on a Linux shell (I used it on my first reply to Hans in this thread.)
[…] Installation went fine (my Linux64 box doesn’t complain for Win64 binaries, since I don’t run them there).
But installation on which machine? Or do you mean "download" went fine? It's all very confusing.
You’re right, Bruce, it was only donwloading the Win64 distribution with `install.sh` (on a Linux64 machine). This workaround (download a complete Win64 ConTeXt distribution on a Linux64 machine, to use them on Windows) was only an alternative way of testing that my usual update (on Windows) was giving me the right binaries.
[…] Okay, so it looks like the permissions are correct. […] You can calculate checksums directly in Windows, rather than over a file share, by using PowerShell:
Good to know, but MSYS2 is fine for me.
I get the same as you do above for mtxrun.exe. […] That definitely sounds like a problem with your work computer's configuration. If you are running 64-bit Windows then the 64-bit binaries should run just fine.
I have been running both 64bit Windows and 64bit binaries (for ConTeXt) for more than five years. I wonder whether this makes more than one hundred binaries, being the latest one the first and only one that has been denied access by Windows.
What do you get if you run
C:\> where.exe context.exe
It's the equivalent of Unix's 'which' command so will help determine if the .exe being run is the one that you think it is.
Typing from what I got with the Windows computer at work: c:\context\tex\texmf-win64\bin\context.exe I thought `whereis` was the Unix counterpart to `where` (but I got exactly the same result with both, in any case). Since the win32 binaries do work, I have to test newer binaries to check whether my issue is persistent, permanent or it just disappears. Many thanks for your help, Pablo