Phex has brain damage
 

My install is: Windows XP, Sun Java 1.4, and Phex 2.0.0.76

This all lives behind a Linux based Firewall/NAT with portforwarding configured.

Phex has a habit of forgetting it's configuration, as well as the list of downloads it's working on. I initially thought it had something to do with having to use task mgr to abort Phex after it has become unresponsive (after hours of uptime), but I've had times when I've closed Phex properly, and it will have lost its config the next time it's loaded. This especially annoying because Phex likes to choose a new listening port, rendering firewall forwarding useless.

It is also having upload problems. Most of the apparently successful uploads (all bytes sent) will be marked at "Aborted". But I get even more 0 bytes sent aborts. Typically there will be a dozen 0 byte sent aborts, followed by a finaly all bytes sent abort.

Suggestion: Would it be possible to set an option to view total bytes for a file uploading, as opposed to the current segment?

Otherwise thx for the java based client,
-kf

Try using the new beta, it might fix the forgetfulness-bug.

The upload-info has been broken for quite some time, but that simply wasn't high priority :)

Yes, please try to replicate this with the latest beta. If you can still get your config file to be long I'll look into this and hopefully resolve it for the next release.

If you can get it to "lose" the configuration, I would be interested in whether your phex.cfg is missing, empty, or with some values missing.

I can think of one way the config file could be broken: if you run out of disk space. Could this have been the cause? Obviously, if there's no space on disk Phex will not be able to create a new file. I'll look at the code and confirm this is a possibility. The workaround would be to not delete the old config until the new one is successfully written. Perhaps the code is doing this already, but as I said, I haven't checked it yet.

I've just added code which should make the configuration more secure: rather than just overwriting the old file, phex now renames it to phex.bk, creates the new file, then deletes the backup. This of course isn't yet well tested, but it should help.

If the cause of the configuration file going missing is something else, maybe more work should be done. But until you try this out or give me more information I won't worry about this any more. :-)

Fixed uploading
 

Hi there.

I've just looked a little more closely at the upload code, and there is indeed a bug! I'm submitting the fix to CVS now, so the next release will be better. (No guarantees the displayed statistics will be right, but I can see I'm able to upload now.

Great, really great!

(Especially. because sharing is one of the main reasons I use Gnutella: I share my own songs and short stories).

I also had a poke around to see what could be done about the reporting - the original poster suggested reporting the total volume transferred. I'm not a real java person and don't fully understand the way the GUI works, and couldn't immediately see how to do that, but it sounded like a good idea to me. I'll play around a little and see I get anywhere though.

All we need now is magnet support and you can give a link to your stories!

Erfolg!

I've got the upload stats correct now. It's in CVS. You can bug gregor if you want (yet) another beta with this and other fixes. :-)

Fantastic!

Another beta would surely be great!
I don't compile Phex from CVS at the moment, because I just rewrapped my whole computer and need to get back quite some data from DVD.

I assume three are not too few people like me who love to try every new beta, they can lay their hands upon (and see how they evolve).