![]() Although I haven't witnessed the problem myself, it's obvious that bitcomet handles torrents and magnet links properly when they are either opened in bitcomet, or properly handed off to bitcomet by the browser. Thanks Kluelos for posting a work-a-round to resolve this, which is a firefox issue, not a bitcomet one. Deleting the mimetypes.rdf file SHOULD have accomplished this, but check anyway, it can't hurt anything. You should be good to go, but check the duplicate entry error above, it definitely shouldn't be that way and you should get rid of the duplicate. Under Integration, check "Always Associate with Magnet URI". (If you can't find it or kill it, then just reboot and delete those two files before you run FF at all.) Make very sure, because if you see a file named parent.lock in that directory, you've likely still got an instance running that you will have to find and kill first. Make sure that Firefox is shut down before you do this. Getting Firefox back to handing magnet links off to BC involves going into your profile folder in %appdata%, and deleting the prefs.js and mimetypes.rdf files. I did have this happen to me today, that BitComet and Firefox would no longer handle magnet links properly, throwing errors like "can't find the file" and "Can't open torrent file". The detailed steps of what you're doing and the EXACT moment you encounter this (I'm assuming it's something that happens every time). torrent file residing on the index server, and which will be downloaded by your browser prior to passing them to your BitTorrent client for opening.ģ. On WHICH type of links it happens: magnet links (which are plain links themselves) or on torrent links which are actually links towards a. Here's a simple guideline for a proper report.Ģ. But unless one of you guys takes a second, sits back and clears his head then comes with a detailed and complete explanation of the issue, there's little we can do unless we'll stumble upon the issue ourselves (which we didn't so far). I can understand someone's frustration when a thing doesn't work as it's supposed to. So, in the end we're here having no idea what every single poster above is talking about, since there's a lot of confusion floating in the air. ![]() Unless a laborious process of actually copy-pasting the link into a text file or whatever is used, I can't imagine how you can save a magnet link to the disk directly. ![]() Then he came along later and spoke about "saving the magnet link to disk" which is at the very least weird since magnet links are just that (URIs or "links" in plain English) not files. Then epdm2be came along and said "wait, no it's about magnet links". The first user started "implicitly" talking about. Remember that if an issue can't be reproduced it can't be fixed. Everybody seems to assume they know exactly what the other person is talking about but no one cares to explain exactly what they mean. Nonetheless, this topic seems muddled with confusion. Opening magnet links works fine for me too. Cleaned my registry with CCleaner, re-installed, removed again, re-cleaned and put 1.31 on my Windows Xp SP3 machine to no avail.įor now I reverted to uTorrent which works correctly as bitcoment used to work i/t past. I tried with EZTV because it gives both magnets and torrentlinks. Torrent-links still work (and show the download-window). This only happens with magnet links (because it's on that window that I checked that item). I wonder if there's a way to reset bitcomet to it's default behaviour ? Perhaps a setting in the options screen can be created for this purpose? After that it won't open magnet-links anymore when I clicked on a link. ![]() In that window is a drive-folder displayed (in my case it was d:/torrents) but there is also a check-box (I think in advanced section) to not show that window anymore and use that folder as default from then on. It used to work fine until i did the following.Īfter clicking on a magnet link, bitcomet opens a download window. Whenever I click on a magnet link it, bitcomet gives this error. May I ask you if you did the following? Because I have the excact same problem. That's all that happens and reinstalling the software did not help. After several searches, I can't figure out why BitComet continually gives me this error message?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |