2014), and potentially in China (Melville et al. Canutus are both huntable in France and hunting of other species can cause disturbance and accidental mortality. The species is hunted illegally for example in New Zealand (del Hoyo et al. 1996) and northern Brazil (Leyrer et al. Islandica and C.

I am looking into making the import of utorrent's torrents far easier. I know that utorrent saves all the torrents' related data to the resume.dat file.

I also know that the resume.dat file is a bencoded file. But I don't know how uttorrent keeps track of which pieces of a torrent it has downloaded. Do you have any idea/pointers on what to look in the resume.dat file? The idea is to take the required data/info from resume.dat and make a *.fastresume file for the torrent, thus skipping the 'file checking' phase. I think I have figured it out.

Feb 19, 2014  All of my torrents have vanished from Bittorrent. They are all still in my download folder, but bittorrent is completely empty. But many were gone forever. Finale 2009 download free. It took hours to repair. The most frustrating aspect was that most of the torrent files that were lost were ones that I was seeding; I had to go back to torrent sites, reload the torrent.

I had forgotten that 1byte=8bits. I think the 'have' field contains the torrent pieces as a bitmap/bitset/bitarray and each bit represents a piece. In my pic the have field has a size of 108bytes or 108*8=864bits. Utorrent reports that this torrent has 860pieces. Obviously the extra 4bits are padding. The only way to check my assumption is to count how many bits are set in this bitset.

If they are equal to the downloaded pieces that utorrent reports then I am correct. This should be fairly easy to code, but I will not do it today. I have made some progress. The fields that are immediately interesting to us: have: a bitset where every piece is represented by a bit. The value is padded to the next byte. When a piece is downloaded(even partially) the corresponding bit is set. Blocksize: the size in bytes of the size of the block(a piece consists of one or more blocks) blocks: it is a list which contains the partially downloaded pieces.

Each item represents a piece. Each item has a variable size and it depends on the number of blocks for each piece. It's size is 4bytes+((piece size / block size)/8) (probably padded to the next byte).

The first 4 bytes is an usigned int representing the piece number(counting from 1). The rest of the bytes are a bitset, where each bit represents a block.

If the block is downloaded the bit is set. On a sidenote: utorrent doesn't seem to keep record of the timestamps for each (download)file and it's (downloaded)size. Thus it cannot detect if a file is current and not modified. If you download a torrent with utorrent to 5%, exit utorrent, import the torrent to qbittorrent, download some data to >5%, exit qbittorrent and launch utorrent: utorrent will start downloading from the 5% mark and thus redownloading already downloaded data. QBittorrent of course(and every libtorrent based client) can detect this situation and will force a recheck before starting the download, thus saving bandwidth. I am looking into making the import of utorrent's torrents far easier.