Date: Sun, 31 Jan 1999 16:10:48 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Martin Str|mberg <ams AT ludd DOT luth DOT se>
cc: DJGPP-WORKERS <djgpp-workers AT delorie DOT com>
Subject: Re: stat on FAT32 (was: Re: FAT32 (xstat.c))
In-Reply-To: <199901311250.NAA08768@father.ludd.luth.se>
Message-ID: <Pine.SUN.3.91.990131160924.19083C@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com


On Sun, 31 Jan 1999, Martin Str|mberg wrote:

> According to Eli Zaretskii:
> > Which brings up a related question: what does `stat' return for the
> > inode numbers on FAT32 volume in plain DOS mode?  Under Windows it
> > obviously invents the inode, but I suspect it does funny things in
> > plain DOS, since it doesn't expect the cluster to be a 32-bit number.
> 
> It seems to work fine. (In my test case it set st_ino to 24936.)

Yes, but is that the correct cluster number?  Can you use some low-level 
disk utility (in plain DOS) to verify?

I suspect that 24936 is only the low 16 bits of the cluster number 
(unless in your case the high bits were accidentally zero).