Finally, when you said
Delete the WireShare folder from your user preferences folder
I guess that you mean
/Users/~/WireShare

On the other hand, it seems that this problem can be fixed deleting the Limewire (in the case of such application) or WireShare preferences. But where are them in the Mac? Thanks.

Normally on MacOSX all you need to do is go to the application folder and send the particular application packages (or their program folders if they have any) into the trash & empty the trash. If you wished to keep them I guess you could zip them first & trash the unzipped programs.

I guess there is a chance opening WS is somehow triggering a reaction from one or more of those programs. I just tested WS & LPE open at same time in another account without issue however.

Preferences folder is where you suggested. Deleting preferences folder on MacOSX. The example is LimeWire, but instead find WireShare's preferences folder.

Thanks. I have also deleted
/Users/~/Library/Preferences/WireShare
to no avail. The problem persists.
Any idea?

BTW, could the issue be related to the fact that I do not have any ports open in the router?

WireShare does have UPnP (port mapping technology) but this does not work with all routers & some routers are not reliable with UPnP. For WireShare I port forwarded for my router because I found UPnP was failing after 2-3 days and I was getting a firewalled message in the Connections window.

Deleting the other gnutella programs might have an effect then.

I have deleted all related to WireShare (as far as I know):

/Applications/WireShare.app
/Users/~/WireShare
/Users/~/Library/Preferences/WireShare

and installed again WireShare. Surprisingly, the
WireShare/Preferences/Advanced/Listening Ports
has values for:
Gnutella port
BitTorrent ports

Is that normal or is WireShare taking such numbers from elsewhere, and thus creating the problem?

That's normal.
In your settings, UPnP is enabled by default and WS will attempt to automatically map the port via communicating with your router if it can find an open one. This happens when WS is first opened. This port might change each time you open WS.
However, when you port forward, the port remains static. It needs to be static (remain the same) and needs to match the port that was port forwarded in the router.
The bittorrent ports might be a built-in default, not sure about that.

There is a chance something is blocking WireShare. Firewall/router. But the question also is what is causing it to open in multiple windows.

I have found that if I block the WireShare connections when it opens (firewall prompt), then the pesky window does not show.

On the other hand, I have re-installed LimeWire (Pirated Edition) 5.6.2 from
http://www.gnutellaforums.com/gettin...e-edition.html
following the directions:
2-Connection and Security L5 June 2014 install.app
3-LimeStart Installer.app
4-LimeWirePirateEdition.dmg

and after that, opening LimeStart.app does not open LimeSire, but WireShare. How to fix it?

Just in case that gives any hint of what is going on.

That's due to LPE & WS both using the same OSX program reference which is com.limegroup.gnutella
This approach is recommended by Apple. Unfortunately LW clones or variations can get into the mix.
I used to have the same problem when I had an old LW4 clone called MP3 Rocket installed. LimeStart started to open MP3 Rocket instead. This issue is user account specific. LimeStart does not open WireShare for me.
The fix would be to remove WireShare.

LimeStart could instead use the program name, but some people rename program titles or/and move the program's location which would prevent LimeStart from finding the program. Some people might also have multiple versions of LW on their system which adds to that complexity.

For WireShare 5.6.4.1 on Mac OS X 10.9.4, I get WireShare is connecting for ever, besides the pesky window (WireShare has encountered an internal error).

For LimeWire Pirate Edition 5.6.2 on the same Mac, I get connecting for ever the the message: You are offline. Please check your internet connection.

Any idea on how to fix any of those? Thanks.

Ignore the message on the main window of LPE. What's important is the connection bars bottom left corner of screen. And if you open Tools > Advanced Tools to open the connection window, this will show connections the program is trying to make. It might also say whether you are firewalled or not.

It's my guess your setup is firewalled in one way or another. WireShare or LPE need to be added to the OSX firewall exception list if your firewall is turned on. I'm curious if you have any other firewall or security software which might be causing the problem.
Try port forwarding your router. You will need to set up a static ip first. This is your computer's internal network ip address not your external ip address. Choose a port to port forward. Perhaps the same port that's listed in your LPE or WS settings. After finishing the process, save settings. Some routers need to be rebooted before the change takes effect. Next time you open LPE/WS go to Advanced > Listening ports & change from using UPnP to Manual Port Forward & add in the port number you used for your router. Sample image here.

You might already know how to port forward your router or have an instruction booklet. You can find instructions here (for Windows but the OSX version should be similar.) Find the brand, then model (ignore the advertisement page just pass through it / close it.) Setting up a Static address would be the first thing you'd do. I made the error of not doing this and my network address would change & the port forward wouldn't work on those occasions. Network address will either start with 10. or 192. and the last number .1 is usually the router's address with your computer's network address anywhere between .2 to .255.

For WireShare it has a backup bootstrap system. So if the program finds there's no connection file it will re-download a fresh one. I'm wondering if this process is being blocked by your system somehow.


On that other side-topic about LimeStart & the reference it uses, I had mentioned to Bigjx before the first OSX release of WS that perhaps we should change this so it's different to LW. But my vague understanding from his reply was it's heavily embedded within the code (thus very difficult to change.)