
Note: the value for this property is obtained through extended functions of BIOS interrupt 13h.] TotalCylinders - Total number of cylinders on the physical disk drive. [The documentation for the Win32_DiskDrive class ( (v=vs.85).aspx) states that: What I care about is why BIOS reports one value and WMI proceeds to use something different when it claims to be using that same BIOS value. I don't care about reading/writing - that all works just fine given a valid LBA. With enough money and time I'm sure the tools could be re-written and the process re-validated but really, that's not going to happen. Anyways, they want a definitive root cause analysis. (If you tell a client the disk is size X, then they want to use all X, not (X - Y)). The issue is causing unused space to be left after partitioning, as well as the capacity not being what's reported. I agree that CHS addressing is really out of date but that's what the client uses and the tool happens to care about cylinder boundaries.
