Could it be that XoloX is misintepeting the metadata data generated by Gnotella, and early Bearshare 2.3.0 betas that work on the open network, as a file? (later BearShare betas are on their own beta network, so you won't see traffic from them)

I have not done the research to know in what order data is collected to represent file name, file ize, host IP, etc... but it seems that when there is metadata present XoloX gets confused and uses it as a file name or file size and the first letter of file names get cut off.

I did a search for Blind Melon, and most of the files I get back as hits are fine except from what I presume is the same host, where I see a couple of hits for "bps 44khz" then 1 hit for several songs in the format "lind Melon - songname.mp3" with a rediculously large file size listed. Trying to download these files gives "xxxxxxxxxx is not a valid integer" if the file size listed is over ~1,107,316,000. In any case the files do not seem to be downloadable.

For debugging purposes, could anyone that sees one of these "bps khz" files search again as 'any type' then sort by size? I bet you will see at least one MP3 along near it (probably right below it) with the first letter cut off of it's file name and also reportign as being over a gig in size.