WireShare (formerly entitled LimeWire Pirate Edition)
 

An updated version of LimeWire Pirate Edition based on the metapirate source.

Download links below. Alternatively see WireShare - SourceForge


Windows version:
Mirrors: . MF Mirror, . Google Drive (2 clicks: down-arrow or click file-name), . SourceForge.

MacOSX version: . (Compatibility @ Intel with OSX 10.5 or higher with Java 6 or higher. @ Older machines: OSX 10.6 or higher with Java 6. Need to install Java first unless you upgraded from OSX 10.6 or earlier. WireShare 5.6.4 will now run with Java 7 or later. If you also have Java 6 installed then that version will be used. . Note: WireShare is unsigned and exceptions need to be made in Gatekeeper to download from 3rd party websites, install and run unsigned apps. Apple Support have pages discussing how to do this such as MacOS security - Using legacy apps on Mac OS . Also a 3rd party website discusses how to allow (download) apps from anywhere. For opening unsigned apps, same 3rd party website.

MacOS download WireShare options:
MF Mirror, . . Google Drive (2 clicks: down-arrow or click file-name), . SourceForge.

Linux version (Debian/Ubuntu):
MF Mirror, . . Google Drive (2 clicks: down-arrow or click file-name), . SourceForge.

Linux RPM distro version (OS/2, Solaris, Linux, Red Hat, Fedora, SUSE, Mandriva, etc.):
MF Mirror, . . Google Drive, . SourceForge.


Screenshots:

Attachment 6769. Attachment 6770[ . Attachment 6655. Attachment 6657. Attachment 6659. Attachment 6661

BigJx

ChangeLog
 

Some of the changes and improvements made to the BigJx version of WireShare releases:
ChangeLog:

6.0.2: . . (2022-10-04)
6.0.1: . . (2020-08-29)
6.0.0: . . (2020-03-30)
5.6.6: . . (2017-05-29)
5.6.5: . . (2016-07-17)
5.6.4.3: . . (2015-08-01)
5.6.4.2: . . (2015-07-07)
5.6.4.1: . . (2014-08-10)
5.6.4: . . (2014-07-07)
5.6.3.1: . . (2014-05-06)
5.6.3: . . (2014-03-26)
BigJx

WireShare released for Linux and Mac OSX
 

* WireShare has now been released for both Linux and MacOSX.

The Linux version has it's Security installed via a separate installer. Choosing 'none' in the security installer will remove any previous security installation.

MacOSX: At this point in time WireShare has been tested with Java 1.7 & Software Update will ask you to install Apple's Java 6 (1.6). The program has been tested on an intel Mac with OSX 10.6-Snow Leopard and OSX 10.9-Mavericks (combination java 1.6 & 1.7 but ran under java 1.6).

Attachment 6663 <- MacOSX Java restricted to Java 6 for WireShare. (Snapshot taken on Mountain Lion)

OSX compatibility: @ Intel with OSX 10.5 or higher with Java 6. @ Older machines: OSX 10.6 or higher with Java 6.

Edit: WireShare for OSX can now use Java 7 or higher (aka Java 1.7 or higher) as of WireShare 5.6.4. But will use Java 6 by default if it is also installed.
It took over 2 weeks to get a java 7 version working for both jre and jdk but to get it to work with both java 6 or later took more time to solve.


Note: The MacOSX installer is Applescript based & does not use a postflight script (does not create a Receipt file), and WireShare is 'unsigned'. This might cause some issues for those whom use Gatekeeper. You will need to make an exception for WireShare in Gatekeeper's settings.

(Articles regarding making exceptions: Unsigned OSX apps, . . WikiHow - Install from Unsigned Devs on Mac, . . Shortcut to install unsigned apps, . . Tweak Gatekeeper's settings, . . Apple Support - About Gatekeeper, . . Ways to Get Around Apple's Gatekeeper, . . How to open apps from an unidentified developer whilst maintaining Gatekeeper.)

Mac OSX version update to fix memory issue
 

WireShare 5.6.3.1a has been released specifically for Mac OSX users to fix a memory issue. The program was not reading its memory settings properly (or at all) and with little doubt was probably using the default minimum java memory possible. WireShare 5.6.3.1a fixes this issue.
Compared to LPE, WireShare's memory handling capability has been increased slightly.
Edit (12 May): WireShare 5.6.3.1b enhances memory efficiency. Looks like LW forgot to use this. Which is probably why LW5/LPE was unreliable to use for multiple day sessions on OSX.

Extra note: a specific OSX 64-bit Java 7 capable WireShare will be worked upon in the coming month. Compatibility will be limited to intel machines with Lion or higher, and will only run with Java 7 (1.7) or higher. (Edit: we made it to work with Java 6 or higher, so compatibility still allows OSX 10.5/.6 Leopard & Snow Leopard users to use WS.)


If anybody finds any issues running WireShare, please report them to the forum so a solution can be worked through.

Definitely something to consider if you are fed up with LPE 5.6.2 I guess?

There's no compulsion to upgrade to WireShare 5.6.3. However, there are notable improvements. There's also no need to use the LimeStart which LPE needs to either overcome Java 7 path issues or the risk of the connection file being erased if not used after 28 days. WireShare has fixed both those issues, as well as a few other bugs & inefficiencies LPE had.

Perhaps it's just my imagination, but I seem to get better search results with WireShare. I've tested certain keyword searches for years to test how good the peers I'm connected to are. Getting over 200-300 search results then a single get-more results for 500-700 on different sessions I considered good compared to some miserable results on LPE or earlier versions of LW. To compare fairly, it seems the average of reasonable search results that appears to have improved. Always exceptions.

I won't drag into possible reasons for this compared to LPE such as less direct connections to the very old type clients that are much less efficient at handling search queries, particularly via UDP (if they are even capable of UDP query handling & responding.) If not, they resort to tcp.

Do i see right that almost everyfile has 1 shares?
I dont wanna use gnutella network anymore if ppl does not use it.

Is the wireshare best gnutella client in your opinion?

WireShare and GTK-Gnutella are both very good. ;) GTK has some advancements in technology. However, WireShare is much easier to learn to use.

Why does the files now have usually only 1 peers? I hate to wait with 9-20 kb/s download speed :)

