Observations and a suggestion or two.
 

The connection speed type selection is nowhere in the options, does not appear when upgrading from an older version, and XoloX does not put the registry key in unless it's installing 'clean' (no registry entries) I only saw it, and the correponding key, after erasing HCU/software/xolox. While speaking of the registry, changing 'fisttime' to 'true' has no effect on how xolox starts, and I still dont' know what 'needtotalinit' is, or when it might be set to false. there is also a rare bug where XoloX will double the shared extentions and directories, but I can't reproduce it at will. (I think it has to do with manually editing the registry while XoloX is running)

I did some tests running BearShare 2.3.0 on port 6437 and XoloX 1.12 on port 6436 (since it can't be changed) My first test was to see if the 'connect to host' line in XoloX works. In my experience, it does not. I enter my IP and port 6347, click add, and nothing tries to connect to BearShare. Is it dumping the IP into the host cache instead of conencting to it? Is XoloX blocking it because it's my IP, even though it's a different port than XoloX uses? Bearshare was able to connect to XoloX with no difficulty, but would frequently drop XoloX claiming the host didn't respond. (this could be due to my severe bandwidth limitations.

The number segments XoloX will attempt to download at once is equal to two times the 'upload speed' setting. Downloads have no speed limits, but I don't have the bandwidth or files to share to observe how uploads work. Does each upload get 'upload speed' K/s, or does each upload get ('upload speed' / number of uploads) K/s?

Downloading a large file from one client to the other I notied that XoloX downloaded from BearShare at about 4.7 Mbits/s (~600 KB/s) but BearShare only downloaded the file at about 1.4 Mbit/s (~170 KB/s using Max speed settings, obviously) I don't know for sure which client is at 'fault' but there was a lot more hard drive grining when Bearshare downloaded form XoloX, so I wonder if the 'slow' speed has to do with how XoloX buffers it's uploads.

Also, as theorized, XoloX is unable to filter out the MP3 metadata BearShare (and gnotella?) send along with query hits. Any mp3 hots that come in from a given host which sends such data will exhibit the following behavior: First hit will be normal and is ok to download. Second hit will be an MP3, but incorrectly display the file name as part of the metadata (eg: 44 kHz 4:09) and have a corrupted file size. All remaining hits from that host will display the filenames with 1 character missing from the beginning, and also have corrupted file sizes. The corrupt file sizes appear to be related to the length of the previous song.

Upon a closer examination of resumeinfo.txt, I found out that XoloX interpets any file matching the search query with the same file size as the same file. However, it appears that XoloX drops any files of duplicate size from the same host. Searching BearShare with XoloX I got 23/31 mpg files returned, and looking at the file sizes ther are 8 files with exact same file sizes as others. This is bad, as many files are chopped into evenly sized chunks to make distrobution easier; file001.ext from one host and file002.ext from another could have the same size, and therefore be seen as the same file, but in reality are just different parts of the same thing.

Only files of the same size AND NAME should be dropped if returned from a single host, and only files with the exact same name should be automatically grouped as a single file. Returns should be sorted as follows: Files of the same size listed next to eachother sorted by rank, with the file size groups listed by order of total group rank. Users should be able to highlight several files and right click to get a menu which lets them do the following: "download" which is similar to the current usage, where any files of seperate sizes are treated as seperate downloads, but when the user selects a download that is the same size (with a different name) as an already downloading job, they should have the option of adding it to the job or making a new one; "download as >" with a list off of the arrow giving them each different file name selected as being the same file; and "Add to >" with a list off the arrow of any downloads currently in progress with the same file size. Double clicking should work the same as "download", in that if a file with the same size is downloading, a yes/no box should appear asking if the user wants to add it to the job.


That's all for now.

wow war and peace !

Nah...
 

That's not a long post: THIS is a long post... Yeah, I know it's not about XoloX, but a game instead, but it shows what I can do when I get into writing. ;)

note: That was the first draft, by the time I had gotten that far I didn't feel like proof reading. Anyhow, I feel it's more worth a developer's time to read a long and descriptive post than a short and whiney one that just says the software is broke.

[edit: fixed link]

Anyway
 

Just a shameless bump to get this to the top of the pile and let me know easier if any new posts have been made to this forum. Also I think that I brought up some very serious problems which will only get worse as people upgrade to Bearshare 2.3.0 or the latest version of Gnotella. Oh, and I'm timing out with Bearshare with out, incoming or auto connections to XoloX on the same computer. XoloX is either sending out malformed packets, or BearShare is wanting a reply to some query, but XoloX is dropping the message and not replying.

I read somewhere that BS is planning to breakoff into thier own network. . .
Maybe now is a good time, and take Gnotella with you. <grins>

I don't know why we don't start calling the gnutella network the xolox network. LOL

Just one lame users opinion. : )

Hi Seeker,
yes serious problems. I only want to give a feedback that Bearshare did never drop the connection to Xolox on my system.

Hmmm
 

I'll re-run my tests on MY computer (the non-Compaq one with an external USR modem instead of a crappy winmodem) which I just got up and running again. *goes to download BearShare*

Ok...
 

What I have found is... when doing tests offline, Bearshare stays connected to XoloX, when connected though, I get dropped very quickly... I think XoloX is dropping the handshake in favor of routing queries or downloading files... so BS disconnects. (remember I'm on a 31200 connection, broadband useres may not experience this.)

For my tests I shared a number of files, including all the Win98_##.CAB files from my 98SE CD that = 1802240 bytes (The size of a DMF formatted disk) with which I re-confirmed my note that XoloX only displays the first file of a given size from a single host that matches a query.

I also re-confirmd that XoloX returns a max of 30 hits at a time (not 100) and that for a given query, will return the same 30 hits every time. A better method than starting at the beginning of the shared files index each time a query comes in would be to save the end position and start at the next entry, starting over from the beggining when you reach the end. (but not going past 'maxreturns' or it's current start point)

Last point of notable mention is that XoloX will 1) Let a client connect to it multiple times, allowing outgoing network connections to computers that it already has inbound network connections to, and 2) will let a client make multiple connections to it.

In bearshare I was able to have

Localhost = IN
localhost = OUT
ACB7205E.ipt.aol.com = OUT
172.183.32.94 = OUT

Those last two are the same. BTW, with AOL you don't even need to do a DNS to get an IP... just split up the hostmask ... AC.B7.20.5E is hex for 172.183.32.94 (Nice and easy, but impossible to put up bans for without blocking the entire AOL user base :P)


Expect more bug reporting regarding actual networks and proxies and stuff from me soon, as I have been given another (somewhat dead) computer with which I shall network with my own as soon as I manage to get it working and get a network card for it *bwahaha*

Example of multiple conenctions to XoloX: