The original default was either 15000 or 20000 & I increased it a few times over the years. Increasing it tenfold might cause problems. Best idea would be to save the report into a text file & upload that as an attachment.

Thanks. OK, here they go as Console save as.

For WireShare:
JavaApplicationStub_2014-08-25-010524_MacOSX-G.wakeups_resource.spin

For LimeWire
org.limewire.ui.swing.Main_2014-08-24-181454_MacOSX-G.wakeups_resource.spin

As far as I understand, ".spin" is a text file. If you cannot open it, just let me know and I will upload it as ".txt".

When I tried to upload to the forum, I got:
Your file of 206.3 KB bytes exceeds the forum's limit of 200.0 KB for this filetype. So, I have compressed them both as ConsoleFiles.zip (47.3 KB)

I just downloaded the LPE 5.6.2 "Package" and installed the Windows version on a Win 7 system. It appears to install without problem, but when launched, tells me I need Java 6.0 or above. I verified my Java Enviroment and have 7.0, both 64 and 32 bit versions installed. (I use different browsers) Every time I launch, it gives the "Need Java" message and take me to the Oracle site. Even after a shut down and restart. Any suggestions?

If you prefer to use LPE, you need to install LimeStart & launch LPE via LimeStart (LimeStart is included in the package.) Installing LimeStart will replace all of the original LPE shortcuts & point to LimeStart instead. Alternatively if you install WireShare then the problem is fixed without need for LimeStart. WireShare has also fixed several other bugs in regards to Java 7. WireShare should also arguably be a little easier to connect with. WireShare (released this year) uses the same sourcecode as LPE (released 2010), bug fixes and improvements have been made & should run more smoothly than LPE.
If you decide to install WireShare, then you should probably first uninstall LPE. Though both can coexist on the system.

Thanks for the files. Console has no problem opening them. Normally I'd have thought 200 KB would be more than sufficient for a standard text file. But yours are considerably large. :D (I think the original forum default for text files was only about 20 KB.)

I have finally done the tests with a brand newly created account, as well as booting from a different disk.

When I create a new account and run WireShare 5.6.4.1, the same previously reported issues remain (pesky window indicating "WireShare has encountered an internal error" and no connection).

When I boot from a different disk (pendrive in which nothing except the Mac OS X 10.9.4 Mavericks was installed), I installed the latest Oracle Java 7 (1.7.0_67) and WireShare and all worked fine (no pesky window and turbo-charged connection in less than one minute). Both for 32- and 64-bit mode.

If then I install Java 6 (1.6.0_65) on such pendrive, the pesky window does not show, but I get no connection. For both 32- and 64-bit mode WireShare always shows Java 6.

When I uninstall Java from such pendrive and re-install Java 7, all works again.

Update: I have uninstalled Java from the Mac mini and re-installed Java 7 only, but the same issues remain (pesky window and no connection).

Amazing test results. :) So glad to hear about the success using an alternate start-up drive.

MacOSX's Java 6 can be difficult to totally uninstall. If there are any other apps or utilities that utilize it or perhaps have indirect unix links to it.

When I earlier hinted at removing Java cache /& settings files, I'm now wondering if this might actually be worthy to try. There's something on your system related to java that's obviously an issue.

And perhaps Java 7 is the go for you. But you now know how to force WS to use it.

Wow, wow, wow!!!

I finally could make ShareWire to work in the Mac mini (turbo-charged connected to five hosts)!!!

I just replaced the following items of the Mac mini using the ones of the pendrive in which WireShare worked:

/Library/Java

/System/Library/Frameworks/JavaFrameEmbedding.framework
/System/Library/Frameworks/JavaScriptCore.framework
/System/Library/Frameworks/JavaVM.framework

/System/Library/Java

And then re-installed WireShare, which is NOT set as 32-bit mode by default (File - Get Info; it did not connect if 32-bit mode was selected, which is the installation default!!!). In any case, since Java 6 is not present, it always showed Java 1.7.0_67.

On the other hand, as previously indicated, WireShare - Preferences - Advanced
is set as default:
Gnutella port - Use Universal Plug 'n' Play (Recommended)

BitTorrent ports - Use Universal Plug 'n' Play (Recommended)

