No, no "call". But I've found why it doesn't work. And you will not believe me! It's really totally immensely strange! So Microsoft!
This command doesn't work:
start /low "D:\BD3D2MK3D\toolset\BlockSleep.exe" c:\windows\system32\cmd.exe /c __ENCODE_3D.cmd
But this one works fine:
start /low D:\BD3D2MK3D\toolset\BlockSleep.exe c:\windows\system32\cmd.exe /c __ENCODE_3D.cmd
The ONLY difference are the quotes around "D:\BD3D2MK3D\toolset\BlockSleep.exe" !
How is it possible!
Anyway, even if removing the quotes works in this case because there is no space in the path, I can't assume that it will work everywhere. So, currently, it is not possible to use BlockSleep with BD3D2MK3D. Or is it another trick to avoid the problems inherent to the bad programming of windows and CMD.exe?
[EDIT] BTW, the cmd.exe /c trick is not necessary. Same for the "call" command. As long as there are no quotes around the BlockSleep command, it works. This one works fine:
start /low D:\BD3D2MK3D\toolset\BlockSleep.exe __ENCODE_3D.cmd