The AREV64 console window closes after displaying "Initialization in progress" in an application after the update to OI 10.2.1. It will open in the SYSPROG and EXAMPLES applications and another application that I created, but not in this particular one. I renamed two SYSENV records that I have associated with this application, however, it did not change the issue. I tried manually running the AREV64_STANDALONE_FORM from TCL in OI and get the same result. The window paints the background and displays Initialization in progress and then closes.

Hi, Andrew. Let's see if we can find out what process AREV64 may be running when it terminates.

Do you have anything specified for the user or application startup in the SYSENV records for the user and application?

Do you have a record in the VOC with the name of the application, the user name, or the word LOGON?

- Bryan Shumsky

Revelation Software, Inc.

Hi Bryan. There were SYSENV records for the application and user names, which I copied to *_BACKUP and then deleted the originals. There also was a VOC record named LOGON which I also copied to LOGON_BACKUP and then deleted. I restarted the application afterward, however, the issue hasn't changed.

Hi, Andrew. Might it be one of the tables you have attached in the app that are causing problems?

You can save the 'dbt' file in your OI folder for this application to some name (such as MYAPP.DBT.BAK) and then copy the SYSPROG.DBT to <yourapp>.dbt. Then start up OI, and then start up AREV64 - does it start successfully now? If it does, then it would appear that one of the tables might be causing your AREV64 to crash.

Do you have any MVBFS or SQLBFS or non-RTP57 tables attached? Are you using UNC paths? Mapped drive names?

Thanks,

- Bryan Shumsky

Revelation Software, Inc.

Hi Bryan. It turned out to be a VOC table that was being attached on another volume. I removed it and ARev64 is starting without issue now. Thanks again for your help!

Wait a minute. Why was this a problem?

Are you saying that you attached another volume that also had a VOC table? I don't see why this should be a problem. Maybe this is precisely what you want?

And it gave no error message?

Robert.

Wait a minute. Why was this a problem?

Are you saying that you attached another volume that also had a VOC table? I don't see why this should be a problem. Maybe this is precisely what you want?

And it gave no error message?

Robert.

Probably because the routine that AREV64 needed was not catalogued in that VOC.

I found I had to copy my arev voc to the default OI Voc (no overwrite) and then not attach my arev voc

Hi Barry,

Yes, that makes sense.

Still, would have expected an error about an uncatalogued routine. Maybe a messaging issue there?

Thanks,

Curious Robert.

View this thread on the Works forum...