the reason the two free space calculations are different is because the "correct" one is using the GetDiskFreeSpaceEx function, which returns a 64-bit value. for some reason the other one is calling GetDiskFreeSpace, which is a single 32-bit value, when used on a drive that contains too much free space, the first bit (the sign bit) is set, and the entire upper 32-bits of the value is lost. Thus the negative and the seemingly unrelated number afterwards.
I just figured it might be disk space because that would prevent defrag from running, and would lead to problems saving files.
It is Word 2000. I recently reinstalled Office 2000 after a file corruption made Word inoperable. I have looked at what folders are in old-c (the set of files copied from the disk of the old PC). It has Office and Windows folders. Is it possible that files in these old folders are being use instead of in the current ones? Should I send the old Windows to the recycle bin?
If at some point you accidentally started one of the office applications from the executable on that disk, it might have rewritten some registry settings to point to it's new location on the old C drive (now D: or some other letter I'm guessing? or a separate folder on your current C:?
This seems to be a problem "deeper" then office... especially when scandisk and defrag won't run, but give Broni's suggestion a shot. who knows?