I make use of the aMule daemon for quite some time already with great pleasure. Now I want to make use of some of the pause/resume functionality, and it seems broken:
aMulecmd$ pause CxDx9xFx9xFxBxBx8xFxFx7xExAx3x3x
Not a valid hash (length should be exactly 32 chars)
Now I know it is a valid hash, since I just copied it from the 'show dl' list. Also typing it in by hand doesn't work, it still complains about not being a valid hash. The same goes for the cancel and resume commands, they all claim to not get a valid hash.
Anybody know about this? And can it be taken up in the bug tracker for next release?