From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <10209142103.AA22000@clio.rice.edu>
Subject: Re: Two rm.exe issues on XP
To: djgpp-workers AT delorie DOT com
Date: Sat, 14 Sep 2002 16:03:21 -0500 (CDT)
Cc: acottrel AT ihug DOT com DOT au (Andrew Cottrell)
In-Reply-To: <3D837E06.F7738F12@phekda.freeserve.co.uk> from "Richard Dawe" at Sep 14, 2002 07:20:54 PM
X-Mailer: ELM [version 2.5 PL2]
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
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

> Do we know for sure that the SFT works on Windows XP? fstat uses the starting
> cluster number from the SFT as the inode, if available. If the SFT is bogus,
> then maybe that number would change per call? See
> src/libc/posix/sys/stat/fstat.c:651. Maybe someone could build the test
> program in fstat.c (build -DTEST) and see whether they can get reproducible
> inode numbers.

Results from Win2K (my XP box is off site and off the network):

C:\v204\djgpp\src\libc\posix\sys\stat>ftest 0 ftest.exe ./ftest.exe
handle-0: -1 268435457 20644 1 42 0 1032018006 Sat Sep 14 15:40:06 2002
Everything checks out OK
handle-1: -1 268435457 20644 1 42 0 1032018006 Sat Sep 14 15:40:06 2002
Everything checks out OK
handle-2: -1 268435457 20644 1 42 0 1032018006 Sat Sep 14 15:40:06 2002
Everything checks out OK
handle-3: -1 268435457 20644 1 42 0 1032018006 Sat Sep 14 15:40:06 2002
Everything checks out OK
handle-4: -1 268435457 20644 1 42 0 1032018006 Sat Sep 14 15:40:06 2002
Everything checks out OK
ftest.exe (5): 2 268435458 755 1 42 87552 1032017710 Sat Sep 14 15:35:10 2002
                        Times: 1032017710 1032017710
                        Block size: 65024
Failed to get starting cluster number; inode defaults to hashing
(if no other messages were printed, then this is either an empty
file on a local disk drive, or a file on a networked drive, or
you run under some kind of DOS clone)
SFT entry found, but is inconsistent with file size and time stamp
./ftest.exe (6): 2 268435459 755 1 42 87552 1032017710 Sat Sep 14 15:35:10 2002
                        Times: 1032017710 1032017710
                        Block size: 65024
Failed to get starting cluster number; inode defaults to hashing
(if no other messages were printed, then this is either an empty
file on a local disk drive, or a file on a networked drive, or
you run under some kind of DOS clone)
SFT entry found, but is inconsistent with file size and time stamp

Results under V2.03:
C:\djgpp\src\libc\posix\sys\stat>ftest 0 ftest.exe ./ftest.exe
handle-0: -1  65536 20644 1 42 0 1032018141 Sat Sep 14 15:42:21 2002
Everything checks out OK
handle-1: -1  65536 20644 1 42 0 1032018141 Sat Sep 14 15:42:21 2002
Everything checks out OK
handle-2: -1  65536 20644 1 42 0 1032018141 Sat Sep 14 15:42:21 2002
Everything checks out OK
handle-3: -1  65536 20644 1 42 0 1032018141 Sat Sep 14 15:42:21 2002
Everything checks out OK
handle-4: -1  65536 20644 1 42 0 1032018141 Sat Sep 14 15:42:21 2002
Everything checks out OK
ftest.exe (5): 2  65537 555 1 42 70656 1032018132 Sat Sep 14 15:42:12 2002
                        Times: 1032018132 1032018132
Failed to get starting cluster number; inode defaults to hashing
(if no other messages were printed, then this is either an empty
file on a local disk drive, or a file on a networked drive, or
you run under some kind of DOS clone)
SFT entry found, but is inconsistent with file size and time stamp
./ftest.exe (6): 2  65538 555 1 42 70656 1032018132 Sat Sep 14 15:42:12 2002
                        Times: 1032018132 1032018132
Failed to get starting cluster number; inode defaults to hashing
(if no other messages were printed, then this is either an empty
file on a local disk drive, or a file on a networked drive, or
you run under some kind of DOS clone)
SFT entry found, but is inconsistent with file size and time stamp

So, it seems consistently broken (ftest.exe and ./ftest.exe should be
the same ...) ... and I also see the same error messages under W98SE,
it hashes (on a 1.3Gb FAT32 drive), and on W95OSR2 on a FAT32 drive
or FAT12 floppy.