|
| |||||||
| Register | FAQ | The Twelve Commandments | Members List | Calendar | Arcade | Find the Best VPN | Today's Posts | Search |
| Getting Started Using LimeWire + WireShare Tips on getting started with LimeWire or WireShare. Also a place to seek help getting started. Includes the original LimeWire Pirate Edition thread, with the most up to date LPE installer packages on the internet including File_Girl's LPE version, and WireShare the most upgraded version of them all. |
 |
| | LinkBack | Thread Tools | Display Modes |
| |
August 23rd, 2014
| ||||
| ||||
 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.  |
|
August 23rd, 2014
| ||||
| ||||
| 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: Code: <key>JVMVersion</key>
<string>1.6+</string> Code: <string>1.7+</string> 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. |
|
August 24th, 2014
| |||
| |||
| 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) Last edited by GeX; August 24th, 2014 at 05:03 AM. |
|
August 24th, 2014
| ||||
| ||||
| 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.  |
|
August 24th, 2014
| |||
| |||
| 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. Last edited by GeX; August 24th, 2014 at 03:32 PM. |
|
August 24th, 2014
| ||||
| ||||
| 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. |
|
August 24th, 2014
| |||
| |||
| 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. Last edited by GeX; August 24th, 2014 at 04:20 PM. |
|
August 24th, 2014
| ||||
| ||||
| Quote:
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: Code: open -a WireShare.app |
|
August 25th, 2014
| |||
| |||
| 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): Code: Date/Time: 2014-08-25 01:00:30 +0200
OS Version: 10.9.4 (Build 13E28)
Architecture: x86_64
Report Version: 18
Command: WireShare
Path: /Applications/WireShare.app/Contents/MacOS/JavaApplicationStub
Version: 5.6.3.1 (???)
Parent: launchd [225]
PID: 49550
Event: wakeups (microstackshots only)
Wakeups: 154 wakeups per second for 293 seconds
Duration: 293.00s
Steps: 289
Hardware model: Macmini6,2
Active cpus: 8
Fan speed: 1797 rpm
Powerstats for: JavaApplicationS [49550]
Start time: 2014-08-25 01:00:32 +0200
End time: 2014-08-25 01:05:13 +0200
Parent: launchd
Microstackshots: 35 samples (12%)
Primary state: 18 samples Non-Frontmost App, Non-Background Priority, User mode
User Activity: 0 samples Idle, 35 samples Active
Power Source: 0 samples on Battery, 35 samples on AC
18 ??? (JavaApplicationStub + 2952) [0x1b88]
18 ??? (JavaApplicationStub + 3161) [0x1c59]
18 ??? (JavaApplicationStub + 3638) [0x1e36]
18 launchJavaApplication + 39 (JavaApplicationLauncher) [0x699f]
18 launchJavaApplicationWithJVMInfo + 1401 (JavaApplicationLauncher) [0xa095]
18 startupJava(LauncherArgsStruct*) + 304 (JavaApplicationLauncher) [0x7268]
18 CFRunLoopRunInMode + 123 (CoreFoundation) [0x9574284b]
18 CFRunLoopRunSpecific + 394 (CoreFoundation) [0x957429ea]
18 __CFRunLoopRun + 1022 (CoreFoundation) [0x9574305e]
18 __CFRunLoopDoSources0 + 235 (CoreFoundation) [0x9574395b]
18 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 15 (CoreFoundation) [0x95752b5f]
18 __NSThreadPerformPerform + 318 (Foundation) [0x9ac6f4b2]
18 -[NSObject performSelector:withObject:] + 70 (libobjc.A.dylib) [0x99a4d2af]
18 -[CPerformer perform] + 259 (libawt.jnilib) [0x3c0024d9]
18 +[AWTStarter startAWT:] + 2019 (libawt.jnilib) [0x3c002d0c]
18 -[NSApplication run] + 727 (AppKit) [0x95c3215c]
18 -[NSApplicationAWT nextEventMatchingMask:untilDate:inMode:dequeue:] + 132 (libawt.jnilib) [0x3c0049e9]
18 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 119 (AppKit) [0x95c3f870]
18 _DPSNextEvent + 1602 (AppKit) [0x95c40349]
18 _BlockUntilNextEventMatchingListInModeWithFilter + 92 (HIToolbox) [0x92dae6bd]
18 ReceiveNextEventCommon + 526 (HIToolbox) [0x92dae8e2]
18 RunCurrentEventLoopInMode + 259 (HIToolbox) [0x92daeb5d]
18 CFRunLoopRunInMode + 123 (CoreFoundation) [0x9574284b]
18 CFRunLoopRunSpecific + 394 (CoreFoundation) [0x957429ea]
15 __CFRunLoopRun + 1779 (CoreFoundation) [0x95743353]
15 __CFRunLoopDoTimers + 349 (CoreFoundation) [0x9580606d]
13 __CFRunLoopDoTimer + 1395 (CoreFoundation) [0x9578b863]
13 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 22 (CoreFoundation) [0x9578bea6]
13 __NSFireDelayedPerform + 422 (Foundation) [0x9ac7027c]
13 -[CWindow runModalLoop] + 266 (libawt.jnilib) [0x3c05e75e]
13 -[NSApplication runModalForWindow:] + 235 (AppKit) [0x95fbc556]
13 -[NSApplication _doModalLoop:peek:] + 209 (AppKit) [0x95fbdb8d]
13 -[NSApplication _realDoModalLoop:peek:] + 828 (AppKit) [0x95fbdedc]
13 -[NSApplicationAWT nextEventMatchingMask:untilDate:inMode:dequeue:] + 132 (libawt.jnilib) [0x3c0049e9]
13 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 119 (AppKit) [0x95c3f870]
13 _DPSNextEvent + 1602 (AppKit) [0x95c40349]
13 _BlockUntilNextEventMatchingListInModeWithFilter + 92 (HIToolbox) [0x92dae6bd]
13 ReceiveNextEventCommon + 526 (HIToolbox) [0x92dae8e2]
13 RunCurrentEventLoopInMode + 259 (HIToolbox) [0x92daeb5d]
13 CFRunLoopRunInMode + 123 (CoreFoundation) [0x9574284b]
13 CFRunLoopRunSpecific + 394 (CoreFoundation) [0x957429ea]
13 __CFRunLoopRun + 1779 (CoreFoundation) [0x95743353]
13 __CFRunLoopDoTimers + 349 (CoreFoundation) [0x9580606d]
13 __CFRunLoopDoTimer + 1395 (CoreFoundation) [0x9578b863]
13 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 22 (CoreFoundation) [0x9578bea6]
13 __NSFireDelayedPerform + 422 (Foundation) [0x9ac7027c]
13 -[CWindow runModalLoop] + 266 (libawt.jnilib) [0x3c05e75e]
13 -[NSApplication runModalForWindow:] + 235 (AppKit) [0x95fbc556] Code: Date/Time: 2014-08-24 18:11:08 +0200
OS Version: 10.9.4 (Build 13E28)
Architecture: x86_64
Report Version: 18
Command: org.limewire.ui.swing.Main
Path: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin/java
Version: ??? (???)
Parent: launchd [225]
PID: 46135
Event: wakeups (microstackshots only)
Wakeups: 200 wakeups per second for 225 seconds
Duration: 225.00s
Steps: 221
Hardware model: Macmini6,2
Active cpus: 8
Fan speed: 1797 rpm
Powerstats for: java [46135]
Start time: 2014-08-24 18:11:09 +0200
End time: 2014-08-24 18:14:52 +0200
Parent: launchd
Microstackshots: 78 samples (35%)
Primary state: 44 samples Non-Frontmost App, Non-Background Priority, User mode
User Activity: 0 samples Idle, 78 samples Active
Power Source: 0 samples on Battery, 78 samples on AC
61 thread_start + 34 (libsystem_pthread.dylib) [0x90582cf2]
61 _pthread_start + 130 (libsystem_pthread.dylib) [0x9057d485]
61 _pthread_body + 144 (libsystem_pthread.dylib) [0x9057d5fb]
60 ??? (libclient.dylib + 83308) [0x21456c]
60 ??? (libclient.dylib + 766115) [0x2bb0a3]
60 ??? (libclient.dylib + 766573) [0x2bb26d]
58 ??? (libclient.dylib + 767008) [0x2bb420]
58 ??? (libclient.dylib + 767137) [0x2bb4a1]
58 ??? (libclient.dylib + 767513) [0x2bb619]
58 ??? (libclient.dylib + 714485) [0x2ae6f5]
58 ??? (libclient.dylib + 715139) [0x2ae983]
58 ??? [0x3801374]
52 ??? [0x3803e31]
51 ??? [0x3803e31]
46 ??? [0x3803e31]
46 ??? [0x3803e31]
43 ??? [0x3bcc138]
43 ??? [0x3ba7845]
43 Java_java_security_AccessController_doPrivileged__Ljava_security_PrivilegedAction_2Ljava_security_AccessControlContext_2 + 46 (libjava.jnilib) [0x240526f]
43 JVM_DoPrivileged + 99 (libjvmlinkage.dylib) [0x4f633]
43 JVM_DoPrivileged + 1277 (libclient.dylib) [0x2ba601]
43 ??? (libclient.dylib + 714439) [0x2ae6c7]
43 ??? (libclient.dylib + 714485) [0x2ae6f5]
43 ??? (libclient.dylib + 715139) [0x2ae983]
40 ??? [0x3bfa214]
40 ??? [0x3803e31]
40 ??? [0x3803e31]
40 ??? [0x3803e31]
40 ??? [0x3803e31]
40 ??? [0x3803e31]
39 ??? [0x3803e31]
39 ??? [0x3803e31]
39 ??? [0x3803f97]
39 ??? [0x3a4412e]
39 Java_java_security_AccessController_doPrivileged__Ljava_security_PrivilegedAction_2 + 47 (libjava.jnilib) [0x2401a02]
39 JVM_DoPrivileged + 99 (libjvmlinkage.dylib) [0x4f633]
39 JVM_DoPrivileged + 1277 (libclient.dylib) [0x2ba601]
39 ??? (libclient.dylib + 714439) [0x2ae6c7]
39 ??? (libclient.dylib + 714485) [0x2ae6f5]
39 ??? (libclient.dylib + 715139) [0x2ae983]
39 ??? [0x3801374]
39 ??? [0x380430d]
39 ??? [0x3803e31]
39 ??? [0x3bcc138]
39 ??? [0x3ba7845]
39 Java_java_security_AccessController_doPrivileged__Ljava_security_PrivilegedAction_2Ljava_security_AccessControlContext_2 + 46 (libjava.jnilib) [0x240526f]
39 JVM_DoPrivileged + 99 (libjvmlinkage.dylib) [0x4f633]
39 JVM_DoPrivileged + 1277 (libclient.dylib) [0x2ba601]
39 ??? (libclient.dylib + 714439) [0x2ae6c7]
39 ??? (libclient.dylib + 714485) [0x2ae6f5]
39 ??? (libclient.dylib + 715139) [0x2ae983]
37 ??? [0x3bfa214]
37 ??? [0x3803e31]
37 ??? [0x3803e31]
37 ??? [0x3803e31]
37 ??? [0x3803e31]
37 ??? [0x3803e31]
37 ??? [0x3803e31]
37 ??? [0x3803e31]
37 ??? [0x3803f97]
37 ??? [0x3a4412e]
37 Java_java_security_AccessController_doPrivileged__Ljava_security_PrivilegedAction_2 + 47 (libjava.jnilib) [0x2401a02]
37 JVM_DoPrivileged + 99 (libjvmlinkage.dylib) [0x4f633]
37 JVM_DoPrivileged + 1277 (libclient.dylib) [0x2ba601]
37 ??? (libclient.dylib + 714439) [0x2ae6c7]
37 ??? (libclient.dylib + 714485) [0x2ae6f5]
37 ??? (libclient.dylib + 715139) [0x2ae983]
37 ??? [0x3801374]
37 ??? [0x380430d]
37 ??? [0x3803e31]
36 ??? [0x3bcc138]
36 ??? [0x3ba7845]
36 Java_java_security_AccessController_doPrivileged__Ljava_security_PrivilegedAction_2Ljava_security_AccessControlContext_2 + 46 (libjava.jnilib) [0x240526f]
36 JVM_DoPrivileged + 99 (libjvmlinkage.dylib) [0x4f633]
36 JVM_DoPrivileged + 1277 (libclient.dylib) [0x2ba601]
36 ??? (libclient.dylib + 714439) [0x2ae6c7]
36 ??? (libclient.dylib + 714485) [0x2ae6f5]
36 ??? (libclient.dylib + 715139) [0x2ae983]
33 ??? [0x3bfa214]
33 ??? [0x3803e31]
33 ??? [0x3803e31]
33 ??? [0x3803e31]
33 ??? [0x3803e31]
33 ??? [0x3803e31]
33 ??? [0x3803e31]
33 ??? [0x3803e31]
33 ??? [0x3803f97]
33 ??? [0x3a4412e]
33 Java_java_security_AccessController_doPrivileged__Ljava_security_PrivilegedAction_2 + 47 (libjava.jnilib) [0x2401a02]
33 JVM_DoPrivileged + 99 (libjvmlinkage.dylib) [0x4f633]
33 JVM_DoPrivileged + 1277 (libclient.dylib) [0x2ba601]
33 ??? (libclient.dylib + 714439) [0x2ae6c7]
33 ??? (libclient.dylib + 714485) [0x2ae6f5]
33 ??? (libclient.dylib + 715139) [0x2ae983]
33 ??? [0x3801374]
33 ??? [0x380430d]
33 ??? [0x3803e31]
25 ??? [0x3bcc138]
25 ??? [0x3ba7845]
25 Java_java_security_AccessController_doPrivileged__Ljava_security_PrivilegedAction_2Ljava_security_AccessControlContext_2 + 46 (libjava.jnilib) [0x240526f]
25 JVM_DoPrivileged + 99 (libjvmlinkage.dylib) [0x4f633]
24 JVM_DoPrivileged + 1277 (libclient.dylib) [0x2ba601]
24 ??? (libclient.dylib + 714439) [0x2ae6c7]
24 ??? (libclient.dylib + 714485) [0x2ae6f5]
24 ??? (libclient.dylib + 715139) [0x2ae983]
12 ??? [0x3cafc9c]
12 ??? [0x3803e31]
2 ??? [0x3803e31]
1 ??? [0x382da4e]
1 ??? [0x3811ce5]
1 ??? [0x382da40]
1 ??? [0x3836043]
1 ??? [0x380aba0] Last edited by GeX; August 25th, 2014 at 10:48 AM. |
|
August 26th, 2014
| ||||
| ||||
| Quote:
|
|
| |
87Likes
Hybrid Mode
