>>>>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.
>>>
>>>As far as I know, it's not partitioned. Besides, it doesn't explain, why I got different results from my Windows 95 computer and the server itself. May be somebody else can test it? I know, we had to upgrade long time ago :)
>>
>>Older boxes (like the one I have at home) that are running Win95 (I'm running Win98SE), couldn't handle a drive larger than 2 gb without a software extension to the ROM BIOS. Perhaps this is the problem. AFAIK, the information regarding the size and free space come from the ROM BIOS which GetDiskFreeSpaceEx() deals with. If the OS doesn't recognize the software extension, that might explain it. I'll try testing tonight on my home machine and report back tomorrow. I do think, however, that I've tried this before and gotten the correct results back.
>
>Thanks a lot in advance, George. My tests indicated a problem with Windows 95 and drives over 64GB.

Nadya,

First, I tested my Win98 box last night and everything was correct with a 13 gb drive.

Second, I seriously doubt that this is a Win95 problem. If I recall correctly, you can get the correct information from a WinNT box with more than 64 gb, can you not? If so, then the problem is with the ROM BIOS, not Win95. The same GetDiskFreeSpaceEx() function is called regardless of where physical location of the computer. When the NT box is queried by the function, the function is merely returning the results from its ROM BIOS. When the Win95 box is queried, its ROM BIOS is the source.