Message-Id: <5.0.1.4.0.20001119153421.02591e50@pop5.banet.net> X-Sender: usbanet DOT farley3 AT pop5 DOT banet DOT net X-Mailer: QUALCOMM Windows Eudora Version 5.0.1 Date: Sun, 19 Nov 2000 15:50:25 -0500 To: djgpp-workers AT delorie DOT com From: "Peter J. Farley III" Subject: Q's re: F_GETLK and DOS/Win interfaces Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Reply-To: djgpp-workers AT delorie DOT com In further researching the F_GETLK fcntl function, I see that Mark E.'s comment in his fcntl source that the int21/5C interface does not return information on what lock prevented this request is true, at least according to the Ralf Brown list. However, I also see in that list that there were internal structures for SHARE.EXE which tracked what "records" (file areas) are currently locked. I assume that the W9x and NT/2K replacement for SHARE.EXE, the IFSManager, has equivalent functions and data structures. Does anyone know the answers to these questions: Q1: Is there any doc (outside of a developer non-disclosure agreement with M$) on the API to the IFSManager locking functions? Q2: If someone already knows about this API, is it worth our time trying to investigate it? I.E., assuming it exists, is it easily callable from a DOS box, and is it functional when used from a DOS box? Obviously, my thought was to use it for the F_GETLK function *if* it's available and usable, and fall back on the current behavior (i.e., do nothing but return failure when the lock is not obtainable) in plain DOS mode. I don't want to waste my or anyone else's time if the API isn't publicly documented, or if it is unusable from a DOS box. TIA for any info or advice you can offer. --------------------------------------------------------- Peter J. Farley III (pjfarley AT dorsai DOT org OR pjfarley AT banet DOT net)