Muta,

> I found that I needed to
> add "c:" before the "/c".

No (not exactly).

> Any idea what that is about?

Yes.

A question though: Have you already tried to replace that "c:" with
something like "foo", "bar" or just some other random string / character ?
Why not ? :-)

> I don't see it mentioned in "cmd /?" nor the CreateProcess()
> documentation.

Look again :

[quote]
If both lpApplicationName and lpCommandLine are non-NULL,
.....
Because argv[0] is the module name, C programmers generally ***repeat the
module name as the first token in the command line***.
[/quote]

("***" added for emphasis)

Regards,
Rudy Wieser

On Tuesday, May 25, 2021 at 6:30:11 PM UTC+10, R.Wieser wrote:

> Because argv[0] is the module name, C programmers generally ***repeat the
> module name as the first token in the command line***.

Thanks Rudy!

I'm now on to hopefully the last problem, this time
seemingly with HX.

But it seems to me that this is quite misleading:

To run a batch file, you must start the command interpreter; set lpApplicationName to cmd.exe and set lpCommandLine to the following arguments: /c plus the name of the batch file.

It doesn't suggest that you're supposed to put something
before the "/c" as mentioned elsewhere.

BFN. Paul.

Paul,

> Thanks Rudy!

You're welcome. And yes, I've run into the same problem myself. :-)

> But it seems to me that this is quite misleading:
....
> It doesn't suggest that you're supposed to put something
> before the "/c" as mentioned elsewhere.

True, but they are talking about a Microsoft OS, not FreeDos. And its
rather possible that its not the problem of the CreateProcess function, but
that of the executed program : /it/ expects the modulename to come first.

Than again, I seem to remember a similar problem, which I solved by starting
the commandline arguments with a single space.

Regards,
Rudy Wieser