>>>I'll try WSH. In Windows Explorer right click on Drive and I see 2GB. For another server drive, which is 18GB, I see the correct results (3.3GB free and 18GB total). This drive is 64GB and it showed incorrectly on my Windows 95. On the server itself clicking in WE gives the correct result. The function also works correctly. So, this API function could not deal with 64GB drives on Windows 95.
>>
>>I don't know Nadya. It would seem that a 64 bit integer should be able to easily accomodate 64 gb. 2 ^ 36 is 68,719,476,736, and that leaves 15 bits not set. I don't see anything in the MSDN mentioning a problem involving the function under Win95 when it's available.
>
>Oops, I was not correct. The disk size is 68.3GB or 73,402,281,984B. Strange, the function works correctly on NT server (e.g. returns the correct result, though it's not integer anymore (I guess, I have to re-test it again, but now the server is busy doing havy replace command)). On my local machine it doesn't work.

If the local disk is partitioned, say at 2 gb, then the value returned will correspond to the size of the logical drive, not the physical one. For example, say you have a 4 gb drive divided equally into 2 logical drives, say C: and D:. GetDiskFreeSpaceEx() would only return 2 gb for either. If it's not partitioned, the function should return 4 gb. Unfortunately, I don't have a Win95 box easily available to test. Further, I don't have an NT server to bang it off of either. Maybe tomorrow I can run that test.