In short the problem is that ooRexx 3.1 is "not putting
its GUID into the registry (as scripting engines are
supposed to do)" for WSH.
I have pasted portions of emails to/from the RexxLa
forum below for a more detailed explanation.
My email to RexxLa:
I am using Windows XP sp2 and ooRexx 3.1.
I use 4Nt from JP Software.
The current problem has to do with running ooRexx
under the Windows Scripting Host (WSH).
I have been using a command line like the following
for some time now using 4Nt ver 7.
cscript.exe //e:"Object Rexx" //NoLogo wsh.rex
I just played with 4Nt 8 beta. Ver 8 has a new
"script" command that should make working with ooRexx
under WSH a bit easier. I ran into a problem. I
reported the problem to Rex Conn, the main developer at
JP Software. I have pasted, below, the pertinent part
of his reply -- part of my email to him quoted first
and then his reply.
If I enter the following command line: script /e"Object Rexx" Wsh.rexh then I get the following error: Error (SYS): Invalid class string
Rex Conn's reply to me (my original email to him):
The problem is actually with Object Rexx; it's not
putting its GUID into the registry (as scripting
engines are supposed to do). Instead, it's relying on
the GUID being embedded in XML code that CSCRIPT parses
to find the script code. (4NT & SCRIPT do not support
the XML code parsing; they expect to simply find the
executable code in the file.)
My question to RexxLa forum:
Is Rex Conn correct that ooRexx should be putting
its GUID into the registry and is he accurate that
ooRexx does not so do?
Mark Hessling's reply to me:
Yes, Rex is probably correct. ooRexx does not add any
GUIDs to the registry for the WSH Engine.
Please raise a bug report on SourceForge.