aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: Mac prerelease (testers call)  (Read 145622 times)

Kry

  • Ex-developer
  • Retired admin
  • Hero Member
  • *****
  • Karma: -665
  • Offline Offline
  • Posts: 5795
Mac prerelease (testers call)
« on: November 19, 2004, 07:45:51 PM »

Anyone wanting to test a Mac prerelease of aMule rc8  use the link bellow.

You can also come to #amule on irc.freenode.net to get the lastest one (link should be updated anyway) or chat with other aMule Mac users to solve your problems (or aMule devs, or other people ;))

Just a 3.5Mb file, unzip, click & play.

No wxMac instalation needed.

UPDATE! Try this zip file and report bugs on Mac forum.

UPDATE! If you're getting:

a) Flashing transfers tab
b) Crashes on server.met download

then re-download the aMule.zip file, as those have been fixed :)

UPDATE!  aMule no longer crashes if exit while prefs windows open.. If you get this crash, re-dl aMule.zip

UPDATE!  Colour boxes on Stats window are now showing ok instead of little dots. If you see little dots... re-download ;)


Thanks for testing :)
Logged

lionel77

  • Provider of Mac builds, Forum Mod
  • Hero Member
  • *****
  • Karma: 4
  • Offline Offline
  • Posts: 1107
  • Mac OS X 10.4 (Power Mac G5)
Re: Mac prerelease (testers call)
« Reply #1 on: November 20, 2004, 05:28:40 AM »

what an amazing progress -- today really was mac day... :)

kry, i already queried you this, but i am curious whether other people experience the same thing:
i get about 15k/s of overhead, both down- and upstream, a short time after i connect to a server (ca. 5 min). so for example amule tells me down and upload are 0k/s and 4k/s but then my network monitor tells me the actual traffic from my machine is 13k/s down and 20k/s up.
 i've tried restarting amule and running it without a server connection using only the handful of sources that connected to me. then the effect does not appear. of course it's hard to tell whether it's the difference in sources or the server-connection that makes the difference. i have only two files in my download queue right now, one with a made up md4 for testing purposes and one real one with about 40-50 sources. i tried reducing the max connections to 100 but that did not have much effect.
i saved the most funky thing for the end: when i click on the menu bar (i.e. the amule menu or the apple menu) then up and down traffic drop to the values amule lists and the overhead is gone. as soon as i leave the menu the traffic climbs again. isn't this weird?

anyway, give the current version a shot -- overall it already looks fantastic! :)
Logged
Current aMule CVS builds for OS X can be found here.

hellimod

  • Newbie
  • Karma: 0
  • Offline Offline
  • Posts: 1
Problems with upload and download
« Reply #2 on: November 20, 2004, 02:24:58 PM »

We are talking about the donkey network now. Its not the same type of network your used to. Over time the download rate improves but at first its going to be very slow.
Logged

lionel77

  • Provider of Mac builds, Forum Mod
  • Hero Member
  • *****
  • Karma: 4
  • Offline Offline
  • Posts: 1107
  • Mac OS X 10.4 (Power Mac G5)
RE: Problems with upload and download
« Reply #3 on: November 20, 2004, 06:42:11 PM »

Quote
Originally posted by hellimod
We are talking about the donkey network now. Its not the same type of network your used to.
i've been using various donkey clients for around 4 years, so i guess i qualify as being not a complete n00b... ;)

if you read my previous posting again (sorry if it was a bit convoluted) you'll see that i didn't complain about low transfer speeds (having only one real file with 50 sources queued hardly guarantees good speeds), but instead talk about a huge amount of overhead traffic that i experience with the current built. every edonkey client is bound to produce a little overhead but this is usually in the 1-3k/s range and not 15k/s. particularly the fact that clicking on the menu bar temporarily eliminates the overhead speaks for just a small bug somewhere and it not being expected or desired behavior of the client...


i haven't really made it out of bed yet and my testing machine is a bit away, so it might take a few hours until i resume testing... ;)
Logged
Current aMule CVS builds for OS X can be found here.