I think that replacing the
/Library/Java
was the one that did the trick, because previously I had replaced the other ones to no avail. Setting it NOT to 32-bit mode could have also fixed it.

So, problem solved. Here I leave it for future reference, in case it may help someone.

Many thanks to all and specially to Lord of the Rings for all the kind support.

BTW, I have found that the files cannot be added to My Files (library or public shared) if they end in .sit, .dmg, etc., which should be a flaw or bug, since many files in Mac have such extension. Curiously, it is possible to add such very same files if they end in .sitx, .dmgx, etc.

On the other hand, with Gnutella port - Use Universal Plug 'n' Play (Recommended), sometimes WireShare connects as turbo-charged to five servers in just one minute, but other times it takes more and even much more (for instance, a whopping 26 minutes). Is there a way to improve that?

I'm glad you were able to resolve the issue you were having. :xeri_ok1ani: You may need to enable sharing "Programs" for them to be added to your library. on the My files tab in Options there is a button to Configure unsafe sharing setting.

That's excellent news the problem is fixed. :yahoo: I'm on an older mac 2008 & open in 32-bit works for myself. I have an issue when it's disabled. No doubt your newer machine handles 64-bit much better.

As BigJx pointed out, the option for sharing programs is the first option window in WS preferences window.

Attachment 6775

If you ever have a situation where you haven't used WS for a long time, perhaps a year & WS struggles to connect, then close WS & delete the gnutella file from the WireShare preferences folder. WS will access fresher information online to recreate a gnutella file next time you open WS.
LPE does not possess this ability.

It works as you both say.

I guess that by WireShare preferences you mean the following folder and its contents:
/Users/~/Library/Preferences/WireShare

Many thanks again for you kind support.

Yes. However if you wished to keep your previous settings, incomplete downloads, library & shared information then simply delete the gnutella.net file.

Thanks.

Update for the record (in case it may help someone): since jDownloader required Java 6, it installed it and now WireShare shows it is using it instead of Java 7 (even though the 32-bit mode is NOT selected in the Finder - Get Info). Amazing. It seems that there was something weird with my previous Java configuration in the Mac mini and the replacements indicated in my message above fixed it.

Additionally, the bootstrap file is no longer in:
/Applications/WireShare.app/Contents/Resources/Java/lib
which is OK.

And the Info.plist shows
<key>JVMVersion</key>
<string>1.6+</string>

On the other hand, the firewalls are open for WireShare:

Apple - System Preferences - Security & Privacy - Firewall - Firewall Options (Two Java lines ALLOW)
Little Snitch - WireShare ALLOW is java.org.limewire.ui.swing.Main

I have also opened LimeWire Pirate Edition (LPE) 5.6.2 just for curiosity (firewalls are also open for it). It always uses Java 6, but never connects in 32- or 64-bit mode. When 32-bit mode is NOT selected, it shows:
You are offline - Please check your internet connection.
and keeps Connecting for ever. If 32-bit mode is selected, then just shows Connecting for ever. In any case, the pesky window does not show. Anyway, since WireShare is in fact the LPE update, that does not worry me at all.

Thanks again for this great site!

Again WOW, WOW, WOW...

I could make LimeWire Pirate Edition (LPE) 5.6.2 to work again: set as 32-bit mode and replacing its
/Users/~/Library/Preferences/Limewire/gnutella.net
by the one of WireShare at
/Users/~/Library/Preferences/WireShare/gnutella.net

Thanks to Lord of the Rings for the tip about the gnutella.net file- Although deleting it was not enough. What worked was replacing it by the one from the working WireShare. Amazing!

It shows a blue five-bar turbo-charged connected to five hosts. Shows Java 1.6.0_65. On the other hand, as previously indicated, LimeWire - Preferences - Advanced
is set as default:
Gnutella port - Use Universal Plug 'n' Play (Recommended)

BitTorrent ports - Use Universal Plug 'n' Play (Recommended)

Of course, the Mac and Little Snitch firewall have permission for LimeWire to connect.

So now, both LimeWire and WireShare work the Mac mini with OS X 10.9.4 (Mavericks).

Just for the record, in case it may help someone.

Suggestion to the admins: perhaps the title of this thread could be changed to LimeWire Pirate Edition becomes WireShare, or something similar.