Either only one person is sharing the file or else, others sharing it have all their upload slots busy. Or perhaps other persons who share the file are offline at the time. People not sharing what they download is a user population issue. Nobody can force anybody to share files. It's a user choice & starts at one. ;)

This is much slower than torrents. I remember when i saw many hundreds of sharers for one file in the network :sos:

Re-searching & get more results tool can often help to get more sources for a particular file. But again, it depends on how many persons are sharing the same file. Also, some files are shared by ShareAza users who have a history of only allocating very low bandwidth toward gnutella network. Always exceptions.

So try the re-search option & also use the 'Get More Results' or 'Find More Sources' option by right-clicking the search tab a couple minutes after the search finishes. Repeat once or twice, then leave it for an hour or two before trying again. Don't do this too often for the same search criteria. Another thing to try is using a different search criteria which is similar to the one you used to find the file in the first place. That can take some imagination. For example, if it's music, try searching just the title of a song instead of the artist or vice-versa, perhaps not the same song you're after. This will help bring in more host results sharing similar files & help to extend your search across the network.

Torrents do have a lot of advantages over the gnutella network or similar networks. People are more likely to allow partial file sharing with torrents which speeds up the downloads for everyone & means much less work needed by the seeders (sharers) of the complete file.
I've had situations like uploading same video file to a few hosts at same time & was obvious at least a couple of them had partial file sharing disabled. So I was expected to upload the file individually to each one by myself. Those who disable partial file sharing make it somewhat harder & unfair on everyone else. If all 3 or 4 of the downloaders had partial file-sharing enabled, they would have downloaded the large file in 10-25% of the time.

WireShare has encountered an internal error
 

I get the error:

"WireShare has encountered an internal error. It is possible for WireShare to recover and continue running normally. To continue using WireShare, close this window. If desired, you can click 'Show Bug' to look at the information about the error."

It keeps on showing for ever.

As described on page 38 of this thread (LimeWire Pirate Edition):
http://www.gnutellaforums.com/gettin...dition-38.html

I have the latest versions installed: WireShare 5.6.4.1, Java 7 update 67, Mac with OS X 10.9.4 (Mavericks).

