aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: Amule not openning after error message.  (Read 2386 times)

laci

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 15
Amule not openning after error message.
« on: June 03, 2006, 02:04:41 PM »

Hi,
I think I have interesting problem that need basic change on the program.

I use SUSE 10.1 and installed Amule version 2.1.1.

I had to make a new installation of SUs 10.0. (I made it)
The directorx of the Amule set on a partition of FAT 32 and got a message that I can not write on it.
"Permissions on the aMule temp directory too strict!
aMule cannot proceed. To fix this, you must set read/write/exec
permissions for the folder '/windows/F/Amule/Temp2'"

Before change back the directory I closed the Amule. Now when I want open I got an error message from Amule that it is not possible write and change the permission of the HD.
I tried to change and I can not.



The problem is that the Amule in this situation not opening and can not change the directory set.
To open Amule as root do not solve the problem because it is an other setting.

The question is;  How can I force to open Amule now?

Thanks.
laci
« Last Edit: June 03, 2006, 02:08:31 PM by laci »
Logged

wuischke

  • Developer
  • Hero Member
  • *****
  • Karma: 183
  • Offline Offline
  • Posts: 4292
Re: Amule not openning after error message.
« Reply #1 on: June 03, 2006, 02:17:17 PM »

Edit the file ~/.aMule/amule.conf to change the directories.
(Search for TempDir=)
Logged

laci

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 15
Re: Amule not openning after error message.
« Reply #2 on: June 03, 2006, 02:21:04 PM »

Hi wuischke,

Thanks for the prompt answer.
Sure this will help.
laci
Logged

wuischke

  • Developer
  • Hero Member
  • *****
  • Karma: 183
  • Offline Offline
  • Posts: 4292
Re: Amule not openning after error message.
« Reply #3 on: June 03, 2006, 02:27:45 PM »

Oh and about your problem:
Add the umask-option to your /etc/fstab-entry of the partition
For me it looked like this:
Code: [Select]
/dev/hdb1 /mnt/win vfat rw,umask=0000 0 0
Logged