Thanks GeX, good point. I'll see how it can be best added. :)

Thanks for creating this new thread as WireShare (formerly entitled LimeWire Pirate Edition).

Update for the record, in case it may help someone:

My fixing procedure above worked as said, but created lots of items with bad permissions related to Java. I have found it today after running Apple Disk Utility and have repaired them all.

So, it is good to run Disk Utility repair permissions after the items replacement indicated in the fixing procedure above.

Your welcome. And thank you for suggesing a logical change. :)
That's not surprising. Files from a different system, different permissions. ;) I remember trying something similar 3+ years ago with replacing java files from the alternate startup drive but can't remember if it fixed the issue or not (maybe not, maybe not the same files). I simply remember one day I realised the problem seemingly vanished out of the blue when I tried to use LW5 or a LW5 based program. I'd been using LW 4.16 instead. (My favorite was 4.14 but couldn't find the installer when I bought this computer. Though found it much later.)

(Re-implementing one or more things from LW 4 is on the list of possible things to do, but no promises it will happen.)

Seems to have stopped connecting?

Not sure which OS system you are using as you didn't specify. But go to your user preferences folder, find WireShare & open that folder. Delete the gnutella(.net) file but only whilst WireShare is closed. Then open WireShare again. Be patient for it to connect.

If you are having constant problems connecting then the problem might be firewall related. Make sure WireShare has an exception in your software firewall. You might also need to give the program & its port an exception in your router depending on router brand & model.

So i opened up %localappdata% using win 7 but I don't see anything for wireshare?

Try using %AppData% instead of %localappdata% and you should see a WireShare folder.

BigJx

Lord of the Rings
 

Hi...it's so long since I asked a question that I only hope I am using the correct approach. Recently I upgraded my iMac to Yosemite 10.10.1 (with upgraded Java 1.8.0_25 which included an upgrade to Jave 1.6) and also downloaded Wireshare 5.6.4.1. I have used Limewire and the Pirate Edition previously without trouble. I have suffered the same problem when trying to open a download as GeX. Unfortunately I got lost trying to follow the solution other than it seems to have been something to do with Java. I show below the Bug details in the hope you can point me in the right direction, hopefully in simple speak!

WireShare version 5.6.4.1
Java version 1.8.0_25 from Oracle Corporation
Mac OS X v. 10.10.1 on x86_64
Free/total memory: 248477760/281018368

