Upgrading an OI 3.0 runtime system to 3.1x (Migration)

About upgradingā€¦

Beginning with 3.12, all official releases (ie. not necessarily pre-releases) can be run on both run-times and development copies.

For upgrading a run-time application from 3.1 or 3.11 up to 3.12, you can simply apply the 3.12 upgrade (which was released on 9/30/96). This upgrade is applicable to both full-development and runtime versions, and maintains user count and serial number information.

For 3.0 to 3.1, the upgrade will not work on a run-time deployment.

How to upgrade a runtime system from 3.0

Users must follow these instructions exactly to upgrade a 3.0 runtime application to 3.1:

1. Copy the full-development oengine.exe and reporter.exe onto a diskette and take them to the customer site

2. Make a complete backup of the OI application in case something goes wrong in steps 3 through 9.

3. Copy customer's oengine.exe to oengine.tmp (this makes a backup copy of the stamped portion of the runtime application)

4. Copy the oengine.exe and reporter.exe from the diskette onto the customer's system (this puts a full-development engine and reporter into the application, allowing the 3.1 upgrade to run)

5. Apply the 3.1 upgrade

6. Copy oengine.tmp back over oengine.exe (this is possible because the engine did not change between 3.0 and 3.1)

7. Copy reporter.run over reporter.exe

8. Delete reporter.run, oengine.run

9. Run MakEng31.exe on oengine.exe to upgrade it to 3.1 (see below)

10. At this point, the 3.12 upgrade can be applied if desired, since the run-time application is now at 3.1.

Download this file to upgrade a runtime OpenEngine 3.0 to 3.1.

Usage: MakEng31 <oengine_file>

Example: MakEng31 c:\deployed\oengine.exe

  • kb/kb_articles/kb0041.txt
  • Last modified: 2024/01/30 13:36
  • by 127.0.0.1