| |||
Limewire 3.8.0 This version doesn't seem to have the little connection rating, has it been removed? Also wasn't all the even number releases previously stated by the Limewire team in a slyck interview i believe that even number releases were going to be final and odd were for beta testing? Last but not least get a change log up |
| |||
Changelog / Version History Amen to the request to get a changelog up. Including a (version) history.txt file with the distribution, tracing back all changes from the program's creation, wouldn't be a bad idea, either. |
| |||
The connection quality indicator is in the 3.8.1 beta . . . and my connections are back to previous stablility so far. Wish I knew whether my ISP or LW gets the credit. Ditto to the changelog.txt . Changelog please? |
| |||
in 3.8.1 the Advanced->Uploads->General->Interrupted stats shows 16,088 (8,187 Attempted) in 24 hrs. just curious what this unusually high number is logging differently, since uploads seem to be proceeding as usual, if not better (average of 50KB/s out of 100 set limit). |
| |||
thanks for the confirmation trap_jaw. I tried to repeat the problem, but I'm still confused. I thought maybe because one of the kids had been running Acquisition on another machine earlier, but since the firewalls are off and the router maps and forwards a different port to each machine, I didn't think that was a factor. After 4 trials, all I can say is that it's not a 3.8.1 problem, and that I don't understand the effect of checking the option to Force IP. Any suggestions for how to understand these numbers, esp. the drop in uploads? |
| |||
The drop in uploads is easy to explain. Some hosts don't use your full upstream, so at times you may upload less although receiving the same number of requests. If you were running as an ultrapeer, your upstream would be reduced even further. |
| |||
Sounds reasonable--I guess it's pretty tough to keep as much as possible constant 'in the wild' but I've been sharing the same 1200 files for about a month, so the demand is pretty constant. btw, all 4 times were as an UP. Thanks for taking a look. Any comment on forcing the IP (or not) since the router is mapped and forwarded and the computer's firewall off? |
| |||
3.8.3 Pro wouldn't connect as an UP on my LAN unless I checked the force IP option. So . . . while trying to connect as an UP with force IP checked/unchecked, I managed to repeat the problem of being a Leaf and an Ultrapeer (previously noted here http://www.gnutellaforums.com/showth...threadid=22591) -- listing session information -- Current thread: AWT-EventQueue-0 Active Threads: 66 Uptime: 2:57:18 Is Connected: true Number of Ultrapeer -> Ultrapeer Connections: 2 Number of Ultrapeer -> Leaf Connections: 1 Number of Leaf -> Ultrapeer Connections: 6 Number of Old Connections: 0 Acting as Ultrapeer: true Acting as Shielded Leaf: true |
| |