java.lang.RuntimeException: java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: com/apple/eawt/CocoaComponent
at org.limewire.ui.swing.player.PlayerMediatorImpl$Pl ayerInitializer$PlayerInitalizationWorker.done(Pla yerMediatorImpl.java:696)
at javax.swing.SwingWorker$5.run(SwingWorker.java:737 )
at javax.swing.SwingWorker$DoSubmitAccumulativeRunnab le.run(SwingWorker.java:832)
at sun.swing.AccumulativeRunnable.run(AccumulativeRun nable.java:112)
at javax.swing.SwingWorker$DoSubmitAccumulativeRunnab le.actionPerformed(SwingWorker.java:842)
at javax.swing.Timer.fireActionPerformed(Timer.java:3 13)
at javax.swing.Timer$DoPostEvent.run(Timer.java:245)
at java.awt.event.InvocationEvent.dispatch(Invocation Event.java:311)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.j ava:744)
at java.awt.EventQueue.access$400(EventQueue.java:97)
at java.awt.EventQueue$3.run(EventQueue.java:697)
at java.awt.EventQueue$3.run(EventQueue.java:691)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$1.doIntersectionPri vilege(ProtectionDomain.java:75)
at java.awt.EventQueue.dispatchEvent(EventQueue.java: 714)
at java.awt.EventDispatchThread.pumpOneEventForFilter s(EventDispatchThread.java:201)
at java.awt.EventDispatchThread.pumpEventsForFilter(E ventDispatchThread.java:116)
at java.awt.EventDispatchThread.pumpEventsForHierarch y(EventDispatchThread.java:105)
at java.awt.EventDispatchThread.pumpEvents(EventDispa tchThread.java:101)
at java.awt.EventDispatchThread.pumpEvents(EventDispa tchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThre ad.java:82)
Caused by: java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: com/apple/eawt/CocoaComponent
at java.util.concurrent.FutureTask.report(FutureTask. java:122)
at java.util.concurrent.FutureTask.get(FutureTask.jav a:192)
at javax.swing.SwingWorker.get(SwingWorker.java:602)
at org.limewire.ui.swing.player.PlayerMediatorImpl$Pl ayerInitializer$PlayerInitalizationWorker.done(Pla yerMediatorImpl.java:692)
... 20 more
Caused by: java.lang.NoClassDefFoundError: com/apple/eawt/CocoaComponent
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java :760)
at java.security.SecureClassLoader.defineClass(Secure ClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader .java:455)
at java.net.URLClassLoader.access$100(URLClassLoader. java:73)
at java.net.URLClassLoader$1.run(URLClassLoader.java: 367)
at java.net.URLClassLoader$1.run(URLClassLoader.java: 361)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.j ava:360)
at java.lang.ClassLoader.loadClass(ClassLoader.java:4 24)
at sun.misc.Launcher$AppClassLoader.loadClass(Launche r.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:3 57)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:260)
at org.limewire.ui.swing.player.MediaPlayerFactoryImp l.createMediaPlayer(MediaPlayerFactoryImpl.java:71 )
at org.limewire.ui.swing.player.PlayerMediatorImpl$Pl ayerInitializer$PlayerInitalizationWorker.doInBack ground(PlayerMediatorImpl.java:659)
at org.limewire.ui.swing.player.PlayerMediatorImpl$Pl ayerInitializer$PlayerInitalizationWorker.doInBack ground(PlayerMediatorImpl.java:624)
at javax.swing.SwingWorker$1.call(SwingWorker.java:29 5)
at java.util.concurrent.FutureTask.run(FutureTask.jav a:266)
at javax.swing.SwingWorker.run(SwingWorker.java:334)
at java.util.concurrent.ThreadPoolExecutor.runWorker( ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.ClassNotFoundException: com.apple.eawt.CocoaComponent
at java.net.URLClassLoader$1.run(URLClassLoader.java: 372)
at java.net.URLClassLoader$1.run(URLClassLoader.java: 361)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.j ava:360)
at java.lang.ClassLoader.loadClass(ClassLoader.java:4 24)
at sun.misc.Launcher$AppClassLoader.loadClass(Launche r.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:3 57)
... 23 more


Detail: Uncaught thread error: AWT-EventQueue-0

-- listing session information --
Current thread: AWT-EventQueue-0
Active Threads: 21
Uptime: 51:58
Is Connected: true
Number of Ultrapeer -> Ultrapeer Connections: 0
Number of Ultrapeer -> Leaf Connections: 0
Number of Leaf -> Ultrapeer Connections: 4
Number of Old Connections: 0
Acting as Ultrapeer: false
Acting as Shielded Leaf: true
Number of Active Uploads: 0
Number of Queued Uploads: 0
Number of Active Managed Downloads: 0
Number of Active HTTP Downloaders: 0
Number of Waiting Downloads: 0
Received incoming this session: false
Number of Managed Files: 1
Number of Mounted Friend Files: 0
Number of Shared Files: 0
Guess Capable: false
Received Solicited UDP: true
Port Stable: true
FWT Capable: true
Last Reported Port: 38685
External Port: 38685
IP Pongs Received: 31
Number of Content Response URNs:
Number of CreationTimeCache URNs: 0
VF Byte Cache Size: 0
VF Verify Cache Size: 0
VF Queue Size: 0
ByteBuffer Cache Size: 2077
Number of Waiting Sockets: 0
Number of Pending Timeouts: 5
Peak Number of Thread: 36
Number of SP2 Workarounds: 0
System Load Avg: 1.21630859375
Objects Pending GC: 0
Free Space In Settings: 472982794240
Free Space In Incomplete: 472982794240
Free Space In Downloads: 472982794240
Heap Memory Usage: init = 134217728(131072K) used = 32540608(31777K) committed = 281018368(274432K) max = 477626368(466432K)
Non-Heap Memory Usage: init = 2555904(2496K) used = 100854840(98491K) committed = 102457344(100056K) max = -1(-1K)
SlotManager dump:: active:0:0 1:0 2:0 queued:0:0 1:0 2:0 resumable:0:0 1:0 2:0 bw now:0.0 session avg:0.0
Number of select calls: 6781
Number of immediate selects: 183
Average time in select: 459165218