lionel77

  • Provider of Mac builds, Forum Mod
  • Hero Member
  • *****
  • Karma: 4
  • Offline Offline
  • Posts: 1107
  • Mac OS X 10.4 (Power Mac G5)
Re: Mac prerelease (testers call)
« Reply #4 on: November 21, 2004, 07:26:01 AM »

ok, i did some additional testing and now i can't reproduce this effect anymore. very weird, it appeared reliably yesterday after multiple restarts and tinkering with various config parameters.
anyway, i guess that's good news... sorta. i'll keep an eye on it...

kry, i found the cause of the server connection problems that i had yesterday after a restart of amule: when you start amule and it loads the servers from the server.met, the order of the digits of the ip-addresses are flipped (1.2.3.4 becomes 4.3.2.1), so amule tries to connect to the wrong ip's. i remember old versions of the offical client having the same problem on the mac.
the easiest workaround is to clear all servers from the list and then to get a fresh server.met.

i really have to say, i'm already pretty contend with the current version -- a little more polishing here and there and we can start getting joe average mac to switch to amule... :)


EDIT:
two vanishing issues:
  • first one is a server issue: amule removes even valid servers from the server list until no servers are left. whenever you get a handful of new servers from another client they get added to the list but vanish soon, too.
  • second one concerns the display of clients that are downloading from us. i took a screenshot that illustrates the problem: in this particular case the first two list entries are filled with the window background so that you can't read the information that's supposed to be there. if you sort by different columns you can alternate which particular client is displayed in the remaining row.

after i took the screenshot the problem went away, but now it's back there again. my guess is that it vanishes when there are no filled upload slots to display, but in order to confirm this i need to do a bit more testing.
[/list]
« Last Edit: November 21, 2004, 09:06:37 AM by lionel77 »
Logged
Current aMule CVS builds for OS X can be found here.

ken

  • Hero Member
  • *****
  • Karma: 4
  • Offline Offline
  • Posts: 825
Re: Mac prerelease (testers call)
« Reply #5 on: November 21, 2004, 11:30:21 AM »

Great work, Kry!  Works well and looks good here.
Logged

Jacobo221

  • Hero Member
  • *****
  • Karma: 3
  • Offline Offline
  • Posts: 2712
Re: Mac prerelease (testers call)
« Reply #6 on: November 21, 2004, 09:04:26 PM »

"first one is a server issue: amule removes even valid servers from the server list until no servers are left. whenever you get a handful of new servers from another client they get added to the list but vanish soon, too." <- possible socket error? maybe this happns because for whatever reason aMule thinks he's lost connection and can't connect to those servers... or maybe it's the endian stuff ("(1.2.3.4 becomes 4.3.2.1)").
no idea, just a guess. never looked at network code since that's only Kry's hehe
Logged

HipHopPunkSuperStar

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 31
Server issues and Crash
« Reply #7 on: November 23, 2004, 09:40:58 PM »

Firstly, a very big Thank You for keeping on the good work..

Okay, now to my problem:
I can't connect to any server!
I tried updating the server.met, but no difference.
I checked LS but amule is allowed any connection.
I checked NB but all the ports are open and I even tried running NB with no restrictions at all, nothing.
My router has worked fine with the current configuration and mldonkey for some time, so I don't think its the router neither.

Now, after some time that amule is trying to connect, it "suddenly quits" = crashes.
I suspect that happens after checking all the servers...

If you want I could post the crash.log...

Cheers
Logged

sssnake

  • Jr. Member
  • **
  • Karma: 0
  • Offline Offline
  • Posts: 69
  • Don't eat the yellow snow (F. Zappa)
Great work, Kry!
« Reply #8 on: November 25, 2004, 12:21:35 AM »

Quote
Originally posted by ken
Great work, Kry!  Works well and looks good here.
I agree completely!
Logged

