Mail Archives: djgpp/1998/05/09/07:17:39
In article <Pine DOT SUN DOT 3 DOT 91 DOT 980508122920 DOT 9473C-100000 AT is>, Eli Zaretskii
<eliz AT is DOT elta DOT co DOT il> writes
>
>On Wed, 6 May 1998, Paul Shirley wrote:
>
>> I've just investigated a related problem (in W95JED)
>
>What's w95jed?
The Win95 native build of JED (the text editor).
>The data I gathered pertained to the time the file was opened, not
>closed, and the difference was much larger (1-3 seconds).
The differences I see are in a program that does this:
1: create file,write file,close file.
(On small files this should show <1 second after rounding...
it should be taking milliseconds to complete)
2: FindFirstFile, extract the last write time, store it.
3: <waste some time>
4: FindFirstFile, compare last write time.
And this step shows a *different* time stamp to that from step 2
This is a problem because Jed uses the timestamp to detect files changed
by other process's/users. Its bloody annoying being wrongly told all
your files have changed after every edit/compile cycle.
>
>Which version of Windows did you test this on? Please look up the
>version in the Control Panel/System/System Properties display, not
>with the VER command.
OSR 2.1 (AKA 4.00.950 B), the most recent win95 version I believe.
>And second, what has cache-flush time to do with file time stamp?
It *should* have nothing to do with it.
Maybe no-one told the clowns in Redmond :)
>So I'm not sure I understand what exactly were you saying. Can you
>please elaborate?
What I'm saying is very simple. Win95's file system probably is screwed
however unbelievable that may seem to you (and frankly to me).
---
Paul Shirley: my email address is 'obvious'ly anti-spammed
- Raw text -