In hope...many thanks...Rollobrowne

Try reinstalling Apple's Java 1.6 & see if you have the same problem.
There's some links for the older Java 6 you can find if you go to the LPE thread http://www.gnutellaforums.com/gettin...e-edition.html under the Pirate Edition & OSX section. I posted 3rd party links also because Apple has a habit of changing the download URL's.
BTW what is GeX? :o

GeX is the person you had a long and detailed discussion with re the same problem as mine ...pages 6, 7 and prior!

I'll try your suggestion. thank you,

Rollobrowne

Did you try this?
WireShare is set to run in 32-bit mode by default. For Yosemite you will most likely need to set it to 64-bit mode. Do that by unchecking the run in 32-bit mode option in the WireShare's information window (ie: control or right-click the WireShare program & choose Get Info) OR if it is already unchecked, then try checking the option to see if that fixes things.

Attachment 6803

I know it's me but I cannot obtain the screen shot you showed to change to 64 but mode. I have tried everything but to no avail. Am I missing something?

In Finder, select Go menu from menu bar, choose Applications. Then scroll down to WireShare. Right-click or Control-click the WireShare program and choose Get info. Else select WireShare & choose command+i or Get Info from the Finder's File menu.

Attachment 6804

If you meant you cannot open the attachment in your browser, then that will be due to a browser security setting. For example, set gnutellaforums.com as an allowed site to open new windows & links from.

Thanks for your quick response. Following your helpful instructions, I have now set Wireshare in 64 bit mode by deselecting the 32 bit mode and removed any control via my firewall for the moment until I have sorted the problem. I also downloaded Java 6 as you suggested.

Sadly nothing I have done allows the download from Wireshare to run.

You will have already guessed that I am not computer literate other than at a basic level.

I have double everything you suggested but without success.

Any other suggestions would be appreciated before I trash the lot!

It seems, by looking at the error report, the error occurred when you attempted to play a file with the internal WireShare player. If this was the case try unchecking the "Use the WireShare player when I play Audio and Video files" box in the Options.

BigJx

If you are unable to open WS at all to change such settings, then go to the WS preferences folder & find the wireshare.props file. Control-click or right-click the file or simply select it & go to the Finder menu bar -> File -> Open With ... and choose TextEdit. Then use Command F to use the search function. Type the word player into TextEdit's search box. You will find a line that says PLAYER_ENABLED=true
Change this to PLAYER_ENABLED=false.
Save the document.

Then try to open WireShare again (WS is an abbreviation for WireShare).

The WireShare preferences folder is found here:
OSX -> Users -> Your Account name -> Library -> Preferences -> WireShare -> wireshare.props

The LimeWire equivalent instructions are here LW preferences folder location but instead do not delete the folder. :)

Any update on your trials?
If you need any more guidance let us know. :)


I am aware of an anomaly with WireShare's launch function on MacOSX. (I don't have the in-built player enabled.) Often when I try to launch a video or image from the upload window I get an error message saying the system does not have a program that can open that type of file.
Yet I've also noticed if I have Mac's Preview program already open it seems to launch the file without issue.
Also noticed that after a video file launch error (VLC has been launched) and if I launch the video from the computer I get the same error message unless I quit the player (VLC) first. I never saw this issue with LPE. It might be a permissions based issue. If that's the case then it's probably due to the OSX installer design or lack of considering registering things to the system.

Attachment 6805 <- Image launch error. . . Attachment 6806 <- Video mp4 format launch error.

Attachment 6807 <- Video mpeg 2 format launch error.
This last snapshot was taken 6 months ago. Not sure this issue is caused by same problem. Different error message you will notice.

Hi LOTR and BigJx

My apologies for not replying sooner but I wanted to be sure that what I had done was reliable. In the end I went to WS - Preferences - My files - and unchecked the box that said 'Use the Wireshare player when I play Audio and Video files', just as BigJx suggested. It was the reference to 'Options' that threw me. I think LOTR said the same but I can only follow simple instructions.

Many thanks to both of you for your help and patience.

Regards

Rollo Browne

