From: SourceForge.net <no...@so...> - 2006-06-22 17:37:43
|
Bugs item #1510821, was opened at 2006-06-22 13:37 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1510821&group_id=119701 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: mdlueck (mdlueck) Assigned to: Nobody/Anonymous (nobody) Summary: DirectX setup and beta 1 are not happy together Initial Comment: Simply swapping out builds of ooRexx from the 3.01 to 3.1 beta 1, DirectX scripted setup now throws a couple of dialog boxes and bombs off. I just reverted our build of ooRexx to the 3.01 and the automated install went directly through the DirectX install just fine, as always. Win2K SP4, all of the hot fixes... but mind you the ooRexx based automated deployment is installing many of those. I don't even being to have a clue how we are going to track this one down. I seem to recall DirectX's setup being grumpy once long ago... no clue what I tracked it down to that time. Anyway, here to help, but I have to call this a show stopper with beta 1. I have tried backing out the ORexxScript stuff, did not fix this bug. (Thus not related to bug 1205338) Oh, error dialog is attached to this ticket. Thanks, Michael ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1510821&group_id=119701 |
From: SourceForge.net <no...@so...> - 2006-06-28 00:49:26
|
Bugs item #1510821, was opened at 2006-06-23 03:37 Message generated for change (Comment added) made by rexx You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1510821&group_id=119701 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. >Category: Installation Group: None Status: Open Resolution: None Priority: 5 Submitted By: mdlueck (mdlueck) >Assigned to: Mark Hessling (rexx) Summary: DirectX setup and beta 1 are not happy together Initial Comment: Simply swapping out builds of ooRexx from the 3.01 to 3.1 beta 1, DirectX scripted setup now throws a couple of dialog boxes and bombs off. I just reverted our build of ooRexx to the 3.01 and the automated install went directly through the DirectX install just fine, as always. Win2K SP4, all of the hot fixes... but mind you the ooRexx based automated deployment is installing many of those. I don't even being to have a clue how we are going to track this one down. I seem to recall DirectX's setup being grumpy once long ago... no clue what I tracked it down to that time. Anyway, here to help, but I have to call this a show stopper with beta 1. I have tried backing out the ORexxScript stuff, did not fix this bug. (Thus not related to bug 1205338) Oh, error dialog is attached to this ticket. Thanks, Michael ---------------------------------------------------------------------- >Comment By: Mark Hessling (rexx) Date: 2006-06-28 10:49 Message: Logged In: YES user_id=86185 No idea if this might have any effect on this bug or 1205338, but the 3.1 beta 2 now installs the file association for .rex to "RexxScript" not "ooRexx" as the 3.0.1 and 3.1 beta 1 did. This was to bring ooRexx back to being consistent with Object Rexx. See HKEY_CLASSES_ROOT\REXXScript ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1510821&group_id=119701 |
From: SourceForge.net <no...@so...> - 2006-10-24 04:32:30
|
Bugs item #1510821, was opened at 2006-06-23 03:37 Message generated for change (Comment added) made by rexx You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1510821&group_id=119701 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Installation Group: None >Status: Closed Resolution: None Priority: 5 Private: No Submitted By: mdlueck (mdlueck) Assigned to: Mark Hessling (rexx) Summary: DirectX setup and beta 1 are not happy together Initial Comment: Simply swapping out builds of ooRexx from the 3.01 to 3.1 beta 1, DirectX scripted setup now throws a couple of dialog boxes and bombs off. I just reverted our build of ooRexx to the 3.01 and the automated install went directly through the DirectX install just fine, as always. Win2K SP4, all of the hot fixes... but mind you the ooRexx based automated deployment is installing many of those. I don't even being to have a clue how we are going to track this one down. I seem to recall DirectX's setup being grumpy once long ago... no clue what I tracked it down to that time. Anyway, here to help, but I have to call this a show stopper with beta 1. I have tried backing out the ORexxScript stuff, did not fix this bug. (Thus not related to bug 1205338) Oh, error dialog is attached to this ticket. Thanks, Michael ---------------------------------------------------------------------- >Comment By: Mark Hessling (rexx) Date: 2006-10-24 14:32 Message: Logged In: YES user_id=86185 Submitter requested this be closed. ---------------------------------------------------------------------- Comment By: Mark Hessling (rexx) Date: 2006-06-28 10:49 Message: Logged In: YES user_id=86185 No idea if this might have any effect on this bug or 1205338, but the 3.1 beta 2 now installs the file association for .rex to "RexxScript" not "ooRexx" as the 3.0.1 and 3.1 beta 1 did. This was to bring ooRexx back to being consistent with Object Rexx. See HKEY_CLASSES_ROOT\REXXScript ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1510821&group_id=119701 |