Kazza tips
- Thread starter Justintime
- Start date
It could be any number of things that you installed on your computer. More than just KaZaA has had spyware in it. Did you have KaZaA "Full" installed on your computer before? That could do it. AOL, ICQ, Yahoo, free versions of many popular programs such as Getright, Gozilla, Download Accelerator, and even many websites can introduce spyware on your computer (thankfully, neither XiBase nor OTC do 
)
)fury said:It could be any number of things that you installed on your computer. More than just KaZaA has had spyware in it. Did you have KaZaA "Full" installed on your computer before? That could do it. AOL, ICQ, Yahoo, free versions of many popular programs such as Getright, Gozilla, Download Accelerator, and even many websites can introduce spyware on your computer (thankfully, neither XiBase nor OTC do
That's what you say.... But would you tell us if they did?
BTW, if you're tracking my usage, can you get me the link to that porn site I was at last night, I forgot to bookmark it.
MitchSchaft
New Member
lol
I don't think I'd live with myself if I let a spyware cookie come anywhere near any of my sites... Even if it's an ad that would bring in a billion dollars a month.PuterTutor said:fury said:It could be any number of things that you installed on your computer. More than just KaZaA has had spyware in it. Did you have KaZaA "Full" installed on your computer before? That could do it. AOL, ICQ, Yahoo, free versions of many popular programs such as Getright, Gozilla, Download Accelerator, and even many websites can introduce spyware on your computer (thankfully, neither XiBase nor OTC do
That's what you say.... But would you tell us if they did?
BTW, if you're tracking my usage, can you get me the link to that porn site I was at last night, I forgot to bookmark it.
OK, well, maybe I'd crack then.
But seriously, I hate spyware cookies as much as anyone else. I run Ad-Aware weekly and have my browser ask me before storing ANY cookie (in IE6, it's Tools\Internet Options\Privacy\Advanced - set both to Prompt)
fury said:I don't think I'd live with myself if I let a spyware cookie come anywhere near any of my sites... Even if it's an ad that would bring in a billion dollars a month.
OK, well, maybe I'd crack then.
If you didn't crack then, we'd all KNOW you are as crazy as some of us think you are.
Did that come out wrong?
I have NEVER had a problem with ads before. I never had full Kazaa installed either. I installed Kazaa Lite, a couple days later my computer was runnign liek shit. brainsoft checked, it was loaded down with spyware. He uninstalled Kazaa, cleaned out all the spyware shit and I haven't had a problem since...
unclehobart
New Member
Stipped Kaaza 100% off again and deleted it from the registry. redownloaded the lite version... and it STILL hogs a CPU... wtf? Anyone know how to clips the code so I can get my cpu back?
Justintime
Guest
Kazza lite is ok, but i never use the internal player, i just copy the dat file and rename the extension to whatever the file is, and test it, if its an avi file, its best to fix the index with avi fixer if trying to play a partially downloaded file.
Kazaa Lite never takes up 100% of my CPU, no matter how hard I try to let it.
Although the internal player really really sucks, takes 5 or 6 clicks to get it to let you preview a file. Kazaa 1.5 was so much better in that aspect, it'd play it on the first try (if it had enough data to start playing)
I hope KL2.0 fixes that.
Although the internal player really really sucks, takes 5 or 6 clicks to get it to let you preview a file. Kazaa 1.5 was so much better in that aspect, it'd play it on the first try (if it had enough data to start playing)
I hope KL2.0 fixes that.
k, i found the problem.
I guess there's a bug in the sending code, something that makes the CPU load go full, probably an "over sending" filling some UDP/TCP stacks in the TCP/IP module. Or probably just a loop causing it to go to the 100%.
See if the cpu load goes down when you cancel all the uploads.
I guess there's a bug in the sending code, something that makes the CPU load go full, probably an "over sending" filling some UDP/TCP stacks in the TCP/IP module. Or probably just a loop causing it to go to the 100%.
See if the cpu load goes down when you cancel all the uploads.
