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 Gone Bad  (Read 1668 times)

buffyslay

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 16
aMule Gone Bad
« on: April 10, 2008, 06:50:34 PM »
I'm using aMule 2.1.3 (the most current version available) with Mac OS 10.5.2 (Leopard) and I'm getting one problem after another after another... First aMule is extremely slow to connect. It will often take half an hour before it finally connects to a server (and 9 times out of ten its always the same server for some reason) then after a short while it will suddenly disconnect and further when I am connected the 'Clients on queue' always stays at 0 plus when I do a 'Global Search' all searches result in nothing ever being found!. This is in stark contrast to when I was running aMule on OS 10.4.9 (Tiger) where it would connect in seconds (and never disconnect) and within minutes I would have over 300 clients on queue and searches would always return 300-400 hits.

So whats gone wrong? I've re-installed aMule several times now and it makes no difference or is aMule 2.1.3 not currently fully compatible above 10.4.9 because nothing else has changed?

Logged

darmok

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 15
Re: aMule Gone Bad
« Reply #1 on: April 10, 2008, 11:15:01 PM »
mhh..

amule has not changed fundamentally or at all (in these functions you described), may be your OS have with this upgrade

Do others have the same problems with amule since that?

Why did you made the upgrade? Just to have the latest Version?  ::)
Logged
Debian sid AMD64
wxgtk-2.8.10
aMule-svn

buffyslay

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 16
Re: aMule Gone Bad
« Reply #2 on: April 11, 2008, 06:51:10 AM »
Right. Its still the same version I was running in 10.4.9. Actually its not Leopard. The problems started as soon as I upgraded to 10.4.10 and its not just aMule I'm having issues with since upgrading past 10.4.9, but that's not for this forum. I think 10.4.10 to  10.5.2 were/are bug ridden because Apple rushed the updates without thorough testing. Its certainly been acknowledged that Leopard was severely rushed to market. So blame Apple and I expect 10.5.3 to create just as many issues as what its supposed to fix in 10.5.2 - which was supposed to fix 10.5.1.....etc.

On the other hand you have some here saying they're not have any issues at all since upgrading so explain that!





Logged