How to fix it?
Thanks.

If it happens again, can you click the Show Bug information button & copy about the first 50-80 lines, that's the most important part. Then post that part in a reply to this post thread. You can post it inside a code bracket. Each report can be a little different due to a different cause & that's what we need we need to find what the cause is.

When you open WireShare, under the WireShare menu > About WireShare, does it say Java 7 or Java 6?

How many incomplete downloads do you have?
How many files are you sharing?
How many files are listed in your library?

When you said the problem was similar to the problem on the page you pointed to, does the program create a folder called .wireshare or .limewire anywhere?

For MacOSX it might be a memory issue. This is something BigJx & I need to sort out. MacOSX's memory use-age is larger than the Windows version uses. If you were using LPE it would probably be worse.

Thanks for the quick reply.

Such error window shows every single time that I open WireShare. In fact, it keeps on showing all the time (up to four stacked error windows). And if I close them all manually, they show again.

WireShare - About WireShare says:
WireShare 5.6.4.1
Java 1.6.0_65

That is amazing to me, since Apple - System Preferences - Java - Update says Java 7 update 67.

Do I have them both Java 6 & 7 installed? How to remove the oldest one?

I do not have incomplete downloads inside
/Users/~/WireShare/Incomplete
or
/Users/~/WireShare/Saved

I have no files in
My Files - Public Shared (top left of WireShare main window)

I have no files in my Library (top left of WireShare main window)

The folder
/Users/~/WireShare
does not contain
.wireshare
or
.limewire
browsing it with Macintosh Explorer which shows invisible items. It contains only two visible folders:
Incomplete
and
Saved

My Mac mini has 16 GB RAM with plenty of free memory. 1TB Fusion drive with 600 GB free space.

I tried Limewire Pirate Edition time ago, yet could not get it connected after months, so I gave up. I previously used it without problema and Limewire before that without problem either. But that was years ago with other Macs and older operating systems...

The Show Bug says as indicated below:

Should you need further information, just let me know.

Many thanks again for your kind help!

Thanks for posting your bug report, much appreciated. :)

Not sure if this will help but you can at least try it for now:
Go to Applications & find WireShare, Control (or Right) click & choose Get Info. Change the option from Run in 32-bit. If it's enabled then disable it or vice versa. See if this fixes the launching problem. (Here is a sample image using LW as an example.)

Another thing you could try is setting up a test account. This only takes a few minutes & can be easily deleted after use. See if WS opens ok in that account.

WireShare will default to using Java 6 if it exists, even if you have Java 7 installed. If Java 7 is the only java installed then it will use Java 7 or later.

Just had a crazy thought. If the above does not work then try this:
1. Delete the WireShare folder from your user preferences folder, try launching WS.
If that again fails then:
2. Delete the WireShare folder from your user preferences folder, try launching WS & set the language to English if the program does not crash before the setup stage, see if that makes any difference.

Thanks for the replies.

I have tried the above to no avail. The problem is even more intense in 64-bit mode.

I have not tried a new account (I will try that later), but I have installed WireShare 5.6.4.1 on another Mac (iMac instead of Mac mini) with the same version of Mac OS X and Java and it works with both 32- and 64-bit mode. No problem there. Such iMac had on older LimeWire Pro 4.9.8 (that is of year 2007) installed, whereas in the Mac mini with the problem newer versions of LimeWire were installed through the years, and eventually the LimeWire Pirate Edition 5.6.2 (yet it did not open since many months ago), as indicated above.

There are probably remains on the Mac mini of LimeWire and LimeWire Pirate Edition. How to remove all files associated with them? Maybe that fixes the issue.

Thanks again.

Just in case it is useful, I had installed over the years the following Gnutella clients in such Mac mini:

Acqlite
Acquisition
Cabos
FrostWire
LimeWire Pro
MactellaX_PPC
WireShare

Additionally, maybe removing Java 6 and leaving Java 7 could fix the problem. I wonder how to remove Java 6.

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.)

Thanks. The connection bars at the bottom left corner of the screen show gray and Connecting for ever.

The Tools - Advanced Tools initially after starting LimeWire Pirate Edition shows many hosts Connecting, but none remains after a few seconds. The incoming searches and Console are also empty. Says nothing about firewall.

