We're pleased to announce that an OpenInsight 9.4.6 "patch" is now available for download.

You can read the details of what's included in this roll-up patch, as well as find the link for generating the download, here.

Note that since the OpenInsight OEngine is updated in this release, it must be "stamped" with your serial number, and so this patch introduces a new patch process. The download request will generate an installation executable that includes an oengine that is stamped with your requested serial number. A link to the installation executable will be shown to you after it has been dynamically created, and you should also receive the same link to download via email.

As always, please feel free to post any questions or issues you may have with the patch on the Works forum.

Thanks,

- Bryan Shumsky

Revelation Software, Inc.

We're pleased to announce that an OpenInsight 9.4.6 "patch" is now available for download.

You can read the details of what's included in this roll-up patch, as well as find the link for generating the download, here.

Note that since the OpenInsight OEngine is updated in this release, it must be "stamped" with your serial number, and so this patch introduces a new patch process. The download request will generate an installation executable that includes an oengine that is stamped with your requested serial number. A link to the installation executable will be shown to you after it has been dynamically created, and you should also receive the same link to download via email.

As always, please feel free to post any questions or issues you may have with the patch on the Works forum.

Thanks,

- Bryan Shumsky

Revelation Software, Inc.

RTI_LHSESSIONLIST is actually RTI_LH_SESSIONLIST

We're pleased to announce that an OpenInsight 9.4.6 "patch" is now available for download.

You can read the details of what's included in this roll-up patch, as well as find the link for generating the download, here.

Note that since the OpenInsight OEngine is updated in this release, it must be "stamped" with your serial number, and so this patch introduces a new patch process. The download request will generate an installation executable that includes an oengine that is stamped with your requested serial number. A link to the installation executable will be shown to you after it has been dynamically created, and you should also receive the same link to download via email.

As always, please feel free to post any questions or issues you may have with the patch on the Works forum.

Thanks,

- Bryan Shumsky

Revelation Software, Inc.

RTI_LHSESSIONLIST is actually RTI_LH_SESSIONLIST

How is this meant to work.

I do retval=RTI_LH_SESSIONLIST() and get <null> returned

Hi, Barry. Thanks for the update on the typo, I'll change it in the readme.

What version of the UD are you running (if any) on that copy of OI 9.4.6? I think that the RTI_LH_SESSIONSLIST will only work when running on a UD 5.x…I'll also update the readme to note that, too.

Thanks,

- Bryan Shumsky

Revelation Software, Inc.

Hi, Barry. Thanks for the update on the typo, I'll change it in the readme.

What version of the UD are you running (if any) on that copy of OI 9.4.6? I think that the RTI_LH_SESSIONSLIST will only work when running on a UD 5.x…I'll also update the readme to note that, too.

Thanks,

- Bryan Shumsky

Revelation Software, Inc.

Why was the oengine.dll needed to be changed?

Probably to update the version number.

The Sprezzatura Group

The Sprezzatura Blog

World leaders in all things RevSoft

Why was the oengine.dll needed to be changed?

Off the top of my head, for at least two reasons:

- We added new functionality in the "alternate debugger" that optionally lets it resume processing after capturing a runtime or fatal error; and

