This is a unstable beta release of Phex 0.8 build 28.
It comes with:

• Ultrapeer Connections
• GWebCache support
• Download and Upload Queuing
• Partial File Sharing
• Browse Host
• Chat with Phex, Limewire and Shareaza Users

You might encounter a few bugs and problems using it and I would very much appreciate it, if you report anything you notice.
You can download it here:
http://phex.kouk.de/download.htm

Thanks,
Gregor

__________________

Havent really got arount to try it yet
because of the attached error
its less descriptive than last time...

Attached Images

phexiniterr.png (15.1 KB, 426 views)

I had basically the same problem and errors; I deleted the user files (for me they were in C:\WINDOWS\phex) such as phex.cfg (making a backup of that one so I could copy the info back into Phex) and when I reloaded Phex it worked again. There was a similar problem previously; iiRC, it has to do with the spacing of the columns (i.e. remote host, vendor, etc. if they are too wide, it creates an error and Phex crashes)

CK

The problem comes when you close Phex while you have a running download.
When you start Phex again it has troubles to determine you local IP.
I will upload a fix soon. The only workaround now is to not close Phex with a unfinished download, or to delete the phexdownload.xml after closing Phex.

Gregor

__________________

A bugfix is released with build 29.

Download at:
http://www.sf.net/projects/phex

__________________

Good Job. I think Phex has a lot of potential.

I agree thanks for the great product and its progress !

Regarding this little prob: Should'nt it be possible to drop a unrecognized xml entry instead of exiting the program ?

Attached Images

phexiniterr.png (13.8 KB, 388 views)

The recent XML problems are due to a new XML parser and generator. Old Phex versions used a data binding technique that I once wrote myself. The new versions now come with a standard data binding solution from sun which is much more powerful. But causes some problems until it is completely tested and adjusted to all the different situations that can occur in the Gnutella network. Thats why 0.8 is still a beta.

I agree that exiting Phex is not the right solution to this, but thats whats happening currently on any kind of startup problems.
I added some code now that solves a few problems and just dropes faulty download candidates or download files.

To workaround this problem delete a row in your phexdownload.xml that look similar like this:
<guid>null</guid>

I will release a new build soon.

Gregor

__________________

Some more problems are resolved with the new beta build 32.

Its available at:
http://www.sf.net/projects/phex

__________________

And continously on with further suggestions
For example I had just lost my download xml in a crqsh (lucky i discoverded in in found and it was still good...)

But what I am thinking it would be nice if every download had its own xml (maybe even standardidezed source and fragment description protocol SFDP) so its harder too loose all that good effort and be able to transfer it to a different machine together with its fragments
Meanwhile it could be used to identify faults and find and reload perfect segments ... Well Im sure You are allready on to that ...

Other than that I still see a little bug in the upload average reporting (see attached image)

Attached Images

phexveloerr.png (3.1 KB, 353 views)