Sender: root AT delorie DOT com
Message-ID: <375D1BA5.5258850B@inti.gov.ar>
Date: Tue, 08 Jun 1999 10:33:25 -0300
From: salvador <salvador AT inti DOT gov DOT ar>
Organization: INTI
X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.0.36 i686)
X-Accept-Language: es-AR, en, es
MIME-Version: 1.0
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
CC: djgpp AT delorie DOT com
Subject: Re: Open file created by child: problems under W95 (most machines)
References: <Pine DOT SUN DOT 3 DOT 91 DOT 990608114053 DOT 4197K-100000 AT is>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp AT delorie DOT com

Eli Zaretskii wrote:

> 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.

Is not the registry, is the file exported by regedit. The /E switch tells
regedit: Export to the following file. I'm not modifying the registry (yet
;-). By now I only search some information like: What's the name of the
directory where programs should be installed? (Program Files in english),
What's the directory for the desktop? What's the directory for the menu?

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

Nope, didn't try.

> 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).

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.

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

Currently I'm trying upto 100 times waiting 100 ms between tries. In this way
if the file remains unaccesable for more than 10 second I give up and also I
don't hog the system trying so quickly.

SET

--
Salvador Eduardo Tropea (SET). (Electronics Engineer)
Visit my home page: http://welcome.to/SetSoft or
http://www.geocities.com/SiliconValley/Vista/6552/
Alternative e-mail: set-soft AT usa DOT net set AT computer DOT org
                    set AT ieee DOT org set-soft AT bigfoot DOT com
Address: Curapaligue 2124, Caseros, 3 de Febrero
Buenos Aires, (1678), ARGENTINA Phone: +(5411) 4759 0013