Menu
▾
▴
#74 ooRexx 3.0.1
OS: Windows XP Home
ooRexx version: REXX-ooRexx_3.0(MT) 6.00 28 Mar 2005
When I try to run any of the sample\wsh\ .htm files in
IE 6, on
Windows XP, I get the following error messages:
i. "WinQapi - RXAPI execution failed. Error Code 2". ii "ERROR - Could not start Object REXX API Manager
(RXAPI.exe)!"
If I start rxapi.exe prior to trying to run the sample
file,
then I don't even get the error messages; IE just instantly
disappears completely.
-- Bernie Schneider --
berniegsemail-junk@yahoo.com
Discussion
Anonymous
Logged In: YES
user_id=1424286
When I include the rxapi.exe file in a windows installer
setup program (using WISE windows installer), I get a
similar error message as follows:
[WinQapi] RXapi execution failed Error Code 2
[ERROR] Could not start Object REXX API Manager(RXAPI.EXE)
Note, this is before attempting to run any Rexx scripts or
any such thing, this is just supposedly while copying files
across.
Logged In: YES
user_id=1223125
Originator: NO
The .htm sample files were written before IE had very much security. I can execute all these examples with 3.2, but IE prevents the Active Controls from functioning.
If such samples are going to be included, they should probably have a disclaimer that practically all security in IE will have to be turned off.
Windows Scripting Host (WSH) has been temporarily disabled in ooRexx 4.0.0. The WSH implementation code is not compatible with the refactored interpreter and needs to be completely rewritten. The old code used undocemented, unsafe, APIs. Those APIs no longer exist.
The WSH bugs are bugs in the old code. The old code is not going to be used, so technically, the bugs are not going to be fixed.
This bug will put into the postponed state and used to ensure that this type of bug does not exist in the re-written WSH support. At that time it will be closed.