PDA

View Full Version : Less Results With 2.6



leontager
12-20-2003, 11:53 PM
Hi, i tested this out with my friend and for some reason I find much less results with kazaa #KlChat rc5 build then with the old kazaa lite. am i missing something??

Tmpj
12-21-2003, 12:35 AM
Originally posted by leontager@21 December 2003 - 00:53
Hi, i tested this out with my friend and for some reason I find much less results with kazaa #KlChat rc5 build then with the old kazaa lite. am i missing something??
I'm a real lamer at programing, but this is only a suggestion of what the problem could be. Maybe those "Search More Limits" are having some influence on the search results.

leontager
12-21-2003, 12:40 AM
oh i was going ot ask about that too...it doesn't seem to be doing the unlimited search more anymore. can someone tell me what happend"?

Elistas5959
12-21-2003, 06:40 AM
The "Auto Search More" feature was a part of Kazaa Lite Extensions coded by Rocko. There are currently no ASM for any Kazaa 2.6 releases. This would definitely have the effect of far fewer results if you are not aware of this. You have to press the Search More button every time manually.

Kunal
12-21-2003, 01:02 PM
Originally posted by Elistas5959@21 December 2003 - 07:40
The "Auto Search More" feature was a part of Kazaa Lite Extensions coded by Rocko. There are currently no ASM for any Kazaa 2.6 releases. This would definitely have the effect of far fewer results if you are not aware of this. You have to press the Search More button every time manually.
Diet-K also adds asm to kazaa 2.6, i think thats on of the main reasons it was included in #klchat build

leontager
12-21-2003, 05:40 PM
hmm...I thought Kazaa #KLChat had all the features of kazaa lite...I also checked that dk has a feature "auto find more results for Diet K quick searches" which is enabled and set at 15 times. wouldn&#39;t that be it? if not i guess i have to downgrade cuz 2.43 worked just fine for me <_<

Kunal
12-21-2003, 06:18 PM
Stick to which ever works best for you, 15 times is more than the 2 minutes that K-lite k++ auto searched more i beleive, you could have just had a 56ker as your supernode that time, try again