PS I still cannot find wireshare.props but that's just my incompetence!

okay so how do we use this thing and does it come with its own karoake player

A good start would be to check some of the main topics here Getting Started Using LimeWire + WireShare which also applies to WireShare. :)

WireShare has its own media player which can play audio and video files but no guarantee it will play all karaoke file types.

As for searching karaoke files, this might be of help: http://www.gnutellaforums.com/343982-post12.html however I believe there are also some newer karaoke file formats these days.
(WireShare has an overall updated file extension list for some of the newer audio & video file formats compared to LimeWire.)
I don't think I had much luck with searching .kar files many years ago but might be a worthy search now.

Wireshare doesn't work for me; it keeps saying it's connecting but never actually connects.

WireShare does not launch under Linux Mint 17.2 Cinnamon ?

Once the deb package installed (WireShareLinux-v5.6.4.3.deb), after I click the "Internet > WireShare" icon nothing appears.
From the terminal, if I type "wireshare" I get "/bin/bash: ./runWireShare.sh: Permission not allowed"

How to run WireShare please ? (I am a newbie on Linux).

In Ubuntu you cannot run a lot of sh scripts unless they have been given permission to do so. Find the runWireShare.sh file and get the file Properties, Permissions & see if there is an option to run as script or similar such as Allow executing file as a program.
That might fix the issue.

Someone else like BigJx will probably give you a better and easier answer.

I have noticed that some WireShare/5.6.4.3 do the same request to GWC multiple times (even more than 10) and every request is distant about 2/5 seconds.
It should wait a lot more otherwise it can cause problems if a large amount of client start doing this.

Also the query has a double "&", it doesn't cause any problem but it is strange: ?get=1&net=gnutella&&client=WSHR&version=5.6.4.3

Note on Start Up
 

Thought I might mention to new WireShare users who transfer to ITunes. When using most LimeWire versions I was usually able to transfer to ITunes regardless of what program you started up first. I've found that with WireShare you must open Wireshare first, or it will only transfer songs to your hard drive only.

So there's an issue with wireshare that started showing up for me recently where advanced tools refuses to open giving an error :
error log - Pastebin.com

Preview showed BB spoiler tags not working so dumped the error into pastebin.

WSHR/LW5’s upload logic is very buggy
 

WSHR/LW5’s upload logic is bugged. Since early in year I’ve been using fibre instead of ADSL.

(i) If I increase upload slots beyond 5, the upload speeds become chaotic. So chaotic that downloaders often drop off. By chaotic I mean the speeds rapidly fluctuate between zero to high speeds every second or two. This appears triggered when there actually are more than 5 uploads. So this is definitely a bug & not anything to do with my bandwidth capabilities after all.

Attachment 6925
5 snapshots over 19 seconds. Not ideal to show how chaotic it actually is. Each up-speed change occurs at a rate of 0.5 to 2 secs. Also this example does not show uploads dropping off. When that happens it’s the ones at zero up-speed. Ideally I should have screen video-recorded this over 3 to 5 seconds. This occasion had up slots set to 7. Generally the up-speed bandwidth changes are much more dramatic, such as from 0 to 120 to 30 to 0, etc. within just a couple of seconds. I had only just started WSHR on this occasion after a router reboot.

(ii) Another side effect of the upload logic bug(s) is if there is a greedy host. That then causes upload bandwidth to vanish into overhead. ie: The total upload bandwidth will show maximum allocated but what the downloaders are able to utilise is a fraction of that. It hampers the speeds available to the downloaders, slowing them down. This generally lasts between 45 to 90 minutes before slowly going back to normal.

Attachment 6923 (-from 2015-) Attachment 6924

Attachment 6921 (-from 2017-) Attachment 6922

The same issue reported July 29th, 2011 here http://www.gnutellaforums.com/gettin...tml#post364493 post titled: 'The Down-sides of LimeWire 5 / LPE - the super-bugs !' from paragraph starting with “The total of upload bandwidth at times either leaks or giving incorrect figures. …” onward. It also seems to affect the queuing process, ie: queued downloads that should have timed into starting to download are left in the queue for longer periods. (Ignore dates on the images, due to a forum crash & backup corruption needed to be re-uploaded in 2014. Original upload bug images dated 12 Dec 2011 & 6 April 2012.)

