Date:	Thu, 10 Apr 1997 20:32:51 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To:	Bernhard Baeumle <bb AT ife DOT ee DOT ethz DOT ch>
cc:	Robert DOT Hoehne AT Mathematik DOT tu-chemnitz DOT de, alaric AT abwillms DOT demon DOT co DOT uk,
	bukinm AT inp DOT nsk DOT su, djgpp AT delorie DOT com
Subject:	Re: Final comments: (Re: Desperately need help with "fopen")
In-Reply-To:	<334D0BCB.5E1B@ife.ee.ethz.ch>
Message-ID:	<Pine.SUN.3.91.970410202716.3026N-100000@is>
MIME-Version:	1.0

On Thu, 10 Apr 1997, Bernhard Baeumle wrote:

> The problem is now solved but I still do not understand why there had to
> be a problem at all!
> - SH_DENYNO = "Deny none mode"
>   ===> so what kind of flag was set by MSWord that has to be denied???
> - No matter what the flag is meant for, why can some programs read and
> others can not? Why do some programs set this flag and others dont?
> - ... and why is DJGPP's fopen() the only function I found which has
> problems with reading??? (so "SH_DENYNO" should be the default!?!?)

Asking questions is important, so thanks for bringing them into the 
open.  

However, it is much more important to dig deeper into the DJGPP library
sources, make changes that seem to solve problems, verify that those
changes don't break in other cases (like when you open a file that has NOT
been open by MSWord or any other program), and finally posting the patch
for a library function to the DJGPP news group.  This way, the entire 
DJGPP user community will benefit from the results of your 
investigations, and you gain thanks, eternal fame, and other favors.

So would you please see if making DENYNONE the default sharing bit will
solve the problem with `fopen', and if so, post the necessary changes
here?  Thanks. 

- Raw text -