Unable to Connect using OS 9.1
 

same on my comp... the conect option is greyed out.. and i cant seem to fix it.. i have road runner cable conection and i cant seem to get it to work no matter what i try

Hi guys

I just tried booting into OS 9.2.2 (usually on OSX, which works very well), installing a new LW Pro 4.0.2--no VM--and couldn't get it to connect. :(

I think it was because the loading of the shared files takes so long and so much processor power, and the Apple's Java for Classic is really buggy. I ran out of time to get it working, but I'll try again tomorrow and let you know.

I was able to install and connect a few weeks ago on both 9.2.2 and a Powerbook 5300 running 8.6, so it should work if I can just remember the settings required, where the java pieces need to be located, and all that other stuff.

I'll let you know how it goes, and if there's a problem with 4.0.2, sberlin the LW developer who knows Classic best might have some suggestions.

In the meantime, check out http://www.gnutellaforums.com/showth...threadid=23077 for some background, and there was a post I can't find just now about where to relocate the Shared folder that seemed to help.

Sorry I can't help more just now.

Yeah it seems there is a bug... I've tried it in classic and it didn't connected at first. I played with some settings, then restarted LW and it worked... I don't know if you have to chage some setting or simply have to restart LW however. One thing is sure, once LW is running on os 9, you can disconnect but right after you can't select the option to connect in the file-connect menu... I'll PM this thread to Sam.

/Ranting that some os 9 users won't like:
LW in os 9 is so slow, why don't LW stop developping for it with it's old java 1.1.8?? I would simply stop take pro subscriptions and in 6 months stop supporting it, but that's just me (there is now 35 000 osx dl / week compare to 7 000 for os 9 compare to 300 000LW multiplatforms total /per week - the % of os 9 users is lower 3% and there is just so many problems coming from os 9)
/End ranting

Ciao

Edit: Sam doesn't accept PMs :(

Thank you Stief for replying & taking the time to try to figure out our problem.

I went to the link you provided. Apparently the solution is for an older version of LW as I could not find the code they were talking about in v4.0.
Where did you get v4.0.2? I could not find a any info on that version. The download page confirmed v4.0 is the latest! :confused:

I used Sherlock to locate the "Shared folder which was in the Preference folder. It's empty as I am disconnected, unable to connect to be able to "share anything". :mad:

Hopefully, you and/or the LW developer will come up with a solution for us OS 9.x MAC users shortly.

Thanks again.

et voilà.......
What settings did you play around with to get it to finally connect in OS 9?

The problem is likely related to a faulty optimization performed by Mac Classic's JIT. (See the 'Why Does LimeWire Seem To Run Slowly?' thread for information on what a JIT is.) Can you check the 'err.txt' file in the folder where 'LimeWire' is located? Please paste the contents of it here? Thanks.

Sam--thanks for responding. [my err.txt is empty]

Bootylicious, you probably are running 4.0.2 (check the "About LimeWire" for the actual version).

Sberlin, thank you for following up on this.
The text of the "err.txt" file is as follows:

A nonfatal internal JIT (3.10.106(MRJ)) error 'chgTarg: Conditional' has occurred in :
'org/apache/commons/httpclient/HttpClient.executeMethod (Lorg/apache/commons/httpclient/HostConfiguration;Lorg/apache/commons/httpclient/HttpMethod;Lorg/apache/commons/httpclient/HttpState;)I': Interpreting method.
Please e-mail this message along with reproducible sample to jit-bugs-ppc@itools.symantec.com


I did follow the "Why Does LimeWire Seem To Run Slowly?" thread. However, the solution code sentence was not in the v4.0.2(which I do have) LimeWire.lax file.

this is what mine says >.<
what shoud it say?
A nonfatal internal JIT (3.10.106(MRJ)) error 'chgTarg: Conditional' has occurred in :
'org/apache/commons/httpclient/HttpClient.executeMethod (Lorg/apache/commons/httpclient/HostConfiguration;Lorg/apache/commons/httpclient/HttpMethod;Lorg/apache/commons/httpclient/HttpState;)I': Interpreting method.
Please e-mail this message along with reproducible sample to jit-bugs-ppc@itools.symantec.com