(iii) If you recall, the other upload bug I was able to overcome when I increased both the individual & overall queueing totals. That upload bug was generally initiated by a greedy host. Then other hosts whom only wanted to download a single file would either have their download stopped or refused & be auto-banned for an hour or longer (this happened to hosts of all modern clients.) ie: the program's auto-banning of a greedy host would spill across & affect one or more other download hosts.
This change most likely also fixed the 'Invalid Request' bug. Something I have very rarely seen since.

I don’t know which is worse, WSHR’s upload bugs or Phex’s 2+ slot bug. If set Phex to more than 1 slot it becomes unlimited. I certainly don’t want 50+ uploads at once. Start of this decade I told Phex dev about this but he seemed disinterested in fixing it. From memory LW4’s upload controls worked flawlessly & gave the sharer much more control over their uploads. (I used LW4 for 7 years after skipping LW3) Whilst I said flawlessly, there could always be the issue of a host stealing most of the bandwidth but that can happen with LW5/WSHR (there are a number of reasons this might happen, not just more hops or bad hops relaying to a specific host.)

Uploads greater than Downloads
 

Apologies if I'm in the incorrect area. I have been reading threads, but unable to find a solution at this current time.
New to Wireshare, and to this Forum.
Using WS 5.6.6, Win 10. Uploads over 1000KB/s, Downloads under 100KB/s
I am sharing over 400 files.
Set Strong security Full J/B
Suggestions?
Also, do users actually chat in WS? If so, please suggest best way to connect.
Many thanks, and Happy Holidays!

Hi ReadyPlayerONE. Not totally sure what your question is. :D I personally don't believe Strong security is necessary, Light is fine and not blocking out Japanese hosts. Reason is WireShare already has built-in support to block out the spam-BOTs and a percentage of the Strong security is arguably out-dated. The Light security already blocks out the remainder hostiles. I had requested big-jx to remove the Japanese blocks two to three years ago as I don't believe it is needed and simply reduces the speed of connecting and retaining persistent connections. Just my personal opinion. I am the person who processes the security updates.

In regards to best connection practices:
1. try to ensure your WireShare is not firewalled. This is probably 'the' most important thing. Being firewalled greatly slows connecting. It also means your WireShare cannot join the DHT for both speedy connecting and making use of the DHT extra search abilities. DHT connections are generally super fast. Also some ultrapeer programs will only allow a percentage of connections to firewalled hosts thus meaning a firewalled host will be competing with other firewalled hosts for a connection slot. To check if your WireShare is firewalled or not, go the the WireShare menu bar and choose Tools > Advanced Tools, then top-left of the window that opens will display what your firewall status is.

2. try to extend your connection periods for as long as possible. If your WireShare is not firewalled and has a high average uptime then your WireShare will inevitably become an ultrapeer and hosts will give preference to connecting to ultrapeers with the greatest average uptime since it suggests there's a greater chance your WireShare will be available when they attempt to connect.

The private chat, referred to as Friends in WireShare works but only if you are not firewalled. You need to know the contact details of someone else on the network to be able to utilize it. Private sharing means you can share directly with persons you know and also chat with them in real-time as in text-chat.

