Filename cropping and seamingly erroneous filelengths
 

Sometimes on a search, the first character of the filename listed gets cropped off.

Files listed missing the first character also have very large file sizes listed e.g. 1,912,615,709.

Only files with file sizes this large seem to lose the first character.

This is on Windows 2000 SP2.

Known
 

This happens whenever you recieve search results from users of the latest versions of Gnotella or BearShare. These clients send out extra data (bitrate and ong length) that XoloX can't interpet correctly, and all but the first returned MP3 will be 'corrupted' in the manner you describe. This effectively makes all MP3's from BearShare and Gnotella worthless, as you can't download them.

For more on this and other things, see this thread.

Ah, ok.

Surely the protocol is laid down and these people should all be singing from the same sheet? :)

I think it's called extended data query hit. Something like that.

It is documented in the protocol so Xolox should cope with it. I'm guessing they will next time. They don't have to interpret the extra data, they can just ignore it as long as they still parse the messages properly. :)

it's time for a new version... but I didn't say that :)