I have the Mac firewall and Little Snitch on, but have granted permission for LPE (none asked about WireShare and it does not show on the list of such firewalls).

I have always used manual private IP numbers. My public IP is dynamic. I have the router ports open and manual port setting in the application. In the past, LimeWire only connected with that.

In summary, I have many years of experience with Limewire without problem, but from some months ago, I cannot connect with Limewire and with WireShare as described below.

So I am lost. There is certainly something in Mac Mac preventing connections, but I wonder what is it and how to fix it.

I'm starting to wonder if the problem is ISP related (your internet service provider.)

Could you try connecting with LPE with Little Snitch temporarily disabled whilst testing the connection, disabling it before opening LPE? I'd recommend adding a fresh connection file: OSX LW connection installer - MediaFire Mirror.

I wonder if any of your gnutella programs will connect. Perhaps try FrostWire v4.

I tried Little Snitch some years ago but due to my ignorance removed it because I found it too naggy & problematic for all the internet apps I use.

It just occurred to me, you were not receiving any emails from the forum mail server. I'm wondering if this is somehow related. Somehow the emails were being blocked or filtered out from receiving them. It seemed odd you did not receive any of the test emails sent. The same tests worked for both Birdy & myself. Nobody else has reported registration issues in recent months in regards to not receiving the forum mailer's emails.
Also, you should have received email notifications for each post reply, so you are notified someone has replied to your posts.

Is there something bad about the word gnutella? :D

I don't suppose Little Snitch has anything to do with email right? Are you using a blocklist with Little Snitch?

I suspect Little Snitch can potentially change the system config files. There might be a change in there which is affecting things. From memory the config files are found in the /private/etc folder, but I might be wrong. Mavericks might be a little different.
Mavericks Gatekeeper might also be an issue.

I'm preferring to stick with Snow Leopard. I don't like having something else control what I wish to open. And the lack of keeping a folder open when opening a sub-folder would slow my work flow down incredibly. Though the work spaces option is good I admit. TextEdit's autosave feature is a PITA & ruined an xml project I was working on. Even the shortcut has changed for selecting multiple random individual files (2 keys instead of one for what should be such a simple task.) If OSX Yosemite doesn't rectify these & some other issues then I'll wait yet a few extra years before upgrading my MP. I get the impression Apple has employed lots of Windows users in its design teams, an OS I hate. lol :p

Thanks again for all the replies.

No problem with FrostWire 5.7.5. It connects turbo-charged in one second.

It is clear to me that this is something LimeWire-related and as said, I am experiencing this problem since many months or even years ago, when I updated its version at some point. And since WireShare is LimeWire-based, the issue remains. But I wonder what is it.

No problem with my ISP. It has no restrictions at all for sure. My email for gnutella forums is not related to my ISP. I think the problem there is related with hotmail.com blocking somehow emails from gnutella. I have no filters to block hotmail at all.

Little Snitch is the best firewall for Mac, but initially you have to let it know the accept/reject connections, which may be a bit tedious. Once done (a few minutes during the first days after installation), it runs in the background like a charm. Little Snitch has nothing to do with my email. I am not using a blocklist with Little Snitch. I will try later on to disable Little Snitch, but I guess that is not the problem, since the iMac in which WireShare works has the same configuration and works as said.

Mavericks Gatekeeper is disabled.

So, here we are.

FrostWire 5 does not use the gnutella network, it's a torrent only program. That's why I suggested FrostWire version 4. :)

Though the fact FW5 has no problems that can be seen is a good thing.

If you wanted to try FW4: FrostWire 4 versions although I think the FW site still hosts some FW4 versions.

You might have needed to have manually added WS to the firewall(s) including Little Snitch.

(There is a command in the WS installer to auto-add WS to the OSX firewall, but perhaps something prevented this happening or else, it does not work on all systems.)

So do you mean you port forwarded your router? Whichever port that is, then use that for LPE.

You said WireShare/LPE open fine on your other Mac (iMac?), but does it connect ok? If it's fully connected it should show 5 blue bars bottom left-corner of the program.

Have you tried the connection fix options suggested here http://www.gnutellaforums.com/connec...t-connect.html such as disabling DHT, TLS & Ultrapeer mode.

