BTQueue has finally found new home

Greeting! I am glad to tell all you that I have found new home to run BTQueue. That means I can continue development to improve and fix more bugs. Anyway, it is FreeBSD. Below is my wishlist.

  1. Web-based interface with access control (may be a module under Drupal)
  2. Support Distributed Hash Table
  3. Support fully secure protocol cloaking
  4. Support one-way communication

If you have any suggestion, please let me know.

At last! :)

Hello! At last I found a full command line bit torrent client, which can work on Windows too. Glad that you will continue to develop this wonderfull app. Good luck, and hope soon to see a new version with lot of bugs solved. Regards!

freebsd and ubuntu

In addition, now I have more experimental environments such as FreeBSD and Ubuntu.

Win32 Beta?

How could one can become beta-tester of future Win32 versions?

checkout cvs

Sure you can! Just check it out from CVS. I always commits only working code to the CVS so you can use it for production run.

sorry...

but I am not a programmer, so compiling from CVS-sources is far away from my knowledge :(

0.0.19?

So...will we have soon (after more than 1 year beta-tests) new release for BTQueue? I hope to see this 100% CPU bug solved (probably with Python change...)

0.1.0

No you will never have 0.0.19 since it was just an alpha version for a year. I will release 0.1.0 as soon as possible.

please wait...

I see. I will release 0.1.0 very soon. Actually, I am mainly developed 0.1.0 on WinXP right now.

GREAT!

This is just wonderfull! Good news to all fans of command line tools. My prays will go with you! Good luck!

A few things you may want to know about current realease.

I want to tell you about few things, present in 0.0.18, which you must have in mind when developing the new BTQueue release (for Windows XP). I am using WinXP SP2, with all hot-fixes. My HDD volumes are Logical, instead of Basic. This probably matters... 1.So, first thing is 100% CPU bug. I can't tell why it happens. Sometimes it is there, sometimes it is not. No matters if leaching or seeding. Sometis it shows when actual data transfer starts, sometimes when start seeding. Another thing - it NOT depends of speed or number of connected peers. I read somewhere, that certain Python versions have some problems. Could this be one of them? May be. 2.There is strange behavoir of ADD mode. In fact BTQueue can't be run in such mode, I mean only to add new torrents. There is always mistake - Errno2: No such file. Related to this is another thing also: file association does not work. Clicking on torrent file brings up console window with "btqueue add", but again there is error. BUT when BTQueue is started in "scheduler" mode - there is NO problems when using "add" command, new torrents are added correctly, regardless of where they are or what file name have. 3.It will be very good if there is a small, really very small, "manual" with only one line per each option in policy.conf. Most of them are obvious, of course, but there are few, which can make regular user very annoyed. Anyway, thank you for the effort you put in this :) There is no other pure console client for Windows out there.

thanks for comment

1. There might be a chance to fix the 100% CPU bug in 0.1.0. A complex loop is removed. 2. Well, I'm so sorry for this bug. I have never used it this way... 3. Ah. I will find a solution for this problem.

Post new comment