comment #2:

> Is the TCC shell using a different environment, like, e.g. %TEMP%, which might not be available or user accessible?

TCC uses TEMP=C:\Users\vefatica\AppData\Local\Temp (the default)

Is the TCC shell using a different environment, like, e.g. %TEMP%, which might not be available or user accessible?

Octave 9.1.0 on Windows 10. Here’s the text of an error message box from Octave.

Could not copy help collection to temporary
file. Search capabilities may be affected.
Cannot open collection file: \scratch\build\mxe-octave-w64\usr\x86_64-w64-mingw32\share\octave\9.1.0\doc\octave_interpreter.qhc

That message only appears when I issue this command in the TCC (JPSoft) shell.

    start D:\octave\mingw64\bin\octave-gui.exe --gui

The error does not occur if I issue the same command in another Windows shell (CMD, Powershell, PWSH) or if I use it (without “start”) in Window’s Start\Run dialog.

Two observations: “scratch” does not seem appropriate for Windows. Perhaps the value of %TEMP% belongs there. And Octave does not try to access that file in that location when it starts without error (so says SysInternals’s ProcessMonitor).

And a question: What would trigger that error? If the TCC shell is (partially) at fault, an answer to that question might help bring about a fix.