I remember my LW 4 versions on this computer would only connect with TLS disabled. As soon as I did LW would usually quickly connect as an ultrapeer. Obviously an issue related to my particular system.

(Thanks Birdy for the suggestions.)

As far as a particular program not working on a particular system, that happened to me a few years ago. Neither LW 4.18 or the early LW 5 versions would open on my main OSX. I could only run them on an different startup drive on same computer. I was not the only person who had this issue according to LW beta forum OSX discussions at the time. Then one day I realised the problem had mysteriously vanished (a year or two later.)

Thanks for all the support. I have installed the latest FrostWire 4 (4.21.8) for Mac, yet it does not open in OS X 10.9.4.

I have turned off both the Mac firewall and Little Snitch, yet the issues remain: LimeWire does not connect and WireShare does not connect and shows the pesky window ("WireShare has encountered an internal error").

I have deleted all rules for LimeWire on both firewalls, and when opening gain LimeWire, both firewalls ask for permission. Yet, there are no rules for WireShare on either firewall and they do not ask for permission ever about WireShare. Anyway, I have added WireShare to both firewalls granting permission to no avail. The issues remain.

Yes, I port forwarded the router, using such ports for LimeWire and WireShare to no avail. The issues remain, even using Universal Plug 'n' play (recommended).

The other Mac (iMac) works OK with WireShare as said, which means turbocharged (five blue bars) in a second. Both Macs are connected to the same router. I have FTTH (200 Mbps symmetrical connection).

Disabling all Ultrapeer, DHT and TLS does not fix the issues on LimeWire or WireShare.

Amazing. I wonder what is going on preventing LimeWire and WireShare connecting on the Mac mini.

The WireShare 5.6.4.1 (Java 1.6.0_65) on the iMac (OS X 10.9.4 Mavericks) with the default installation takes one minute to connect (turbo-charged with five green first to eventually blue bars).

It is set as 32-bit mode in the
Finder - Get Info
and has the
WireShare - Preferences - Advanced - Listening Ports
as
Gnutella port: 6346
Use Universal Plug 'n' Play (Recommended) SELECTED
Manual port forward: 6346 NOT selected
BitTorrents ports: 6881 to 6889
Use Universal Plug 'n' Play (Recommented) SELECTED

On the other hand, the
Tools - Advanced Tools
shows
Port 6346
and shows five connected servers eventually.

With the same configuration, WireShare on the Mac mini never connects (shows Connecting all the time with all the five bars gray) and takes a frustrating 20 minutes to check all servers at
Tools - Advanced Tools
and shows
Port 6346
on such window with no connected servers at all.

During such 20 minutes, up to three "WireShare has encountered a problem" pesky windows show (stacked one below the other). If you close them all manually, they show again for such 20 minutes. During that period you cannot select any menu or change any configuration until you close all and every of such pesky windows, and since they show again after two or three seconds once manually closed, it is almost IMPOSSIBLE to do anything during such 20 minutes (not even quitting WireShare, until you close such pesky windows, which is not easy since they reproduce after two to three seconds). REALLY FRUSTRATING. I think that such window is shown every time that
Tools - Advanced Tools
scans a new server with no connection, since after 20 minutes such scan stops and also the pesky window do not show again if manually closed. Update: it shows again (up to three stacked windows as well), but if you close them manually they do not show for 1 minute and 30 seconds (instead of two or three seconds as described above), so is less frustrating.

It would be great if such pesky window showed ONLY ONCE in future versions of WireShare, or at least did not block selecting menus, changing configurations, etc as now happens. As said this is the most frustrating part, besides not having connection, of course.

But there is something else which is weird. Even if I set the
Manual port forward: 6346
on the Mac mini, and later on I select
Use Universal Plug 'n' Play (Recommended)
when I close such window and open again or when I quit and open again WireShare, it has changed to
Manual port forward: 46189
even though it is not selected, because the
Use Universal Plug 'n' Play (Recommended)
is selected as said. So, it changes automatically from 6346 to 46189. I do not know if that gives some clue of what is going on, or if it is relevant at all, but that does not happen on the iMac where ShareWire works. Doing more testing it changed from 6346 to 50672 on both
Gnutella port
and
Manual port forward
even though the
Use Universal Plug 'n' Play (Recommended)
was selected. But remained as 6346 on
Tools - Advanced Tools
Just in case such information is useful.

