Zorro command line issues

Hi jcl. In testing Zorro's command line features over the weekend I came up with these issues / potential misunderstandings / enhancement request:

a) The 2nd example in the manual appears incorrect - doesn't the script name need to be at the end? I couldn't get it to work placing the script name after -run when a further option was used.

b) For Zorro S users, all the examples are incorrect? On my test system, Zorro does not start in S mode unless it's started in the Zorro folder - either by 1st cd to that folder (command line or Explorer), via using a shortcut with the Zorro folder specified as Start in, or via the start command with the /d parameter...

c) The -d switch does not appear to accept a value for the name - is this correct? If so, can this enhancement be made; or more generally just allow the entire #define statement to be passed?

Thanks.

The order of options does not matter, and the script name needs not be at the end - it can be anywhere as to my knowledge.

And of course the examples are no different for Zorro S. I'm not sure why you got problems, but when experimenting with the command line, check that you start the right Zorro if you have different versions installed.

Thanks jcl.

a) I can't reproduce the problem I was having, so I guess for now we'll call this another late night user error.

b) I have only 1 Zorro install on the test machine. If I "cd \" and then "\my program files (x86)\zorro\zorro" I do not get S. If I "cd \my program files (x86)\zorro" and then "zorro" I get S.

c) Can -d pass a value as well as the name? Or perhaps an entire #define string?

Thanks.

When starting Zorro from a command shell, make sure that the current directory is the Zorro folder, otherwise it can not access certain files in that folder, such as your S registration. -d creates a name definition, not a value. For numeric data or for passing more information to the script, use an .ini file.

Thanks jcl.

Re. Zorro folder, I'm not sure what you mean by "can not access". There is no permission problem - Zorro just appears to be looking for these files in the current folder rather than in (or relative to) the folder where the program resides.

Re. -d, can it be enhanced to pass value also? Or the entire #define?

Re. .ini, you mean a .ini of my/our own creation, correct? Not Z.ini?

Thanks.