To produce the bug create two big files as follows: $ dd if=/dev/zero of=tmp.dat count=8388607 4294966784 bytes (4.3 GB) copied, 252.983 s, 17.0 MB/s
$ dd if=/dev/zero of=tmp.dbt count=8388610 4294968320 bytes (4.3 GB) copied, 225.764 s, 19.0 MB/s The ls command (and also the dir command) in a shell session prints the filesize right. bash-3.2$ ls -l total 8388612 -rw-r--r-- 1 MaierHa users 4294966784 Apr 25 17:43 tmp.dat -rw-r--r-- 1 MaierHa users 4294968320 Apr 25 17:47 tmp.dbt But in dired the result is as follows: d:/tmp: total used in directory 4194305 available 7443304 -rw-rw-rw- 1 MaierHa root 4294966784 04-25 17:43 tmp.dat -rw-rw-rw- 1 MaierHa root 1024 04-25 17:47 tmp.dbt It looks that filesizes greater max integer are not displayed correctly. This bug happens only on the W32 platform. Harald In GNU Emacs 22.0.99.1 (i386-mingw-nt5.1.2600) of 2007-04-24 on LENNART-69DE564 (patched) Windowing system distributor `Microsoft Corp.', version 5.1.2600 configured using `configure --with-gcc (3.4) --cflags -Ic:/g/include' Important settings: value of $LC_ALL: nil value of $LC_COLLATE: nil value of $LC_CTYPE: nil value of $LC_MESSAGES: nil value of $LC_MONETARY: nil value of $LC_NUMERIC: nil value of $LC_TIME: nil value of $LANG: DEU locale-coding-system: cp1252 default-enable-multibyte-characters: t
