Hi Roger,

On 8/13/2013 5:29 PM, Roger Bilau wrote:
another little problem: at the beginning I used Windows_BSF4ooRexx_Setup_406-20110822-x64.exe

Because of my problem I download the new version, uninstalled 406 with the function, that was available in the

Windows Menu and installed BSF4ooRexx_install-20130107-GA.zip as described in bsf4oorexx\install\readme-Windows.txt.


After the installation, I had once various issues:

1.       I could’nt start the jrexx scripts as before (instead my editor opened with the script)

2.       In attempt to solve the problem I wanted to start SetupBSF.rex and got


C:\Program Files\BSF4ooRexx\install>rexx setupBSF.rex

   241 *-* call SysFileTree cmd.eSuperDir2||"bsf*.jar", "cmd.eJarBaseNames.", "FO" /* query for the jars we need */

Error 40:  Incorrect call to routine

Error 40.919:  Argument 2 must have a stem object or stem name value; found "cmd.eJarBaseNames."

Ah, yes, I seem to recall that this is new to ooRexx 4.1.3 where a compound variable must not have a trailing dot.

The solution: I copied BSF4ooRexx.dll, libBSF4ooRexx.dylib and libBSF4ooRexx.so from C:\Program Files\BSF4ooRexx\install\64  to the C:\Program Files\BSF4ooRexx,

run setupFileAssociations.rex and three fileAssociations_for_RE*_add.reg files (don’t know I any was necessary).


After changing the extension of my script I could continue with my JDBC Tests, but I’m not sure that anything is now correctly installed!?

What I lost are the entries in the Windows Menu.


So it seems to me that the installation instruction in the readme are not complete or the C:\Program Files\BSF4ooRexx\install\windows\install.cmd don’t work correct.

Or did I miss something?

Well, you have been bitten by a reimplementation of SysFileTree in ooRexx 4.1.3 which adheres to the original definition of what constitutes a stem (simple name having a single trailing dot).

Luckily, there is a solution to this in the current beta of BSF4ooRexx, which has been stable, such that I can advise to use that even for production systems.