Date: Wed, 9 Jun 1999 11:22:20 +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: <375D1BA5.5258850B@inti.gov.ar>
Message-ID: <Pine.SUN.3.91.990609112150.11862D-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Tue, 8 Jun 1999, salvador wrote:

> > 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.
> 
> Is not the registry, is the file exported by regedit.

Yes, I misunderstood your message.  Sorry.

Is it possible that running regedit actually runs two programs, and
the other one is still updating the file when regedit exits?  Perhaps
the systems where this problem shows have some ``improved'' version of
regedit?

> Ok, send me it, the problem is how to run it in the right moment, I hope
> I can spawn it while the file stills unaccesable.

The source sent in a separate message.

I suppose you could run it from the same loop that waits for the file
to be accessible, just redirect its output to a file and then examine
that file.