As always, any idea will be most appreciated.

I only use Mavericks for testing. On my Mavericks, FrostWire 4.21.8 & 5 won't open. From memory of couple months ago, FW5 crashes on startup. FW4.21 vanishes when trying to open. FW 4.20.9 opens fine however & connected quickly after I used the latest connection installer, turbo-charged after a minute. FW was stubborn to close however.
(I'll need to fix the launch option in the FW connection installer as this launched WS instead. I guess I'll revert to the previous technique i used from 2 years ago. Can't remember why I changed it, but seems to fix the issue. Multiple copies of FW on system was probably the reason. Mavericks won't let you move apps outside the app folder once it's actually there. Edit: created a script that only opens FW4, but can take notable amount of time to find right version if multiple internal HD's like mine; over 10 seconds. It refuses to open FW5.)

WS opens & connects quickly & is using Java 6. Both java 6 & 7 are installed on my Mavericks.

WireShare is listed as Java in the firewall. So check to see if your firewall(s) have java listed. I forgot about this aspect. Console also lists WS as java. (BTW Console will also list Phex as java.)

It might be an idea to reinstall Apple's Java 6 (1.6). Your original java installation might be corrupted. I know it's a large installation file but this is at least something you can try. A quick download link to Apple's OSX java 6 here.

I'm not sure why you are getting multiple error windows. I have seen this before but only after either LPE/WS ran out of memory overnight after a several day session. Normally you should only get a single error window popup, at least initially.

I think there was something else I was going to say but my computer crashed as I was replying to your posts (after a 2 week run & as I was launching Mountain Lion.)

We've at least ascertained the problem is only your MM computer. So something with the system is not liking java applications &/or not allowing them to connect.

Here's a couple things you can try:

1. Go to your Applications folder, find WireShare. Control-click the program & choose Show Package Contents. Open Contents. Open the Info.plist file using TextEdit or similar program to be sure it is only saved as basic text only. About 3/4 way down find the line:
Change the <string>1.6+</string> line to:

by simply changing the number 6 to a 7. Save the document. This will force WS to use Java 7 or later.

2. Keep the Contents folder of WS open. Open the Resources folder. Open Java folder, then lib folder. If you find a file called bootstrap in this lib folder, delete it. This file is normally deleted after the first run. But since your WS is not opening properly, it may still exist.

Thanks to BigJx for the 1st how-to & last suggestion.

Thanks for the replies.

You can move a stubborn item on Mac clicking the Command (Apple) key before dragging the item. Then the item is moved instead of creating an alias of it.

WireShare is listed as java.org.limewire.ui.swing.Main in Little Snitch. In the Apple firewire only Java is shown. Both have permission.

I have done the things that you say on your second message above. Indeed, I had the bootstrap file that you indicate. After doing what you say, WireShare shows
WireShare 5.6.4.1
Java 1.7.0_67

And now the bootstrap file is also in:
/Applications/WireShare.app/Contents/Resources/Java/lib
Should I delete it?

On the other hand, the WireShare installer prompts to select
Light Security - Strong Security - No Security
Standard - Full Japanese Block
I previously selected Strong Security with Japanese Full Japanese Block. Now I have selected No Security.
Which is best (pros and cons)?

Anyway, the issues remain. I have tried with both 32-bit (default) and 64-bit modes. In fact, the pesky window was then much more aggressive, and it was almost impossible to get rid of it. I you closed it, it showed again several times per second. Amazing. That was initially; later on it took three or four seconds to show after closing such window.

After re-installing Java and also WireShare, the issues remain. Tested for both 32- and 64-bit modes. Now WireShare shows
WireShare 5.6.4.1
Java 1.6.0_65

As said, FrostWire connects (turbo-charged) in one second and shows:
FrostWire 5.7.5 (build 1)
Java 1.8.0-internal

I wonder if such new Java 1.8-internal could be also implemented in WireShare. Maybe that could fix the issue.

