forum.vdsworld.com

[mikeholmes]

I am using vds3.51 and have found that the @file function returns a negative file size in bytes when using the Z option with a large file. It works fine on a 1500Mb file but with a file of 2291Mb I get a negative number -1948598102. Have I hit a max file size problem, or a bug, and is there any way round it?

[jules]

It looks to me as if VDS 5 might have the same problem, because the data structure that returns the file size is a 32-bit integer, which limits the maximum size it can handle to 2GB. (Can anyone verify this? I don't have any files that big.) Since you're getting a negative number, you can work around the problem for files up to 4GB by using floating point arithmetic to add this negative number to 2^32.

It is unlikely that this issue can be fixed in VDS 5, because it has been developed using a tool that doesn't support larger than 32-bit numbers.

[mikeholmes]

Thanks for your quick reply Jules. That was what I suspected. Since the file is just over 2Gb I have used your workaround to keep me going. I'll have to look at ways of getting the file size information from outside of vds - ironically I only need it to the nearest Mb.
Thanks
Mike

[trapper]

Is it possible to use the GetFileSizeEx API call? http://msdn.microsoft.com/library/default.asp?url=/library/en-us/fileio/fs/getfilesizeex.asp

If so, has anyone done it and can post their code?

Cheers.