aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: upgrade: uninstall first?  (Read 3536 times)

bobmarleyfan

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 42
upgrade: uninstall first?
« on: May 13, 2009, 02:18:24 PM »
I am using amule on OS X. How to upgrade?
Do I just delete the old app and replace it with the new one or do I have to uninstall first?

How do I keep my preferences and DL-queue?
Logged

wuischke

  • Developer
  • Hero Member
  • *****
  • Karma: 183
  • Offline Offline
  • Posts: 4292
Re: upgrade: uninstall first?
« Reply #1 on: May 13, 2009, 04:45:30 PM »
Quote
Do I just delete the old app and replace it with the new one
yes
Quote
How do I keep my preferences and DL-queue?
They are stored in your user's folder and will be kept automagically.
Logged

bobmarleyfan

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 42
Re: upgrade: uninstall first?
« Reply #2 on: May 16, 2009, 01:40:22 PM »
Thanks for the info. 2.2.4 is not available as binary for OS X though and frankly I am not very optimistic that 2.2.4 will work because I don`t get downloads (always Low ID and 0 sources for all but 1 download) with 2.2.3 despite various tries with portforwarding ports (tried standard ports and 5-digit custom ports) aswell as switching off the software firewall.
eMule on Windows worked immediately after setting up port forwarding.
Logged

wuischke

  • Developer
  • Hero Member
  • *****
  • Karma: 183
  • Offline Offline
  • Posts: 4292
Re: upgrade: uninstall first?
« Reply #3 on: May 16, 2009, 04:09:42 PM »
Actually there are packages for 2.2.4 in the Mac section.

Mac OS X has a built-in firewall, too - you have to open it for every new version of aMule, because the executable files will differ and Mac OS X allows opening based on executable files.
Logged

bobmarleyfan

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 42
Re: upgrade: uninstall first?
« Reply #4 on: June 04, 2009, 10:47:15 AM »
Quote from: wuischke on May 16, 2009, 04:09:42 PM
Actually there are packages for 2.2.4 in the Mac section.

Mac OS X has a built-in firewall, too - you have to open it for every new version of aMule, because the executable files will differ and Mac OS X allows opening based on executable files.

I have allowed all connections for amule in OS X` internal firewall. I still get low IDs. People can download but I only get downloads for 1 of 40 files.

There are no binaries of 2.2.4 or 2.2.5 for OS X:
http://www.amule.org/files/files.php?cat=44

amule is no use to me if I can search and find files but not download.
Logged

gtoso

  • Official MacOSX Packager
  • Full Member
  • ***
  • Karma: 24
  • Offline Offline
  • Posts: 206
Re: upgrade: uninstall first?
« Reply #5 on: June 04, 2009, 11:55:27 AM »
Hi,
you can find aMule 2.2.5 here or directly here.

For the other problem see here and here.
I suggest you to keep OSX firewall disabled and if you want enable it only after you have resolved the problem.

Now there are few ed2k server and someone doesn't return results during searches, so make sure that kad is working.

Logged

bobmarleyfan

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 42
Re: upgrade: uninstall first?
« Reply #6 on: June 05, 2009, 07:12:54 PM »
Quote from: gtoso on June 04, 2009, 11:55:27 AM
Hi,
you can find aMule 2.2.5 here or directly here.

For the other problem see here and here.
I suggest you to keep OSX firewall disabled and if you want enable it only after you have resolved the problem.

Now there are few ed2k server and someone doesn't return results during searches, so make sure that kad is working.



Thanks for the links.

I did read the info in the wiki about port forwarding which is not a new topic for me.
Now it works. The reason was that the internal IP address is different now so the forwarding was assigned to the old internal IP of my PC (which is no longer used at the moment).
Before I noticed the IP issue I had also turned off OS X internal firewall but obviously that didn`t have any effect.
Logged