>>>>>>Hi everybody,
>>>>>>
>>>>>>We have a server with 64GB hard drive with 48GB free. On my Windows 95 machine if in WE I choose properties, it shows incorrectly 2GB free and total. >Nadya,
>>>>>
>>>>>Gee, this looks familar< s >(thanks for the recognition there). If I were to hazard a guess here, I'd say that 2gb would be the amount allocated to the user. You could test this by retrieving the value that returned in lcCaller or lcFree.
>>>>
>>>>All three values are identical and equal 2147450880.00 (after converting them to Integer).
>>>
>>>You mentioned WE (I assume you mean the Windows Explorer). What shows in the drive's properties dialog that you get from the context menu? If it shows the same, then I'd guess you're seeing the limitations imposed by the network.
>>>
>>>I'm going to look a bit at the code you posted earlier to make sure that's right. I've tested against a 7+ gig drive under Win98SE and a 40+ gig under Win2K and gotten the correct results, so I'm pretty sure that it should work.
>>
>>George;
>>
>>Seems like the first version of Win 95 had a 2 gig limit. That may have nothing to do with the price of eggs in China though.
>>
>
>Tom,
>
>Oh, I know. That's why the calls to GetProcAddress() and GetModuleHandle(). The GetDiskFreeSpaceEx() wasn't available until Win 95 OSR 2, those two function calls determine if it's available.
>
>I'd suggest testing using the WSH's Scripting.FileSystemObject, but with any version of Win9x, it seems to cap the value at 2 gb.

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.