Date:	Tue, 8 Jun 1999 11:41:13 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	salvador <salvador AT inti DOT gov DOT ar>
cc:	djgpp AT delorie DOT com
Subject:	Re: Open file created by child: problems under W95 (most machines)
In-Reply-To:	<375C0879.A0720BD2@inti.gov.ar>
Message-ID:	<Pine.SUN.3.91.990608114053.4197K-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Mon, 7 Jun 1999, salvador wrote:

> But the problem comes whe I try to
> read the information from this file. Looks like even when the file
> exists I can't open it for a while (more than 1 second!), the most crazy
> detail is that it happends in most machines I tried, but not all.

It could be that Windows denies access to the registry for a while,
after it has been changed, perhaps because some OS components re-read
it.

Did you try to set some bits in __djgpp_share_flags?  It might help.

I have a working program that lists all files open on a Windows 9X
system, including those open by system DLLs and all Windows programs.
The program lists every file with its open flags, so you could see
whether the registry is open, and if so, why is Windows denying access
to it.  I can send you the source if you want (it is compiled with
DJGPP).

If nothing else helps, you could write a busy-wait loop that waits for
the file to become accessible, with some appropriate time-out.

- Raw text -