Shareaza

In the last couple weeks I have been unable to download files from some seeders.
I get a Shareaza error that it may not be a valid torrent file. I have written to one seeder.
I was able to open his torrents before he changed from utorrent 2.21 to utorrent 3.1.2.
sometime after Feb.6
His torrents list............
http://www.demonoid.me/files/?uid=1643125&seeded=2

Today another seeder causes the same error msg
All of his previous torrents open OK, those he put up today don't.
http://www.demonoid.me/files/?uid=3745773&seeded=2

Any help, ideas or fixes appreciated.

Those are not pirated files? Because linking to such is against forum rules IIRC...

Anyway, you can start by installing the debug version of Shareaza r9084 (not yet up when I am writing this, might need to wait). Lots of BitTorrent related code has been added lately and there is a good chance your problem will be solved with the update. And even if it isn't as a BitTorrent user you will appreciate the improved features.

Well I tried the update, and that didn't change my ability to open torrents from users
of utorrent 3.1.2.0. "utorrent" updated this past month to this new version. In fact
I'm finding up to 25% of possible torrents are coming up with the same error. One
torrent seeder switched back to his previous version of utorrent and his files started
loading again. I know I'm not alone here since Ive noticed on seeders stats a decline
in completed files for those who use utorrent to seed recently.

Its non-standard elements of torrent files "file-duration" and "file-media" with format error in b-encoded numeric value "-1" but standard allowed positive numbers only. Probably uTorrent's team added negative numbers since version 3.1 and broke many trackers and BitTorrent clients as they always like to do...
http://forum.utorrent.com/viewtopic.php?id=110252
http://torrent-invites.com/help/180267- ... 8-9-a.html
(Russian) http://rutracker.org/forum/viewtopic.php?t=2263006
...

I made some compatibility fixes in latest daily build.

That last fix did it. Looks like the utorrent problem is no more.
Much Thanks.