Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

At 06 MAR 1998 01:07:54PM David Blythe wrote:

Our application calls GET_LH_INFO on startup every day to force our files' SIZELOCKs to 0. (They are sometimes left non-0 by various OI tools.) At several customer sites, we have found that OENGINE becomes terminally busy upon doing this to some files. The .LK portions of the files in question are almost always exactly 5,820,416 bytes, or 5684 frames. OI's Database Manager locks up the same way when using its LH Info function (probably because it calls GET_LH_INFO). I've also seen other file sizes involved, but mostly 5,820,416.

This seems to be a problem with OI in general, rather than our files in particular. You can reproduce the problem by creating a .LK file as follows:

CREATE_TABLE 'DATAVOL','TEMPFILE',0,'',5740,997,1,1024,100,0

Then use OI's Database Manager's LH Info function and watch OENGINE lock up.

Any idea what is going on?


At 12 MAR 1998 10:25AM Aaron Kaplan wrote:

Didn't bother to dupe since

  • not much I could do to fix it
  • don't feel like hanging my machine.

If you download the Advanced Revelation Developers Disks you will find a SIZLOCK program in Series 5. Source is there, and even though the program was written for ARev, you'd just have to change the UI stuff for it to work. The core functionality is there. This way, you can just change the sizelock in a single whack instead of running the GET_LH_INFO program.

[email protected]

Sprezzatura, Inc.

www.sprezzatura.com_zz.jpg


At 13 MAR 1998 09:59AM Cameron Revelation wrote:

David,

The issues you reported has been logged as CPUY3SJJJ6 in our problem tracking database.

Cameron Purdy

Revelation Software

View this thread on the forum...

  • third_party_content/community/commentary/forums_nonworks/b3253a55e497a76d852565bf006399e2.txt
  • Last modified: 2023/12/28 07:40
  • by 127.0.0.1