Richard from mrgender at shaw dot ca
I submitted a followup comment to 1123767 but it
doesn't show as part of the text for this bug?! :-( So it
appears I'm forced to submit another bug instead.
As Administrator I changed the permissions on the "ed2k
links.txt" and "ed2k links backup.txt" files to be writable
by regular users and now the utility appears to trap ed2k
links.
(( I suggest the install process create these files with
writable by regular or all users ))
But now the utility will not submit the links to my eMule
client. This problem now appears to be similar to
1070333.
I see how Windows traps the ed2k link using the registry
settings, but how does this utility send them to an
eMule client?
I have a suggestion for a feature - allow the user to
cancel or delete any ed2k links that are trapped if he
would rather not send them onto an eMule client.
Feel free to send me email directly if you wish to
correspond.
Richard
Logged In: YES
user_id=1113627
> I suggest the install process create these files with
> writable by regular or all users
Good idea, thanks :)
> how does this utility send them to an
> eMule client?
The catcher registers itself as handler for ed2k:// URLs. It
"sends" them to the ed2k client by restoring the original ed2k
URL handler and simply ShellExecuting all the caught links
(ShellExecute is the Win32 API way of executing something
via the "Run..." dialog).
> allow the user to
> cancel or delete any ed2k links that are trapped
Something like this is already on my todo-list.
As a workaround, you can click on "show caught ed2k links",
remove unwanted links and save the "ed2k
links.txt" file.