Exception occurred during event dispatching:
java.lang.ExceptionInInitializerError
at com.limegroup.gnutella.gui.GUIMediator.showDialogs ForFirstVisibility(GUIMediator.java:342)
at com.limegroup.gnutella.gui.GUIMediator.access$000( GUIMediator.java:49)
at com.limegroup.gnutella.gui.GUIMediator$1.run(GUIMe diator.java:325)
at javax.swing.SystemEventQueueUtilities.processRunna bleEvent(Compiled Code)
at javax.swing.SystemEventQueueUtilities$RunnableTarg et.processEvent(Compiled Code)
at java.awt.Component.dispatchEventImpl(Compiled Code)
at java.awt.Component.dispatchEvent(Compiled Code)
at java.awt.EventDispatchThread.run(EventDispatchThre ad.java)

We're looking into it. Hopefully there's a fix. I do suggest that you all upgrade to OSX, though.

Do you know that registration of LimeWire Pro includes the possibility to download PRO versions of installers for other systems? This means that you can get the OSX version when registering the Mac OS9 version.

The private download page you receive after the payment gives access to all versions of installers. So you can download LimeWire Pro for both OSX and OS9, or even for Windows or Linux if you also have a PC.

Sometime in a near future, we'll probably have also a Win64 version for IA64 PCs (but first Java must be certified on that new platform... which will be only stable with Java 1.5 final release). For now, only Java for Win32 is supported on Windows. I don't know if that version works correctly on 64-bit versions of Windows (through the WOW32 support layer), as there are critical compatibility issues with multithreading, native I/O or display, or with new possible return values in WOW32 (which may not support the whole Win32 API that may be needed to support Java). For us it is a bit too soon to support it, and most users of Win64 probably use it for mission-critical servers, on which Gnutella is not desirable.

I know that Philippe, but in the scenario I suggested, there would be a big warning in the pro subscription page if you intend to use LW on an OS9 system. What I mean is that some users would feel screwed and I'd be on their side. LW will have to suspend os 9 updates on day or the other, when they feel the extra work supporting the aging 1.1.8 java will not be worthing it.

À+

OK Apple has stopped since long to support for Java on Mac OS 9. Mac OS X is fully mature now, and most Mac OS 9 users that have the first PowerPC blue boxes should have no problem to upgrade, given the huge performance benefit and the decreased price of memory upgrades.
I just wonder if Apple has made a "light" version of Mac OS X which can be installed without the lots of supplementary stuffs.
What I don't understand is why Apple has not placed its port of Java on Mac OS 9 as an open-source project.
I know that porting the Java 2 platform, notably the exception handling and multithreading support is quite tricky on Mac OS 9 with its partial support for virtual memory, and its single flat memory map. However the open-sourcers could have ported a better multithreading engine on Mac OS 9, patched the 100% pure Java core classes to run in a degraded Java environment.
The main problem in Mac OS 9 is the slow virtual memory management (and absence of security caused by the flat memory model which looks more like Windows 3).
Aren't there replacement for Java 1.1.8 on Mac OS 9, for example in Apache or Mozilla hosted projects ? Is it completely impossible to support at least the Java 1.3.1 VM on Mac OS 9?

Try using LimeWire 4.0.3, just released. Mac Classic connections should be fixed.

Sberlin, I downloaded & installed the free 4.0.2 version of LW & ran into the exact same probroblem. I opened up the err.txt file & got this message:

A nonfatal internal JIT (3.10.106(MRJ)) error 'chgTarg: Conditional' has occurred in :
'org/apache/commons/httpclient/HttpClient.executeMethod (Lorg/apache/commons/httpclient/HostConfiguration;Lorg/apache/commons/httpclient/HttpMethod;Lorg/apache/commons/httpclient/HttpState;)I': Interpreting method.
Please e-mail this message along with reproducible sample to jit-bugs-ppc@itools.symantec.com

