Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[ultreya]

hello, this is my 3rd installation of linux, and my 1st installation of aMule , i'm trying an experiment, i install linux in an extraible HDD, i change the disk when i would start wiht windows (cool ), and i have another HDD that contains data in NTFS system files (i try to access to these files thorugh konkeror and there is no problem, i can list and see them (i had no problem opening images jpg, gif or text files).

i open aMule after i do an "su" command because i ever see an alert that say "this is the first time you open amule... etc", i haven't that warning yet.

MY PROBLEM is when amule try to load the .part.met files, no one of them are load, the message for all them seem to:

Loading 085.part.met...-filename Buscate La Vida - 34 - 1977 2000.avi-ERROR!

My goal is to download and share files from and to win32NTFS file system, that are in the same dir of my win32Emule, i can share them, but, as you can see, i can't download!!!

thanks!!!

[Jacobo221]

You can't, ideed. NTFS support in the kernel is read-only. The write support is experimental and therefor is disabled by default. To enable it, recompile the kernel checking "File systems -> NTFS support -> Write support (EXPERIMENTAL)" (or something like that). Maybe you have the kernel with NTFS write support already (I don't think you have, but maybe...). In that case, remove "ro" from the NTFS partition's options's mounting line in /etc/fstab .
Anyway, I would recommend you not to enable write access to ny NTFS partition. It has no severe bugs now... but who knows? Avoid enabling it untill it becomes stable.
In the meanwhile, change that partition's filesystem to FAT32 (which has complete write access support by the kernel). There are lots of tool in both Linux and Windows which allow you to do this conversion.

Greetings.

[anybody]

There are 3 ways of getting NTFS Support in Linux:

a) NTFS Support in Kernel 2.4.X - works fine in read only mode, writing to NTFS should not be enabled as it REALLY is dangerous (!!!)
b) NFFS Support in Kernel 2.6.X - works fine in read only mode, writing to NTFS can be enabled, it is not dangerous, HOWEVER, writing support is so limited (files cannot be  created, only changed and that also not all the time, IIRC) that it doesn't make much sense.
c) http://www.jankratochvil.net/project/captive/ - Full Read+Write capably driver that uses a wine-like enviroment to fool an NTFS.SYS (which you need to copy from your windows installation along with some other files) into thinking it is running in windows, while it is providing NTFS Support to your Linux installation. Cons: Needs binary files from windows, might be difficult to install (?), performance might be slower due to the emulation layer. Driver is supposed to work fine as i heard and won't destroy your data.

Regarding FAT32: Converting to FAT32 is not really an option for many people these days because of it's file-size limit.

[emperor]

I confirm captive works fine (i read a HDD with NTFS file system with it properly and was able to read/write quiet well),but i guess I do not need to confirm.
Well I'm just posting to tell you that obtaining the files you will need for it is not difficult. The captive installer has an option to download the necessary files from the internet. It will download a windows service pack in order to obtain the files. However due to legal reasons you must own the windows OS of course..or else you mustn't have microsoft's code on your pc...
Oh yeah and there is another way to add NTFS support...
It's Paragon's NTFS for linux. However you need to pay for it and it's closed source and therefore only costs money and brings security risks...

[Jacobo221]

Very nice posts anybody and emperor, thanx :-)
Just a little off-topic note to anybody: the NTFS support on 2.6 kernels was limitted because a goal in the 2.5 branch before becoming stable was to add complete NTFS built-in support. Since the NTFS filesystem table isn't yet completely "reveresed", al the unsecure capabilities were removed from the stable branch, but will be added as soon as they are reliable (probably from a future 2.7 branch?)

Thanx a lot to both of you for your posts. I guess ultreya will be very grateful ;-)
Regards!