Finally, Console says nothing about these issues, but when I quit WireShare, Console says:
24/08/14 14:02:22,210 gkbisd[199]: Unable to collect cdhash for /Applications/WireShare.app (error code 100024)

Yes, delete the bootstrap file. First we want the program to be able to open properly without errors. There's a small chance that file is causing an issue.

At this point it doesn't matter about the security. The security is a hostiles file to block out BOT's etc.

I don't know why FrostWire 5 decided to keep the connection icon bottom left corner of the window, since it does not connect to the gnutella network. It gives a false impression.

The hash data I presume will be related to OSX's stricter control over user tampering with apps. Irrelevant for WS presently IMHO.

So WS is still not opening properly even when it's set to use Java 7?

This might not make any difference, but there's a WS app here which is only the application itself. Simply download & copy to application folder & try to run it. See if you get same error on first run. This version was compiled on OSX ML.

I presume WireShare 5.6.4 was your first WS version to try?

Thanks for the Mavericks keyboard tip. :)

Thanks. I have deleted the bootstrap file to no avail. The issues remain both at 32- and 64-bit modes.

Yes, WireShare 5.6.4.1 is not opening properly in any case so far: the pesky window shows all the time and reproduces itself when manually closed (WireShare has encountered an internal error), and WireShare never connects.

I get the same issues with the WireShare copy that you indicate on your message (link), again, both at 32- and 64-bit modes. And both with and without the bootstrap file (which I also found inside that copy of your link after the application had been open and closed several times).

Curiously, the bootstrap file is not present in the WireShare of the iMac (where it works and connects in one minute as said before). So, maybe the issues on the Mac mini have something to do with the presence of the bootstrap file even after opening and quitting the application several times. Although, as said, the issues remain after manually removing the bootstrap file.

WireShare 5.6.4.1 is the only version that I have tested so far. Previously I used different versions of LimeWire:

LimeWire Pro 4.12.11 to LimeWire Pro 4.18.8
Limewire Pro 5.1.2 to LimeWire Pro 5.5.16
LimeWire Pirated Edition 5.6.2

That is on the Mac mini. On the iMac (where WireShare works) I have LimeWire Pro 4.0.8 which is very old.

And as said before, at some point (months or years ago) LimeWire stopped connecting. I think that the problem arose then for some reason and has been maintained until today with both LimeWire and WireShare (in the latter case, with the pesky error screen as well).

So, I am stuck with WireShare on the Mac mini. Really weird.

I'm curious to know if you can possibly connect with any gnutella program. Possibly try GTK-Gnutella? Gtk-Gnutella - Browse Files at SourceForge.net

As for WS, perhaps you could try the earliest WS version: WireShare - Browse Files at SourceForge.net
which should not be dramatically different from LPE except in the way it's installed.

I use applescript installer without a post-flight script like the original LW/LPE does & which used a java based installer instead. Thus no Receipts registered by OSX for the installation. I would think this should not be an issue. But then I could be wrong when considering the way OSX is heading.

BTW I am wondering about your port forwarding. Did you enter the correct internal address of your MM computer? And not your iMac. This can be checked by checking your MM's system prefs > Network > ip address. And comparing it to your router's port forward rules & which address they are assigned to.
BTW a port forward rule can only apply to one application and only to one computer on the local network. And you cannot have two port forward rules using the same port.

Thanks. I have installed Gtk-Gnutella 1.1.0 and as far I can see, it has connected in a second or less!!! It shows activity and it shows items when I search for keywords. I did not open any port in the router. There is a connected gray cable on the left bottom, and a violet plug icon on its right and the "http://gtk-gnutella.sourceforge.net/" URL shown on the its right side. If I place the mouse pointer over the plug icon, it says: Port mapping configured though UPnP. I understand that it means that no port mapping is required in the router. Right?

I have also installed WireShare 5.6.4 as well as WireShare 5.6.3.1b, yet the same of WireShare 5.6.4.1 issues arise. I could not find older versions to install and test.

In my latest tests I used Universal Plug 'n' Play, so no port forwarding in the router is required as far as I understand. As indicated above, that is default WireShare installation and the way it is configured in the iMac where WireShare works OK.

Previously I did tests mapping the ports on the router using the private IP of the Mac mini (not the iMac). I have experience with that, since have done it also in the past with LimeWire when it worked and with the numerous testings when it stopped working, as well as after installing WireShare some time ago.

