>>>>>>>No, it's running Win9x, and cast the return value as an Integer; the value returned is the largest available integer in a VFP integer value (2^31-1). It's a problem related to how Win9x interprets the data type; NT and NT derivatives will use a real rather than an integer, and will return the correct size. I thought this was corrected in WSH 2.1 or 5.
>>>>>>
>>>>>>Ed,
>>>>>>
>>>>>>As I've found out, the same is true under VFP 6.0 SP5. Under Win9x, DISKPACE(), for example, will return values that are capped at 2gb. However, under Win2K Pro, it returns the correct amount.
>>>>>
>>>>>After upgrading to WSH 5.6 Driver object properties return correct values under Win98SE.
>>>>
>>>>Did you *just* upgrade to 5.6? Do you still get the same (original) error?
>>>
>>>Yes, I just upgraded. It didn't fix problem with folder's object Size property for the root directory.
>>
>>Thanks for the info. GT and I separately figured out that the folder object trying to hit the "C:\System Volume Information" folder under W2K failed because access was denied.
>>
>>You and Nadya are under W9x. AFAIK you won't be denied access to any folders on your local C: drives so I wonder what's causing the root folder size problem on your machines?
>
>I don't have such folder on my Win2k Pro SP2 and ? oFolder.Size doesn't generate any errors but returns used space in bytes in no time.

You don't have the folder? It's hidden, on my system. I'm running under NTFS and with a bare-metal installation of W2K - not an upgrade.