> On 11 Jul 2025, at 15:42, Pablo Rodriguez via ntg-context 
> <[email protected]> wrote:
> 
> On 7/10/25 22:37, Bruce Horrocks wrote:
>> On 10 Jul 2025, at 15:25, Pablo Rodriguez via ntg-context <ntg-
>> [email protected]> wrote:>>
>>> It seems to work fine, except for `mtxrun.exe` (which isn’t downloaded
>>> to `bin/` or to `tex/texmf-win64/bin`).
>> 
>> mtxrun.exe comes from the .zip file you download from the installers
>> page on the Contextgarden website.
> Many thanks for your help, Bruce.
> 
> 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.

> 
> This was the reason why I invoked `./install.sh --platform=win64`.

It has never occurred to me that install.sh might be able to act as a file 
downloader. I thought the reason for being able to specify a version is for 
when the script is getting confused and failing to recognise the machine type.

> 
> Two minutes after sending my message, I downloaded it from
> http://lmtx.pragma-ade.nl/install-lmtx/context-win64.zip.
> 
> 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.

> 
> On my Win64 at work, `mtxrun --generated` gives the already referred
> message "Access denied" (well, in Spanish).
> 
>> If that doesn't show anything unusual then try the icacls command. I
>> got the following output:>
>> c:\context\bin>icacls mtxrun.exe
>> mtxrun.exe BUILTIN\Administrators:(I)(F)
>>           NT AUTHORITY\SYSTEM:(I)(F)
>>           BUILTIN\Users:(I)(RX)
>>           NT AUTHORITY\Authenticated Users:(I)(M)
>> 
>> Successfully processed 1 files; Failed processing 0 files
> 
> I get the same output for both not working newest lates and working
> previous latest (but in Spanish):
> 
> C:>icacls "c:\new\tex\texmf-win64\bin\mtxrun.exe"
> c:\new\tex\texmf-win64\bin\mtxrun.exe BUILTIN\Administradores:(I)(F)
>                                      NT AUTHORITY\SYSTEM:(I)(F)
>                                      BUILTIN\Usuarios:(I)(RX)
>                                      NT AUTHORITY\Usuarios
> autentificados:(I)(M)
> 
> Se procesaron correctamente 1 archivos; error al procesar 0 archivos
> 
> C:\Desktop>icacls "c:\old\tex\texmf-win64\bin\mtxrun.exe"
> c:\old\tex\texmf-win64\bin\mtxrun.exe BUILTIN\Administradores:(I)(F)
>                                      NT AUTHORITY\SYSTEM:(I)(F)
>                                      BUILTIN\Usuarios:(I)(RX)
>                                      NT AUTHORITY\Usuarios
> autentificados:(I)(M)
> 
> Se procesaron correctamente 1 archivos; error al procesar 0 archivos

Okay, so it looks like the permissions are correct.

> 
>> Try the above first and we can troubleshoot a bit more if the cause
>> still isn't clear.
> To confirm that I speak of the same binaries (old and new) as you:
> 
> $ sha512sum /c/new/tex/texmf-win64/bin/*.exe
> 831e6fdd20ef32c5d8397c6eaa43c6fcf824c4f05720eb0ef9ec40c240de74b33c388d77af06fe59b24f5b548c9a9454a10cbcf0b5c55f5767866c7c99eb016e
> */c/new/tex/texmf-win64/bin/context.exe
> 831e6fdd20ef32c5d8397c6eaa43c6fcf824c4f05720eb0ef9ec40c240de74b33c388d77af06fe59b24f5b548c9a9454a10cbcf0b5c55f5767866c7c99eb016e
> */c/new/tex/texmf-win64/bin/luametatex.exe
> e156a063e5459a9ad9840d816ba69f9edfc448e71fda15b7d0f392cc9bfd4972e56584f2e874d67ffdf12787c969ae3cbdf5c73554cb1dff8edba518ebb50d81
> */c/new/tex/texmf-win64/bin/luatex.exe
> 831e6fdd20ef32c5d8397c6eaa43c6fcf824c4f05720eb0ef9ec40c240de74b33c388d77af06fe59b24f5b548c9a9454a10cbcf0b5c55f5767866c7c99eb016e
> */c/new/tex/texmf-win64/bin/mtxrun.exe
> 
> $ sha512sum /c/old/tex/texmf-win64/bin/*.exe
> b18ef7b0b49ea6423920b1dd50aaa643ebc984a437acc602e9c949855742e768510cc765e1c3ef75ed18b18279bb996b80ac56d380a65a325d2b6663ff2a9167
> */c/old/tex/texmf-win64/bin/context.exe
> b18ef7b0b49ea6423920b1dd50aaa643ebc984a437acc602e9c949855742e768510cc765e1c3ef75ed18b18279bb996b80ac56d380a65a325d2b6663ff2a9167
> */c/old/tex/texmf-win64/bin/luametatex.exe
> e156a063e5459a9ad9840d816ba69f9edfc448e71fda15b7d0f392cc9bfd4972e56584f2e874d67ffdf12787c969ae3cbdf5c73554cb1dff8edba518ebb50d81
> */c/old/tex/texmf-win64/bin/luatex.exe
> b18ef7b0b49ea6423920b1dd50aaa643ebc984a437acc602e9c949855742e768510cc765e1c3ef75ed18b18279bb996b80ac56d380a65a325d2b6663ff2a9167
> */c/old/tex/texmf-win64/bin/mtxrun.exe
> 
You can calculate checksums directly in Windows, rather than over a file share, 
by using PowerShell:

  PS C:\> Get-FileHash -Algorithm SHA512 C:\new\tex\texmf-win64\bin\mtxrun.exe 
| Format-List

I get the same as you do above for mtxrun.exe.

> BTW, this made me realize that `mtxrun`, `context` and `luatematex` are
> exactly the same binary.
> 
> Old worked and new didn’t. What worked for me were the 32bit binaries
> (full install from
> http://lmtx.pragma-ade.nl/install-lmtx/context-mswin.zip),

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.

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.

> 
> My Windows installation may be picky with the newest binaries, but I
> think there may be something with them.
> 
> Of course, I cannot say what that might be, but something different from
> previous compiliations.
> 
> Many thanks for your help,
> 
> Pablo



—
Bruce Horrocks
Hampshire, UK

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : [email protected] / 
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

Reply via email to