That's good news that you can actually connect to the gnutella network using your MM and using UPnP. :) If that's the case then manual port mapping should not be required. (Sometimes there's another icon to say you are connected via DHT.) I haven't updated my GTK & the Dec./January release kept crashing after several minutes.

I'm quite stumped about your issue with gnutella java programs though and why WS has errors upon startup. Not sure what to suggest to try next.

Did you try a different MM account yet? This might not make a difference but possibly worth a try. A test account can always be deleted after it's no longer needed (to save space.)
It's my guess if you had an alternative startup drive on the computer things in that startup environment would be ok. But I wouldn't ask you to do that. It was easy for me because I have 4 internal drives & I use the alternate startup drive either for testing, maintenance or for emergencies, all of which have applied.

From memory, Java caches certain information but I'm not sure it's worth mucking around with it or it could potentially cause other problems.

Does Console have any report listings for WS? Console has sections of reports, such as crash reports, etc.

One thing I can think of is to enable WS's logging. I'll need to ask Bigjx if I need to recompile to set them on by default. Then these will be fed to the OSX Console as soon as the program opens. Alternatively, WS menu bar, Tools > Advanced Tools, select Console instead of Connections. I guess Enable all & Apply. Save the report. Upload a copy here. If the error windows prevent you doing this then that idea is out.

Another idea is to open WS via Terminal. And see if any errors show in either Terminal or Console (keep both utilities open.) Two approaches: one is for Terminal to launch the WS program package. Another approach is for Terminal to launch the WS executable within the MacOS folder of the program package. This latter one I used to use in testing & terminal would report any errors. Console's reports might be similar but include some other details.
In Terminal type/paste:
Although you have given a report, there might be something else that is applying. Terminal will normally list all actions or errors as they occur. Instead of a summary type of report.

Thanks again for your help. I am also quite confident that booting from a new account will remove the issue. I will do it soon, but right now I cannot reboot the Mac because it is working on a project that takes days. I will let you know as soon as I can. Sorry about that.

Console has reports about application crashes, but WireShare did not crash. But I found a System Diagnostic Report in Console about WireShare (cannot paste it all because the forum says: The text that you have entered is too long (233223 characters). Please shorten it to 26000 characters long):

<-- See next post

And about LimeWire (cannot paste it all because the forum says: The text that you have entered is too long (233223 characters). Please shorten it to 26000 characters long):

<-- See next post

And about this Unknown.

I have run the
open -a WireShare.app
in Termina, but Console says nothing, as well as Terminal, except this in Console, but I think that it is not related:

Console has reports about application crashes, but WireShare did not crash. But I found a System Diagnostic Report in Console about WireShare (cannot paste it all because the forum says: The text that you have entered is too long (233223 characters). Please shorten it to 26000 characters long):

And about LimeWire (cannot paste it all because the forum says: The text that you have entered is too long (233223 characters). Please shorten it to 26000 characters long):

Many thanks for the reports. :)

.. CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION is signalling an issue from my understanding. But the source of the problem I can't see. When Bigjx can find time, he might be able to help find where the problem is. Apologies, Bigjx is presently very busy this month.
I get the impression one of the java libraries has an issue upon loading. Some kind of conflict. But I'm guessing. Edit: Probably more likely CFRunLoopDoSources0 is the issue. But this doesn't say much unless we look at your original report. Perhaps even a permissions issue with either the bootstrap or gnutella file.

WS 5.6.3.1 was the first OSX release version. This release should not be very different to the original OSX LPE release. Some extra VM parameters were added using the Apple recommended method, but not sure this should cause any issues. You could try removing these to see if it makes any difference.
The unknown report, no idea, but I highly doubt it's WS related.

I'd be interested to know if any other MacOSX users have had a similar issue with either crashing or error messages when WS starts up. If yes, please post your experience.

At a time I installed previous versions as you suggested, but later on I re-installed WireShare 5.6.4.1. So, any report about previous versions was just during the minutes it was installed for testing.

If you need the full reports, just let me know (the above ones are truncated because the forum web form did not allow so many characters, as indicated above).

Many thanks for your kind support!