I have Paradox 4.5 running under vDOS and configured to use an external script editor located at c:\me\me (yes, that's the correct vDOS path) When I invoke the editor from Paradox I land at a c:\ prompt, and the editor is not invoked. I can manually invoke the editor by typing c:\me\me, so I know it should work, but the command does not execute automatically. I have to "exit" in order for Paradox to resume.
Looking at the vDOS.log I can see "Execute: C:\COMMAND.COM(/cc:\me\me)". It appears that the lack of a space after /c causes the command line not to be recognized. This is confirmed by adding a space to the start of my command " c:\me\me" and then the program runs as expected, with the log showing "Execute: C:\COMMAND.COM(/c c:\me\me)" (note the space after the /c)
Although adding the space is a tolerable workaround in this situation, I'm seeing other command calls from Paradox that are also failing because of the lack of a space after the /c. For example, one log includes:
Because of the lacking space, the erase command is not executed and I'm left at a command prompt, and I then have to "exit" in order for paradox to resume. In this situation there is no way for me to insert the missing space, since it's a completely internal Paradox command.
Am I missing something? I've been through the documentation in detail and this issue doesn't seem to be addressed. Thanks.