- So that it could be updated to match the proper new version number of 9.4.6 (admittedly, reason #2 isn't as important…)

- Bryan Shumsky

Revelation Software, Inc.

If you have already downloaded the OI_ROLLUP_PATCH_946 files, and you need to deploy them on additional systems, you can choose to download just the stamped oengine.dll.

How do you re-package the setup_OI_ROLLUP_PATCH_946_…exe with a different oengine.dll?

Cheers, M@

Vernon Systems

If you have already downloaded the OI_ROLLUP_PATCH_946 files, and you need to deploy them on additional systems, you can choose to download just the stamped oengine.dll.

How do you re-package the setup_OI_ROLLUP_PATCH_946_…exe with a different oengine.dll?

Cheers, M@

Vernon Systems

My take on this is that you run the intial 'setup_OI_ROLLUP_PATCH_946_…exe' on each user system and then copy over the oengine.dll you created for each serial number using the second option.

My take on this is that you run the intial 'setup_OI_ROLLUP_PATCH_946_…exe' on each user system and then copy over the oengine.dll you created for each serial number using the second option.

If I try that, it just complains about the serial number being incorrect.

I guess you could first replace the target 9.4.5 oengine.dll with the stamped dll that the upgrade is built for, then run the Setup…exe, then replace with the supplied 9.4.6 dll.

Cheers, M@

Vernon Systems

My take on this is that you run the intial 'setup_OI_ROLLUP_PATCH_946_…exe' on each user system and then copy over the oengine.dll you created for each serial number using the second option.

If I try that, it just complains about the serial number being incorrect.

I guess you could first replace the target 9.4.5 oengine.dll with the stamped dll that the upgrade is built for, then run the Setup…exe, then replace with the supplied 9.4.6 dll.

Cheers, M@

Vernon Systems

it just complains about the serial number being incorrect.

Oh, I thought it must have just replaced it, for all this to work.

If you have already downloaded the OI_ROLLUP_PATCH_946 files, and you need to deploy them on additional systems, you can choose to download just the stamped oengine.dll.

How do you re-package the setup_OI_ROLLUP_PATCH_946_…exe with a different oengine.dll?

Cheers, M@

Vernon Systems

Hi, Matt. When the new patch process was developed, the files were downloaded as a zip file rather than an installable exe, so it made sense to offer the option to just download the oengine.dll (which could be used with the rest of the zipped up files). However, once we made the download process "easier" (so that it now did the RDK install for you, and all the copies, etc., via an installer), and we made the installer more "fool proof" by checking for the correct serial number to replace, that functionality is no longer useful and perhaps should be removed…

HOWEVER, now that you've pointed that out, I will investigate whether I can update the installer so that if you run it with a specific command line switch, it will NOT check, nor swap out, the oengine.dll, but will rather copy in all the rest of the files and run the RDK, leaving you to manually put in an updated oengine.dll by hand…

Stay tuned for updates

- Bryan Shumsky

Revelation Software, Inc.

HOWEVER, now that you've pointed that out, I will investigate whether I can update the installer so that if you run it with a specific command line switch, it will NOT check, nor swap out, the oengine.dll, but will rather copy in all the rest of the files and run the RDK, leaving you to manually put in an updated oengine.dll by hand…

Thanks Bryan. That change sounds ideal :)

Just curious about what might happen if the 9.4.5 oengine.dll inadvertently doesn't get replaced with the 9.4.6 version? I gather that the only technical change in the dll is an enhancement to the debugger replacement. I've just tried it out of curiosity, and it seems backward compatible.

Cheers, M@

Vernon Systems

HOWEVER, now that you've pointed that out, I will investigate whether I can update the installer so that if you run it with a specific command line switch, it will NOT check, nor swap out, the oengine.dll, but will rather copy in all the rest of the files and run the RDK, leaving you to manually put in an updated oengine.dll by hand…

Thanks Bryan. That change sounds ideal :)

Just curious about what might happen if the 9.4.5 oengine.dll inadvertently doesn't get replaced with the 9.4.6 version? I gather that the only technical change in the dll is an enhancement to the debugger replacement. I've just tried it out of curiosity, and it seems backward compatible.

Cheers, M@

Vernon Systems

Maybe you just dont get this:

- We added new functionality in the "alternate debugger" that optionally lets it resume processing after capturing a runtime or fatal error; and

- So that it could be updated to match the proper new version number of 9.4.6 (admittedly, reason #2 isn't as important…)

OK, by popular demand, I have updated the patch (and the instructions as well). As before, you can choose to download the "customized" full installation executable, which contains all the updated files (exes and dlls), the "stamped" Oengine, and the RDK. Running the full installation will verify that the serial number of the oengine contained in the installation executable matches the serial number of the oengine that you're trying to upgrade, will copy in the files, and will run the RDK into OpenInsight.

If you have additional copies of OpenInsight that you wish to update, you can either re-download a full installation executable customized with the other serial number(s), OR you can now choose to just download the new oengine stamped with the other serial number(s). You can then run the full installation executable with the /O option, specifying the location of the oengine.dll that is specific to this install - for example, if you've previously downloaded the full patch for serial number D1231234, and you have now downloaded the zipped-up new oengine for serial number D3214321 and unzipped it to c:\temp:

setup_oi_rollup_patch_946_D1231234.exe /O=C:\TEMP\oengine.dll

Running the full installation with the /O option will verify that the serial number of the oengine located where /O specifies matches the serial number of the oengine that you're trying to upgrade, will copy in all the files from the installer executable EXCEPT the "embedded" oengine.dll, will copy in the oengine.dll from the specified /O location, and will run the RDK into OpenInsight.

As always, please feel free to let me know if you have any questions, or encounter any problems, during this process.

(NOTE: I'm going to also post this as its own topic, so that it's easier to find…)

- Bryan Shumsky

Revelation Software, Inc.

View this thread on the Works forum...