CTorrent

[lurkist]

Just noticed that the default cache size for ctorrent is 16MB.  Normally that would make sense and persuade me that everything is in fact working well, but if you (Zyphoid) have reached 19MB of stuff into RAM and still no HD activity, it's back to the drawing board.

[pVC]

zyphoid: you can "end" it just like any other shell command.. with ctrl-c.

And it downloads files to current working directory. So cd where you want to get files and run ctorrent there.

[zyphoid]

@pvc you're seem to know how ctorrent works :-D what's the command line you use as in cd directory for download since i assume it defaults to ram.  WE me and Lurkist are almost got the hang of this I think. Also I tried ctrl-c but nothing happend it just hung and the little slash kept spinning! weird! :-?

[lurkist]

I think you need to ctrl-c for each file (or maybe folder) within the torrent.

I feel we're so close!  This time I've persevered with a large torrent.  I'm just over halfway through, with 45MB "downloaded".  Ram hasn't decreased, still no hard drive activity, and this is after changing the cache to 1MB (I assumed I would see HD activity after every 1MB, but no).  I'm sure I'll end up with nothing but those "virtual" files at the end of the day.  I'm missing something obvious, I know it! :crazy:

[Piru]

The client will continue to seed the file(s) even after you've downloaded it all. Once the client reports the file(s) being fully downloaded, it's good manners to keep seeding for some duration, preferably at least to 1:1 ratio. Once you no longer want to seed, ctrl-c.

Also, you can abort and continue the downloading later. The client is smart enough to resume properly.

The "virtual" files are in fact the actual files you're going to get. It's just that their content is garbled until the torrent has downloaded fully.

These notes apply to all bittorrent clients universally. Oh, and please do read the bittorent wikipedia entry.

[pVC]

zyphoid: I don't see what's so hard here I have tested ctorrent one or two times, but as my ISP restricts the torrent transfers it's pretty useless to try to use client without encrypted transfers (as my version of ctorrent is, I don't know if there's newer ones).

Here's an example:

New Shell process 11
Ram Disk:> Store2:torrents/
Store2:torrents> list
AmigaMusic.com - Best of Amiga Music Vol 2.torrent   21038 ----rwed Today     17:50:43
1 file - 21038 bytes used
Store2:torrents> ctorrent "AmigaMusic.com - Best of Amiga Music Vol 2.torrent"

-clipclap-

| 0,[0/937/0],0,0 | 0,0  E:0^C                                            
Store2:torrents> list
AmigaMusic.com - Best of Amiga Music Vol 2     Dir ----rwed Today     17:52:18
AmigaMusic.com - Best of Amiga Music Vol 2.torrent   21038 ----rwed Today     17:50:43
1 file - 1 directory - 21038 bytes used
Store2:torrents>

Nothing came to ram: and files were created to the (sub) dir I was CD'ed. ctorrent exe was in C:.

[lurkist]

Piru wrote:

The "virtual" files are in fact the actual files you're going to get. It's just that their content is garbled until the torrent has downloaded fully.

Downloaded at all would be good.  Nothing seems to be saving - not in RAM, the current directory, a temp file somewhere, or those virtual/actual files.
Sort of like a drip filling up a bucket, but when you come back to it the next day the bucket is empty.  Maybe a hole in the bottom, maybe some other little creature is drinking the water, who knows!?!

Piru wrote:

Oh, and please do read the bittorent wikipedia entry

It was very informative and cleared up many issues.
Just not this (seemingly CTorrent related) one.

Cheers

[lurkist]

Okay, feel free to give me a virtual slap (Piru especially!).  The d/l is complete and those virtual files have filled up with real data.

What kind of insane wizardry is this!?!

Oh well, I won't question it because

It works! It works! It works!

Cheers,

lurkist

[zyphoid]

Damn! now its on me to get mine going
 lurkist you changed something, what? I hate feeling like an idiot!

[pVC]

Torrents are downloaded in some size of pieces. And it probably downloads each piece in memory before writing it to HD. With slow transfer rate or at the beginning it may look like it won't write anything to HD.. you just haven't looked HD led long enough?

[zyphoid]

ok.  one last thing. does ctorrent need to be in sys:c drawer? mine isn't. it is in a partition drawer.

[lurkist]

@pVC -

Believe me, I stared at that sucker until my eyes went squiffy!  Also I had the dir open in Opus and kept refreshing the page expecting to see the date / time change as it updated, but no.


@zyphoid -

Check your original d/l (the small one which went into ram) it should be complete.  The larger one which is also going into ram is probably stuffed when you run out of ram.

If you are using a gui, bests to stop.  Using CTorrent through the shell worked better, and is not really difficult.  My executable is in SYS:C and here's what I used -

sys:c/ctorrent -s work:TORRENTS -P BT4103 work:WHATEVER.torrent

The "-s work:TORRENTS" just means that the files will end up in a place I can find easily.

The "-P BT4103" is reccommended in the docs as the latest peer ID

Hope this helps.


Now my next stupid question.  When a torrent is only partially available, when I reach the point where no more is available should I just leave it running until more comes along?  Or will more never come along?

OK, OK, I'll read the faqin faq!

[pVC]

No, it's like any other normal Amiga command, which can be anywhere... just makes easier to have it in path (like in sys:c) so that you don't have to write it's path every time.

[pVC]

No, it's like any other normal Amiga command, which can be anywhere... just makes easier to have it in path (like in sys:c) so that you don't have to write it's path every time.

[derringer3]

Some weeks ago i saw this program on aminet, so i diceded that i will try. I never hope that exist any torrent utility for miggy.  Now this is my first post with my amiga, so my miggy is ready for the world of torrent. :-)