Print

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

[loco_bel]

Hi guys,

Today I have had a small incident with aMule.  I let it run over the day, and when I came home, I saw a window with something like: "The file FILENAME.... could not be save.  No access rigths."

I pushed ok button and went to see what the problem was.  Indeed, where aMule tried to put the file, "Incoming" it was not given write perssion.  I gave it manually, but nothing happened.

Now ... where is the file?  I looked in the temp directory, but there ... it does not seem easy to figure out what it is.  Meanwhile, I have restarted aMule and still no retry to save the file or something of that kind.

Could somebody give me a hint on wheter I would still be able to recover the file and how?

Thanks.

[Jacobo221]

the file is in the temp directory. it's called xxx.part where xxx is a number.
You have to guess which one it is now ;-)
I hope you don't have much *.part files there!

[deltaHF]

hi,

where is your incoming dir? i hope not ntfs ...

check the *.met files in your temp dir for all that you are still downloading (show file details in aMule) ..
try to rename the *.part that you don't see in your downloads (mv 011.part the_file_u_was_trying_to_dl.avi/mpg/zip)

cheers

[loco_bel]

Hi,

Yes, my Incoming is a symblink towards a mounted ntfs.  I did look into temp dir and took file by file, but it is not there...

Regards

[Jacobo221]

ntfs is not writtable. at least, it shouldn't be. if you have write-to-ntfs option enables in kernel, i suggest you to disable it.
That may be the source of your problems.
Greetings!