|
Register | FAQ | The Twelve Commandments | Members List | Calendar | Arcade | Find the Best VPN | Today's Posts | Search |
User Experience Tell us what you like/dislike about XoloX. XoloX has been discontinued. We highly recommend you use an actively developed client instead. |
| LinkBack | Thread Tools | Display Modes |
| |||
i've had enough!!! i'm using xolox since nearly the day the very first version was released. at this time i was filled with enthusiasm: really nice and intuitive interface, easy to use, fast downloads ... in the meanwhile i'm tired of the bugs. it's not only the well known access violation which rises after a few hours. this (or maybe: these) bugs is/are not the worst ones. there is another bug which is really serious. the first time i encountered this problem i thought i'd smoked too much pot ... but yesterday xolox drove me crazy: i download a 570 mb movie for 2 weeks or so. yesterday i was glad: 99%. i watched the last minutes of the download. a few minutes after showing "queued ..." the movie wasn't finished ... the progress counter showed 70% ! it'll last another week to finish this file ... if it's shared once again ... i cannot understand that a program with such a serious problem like the one i've written about wasn't updated for nearly 1.5 months. HELLO DEVELOPERS! ... WHAT'S GOING ON? ... ARE YOU IN HIBERNATION? ... WHERE IS THE NEXT VERSION? ... DID YOU ACCIDENTELY DELETE THE SOURCES??? i'll look for another gnutella client if there's no updated in the next weeks. it's a pitty because i like xolox but in the moment i hope many other users will follow ... maybe this is the only way to make the developers understandable that IT'S TIME FOR A BUG-FIXED VERSION ... sorry for my bad english - it's not my native language. i hope everyone got the point nethertheless. christian |
| |||
its not an error xolox downloads in segments as progress goes down, xolox checks to see if the segments match up (ie if those segments are from the same original file) if they arent, xolox has to find another segment to download, thus progress goes down i think thats how it works |
| |||
Segment shmegment Here's an idea: When XoloX finds the first user that has a file, it should try to download small (2-4k?) piece every 10% of the way through the file. Then, when it encounters the next user that has the file, it can start the downloading at exactly one of these spots and *IMMEDIATELY* see if there's going to be a segment mismatch, instead of downloading 200MB, *THEN* finding out the first 2k overlap doesn't match. What would make this alot easier would be if segmented dowloading was more native to the gnutella standards, such that you could request multiple chunks during a single request. Get it added to the standards, guys: it's not rocket science. - JL |
| |||
i'm going crazy ... in the meanwhile ... i could finish the 560 mb movie ... by myself - not by xolox. after xolox downloaded 99% and copied all temporary xlx-files to one xlx-file i closed xolox and copied the 564...... byte file from the xolox-temp directory to another directory - just in case. after this i restarted xolox: after a while it showed 48 percent. now the best: i tested the 560 mb avi file i saved from the temporary directory. and guess what happend: i could watch the complete movie without any problems - IT WAS DOWNLOADED CORRECTLY !!! to unregistered: it's completely nonsense that xolox thinks the segments doesn't match. how should xolox know that ? the segments are plain parts of the file you're downloading - there is no additional data like crc sums or so which xolox could use to check the downloaded segments. christian |
| |||
Re: i'm going crazy ... Quote:
|
| |||
hmmm ... but why the heck xolox joines all segments and checks afterwards if the overlapping parts of the segments are equal ? this is illogical ... at least to me. i'm software engineer and i would check to segments first - as everyone - because after merging all segments there is nothing to check left. i forgot : as i wrote in a previous posting i've watched the complete movie. the mpeg4 codec is very sensible at file corruptions. nethertheless i haven't seen any bad frames. peace - christian Last edited by iluvatar; November 13th, 2001 at 01:13 PM. |
| |