PerfectDisk uses the API, but they are not the ones that helped Microsoft develop the API used.
I'm pretty sure they didn't help write or design the actual nt api's, I think they helped with the
user api's so microsoft wouldn't have to get involved in supporting the product but I am not exactly sure which wags first, the tail or the dog
GetVolumeBitmap, GetRetrievalPointers, MoveFile, GetVolumeData, ReadMFTRecord are sort of semi documented...don't know the entire story here
there were/are some "secret" api's which are always running NT, using these makes fewer calls and is almost always faster.
I'm pretty sure they didn't help write those but to be fair am not exactly sure...could you link me to a semantic article making the claims?
if Greg comes back I hope he tells us the real history, and does perfect disk use the
user api's or the "secret" api's...the problem with using "secret" api's is the fact that microsoft could and would deliberately change those api's because they are supposed to be secret
on the other hand, if microsoft endorsed a product, even if it used those 'secret' api's then they obviously wouldn't change them...or would they, just to corner the market and produce a more efficient product?
would like to see some first hand information on this diskeeper legacy stuff with fragmentation