>>Well, if the Windows Explorer is returning the incorrect results on one machine and not another, then I would say that it's almost a 100% sure thing that it's a ROM BIOS issue rather than a problem with the function. Simply consider the fact that the same exact function, in the same exact DLL is being called in both cases. Yet you get the wrong result from one machine and the right result from the other.
>>
>>I'd look at the setup routine that you can access when the computer boots. That will give you one clue. Further, a BIOS extender will have it's own setup program you may want to check.
>
>George, let me repeat my statement. I checked on two Windows 95 machines in the office and both returned incorrect result. I then checked on Windows NT machine (this machine is terribly slow, each operation takes ~5-10 min., the owner said, that he is working "slowly" :)) and it returned correct results both from WE and from VFP. So, my conclusion is that it depends on OS. For purity of the experiment I should try from home, where I'm running Windows 98.

Nadya,

Let me clarify what I'm saying. If you have a local computer connected to a remote server and both have drives greater than 64 gb, and the local machine is reporting the wrong amount, and the remote machine is reporting the correct amount, it is not the operating system or the function. It is the ROM BIOS. Checking machines independently will not necessarily reveal what the problem is.

If you install a drive greater than 2 gb in an older machine, like my P200, but do not run the installation software to properly install the BIOS extender, if the drive functions at all, it's almost certain that it won't "see" anything above 2 gb because the BIOS won't recognize it.