Date: Wed, 17 Jan 2001 13:54:48 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: "Peter J. Farley III" <pjfarley AT banet DOT net>
cc: djgpp-workers AT delorie DOT com
Subject: Re: patch for statfs.c
In-Reply-To: <5.0.2.1.0.20010116201246.027709d0@pop5.banet.net>
Message-ID: <Pine.SUN.3.91.1010117135429.18768T-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Tue, 16 Jan 2001, Peter J. Farley III wrote:

> Wherever I got the 8-26-97 version of df.exe, it is the 
> *only* version that agrees with WinExplorer, and therefore I think we 
> must conclude that *someone* updated that version to use a statfs.c 
> that uses AX7303, which is the only place that value could come from.

It should be possible to trace the interrupts issued by that strange
version of df.exe, using a suitable tool.  I believe some people on
this list have such tools (I've seen in the past output which suggests
that).  Perhaps they could run 2 or 3 versions of df on the same CD
and see what functions do they call.  That might give us a clue as to
what's going on there.

Martin, is it possible that there was any code in August 1997 which
used AX7303, and that a version of df was built with that code?  I
think the only possibility is that you built such a version and
distributed the binary, but I don't remember when was the initial
version of FAT32 support written.