Phex 0.7.1 released.
 

Phex 0.7.1 fixes problems with corrupted class files causing drawing problems and other strange behavior of the user interface in Phex 0.7.

This new Phex release is packed with new features and brings an improved interface look.
Changes in this version include:

• New multi-source download engine.
• Minimize to system-tray on Windows platforms.
• Filtering of search results by media type.
• Download candidate rating.
• Extensive table configuration to hide/show, auto-resize and sort columns.
• Interface settings are saved on exit.
• Big performance improvements.

macXster has been /. ?
 

Mac Users:

Congratulations to the MacPhex users! The site has been suspended by Apple for excessive bandwidth use! :eek: To make things worse the redirecting url macxster.n3.net will be down for a few days. When the site comes back online, you will still be able to go to it via: http://homepage.mac.com/macxster/index.html or you can go now and marvel at the temporally suspended sign. You can still download MacPhex 0.7.1 from here but the update program will not work until the normal site is back.

Any one who would like to help by mirroring please send an email to macxster@mac.com. I'll keep you updated to when we have more mirrors and / or the site comes back online.

Update
Site's back and we're in the process of buying a new server.
Update 2
We have our new server and domain: macxster.com

If I were you I would mirror it on gnutella, and at the same time make gnutella a contender to the internet. (multi-source download, huge bandwith savings, this web site is powered by thousands of volunteers...)

Dream on!

The new Phex is cool. It is good that I can shose 56k moden and isdn as a connection, because I have only ISDN and it would be like lying to the other user if I can only shose DLS as the slowest connection.
The Only thing I don't like, are the little Icons next to the "Gnutella Net", "Search" Button and the other Buttons.
An Option to ignore people who don't share any files will be good.

Very Nice - Only a few things:
 

First it used to be that Remove Download would not delete the downloaded file if it was done ! I just found out the hard way now it does ! - this is a mayor bummer ...

Second the bandwidth usage in the network tab used to show the network traffic now it shows the combined traffic
maybe it would be nice to keep it separated ? Or separated as incoming/outgoing traffic ? With long-term average ?

I used to be able to push the program to search again by use of the 'Stop Search' 'Start Search' buttons now one of them is gone -Maybe it would be nice to have that type of control still ?


---------------------

Otherwise great improvement of the programs efficiency ! I really think it gets candidates to send more easily ... is that because it use some form of multicast for the shared content ???

Thanks Guys !!!

Correct myself ...
 

After reading in the other Tread I checked and found the removed download wasn't really gone it was just in the Phex Program Folder ...

Much Better !
BTW I am using Sun JSDK 1.4 on Mandrake 8.2 i586

cheers

Other curiosities
 

Why doesn't the download start at 0 ?
I have seen it a few times now it starts wit 1MB skipping the first meg - so I cant preview the content till I find a second server or at least get another chance to connect , why ?

Also I think it would now soon be nice and necessary to start developing some kind of verify and repair mode in which instead of a download a system could ask some md5sums of segments to search and find problems and then if it found the difference request that specific segment ...

I think this will be necessary because we just increased the number of chances to get faulty files now its time to talk about adding some solutions...

Cheers!

I like the new version – especially swarming – but I miss the retry counter and the log feature. Could they be reimplemented (at least the counter) ?

Two small bugs :
- The "Abort upload" button is always greyed out, wether an upload is selected or not.
- All my downloads have a "queued" status whereas they actually have no candidates. Is it a bug or only new terminology ? :)

Thanks

Bug in 0.7.1 with not being able to connect?
 

For some reason after running Phex for several hours, it can no longer connect to _any_ Gnutella hosts. As well it just keeps spawning new processes that never seem to die. I'm up to about 500 right now, after 5hours of uptime, and I've seen it go as high as 1000. I have to quit Phex and restart it then it seems fine for a few more hours afterwards. Has anyone else noticed this?

Re: Bug in 0.7.1 with not being able to connect?
 

I noticed it after 2 hours of uptime. I dont know where it comes from. I was thinking my ISP has blocked the ports.

Re: Re: Bug in 0.7.1 with not being able to connect?
 

This isn't the case for me, since I can quit Phex, and go back in to it and it makes connections instantly. Therefore no blocking is taking place.

Actually I've also noticed that when I first run Phex, in the middle of the "Gnutella Net" screen it says: My Address 127.0.0.1:3617, then Phex tries to connect to about 5 other hosts, they all sit there "connecting" until My Address changes to my "Internet IP" then instantly the 5 hosts change to "Outgoing" and connections are made. After several hours, all of a sudden My Address changes back to 127.0.0.1:3617 and no more connections or downloads can happen afterwards, and Phex can no longer connect to more hosts so they slower drop off. I'm trying to find a relation between this weird IP address thing and the problem with 1000's of Phex processes.

I'm currently at 1011 processes and my IP address in Phex just changed to 127.0.0.1 while I wrote this. Could it be Phex's way of limiting the processes? Once too many are spawned it changes the IP address in an attempt to bring the processes down? Though I've never had it recover after about 500 processes. My Phex uptime is only 20mins. :(

Re: Re: Re: Bug in 0.7.1 with not being able to connect?
 

Hi...

could you please explain me better what you mean with >1000 processes?
What OS are you using? How do you determine the number of processes Phex is using? Can you send me screenshots?

There should be no relating I know between so called 'processes' and the IP.

Gregor

auto connect doesn't work
 

I think i've got kinda the same problem. 127.0.0.1 ( localhost ) is listed as my IP adress. I explicity changed it to my actual (outside world internet ) IP adress, my local address, and several other adresses just for the hell of it.

No matter what it's listed as, Autoconnect still won't try and connect me to any sites in the host catcher.

On the plus side, i can still connect to sites manually by clicking on a host catcher IP and hitting connect, but it's a tedious process getting a solid connection.

I can still get a list of sites from a host to fill the catcher up too. Just seems like that little checkbox for auto connect doesn't seem to realize it's checked.

I had phex running quite well, was impressed with the whole gamut and was very much converted from limewire up until this happened. Had an uptime of several hours, and now no amount of quitting or rebooting seems to fix it.

I didn't notice any extra processes running, but them i'm Running OS X so maybe it's not handled the same.

My OS is Windows XP with J2SDK 1.4 and there is also the problem with the own IP address 127.0.0.1. The first time I used Phex the IP was right but after quit and a 2nd start Phex always uses 127.0.0.1.
Then it seems to be in an endless loop. I can choose the disconnect menu but nothing happens.

One suggestion, one big problem
 

Okay, the thing I miss most from earlier versions from Phex is the ability to highlight multiple search results at once (using CTRL or SHIFT) and then hit "download" (or "quick download") once to transfer ALL of them to the download list. Now that only transfers the first one selected, making trying to download a large number of files at once a very tedious process indeed. Could this functionality be brought back in future versions, please?

As for the big problem, Phex constantly crashes on me now. I tried running the debugger but that gave me no useful information whatsoever before locking up. I have not yet been able to determine what causes the crashes, but I never used to have this many lockups with previous versions...

Thanks for listening.

Jonathan Hagn
jhagn@mindspring.com