Windows 10 - Mozart doesn't work if installed to a path with spaces

[Etherealflux]

Mozart 2's installer defaults to dropping everything into C:\Program Files\Mozart, as is standard. However, this causes oz.exe to silently quit when run. I couldn't coerce an error message out of it, no matter how hard I tried!

Installing into C:\Mozart worked flawlessly.

I'm guessing that this isn't an easy fix, so it would make sense to just make the installer default to C:\Mozart.

[layus]

These spaces in paths have been a pain for ages. We should really fix this. Mozart also fails at opening .oz files containing spaces.

That being said, we had a lot of successful windows 10 installs. May I ask what version you installed ?

[Etherealflux]

The installer is named mozart2-2.0.1-x86_64-windows.exe, and I installed it on Windows 1803 (should really get around to that update...).

[layus]

@anthonygego Any idea on what could be the root cause of this issue ? I know for sure it worked for many users on Windows 10.

[layus]

First example of bad path handling in oz: a null first parameter in CreateProcess which is kind of expected to fail as per https://docs.microsoft.com/windows/win32/api/processthreadsapi/nf-processthreadsapi-createprocessa

mozart2/opi/emacs/windows/oz.cc

Line 126 in db41d83

if (!CreateProcess(NULL,buffer,NULL,NULL,TRUE,0,NULL,NULL,&si,&pi)) {

We need to track these down...

[Etherealflux]

Hmm, this is odd. I just updated to Windows 1903, and now Mozart isn't working again..except in one case.

• If I run it from the Start Menu, a Powershell window opens, hangs there for a moment, and then vanishes.
• If I open Powershell 5.1 (Build 18362, Revision 145) and run .\oz.exe or ./oz.exe, the program quits silently.
• If I open Powershell 7.0 and run .\oz.exe or ./oz.exe, the same thing happens.
• If I run bash (I'm not sure where that's even coming from..) and then run ./oz.exe, it works.

I wonder if this is an issue with environment variables or something similar?

[anthonygego]

@layus The doc seems to say that as long as the executable name is put between quotes, this should work anyway. However it would be better to do this correctly and "fix" it :-)
@Etherealflux oz.exe actually simply launches emacs with some parameters. Are you able to launch emacs from those shells ?

[Etherealflux]

Ah, so you think it's an environment problem? That would make sense - I will check that when I get the chance.