ld (listdrives) command under windows occasionally takes excessive time to execute.
Disk diagnostic for disk/controler/driver testing
Brought to you by:
samiam95124
Menu
▾
▴
#4 ld (listdrives) command under windows occasionally takes excessive time to execute.
Seemingly at random times, the ld command seems to hang up. Left alone, it resolves and completes. Apparently windows is holding the disk open call or size call for some reason, like waiting for an unmounted drive to come on line.
This is cosmetic, but annoying. Need to find a way to supress the wait.
It was tracked down to the deviceiocontrol() call. It is entirely up to windows. Strangely,
it does this on the call to find size for the fixed C: drive. It will take some Windows
research.
I found that the halt was occuring on the dvd drives. I believe it is standard for Windows to wait for those drives to spin up. I don't know why it does not just detect that there is no disk in the drive.
In any case, its up for debate what discdiag should do about it. Find what drive type is there and reject DVD/CDs? There is no reason that discdiag should not be usable with such drives.
Thus I am closing this as unresolvable and adding a section to the document.