I've been getting problems occasionally with v3.33 and network drives
when running JkDefrag (or JkDefragCmd) without parameters.
Usually, JkDefrag identifies the network drives as "removable" and
ignores them (as expected), but every now and then it appears to
misidentify one of the network drives as local and tried to analyse it
...and then crashes.
There isn't much in the logfile to give a clue as to why this is happening.
When things are OK, JkDefrag will typically output a line such as...
Ignoring volume 'H:\' because it is a removable disk.
...whereas when it fails, the only clue is...
Analyzing volume 'H:\'
This is probably due to something weird about our corporate network
causing JkDefrag to choke, as I notice that there are times when
JkDefrag will consistently run OK and times when it will consistently
fail (and yes, I have checked that the relevant drives are still accessible).
The servers implementing these network drives are "NetApp" servers.
Unfortunately for me, I have local drives with drive letters after H,
so this means that I can't rely on running JkDefrag in its default
mode to defrag all drives. Well, OK: it is utterly trivial to knock up
a script to explicitly defrag each drive, but that's not the point...