After re-reading your post I realise your question appears to be more about the chat feature? (sorry I'm half-asleep)

As I mentioned above, I'm not sure it is possible to successfully use Friends if either party is firewalled. If it is possible then it might be a little problematic.

I haven't used WireShare chat for over 4 years. The difficult part is the setting up with a friend. There are 3 types of communication protocols. GMail, Jabber and Live Journal. This can be set up in Settings > Miscellaneous. Set both your preferred communication type and enable Sign into Friends when WireShare starts. After doing this you will be prompted for your gmail, jabber, or live journal ID and password. However you can sign in manually each session via the menu bar > Friends > Sign in.

These days with GMail it is more difficult to log-in via WireShare due to GMail/Google's stricter security policies.
"Google prevented someone from signing in to your account using a non-Google app." If you receive such an email after failing to log-in with WireShare then choose the ‘Yes, it was me’ option. Also https://myaccount.google.com/lesssecureapps setting should be enabled to ON. That will prevent such blocking of logging-in in the first place.

If you know a fellow WireShare user's gmail, jabber or live journal address then you can send them an invite to become a friend via WireShare. Once logged-in you will see more options in the WireShare menu bar > Friends menu. You can use the Add Friend option. You can also set the Available or Do not Disturb options.

For chat, you will have a chat option and chat window within WireShare (on the right-hand side.) For gmail this conversation is duplicated within gmail so you can communicate either way.

Setting up private shares: Choose the My Files tab top-left of WireShare. There you will see a Private Sharing or Friends tab. You can create custom share lists and add whichever friends to each list.

An issue we noticed mid-decade was the updating of the private shares in real-time. Adding fresh private shares sometimes does not update for the other person immediately. Re-browsing/refreshing host sometimes fixes this. We consider this a bug.

You will notice for WireShare the chat option is limited to Friends. Unlike LimeWire v.4 which allowed you to chat with any other public hosts on the network that also enabled chat. Not many LW 4 hosts around any more.

Many thanks for your response.
I have reset security, and will stay on as long as possible. However, I do not know how to remove firewall for WS. I will look through the amazing world of google to help me find the solution...that is of course unless you might know how.
Get some sleep LOL.

Generally two types of potential causes for the firewall issue. Software and hardware. Software referring to your system's firewall. Check your advanced settings of system (Windows) security (firewall) to see whether WireShare is on the exception list. If not you can manually add WireShare to the exception list.
There are other possible software causes be it a second firewall or other security software that might be having a similar effect.

Hardware referring to your modem-router. If this is the cause then this can be solved by either enabling UPnP within your router or if it is enabled, instead choosing Port Forward the port that WireShare is using. Some brands/models of router have UPnP disabled by default, and some use a version of UPnP that does not work well.
There is also a chance your computer system's UPnP is disabled. https://www.computerhope.com/issues/ch001367.htm which you can check first or second.

How to log-in to your router's control centre? If you don't know you can either check the manual that came with your router or find your brand and model here https://portforward.com/router.htm

First thing to check is if UPnP is enabled. If it is (which means it is not working properly) then the best answer is to port forward your router which means making an exception in the router's firewalling for WireShare and the port it uses. This port only remains open whilst WireShare is running. Port forwarding is generally more reliable than UPnP, especially for extremely long sessions where UPnP might start to fail.

If you do port forward, you need to mirror the settings within WireShare and change WireShare's setting from UPnP to Port Forward using the same port number as the one you enter in your router's control centre port forward rule. You should set up a port forward rule for BOTH TCP and UDP. Traditionally it was more reliable to do a separate rule for each but not always necessary. You would also need to setup an internal static ip address on your local network. Example if your router's address is 192.168.2.1 then you would set your internal address to 192.168.2.2 or 192.168.2.3, etc. Or if your router's address is 10.0.0.1 then you would change the last number to any between 10.0.0.2 to 10.0.0.255 (Router LAN address always ends with .1 and computers on the network can not use the same .1 address.) * I would suggest you choose a relatively high internal address number; example: 10.0.0.30 or 10.0.0.50 or 10.0.0.125 etc. Reason: If your computer is shutdown overnight there is a possibility another device might grab that same address before you restart your computer, thus your port forward rule would no longer work. For at least some routers, a static internal address is not reserved if that device is no longer on the network. Another device such as a mobile phone, iPad, TVs, etc. will obtain the first available address in sequential order after the router's address.
For port forwarding it is very important to set up a static ip address before you create a port forward rule, otherwise the internal address (LAN address) for the rule and your computer might not match and the rule will not work. Internal LAN addresses can change from session to session unless a static ip address has been set.

Port forwarding is sometimes referred to setting up a Virtual Server. My description of port forwarding is probably more difficult to read than the actual process itself.

There are other possible causes for firewalling but much less common. One is in regards to those who use satellite connections. This is either an internet provider cause which means you'd need to discuss the issue with them or a hardware issue. Some satellite service providers use a firewalling system by default.

These image attachments more or less walk you through how to check if WireShare is already on Windows 10's firewall exception list. If not, you can choose 'Change Settings ...' and then choose 'Allow another app ...' as shown in the 3rd image.
Firstly find your system Control Panel, choose the 'System and Security' link.

Attachment 6992

Attachment 6993

Attachment 6994