Exception occurred during event dispatching:
java.lang.ExceptionInInitializerError
at com.limegroup.gnutella.gui.GUIMediator.showDialogs ForFirstVisibility(GUIMediator.java:342)
at com.limegroup.gnutella.gui.GUIMediator.access$000( GUIMediator.java:49)
at com.limegroup.gnutella.gui.GUIMediator$1.run(GUIMe diator.java:325)
at javax.swing.SystemEventQueueUtilities.processRunna bleEvent(Compiled Code)
at javax.swing.SystemEventQueueUtilities$RunnableTarg et.processEvent(Compiled Code)
at java.awt.Component.dispatchEventImpl(Compiled Code)
at java.awt.Component.dispatchEvent(Compiled Code)
at java.awt.EventDispatchThread.run(EventDispatchThre ad.java)
Exception occurred during event dispatching:
java.lang.NoClassDefFoundError: com/limegroup/gnutella/settings/StartupSettings
at com.limegroup.gnutella.gui.TipOfTheDayMediator.con structDialog(TipOfTheDayMediator.java:392)
at com.limegroup.gnutella.gui.TipOfTheDayMediator.<in it>(TipOfTheDayMediator.java:167)
at com.limegroup.gnutella.gui.TipOfTheDayMediator.ins tance(TipOfTheDayMediator.java:177)
at com.limegroup.gnutella.gui.GUIMediator.closeStartu pDialogs(GUIMediator.java:355)
at com.limegroup.gnutella.gui.GUIMediator.showInterna lError(GUIMediator.java:1748)
at com.limegroup.gnutella.gui.Finalizer.shutdown(Comp iled Code)
at com.limegroup.gnutella.gui.GUIMediator.shutdown(GU IMediator.java:1017)
at com.limegroup.gnutella.gui.GUIMediator.close(GUIMe diator.java:1010)
at com.limegroup.gnutella.gui.MainFrame$1.windowClosi ng(MainFrame.java:196)
at java.awt.AWTEventMulticaster.windowClosing(AWTEven tMulticaster.java)
at java.awt.Window.processWindowEvent(Window.java)
at javax.swing.JFrame.processWindowEvent(JFrame.java: 182)
at java.awt.Window.processEvent(Window.java)
at java.awt.Component.dispatchEventImpl(Compiled Code)
at java.awt.Container.dispatchEventImpl(Compiled Code)
at java.awt.Window.dispatchEventImpl(Compiled Code)
at java.awt.Component.dispatchEvent(Compiled Code)
at java.awt.EventDispatchThread.run(EventDispatchThre ad.java)


Appears to be some sort of java error which is over my head as I am not a comp geek. I was going to run DiskWarrior. Now it looks like I'll just have to sit back & wait for you guys to figure out a fix for us OS 9.x users if there is one.

Purchasing one of the OS CATs (Panther or Tiger is not an option for me at this time. :mad: That is why I appreciate all the developers who still work of products for us users still using the older OS systems.:cool: :D

Hi Bootylicious -- Try using 4.0.3. The error may still appear in the err.txt file, but it should connect fine. I cannot promise that Mac Classic support is going to continue far into the future -- it is increasingly hard to develop for the current operating systems and remain compatible with Mac Classic. Many other vendors, such as Adobe (and even Apple themselves) have dropped Classic support entirely.

ok but where do u dl 4.0.3? all i get is 4.0.2 ;__;

Go to limewire.com and download the software. Download.com may have the wrong version number, but what you download _will_ be LimeWire 4.0.3.

Sberlin a special THANK YOU!!!!!!! THANK YOU!!!!!! THANK YOU!!!!!!

Version 4.0.3 did the trick! :D

Thanks for staying on top of this. After this fiasco I will NOT be doing any further updating as long as I can connect using v4.0.3.

I will be moving to the CAT system eventually. Probably by then, Apple will have run out of CATs & will then resort to the DOGS.:eek:

Thanks again.http://www.gifs.net/animate/bacio.gif

Bootylicious--glad to hear it works, but PLEASE--keep on updating. You've fine forum stlye and have gained a lot of experience with LW testing. ;) Most of us around here who try and help out the Mac users are losing our experience with the Mac OS, and so Classic problems often get delayed and inadequate responses.

Those of us who try to help the devs avoid problems like this thread sure could use your help beta testing and responding to other Classic users.

Cheers :)

btw--the fact that LW is the ONLY dev who has stuck with the Classic users has earned LW lots of loyalty points here at least.