I noticed one similar topic to this one, but not identical.

Basically, I dual boot, and have over the last few months downloaded some stuff that needs constant seeding to my NTFS drive. Recently I've been starting to use linux (ubuntu) more and more, and ideally need to start seeding these torrents from within linux as well while I'm working.

The files are large, and I have limited space on my linux drive, so would prefer to seed them straight from NTFS. However, the drive is read-only, and it seems ktorrent isn't happy to read from a read-only drive

Does torrent software really need write access to seed? And if not, is there a way around this problem?

As an aside, the error I received was very confusing. It looked like the cache directory was not writeable, but it turned out that the original file location was at fault.

Currently we allways open files for reading and writing. It makes things a lot easier when you suddenly need to start writing to the files again (i.e. a corrupt chunk is detected).

Is there any way of getting KTorrent to run in some kind of read-only mode? And if not, do you think you might implement it in a future version for all the poor (?) windows users out there?

dutch_gecko wrote:Is there any way of getting KTorrent to run in some kind of read-only mode? And if not, do you think you might implement it in a future version for all the poor (?) windows users out there?

I will have to see what impact this would have. Maybe we can get it in the final 2.1 version.

Nice. Always glad to find a software group that listens to the users!