Phex 0.6.3 released. Phex 0.6.3 has been released. You can download it here: http://phex.sourceforge.net This Phex release contains many bug fixes and other minor improvements of the user interface, download engine, and research engine. They make Phex much more stable and efficient. |
1 Attachment(s) Hi. I have a few things to say about running this release on my machine. 1. The unreadable % column is no longer the problem, even if the solution doesn't seem to be right for all the fonts. When I choose 'Dialog' font I see different row heights for download/upload then normaly expected and displayed in all other fields (see attached picture for comparison of upload and shared files). I have checked some fonts and this also happens for Helvetica, Courier, Times and a few others. 2. Now, after three days of running 0.6.3 there seems to be some problem with uploads. When I start phex everything works just fine for a few minutes. People download the filels from me. But then every new upload (well about 99.99%) stalls after a few seconds with no more than 12800 B transfered and mostly also gets interrupted with 'Error Broken pipe'. And this is what phex writes to stderr from time to time: java.io.IOException: Broken pipe at java.net.SocketOutputStream.socketWrite(Native Method) at java.net.SocketOutputStream.write(SocketOutputStre am.java:83) at phex.share.ShareManager.sendString(ShareManager.ja va:619) at phex.share.ShareManager.upload(ShareManager.java:3 18) at phex.share.ShareManager.httpRequestHandler(ShareMa nager.java:273) at phex.ReadWorker.handleIncomingConnection(ReadWorke r.java:189) at phex.ReadWorker.run(ReadWorker.java:143) at java.lang.Thread.run(Thread.java:484) It also happens that phex freezes and I have to kill it. It has never happend to me before. Download works fine. I run phex on Linux Debian 3.0 with j2re 1.3.1. Javier |
Probelms with uploads The same is here (Windows 2000, J2SDK 1.4.0). I am going back to 0.6.2. |
Hard times For my Phex World ! The newest news is - my administration must have found a way to block incoming connect requests ! So now I can only connect to Outgoing Hosts ! and If you remember I mentioned that the default port on my net has been blocked to the outside Then considering the percentage that is still using the default port I have the hardest time to maintain connections ! I NEEED AN OPTION TO EXCLUDE CERTAIN HOST PORTS TO BE COLLECTED IN THE CATCHER !!! my computer is wasting time trying to connect to hosts on default ports there is no need to block possible transfers from hosts with files that use dafault ports because they be crossing over to my nonstandart open port ... and at least can push transfer if necessary ! I'd really like to know how this was implemented to block incoming Phex connect requests... Those were the ones that before sustained my connection because I would have to only hook up to one nonstandard Outgoing from www.gnufrog.com and then see the incoming nonstandart ports by themselves ... NOW THAT I CAN'T GET INCOMING THE CATCHER FILTER HAS BECOME URGENT PLEASE ! Thanks Eagle3yes |
Re: Hard times For my Phex World ! Quote:
What do you think about using a random open port the first time you open the program (but not everytime, just the first one)? That way there would be a lot more hosts out there to connect to that are on non standard ports, and make gnutella a LOT harder to block out. |
All versions of Phex use a random port on first startup. A port filter is available in the next release. Gregor |
Already possible? iirc you can do that already by going into invalid hosts (in settings) and insert one as *:[port number] or am I wrong? free_bound |
I dont think it will work... the current IP filter will cut of the port after the :. You might filter all IPs with this line. The next release which is comming soon contains the required port filter. Gregor |
Gnufrog Plastered Now that Gnufrog doesn't list active clients anymore (they changed to be some kind of Netmeeting Hub) I got the problem of finding fresh first connect hosts ... If my Hostcatcher was worth anything that would be less of a problem Also it would be nice if there was a more convenient way to copy and paste hosts (from the connected to or download hosts) to the auto connect host list .... -+= Desperately waiting for the Host Filter Release ! =+- thanks ! |
This is from the FAQ, Connection Problems : 3 You can download a large phex.hosts file from the Phex developers site at Sourceforge Just place this file into your phex directory where your phex.cfg is located and also raise the value mNetMaxHostToCatch in your phex.cfg file to 3000 or higher. At gnutella uk they also have a hosts file, they call it a gnutella.net file. You can copy the adresses from that file and replace the adresses in your phex.hosts file (use a tekst editor like notepad to open your phex.hosts file) |
All times are GMT -7. The time now is 11:37 AM. |
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2024, vBulletin Solutions, Inc.
SEO by vBSEO 3.6.0 ©2011, Crawlability, Inc.
Copyright © 2020 Gnutella Forums.
All Rights Reserved.