Unable to Connect using OS 9.1

[Bootylicious]

I've tried all the ideas previously mentioned that I could use for my OS & MAC.

I am using LW Pro v4.0. I just downloaded it this AM.
I am using an iMac 266 MHZ, OS 9.1.
No Firewalls.
Comcast cable.

The "connect" is greyed out! I have rebuilt my desktop, reinstalled, trashed LW preferences & still "connect" is greyed out & I am disconnected.
However, at the bottom left of screen the tower thingies are red but says Quality: Connecting.


PS: I had problems downloading, so I had to download the NOVM installer & install w/extensions off because the installer would not work with the extensions on.

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

[stief]

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.

[et voilà]

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

[Bootylicious]

Originally posted by stief
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.

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!

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

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

Thanks again.

[Bootylicious]

Originally posted by et voilà
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

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

[sberlin]

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.

[stief]

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

[Bootylicious]

Originally posted by sberlin
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.

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/HttpStateI': 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/HttpStateI': 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)