Thank You, and a question

[PhilKab]

Hello,

(Context : Window 11 with VSCode)

Very pleased to find a new version 0.91 of Extempore now,  using Scheme S7.
However I have un problem with this version: as soon as I try to run the program "./extempore.exe"" in VsCode, it raises an error "unable to locate the file init.xtm" which is there in a sub-directory, the problem reminds the same when I put it in the same folder (yet version 0.89 works perfectly well).

Is that a bug, or something I have not understood ?

Thanks for your help

Regards.

Ph.C

[George]

PhilKab

I'm running MacOS Tahoe 26.5 on a MacBook Air and not familiar with Windows.

However I had the same problem. I asked on this thread: 

https://groups.google.com/g/extemporelang/c/A7hrvQkDfUs/m/uIrT_h3IAAAJ

and Ben sent this solution which worked for me:

https://groups.google.com/g/extemporelang/c/A7hrvQkDfUs/m/FDhP-i_XAAAJ

attr -dr com.apple.quarantine extempore 

Of course the "com.apple.quarantine" would have to be different on yours.

Regards

George

[Ben Swift]

Hey Phil

There was a packaging bug with the 0.9.0 release - try the new 0.9.1 tarball and see if that works.

Ben

>--
>You received this message because you are subscribed to the Google Groups "Extempore" group.
>To unsubscribe from this group and stop receiving emails from it, send an email to extemporelan...@googlegroups.com.
>To view this discussion visit https://groups.google.com/d/msgid/extemporelang/d95d7083-2224-4832-9cd7-328f22a07f4fn%40googlegroups.com.


--

Cheers,
Ben

[PhilKab]

Hello George and Ben,

(Thank you for your replies)
Unfortunately, I tried versions .90 and .91, and got the same error on init.xtm. Regarding the solution mentioned for Mac, I asked DeepSeek/Gemini if ​​there was an equivalent solution for Windows 11, but without any real success.

And in fact, I don't quite understand this attribute problem (I'm not very familiar with it).

Best regards, Ph.C

[Ben Swift]

Hey Phil,

The "attribute" thing George mentioned was the macOS quarantine flag --- Windows doesn't have an equivalent, so you can ignore that part.

In v0.9.1, extempore.exe looks for runtime/init.xtm relative to the current working directory. So the CWD when you launch it needs to be the unzipped extempore folder (the one that has extempore.exe, runtime/, libs/ etc. sitting side by side). VSCode's integrated terminal often opens at the workspace root, which may not
be that folder.

Two things to try:

1. Before running, check where you are. In the VSCode terminal:

Get-Location

1. If that isn't the unzipped extempore folder, cd into it first, then run:

cd C:\path\to\extempore-windows-x86_64-v0.9.1
./extempore.exe

2. Or skip the CWD step entirely by passing an absolute --sharedir:

./extempore.exe --sharedir "C:\path\to\extempore-windows-x86_64-v0.9.1"

If neither helps, could you send back:

- the output of Get-Location immediately before running extempore.exe
- the full path you unzipped the release into
- the exact command line you ran
- the complete error output (there may be more than just the init.xtm line)

And confirm that runtime\init.xtm actually exists inside the unzipped folder. With those, we should be able to nail down what's going on.

Cheers,
Ben

>To view this discussion visit https://groups.google.com/d/msgid/extemporelang/a5a6ea4d-a164-4949-89ba-4292f79c8e02n%40googlegroups.com.


--

Cheers,
Ben

[PhilKab]

Hi Ben,

It works perfectly well with " /extempore.exe --sharedir "C:\path\to\extempore-windows-x86_64-v0.9.1"  " :

C:\Users\phili\Documents\Programmes\extempore0.9.1> ./extempore.exe --sharedir "C:\Users\phili\Documents\Programmes\extempore0.9.1"                          
------------- Extempore --------------
Andrew Sorensen (c) 2011-2026
and...@moso.com.au, @digego

ARCH           : x86_64-pc-windows-msvc
CPU            : meteorlake
LLVM           : 22.1.1 ORC JIT
Output Device  : Haut-parleurs (Realtek(R) Audio
Input Device   :
SampleRate     : 44100
Channels Out   : 2
Channels In    : 0
Frames         : 1024
Latency        : 0.0928798 sec
Primary        : thread 0
---------------------------------------
INFO: starting utility process...
INFO: server: accepted new connection to utility process
INFO: client: connected to server utility process at localhost:7098
Listening on TCP port 7099 --- connect your editor to send code.
INFO: starting primary process...
INFO: server: accepted new connection to primary process
INFO: client: connected to server primary process at localhost:7099
Loading xtmbase library... done in 2.040183 seconds

Ready to explore the new extempore.

I'm very grateful that you took the time to fix it, 

best regards from France (Lyon)

Phil