Print

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

[girl7]

I have 3 questions/issues, and since I don't know if they're bugs and I'm a Mac user, this seemed like the place to post them.

(aMule 2.0.3; OS x 10.3.9; 1GHz PowerBook 1gig RAM)

1 - Are the little buttons on the search tabs actually supposed to close the tabs or are they just there for show?  They haven't worked for me in the past 2 versions.

2 - Is the search function intentionally limited to 300 results?  If so, what is the best way to get search to show different results on subsequent searches (instead of getting the same 300 over and over)?

3 - When I cancel an active d/l everything else stops for about 60 seconds and all of the other active connections to sources are dropped (which *really* sucks.   )
Am I the only person experiencing this?

Thanks,
girl7

[Gomaaz]

hiho

1. right click on the tab to receive the tab-options

2. 300 results is the limit....try to make you keywords more specific

3. Ken/Kry/steffanero where are you ?  :rolleyes: ....I expieriencing the same so don't worry. I think it is because amule sends the commands to delete the file and taht would take lots of time ...but I don't really know actually..

hope I've helped u  

[ken]

The close boxes ('x') on the search results tabs work on other platforms, which is why they are there.  aMule uses the cross-platform framework wxWidgets to support multiple platforms.  Unfortunately, wxWidgets on the Mac doesn't support the necessary capabilities to make those close boxes work.  As Gomaaz suggested, use control-click or right-click to get a menu for the currently selected tab, from which you can close it.

The limit of 300 search results comes from the servers.  Some ed2k clients support a way to ask the server for more after the first 300, but aMule doesn't currently.  You might try to do a global search, since the limit is 300 from any given server, but each server's 300 doesn't necessarily overlap with another's.

When I Cancel a download, I see a pause of a few seconds, but never 60.  And I don't generally drop any uploads or downloads.  I don't know what's causing this.  My system is pretty weak compared to yours, I think, but it is dual-processor (it's a PowerMac G4 dual 450Mhz 512MB RAM).  I wonder if that has anything to do with it.

Here's something for each of you to try.  With aMule running and has a download you want to cancel, first open Terminal.app and type this but don't press return yet:

sample amule 10

In aMule, cancel the download and quickly switch back to the terminal and press return.  Hopefully, the sampling will begin while aMule is stuck in the middle of canceling.  The sample program will then report that it wrote the output to a file.  Attach that file to a posting here.

[girl7]

Thanks for the quick response, ken!  

I already knew to ctrl-click the search tabs and had a feeling the non-function close box was a Mac specific issue, but I just wanted to verify.

As far as searching goes, what operators (is that the correct term?) will aMule accept to produce more specific results?

Heh, I may have exaggerated the length of the hang time when canceling a download a little, but my concern was more about the downloads being dropped.  I'm not sure if any of the uploads dropped...

The next time I run aMule I'll bust out the Terminal and and do some test cancellations to see if I can produce a couple reports for you.

[ken]

It's not a question of what search operators aMule will accept, but what the servers will accept.  And, to my knowledge, none.  They just take keywords and perform an implicit "AND" on them.

The sample reports from when you cancel a download will be interesting.  The "10" in the sample command I suggested is the number of seconds over which to sample.  If the pause when canceling is not that long, then use a smaller number.  It should be large enough to get a good sampling of what aMule is doing, but small enough not to keep sampling after aMule recovers and returns to normal operation.

[girl7]

Well, I ended up giving the 8-24-2005 CVS version a go, and although it is supposedly unstable it seems to run better for me than 2.0.3 did.

The hangs and drops upon cancellation no longer occur, however, aMule now seems to exhibit a similar problem upon completion of a download.  I am seeing a definite drop in transfer speeds when this happens and a massive hang in the GUI.
Most of the sources, however, appear to be retained and tranfers return to their previous speeds once aMule begins functioning normally again.

The odd new bug I've experienced is that this version of aMule seems to have some sort of conflict with Stuffit.
Up and download speeds come to a halt and aMule hangs every time I happen to stuff a file while  aMule is running.

These are the only problems I've experienced after leaving aMule running almost non-stop for the past 2 days, though.  

[Kry]

Those seem more like bottlenecks on your filesystem than any aMule related bug.

[ken]

I'm guessing you have a single CPU system.  When aMule completes a download, it hashes the file to make sure it matches what was expected.  This is a CPU intensive operation.  It is done in a separate thread, but that thread may be monopolizing your CPU.  Similarly, unstuffing a file can be CPU intensive.

Or, Kry could be right.  

[Kry]

Or Ken can be right.