SourceForge has been redesigned. Learn more.
Close

#78 v3.0.1 causes explorer.exe to crash

closed
nobody
None
5
2012-08-14
2005-05-19
mdlueck
No

This one looks to be no fun at all to track down. Issue
involves migrating a controlled OS imaging environment
from ORexx 2.1.3 to ooRexx 3.0.1 - only the rexx
version is changed to cause the following error.

Win2K SP4 is the OS, some fixes in the image, others
are script installed.

IE is not upgraded in the image, an IEAK created
IE6SP1build is script installed once Win2K is booted.

Image is set to auto logon to the Administrator local
account to allow the scripting to take place.

At the next boot after IE is script installed, it does
some RunOnceEx keys to finish the install. While that
is processing, if ooRexx 3.0.1 is the rexx installed, a
dialog box pops stating explorer.exe crashed. This has
never been an issue with any ORexx version going back
to 1.0.3.0.

I have tested not setting up the RxAPI service to see
if that was the issue, the crash persists.

Migration to ooRexx pauses for now I guess...

Discussion

  • mdlueck

    mdlueck - 2005-05-20

    Logged In: YES
    user_id=1014305

    It seems the crash is related to the class registry entries
    - some of the Windows OLE bla bla bla stuff I think. A .reg
    is attached of the entries / keys I dropped. IE installs /
    does the RunOnceEx perfectly now.

    What exactly did I disable by dropping this bit? If I invoke
    rexx only from rexx.exe (or mod_rexx) is anything inside the
    rexx source files affected by this, or is this class stuff
    for the WSH, etc... and thus I should be OK? (I guess the
    fact that it got through an entire load process which is
    driven by rexx is a pretty good indication that I should be
    safe. OODialog need this stuff?)

     
  • mdlueck

    mdlueck - 2005-05-20

    Removed Registry Keys and Entries

     
  • mdlueck

    mdlueck - 2006-06-22

    Logged In: YES
    user_id=1014305

    Tested with ooRexx 3.1 beta 1 and this is resolved with that
    build. Once 3.1 is released I will test again.

     
  • mdlueck

    mdlueck - 2007-04-05

    Logged In: YES
    user_id=1014305
    Originator: YES

    This problem has been resolved with, at least, the current stable build of ooRexx: 3.1.1rc2.

    This bug report may thus be closed.

     
  • mdlueck

    mdlueck - 2007-04-25

    Logged In: YES
    user_id=1014305
    Originator: YES

    Fix confirmed with ooRexx 3.1.2

     

Anonymous
Anonymous

Cancel  Add attachments