Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!snorkelwacker.mit.edu!bloom-beacon!eru!hagbard!sunic!news.funet.fi!polaris.utu.fi!polaris!sutela
From: sutela@polaris.utu.fi (Kari Sutela)
Newsgroups: comp.sys.amiga.introduction
Subject: Re: Locks and XOper (also alerts on os 2.0)
Keywords: Xoper ARTM
Message-ID: <sutela.672658357@polaris>
Date: 26 Apr 91 09:32:37 GMT
References: <1991Apr19.122837.1@watt.ccs.tuns.ca> <1991Apr21.223326.46280@vaxb.acs.unt.edu> <75@taloa.unice.fr> <1991Apr24.231538.7134@sbcs.sunysb.edu>
Organization: University of Turku, Finland
Lines: 20

In article <75@taloa.unice.fr> beust@mimosa.unice.fr writes:

>
>  Regarding XOper: it provides a "Lock/UnLock" function, but I never managed
>to make it work. I suspect it allows you to unlock Locks that haven't been
>released by some programs.

Yes, I have managed to do so.  I *think* (but am not sure) that you must
provide the *address* of the lock as the parameter, not the name of the
locked file.  You also can use the `menu' feature; hit <esc> (I think <esc>
is the correct key) and move the cursor on the lock and type `unlock'.

Anyway, it seems that Xoper doesn't like some os 2.0 features.  I have managed
to cause a recoverable alert (Free Memory Twice) when I have used the `zoom'
gadget on the Xoper window.  Unfortunately, the alert isn't recoverable:
shortly afterwards the machine locks up.  I'm using os release 2.01 on an
A3000.

-- 
Kari Sutela	sutela@polaris.utu.fi