Acqlite problems...
 

G4 PPC running 10.4.11. Plenty of RAM, plenty speed, 500gb drive.

Immediately after launching Acqlite a popup with "wants to connect to" starts. It continues popping up over and over asking to connect to an endless number of sites. It won't give me time enough to quit Acqlite and I have to use esc for a force quit. Even after quitting, it keeps popping up and even if I open a browser or other app it stays on top. I have to restart to finally get rid of it. What is this and how do I get rid of it?? :bangh:

I've never seen that before. Did you add Acqlite to your OSX firewall as an exception?
Since you are using OSX 10.4 the first post is applicable to you http://www.gnutellaforums.com/mac-os...tructions.html but perhaps use the description Acqlite instead of Gnutella/LW. By default Acqlite uses port 6346.

Have you tried a fresh connection file? You can find a combo connection installer here.
I hadn't used Acqlite for about 6 months & couldn't connect. After using the above connection installer Acqlite connected within about 5 seconds. ;) If Acqlite does not connect after 15-20 mins, close it & open again. If still no connection repeat connection installer process.

The only sites Acqlite should be attempting to connect to are GWC (GWebCache) sites to obtain a small list of peers (gnutella hosts running as ultrapeer) to connect to. Your connection list will probably have a list of between 5-20 of them. If Acqlite works like many other gnutella client programs, it will attempt to connect to a single GWC after trying to connect to every 15 hosts from your connection file. (That is if it can connect to the particular GWC otherwise will try others.)

(OSX 10.8 would not allow me to copy-paste a url into the browser, it would say could not find. Whereas if I directed the browser to the url address manually it had no problem with it. I do not understand that logic.)

BTW in the Network window, once you are properly connected to 3 or 4 peers, if you see yourself connected to any host address ending in :27016 then remove them. Hosts that use port 27016 are Spam-Bots. Also any with port 7001. There's a 3rd party app for OSX called WaterRoof which can be used to block ports which is what I'd use on most occasions.

Solved: I went to Little Snitch and turned off the Network Filter in Preferences. Went back to Acqlite and it worked perfectly.

Cool! Yeah Little Snitch can be a pain sometimes. In fact I removed it for the reason you were seeing above. I'd totally forgotten about that aspect of its behavour.

You needn't remove it and in fact you should use it religiously IF you have ANY files in your drive that are pirated or downloaded without permission. That probably applies to some of your apps and some of your music. Of course, I am totally pure and innocent in that regard, but still I trust Little Snitch. It's a great program if you take the time to know how to use it.

Yes I probably should learn how it works properly, though I know what it does. Two alternatives. Disconnect internet or block the address via the system's config file (if you know how.) . WaterRoof could possibly do the same thing, if you know which address to block. It can block incoming or outgoing connections for specific addresses.

BTW in recent times (a month or two ago) I've read on various forums including apple forums that later versions of Snitch causes conflicts with other programs, stopping them from running properly or crashing, including the blue screen kind of system reaction (Kernal panic crash.)

panic(cpu 0 caller 0xffffff80026b8b45): Unexpected user trap, type 15
at.obdev.nke.LittleSnitch
com.apple.filesystems.smbfs
com.apple.driver.AppleHWSensor
com.apple.driver.AudioAUUC
com.apple.filesystems.autofs
com.apple.iokit.IOBluetoothSerialManager
com.apple.driver.AGPM
com.apple.driver.AppleMikeyHIDDriver
com.apple.driver.AppleHDA
etc.
(A quickly googled example.)

You no doubt have an Intel machine and I've heard Little Snitch had problems revising their software for Intel.

I have so many high end programs and sound equipment that work perfectly on standard OSX but wouldn't at all on an Intel. So I don't use Intel even though I do have it on another machine. If it works don't fix it.

Still, if you get the latest version of LS from their website, they may have fixed the problems you ran into. The problem I had really was irritating until I realized it was my fault for checking that particular preference.