Wrong filesizes in AjaXplorer

Are files < 2 GB reported correctly? I am thinking that the app might be doing 32 bit arithmetic.

looked at some files and this is correct, however one file of 3,8G was also reported as 3,88Gb, 4,1G was reported as 110,7 Mb.

This was fixed in a recent ajax explorer update. 5.something I think. What version did you install?

steve

Strange I installed 5.1 from this forum but the version in xlporer says 4.2.0...
Just checked the forum and Xplorer - aka Ajaxplorer version 5.1 is indeed 4.2.0 (the latest version).

It's fixed in the latest versions, but you still need to use the AllowRealSizeProbing feature. Here's a copy of what i wrote in another thread :

"The issue with PHP filesize was that PHP, at least in 32 bit environnement, encodes the filesize with 31 bits, meaning that filesizes over 2GB are always false (there is a tweak to use the 32nd bit to increase the filesize to 4GB).
What i wrote in another thread is that it doesn't matter when i'm moving files in the same repository, but each time the filesize was used (copy, download...), there was an error.
With the new version and it's new config system, the AllowRealSizeProbing feature (which uses the filesize function of the system, instead of the PHP function) finally works for me, and i finally get all my filesizes over 2GB correctly."

In this thread :
viewtopic.php?f=36&t=59985


Btw, the AllowRealSizeProbing feature doesn't work for remote repositories, because it can't use the system filesize, you'll always see 2GB files (i do with both my brother's own ftp). I haven't tried with anything else than ftp.

tiranor wrote:
...Btw, the AllowRealSizeProbing feature doesn't work for remote repositories, because it can't use the system filesize, you'll always see 2GB files (i do with both my brother's own ftp). I haven't tried with anything else than ftp.

This would be with AjaXplorer???

ftp certainly does display the correct size for files > 4 GB.

Ajaxplorer uses the PHP filesize, with all its limitations.
When using the AllowRealSizeProbing feature, it uses the system filesize for the local repositories, but i guess it can't with remote repositories.

Got it. The ftp remark is what was confusing me.

Ok the problem seems somewhat fixed now.
I enabled real size probing in global configurations-access-file system (standard)
The size shows now ok, but when copying a file larger than 4 something G, to the connected usb drive only the first part get copied.
The new file size is 4,29 GB which means the file is corrupt.

So problem partially solved, any suggestions?

Is the USB drive formatted as FAT32? That format is limited to 4G file sizes.