Cant find anything,it just sits there.

[BradBo]

I am using Xolox.
When I type in a search like "Led Zepplin",it just sits there.
At the bottom of the Xolox screen it says " Connecting to network. Hosts left to try:4(6) (5)". It actually switched between these numbers. So it seems like it is looking and not finding.
I have left it on for hours on a search and it just keeps searching for a network.
Help.

[Moak]

Hi, suddenly I have the same problem on my home computer too, it worked for days, now this. Hmm, at office I have no problem (I use DSL and the same router/ISP).
I tried to use a new hostslist.txt and clear registry settings... no solution, I have no idea at the moment. Anyone?

Moak

[Moak]

Okay, I made it work again.

It seems that the hostslist.txt in the Xolox directory made itself corrupt, deleting & restart doesn't help. It looked like this (only 3 lines posted):

;<?$8>=$;3;$;20<9><
8;9$;;?$>$380<9><
;8=$:$:$;0<9><

I replaced it with one of my old hostslist files, which looks like this (only 3 lines posted):

I;2;>8;2:6346
KI>2;2>8:6347
2?L:;3>;:6346

Try to download a fresh hostslist.txt and make sure it looks like the last one! I'm using Xolox V1.12 - don't know what happened, maybe a bug in Xolox.

Hope it helps, Moak

[The Seeker]

This means your hostslists.txt file has been exhausted, and it's trying the GSPs built into the program.

Look at address D4578 in the XoloX exe... looks somethine like this:

____ 63.211.153.119 ____ 6346 ____ 64.61.25.139 ____ 208.239.76.100 ____ 216.231.59.208 ____¤ 208.245.164.155 ____ 24.95.35.22 RM Ahost


Looks like 6 host IPs to me... This makes me think the problem is that they hard-code the current IP of the GSPs when they release a version, instead of using the domain name, like:
connect1.gnutellanet.com:6346 or
public.bearshare.net:6346 or
connect.limewire.com:6346 or
router.limewire.com:6346 or
... I think you get the idea ...

They use domain names to make chaning the IP they point to easy, it's no wonder the built in hosts for XoloX stop working after a little while. My advise in the short term: Shut down XoloX, and download a recent hostcache.txt. My advise in the long term is to the devs: Take the extra half a second to resolve connect.limewire.com (or whatever) to it's CURRENT IP instead of hard coding whatever the IP happens to be at the time of compile.

[The Seeker]

Moak: You were posting while I was typing. That's not a corrupt hostcache, it's one from a client prior to 1.12. My guess is that someone (probably) trying to help, posted their hostcache in the hostcache thread without bothering to make sure they were running 1.12, you downloaded it, and XoloX couldn't make sense of it because it was from an old version. (Does the setup handle the file compatability conversions, or woudl settign "firttime" to 'true' make XoloX check the data files for compatability?)

[Moak]

Posted the answer here:
http://gnutellaforums.com/showthread...9&pagenumber=2