rc>> NetWare supports full file locking, to the same
 rc>> extent as SHARE, as far as I know.

 DN> Well, sort of, but 'no'.

 rc>     Sure about that?

Yes.


 DN> file locking is not explicitly supported by the NetWare shell. You
 DN> can,however, load a small TSR called INT2F.COM and install support -
 DN> that translates share calls to IPX locking calls.

 rc>     It's supported by the shell we use.

Explicit support must have been linked in. This isn't, however, the
default. ..or wasn't, at least, with Novell 3.12 and earlier.


 rc>     Ezychat, written in a mix of QuickBASIC and ASM. 
 rc> (Please don't lynch me. :) ). At initialisation, I 
 rc> check for generic SHARE capability by creating a temp 
 rc> file (in denynone mode), and attempting to lock it. If 
 rc> that fails, then Ezychat refuses to continue.

How do you check?

BTW, the "is share installed" check via INT 2Fh will succeed on
Novell and even under Windows even though it isn't. Some of the
functionality (specifically involving FCBs) is actually present, but
locking and unlocking will both return dos error 1 (unsupported/unknown
function). The same goes for situation where share is loaded with the /NC
switch, or automatically if it resides in the root directory and there's a
large DOS partition present.

If the file locking calls themselves are actually working, though, you
obviously don't have a problem.



--- Maximus/2 3.00.568 beta