Moved downloaded files still seeding?

[Raiko-san]

My internal hard drive has crap for space (150gb), but runs at 10,000 RPM, so i use it mainly for gaming for my main games. My external hard drive, however, is 500 GB; therefor that's where i store all my anime/other huge files.
So you ask, why not just download your files to your external hard drive and live happily-ever-after? Well because this hard drive doesn't like files bigger than 4 GB to be downloaded...which is most things. The external hard drive itself is fairly old, so it is a different "type" of hard drive, as compared to those used today. I dont remember what it's called, but i just know i cant download anything bigger then 4gb; i can however, transfer/move files into that are.

So I am using Vuze(aka azureus), and i am having it download everything into my internal hard drive, then from there i move them onto the external, then delete them from internal. In order to delete them i need to close Vuze, which tells me its using the files in THAT folder to seed. Because of this, my seeding ratio is terrible, even though i always have Vuze open, so i should ALWAYS be seeding.

How can i fix this?
A) possibly forcing the external to not care about the 4gb+ thing?
B) telling vuze to download to one folder, but seed from a different one?
C) minipulate the download so that i can download it in parts? ( for instance, take a 6 GB torrent and split into two halves, so i can download two 3gb to the external?)

Help!

p.s., sorry for the wall of text.

[blubart]

A) convert your drive from fat32 to ntfs - that's even possible with files on the drive - check google for a guide.
B) you can just use the relocate option in Vuze to shift the source of the files
C) not needed

[Rebs]

Hmm, I think I might be of help to you in relation to problem A): possibly forcing the external to not care about the 4gb+ thing?

This is probably a case of FAT32 formating of your external HDD. For FAT32 formatted drives do not support single files greater that 4GB.
Assuming that this is the case...
The solution: reformatting to NTSF, which does support files potentially up to 2TB in size.

Of course reformatting would mean losing all data on the target drive. However, it seems like one can convert to NTFS from FAT32 at anytime, but not the other way around. Do not take my word for it. Do a quick research on NTFS and FAT for yourself and discover that there is no real advantage in using FAT for regular everyday computer usage.

Edit: Damn you Blubert . Taking away my moment of glory

[Raiko-san]

 
i'm complety shocked that either of you responded so fast! at 3:30 ish in the morning of all times! But yeah, those formats your guys are talking about it was i was refurring too. i had read up on it before, and thought i did the conversion, but i guess it didn't actually change anything. maybe i did it wrong. *shrug*

If i were to change the taget folder for Vuze to download, would it start seeding the files from that new folder, even though the files were there before i set it to be "in" that folder? does that eve make sense? i'll re-read this post when its NOT 4:02 AM.

and on that note, i think i'm going to bed.

oh, and you guys are equally awesome in my books. no moments of glory was being stolen.

[Mirgond]

Na, it's 3.30am were you life, but many in the forum here are from Europe were it is midday

Anyway, shortest solution would be that here: click me

[Raiko-san]

  i'm pretty sure i know what time it is here >_>
My location/time zone is probably wrong, for this is still a very new profile. i'm updating things practically right now actually. screw sleep.

edit: and i love your avatar blubart. Toradora is my current obsession.

[Southrop]

One thing confuses me here. If your drive was formatted as FAT32 before, you shouldn't even be able to move/copy a >4GB file into it.

[Rebs]

One thing confuses me here. If your drive was formatted as FAT32 before, you shouldn't even be able to move/copy a >4GB file into it.

Lol, I thought about that, then I forgot about it. However, he may have archived them into parts...

[blubart]

i understood it that the individual files are smaller than 4gb, but the torrent as a whole was above 4gb and vuze is most likely pre-allocating the space by trying to write a massive bogus file.

[Raiko-san]

i might jsut be saying the same thing as blubart, but my theory on that is when its downloading it sees the torrent as a whole being more than 4gb, but when moving the file, it can see that it is just a large collection of smaller files, in one folder.
I'm running Windows Vista 64 bit btw.

[Rebs]

Blubart has made a valid point, once more. I need to improve my general PC knowledge.