Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#949 Windows 2003 compatible rexx version?

vX.X.X
closed
nobody
5
2012-08-14
2010-10-20
tim27
No

I am trying to get a legacy Object Rexx script (developed with v 2.1) to run on a Windows Server 2003 R2 platform, and I'm getting various problems with things like spawning of windows commands and rexx scripts, RXQUEUE's to synchronise them, and a strange error warning of 'regina.exe - Application Error The instruction at "0x77bd92f9" referenced memory at "0x00000000". The memory could not be "read".' if I try to run the script from a command prompt (i.e. outside the Object Rexx Workbench). (Very odd since as far as I can tell regina.exe is not even installed on the machine). Can you recommend a version of Object Rexx that is compatible with Windows Server 2003 R2 that might be able to run this 2.1 script? Is 2.1 Object Rexx supposed to be compatible with Windows 2003?

Discussion

  • Mark Miesfeld
    Mark Miesfeld
    2010-10-20

    " 'regina.exe - Application Error The instruction at "0x77bd92f9" referenced memory at "0x00000000". The memory could not be "read".

    For sure you have regina on the machine. As I recall there was a Windows took kit that supplied a buggy version of Regina. You'll need to find regina.exe and delete it and any files you can see that are releated to it. I'm not sure, but I think there is a regina.dll at least.

    On SourceForge, there is project called, I think, GnuWindows32. It has a whole series of Unix tools, and I believe you can download individual tools. The 'which' tool, when run form the command line where you get the Application Error will tell where regina.exe is. The command is: which regina. Similar to this:

    C:\work>which rexx
    C:/home/Interpreters/Rexx/ooRexx/rexx.EXE

    Otherwise, you will have to search the system for regina.exe. You can narrow the search down because it will be in one of the directories in the PATH.

    That said, ooRexx would be a good replacement for the very old Object Rexx. ooRexx has fixed a lot of bugs that existed in the original Object Rexx. However there is no Object Rexx Workbench.

    Object Rexx 2.1 is compatible with Windows Server 2003. I used it on Windows Server 2003 in the dim past.

    But, no matter whether you stick with Object Rexx or use ooRexx, you will continue to have problems until you locate and delete regina.

     
  • tim27
    tim27
    2010-10-20

    Thanks Mark.
    I can't find the 'which' tool, can you provide a link?
    The odd thing is if I type 'regina' or 'regina.exe' at the command line it says it can't find it, and the .rex file extension assoc definietly refers to '\odbjrexx\rexx.exe'. Also, if I bring up the task manager while the error is displayed there is an application listed as 'regina.exe - Application Error', but when I switch to the items process it's listed as 'csrss.exe'.

     
  • Mark Miesfeld
    Mark Miesfeld
    2010-10-20

    Rather than struggle to get 'which' it might be easier for you to just start Windows find and searach the whole system. It will take a while, but you could just run it in the background.

    Although, downloading which doesn't look that hard after all. Go to this page:

    http://gnuwin32.sourceforge.net/packages.html

    and follow the instructions.

    "if I bring up the task manager while the
    error is displayed there is an application listed as 'regina.exe -
    Application Error', but when I switch to the items process it's listed as
    'csrss.exe'.

    I believe you get that behavior because regina is running in a console window, quote from WikiPedia: CSRSS is mainly responsible for Win32 console windows

     
  • Mark Miesfeld
    Mark Miesfeld
    2010-10-28

    I'd like to get this resolved. On the face of it, it does not seem to be an ooRexx bug.

    To determine if it is a bug in the current code base, would you please attach an example Rexx program that produces what you think is the bug. I'll run it against the ooRexx 4.1.0 source and see if the bug exists. Thanks.

     
  • tim27
    tim27
    2010-11-22

    I found the cause of the problem was that the 'assoc' and 'ftype' method of associating the '.rex' file type with the objrexx script engine was being over-ridden by the Windows 2003 system's 'File Type' setting, so it was trying to run the scripts against a network version of regina instead of my local objrexx installation. Thanks for your help.

     


Anonymous


Cancel   Add attachments