cthulhu11

  • Approved Newbie
  • *
  • Karma: -2
  • Offline Offline
  • Posts: 12
Hot damn!
« Reply #9 on: November 27, 2004, 08:47:45 AM »

I'd about given up on aMule; glad to find a binary at last.
The instructions are frustrating because there doesn't appear to be a copy in Fink at all.
I had a heck of a time compiling WxMac, then a worse time getting the demo progs to invoke properly -- they couldn't get the input focus / be the topmost app.  I managed to get around that, but once I got aMule (rc7) to link, it had the same problem.  Sigh.  I miss X....

So, I'm really glad that you're making binaries available -- it fires up just fine on my G5 with 10.3.6, though unless I can import my eMule parts, it'll be a few days before I can really test.
Logged

HipHopPunkSuperStar

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 31
Re: Mac prerelease (testers call)
« Reply #10 on: November 27, 2004, 11:54:40 AM »

Okay, tried again, removed prefs and server.met manualy and now it works fine...
Logged

Kry

  • Ex-developer
  • Retired admin
  • Hero Member
  • *****
  • Karma: -665
  • Offline Offline
  • Posts: 5795
RE: Hot damn!
« Reply #11 on: November 27, 2004, 01:07:10 PM »

Quote
Originally posted by cthulhu11
I'd about given up on aMule; glad to find a binary at last.
The instructions are frustrating because there doesn't appear to be a copy in Fink at all.
I had a heck of a time compiling WxMac, then a worse time getting the demo progs to invoke properly -- they couldn't get the input focus / be the topmost app.  I managed to get around that, but once I got aMule (rc7) to link, it had the same problem.  Sigh.  I miss X....

So, I'm really glad that you're making binaries available -- it fires up just fine on my G5 with 10.3.6, though unless I can import my eMule parts, it'll be a few days before I can really test.

Jusar put the contents of your Temp folder on aMule's  temp folder :P
Logged

Jacobo221

  • Hero Member
  • *****
  • Karma: 3
  • Offline Offline
  • Posts: 2712
Re: Mac prerelease (testers call)
« Reply #12 on: November 27, 2004, 01:17:24 PM »

cthulhu11:

you can take all stuff from eMule into aMule. Just read http://www.amule.org/wiki/index.php/FAQ_aMule#Can_I_use_eMule's_files_and_settings_and_vice-versa?
and follow instructions ;)

Greetings!
Logged

ken

  • Hero Member
  • *****
  • Karma: 4
  • Offline Offline
  • Posts: 825
Re: Mac prerelease (testers call)
« Reply #13 on: November 28, 2004, 10:36:31 PM »

The problem with GUI programs not getting focus is what happens when you run an executable which isn't wrapped in a proper application package (bundle).  Steps 14 through 17 of the HOWTO are intended to address that.  If step 16 ("tar -xjf ...") doesn't work, and if you have an up-to-date version of StuffIt Expander on your system, then you can try this as a replacement for step 16:

16. Extract it: open aMule-App-Container.tar.bz2

Replacing "tar -xjf" with "open" causes the system to launch StuffIt Expander to extract the contents of the archive.  It might succeed where tar fails.

Of course, all of this is moot now that we can just download a binary.  :)
Logged

sssnake

  • Jr. Member
  • **
  • Karma: 0
  • Offline Offline
  • Posts: 69
  • Don't eat the yellow snow (F. Zappa)
Re: Mac prerelease (testers call)
« Reply #14 on: December 04, 2004, 07:36:52 PM »

Quote
Originally posted by HipHopPunkSuperStar
Okay, tried again, removed prefs and server.met manualy and now it works fine...
I have the same problem here too, only I have to do it, every time I start amule. That means, there seems to be a problem generateing the server.met and/or reading it out on the next start. Has anyone else this kind of problem?
btw: here, only server.met needs to be removed (and - I forgot -  maybe the server.met-backupfile too)
« Last Edit: December 04, 2004, 07:38:25 PM by sssnake »
Logged