|
Register | FAQ | The Twelve Commandments | Members List | Calendar | Arcade | Find the Best VPN | Today's Posts | Search |
General Mac OSX Support For general issues regarding Mac OS X users |
| LinkBack | Thread Tools | Display Modes |
| |||
I don't have that information in .lax Hello. I'm using Limewire 3.4.5 on an iMac 233. I located the limewire.lax text document, but cannot locate the line you mentioned in order to make the suggeted modification. The text I located begins with "# LaunchAnywhere (tm) Executable Properties File - Zero G Software, Inc." Are you referring to a different version of Limewire, or am I doing something wrong? Thanks. |
| |||
Slow running I downloaded the newer version, as you suggested, and made the recommended change to the .lax file. It then took 3 minutes to open the 3.8.6 version of the program. Is that normal? I am running 0S 9.2 on a 233 iMac. Thanks. |
| |||
I'm using the new LW 4.0.3 on Mac OS 9.2.2, tell me where to look for the line to change lax.nl.macos.java.compiler=off to #lax.nl.macos.java.compiler=off, I can't find it, even with a word search. And my downloads are slow as molasses on this. This is my limewire.lax file. # LaunchAnywhere (tm) Executable Properties File - Zero G Software, Inc. # LAX.APPLICATION.NAME # -------------------- # the default name of this executable -- do not edit lax.application.name=LimeWire # LAX.CLASS.PATH # -------------- # the Java classpath necessary to run this application # Can be separated by colons (Mac OS/Unix) or semicolons (Windows) lax.class.path=MessagesBundles.jar:jl011.jar:swing .jar:xerces.jar:LimeWire.jar:logicrypto.jar:collec tions.jar:themes.jar:ProgressTabs.jar:mp3sp14.jar: icu4j.jar:i18n.jar:commons-logging.jar:commons-httpclient.jar:id3v2.jar:lax.jar # LAX.COMMAND.LINE.ARGS # --------------------- # what will be passed to the main method -- be sure to quote arguments with spaces in them lax.command.line.args=$CMD_LINE_ARGUMENTS$ # LAX.DIR # ------- # path to directory holding LaunchAnywhere's native launcher lax.dir=/Macintosh HD/Applications (Mac OS 9)/LimeWire/ # LAX.MAIN.CLASS # -------------- # the class that contains the main method for the application lax.main.class=com.limegroup.gnutella.gui.Main # LAX.MAIN.METHOD # --------------- # the method in the main class that will be invoked lax.main.method=main # LAX.NL.CURRENT.VM # ----------------- # the VM to use for the next launch lax.nl.current.vm= # LAX.NL.JAVA.LAUNCHER.MAIN.CLASS # ------------------------------- # main class of LaunchAnywhere's java launcher -- do not adjust lax.nl.java.launcher.main.class=com.zerog.lax.LAX # LAX.NL.JAVA.LAUNCHER.MAIN.METHOD # -------------------------------- # main method of LaunchAnywhere's java launcher -- do not adjust lax.nl.java.launcher.main.method=main # LAX.NL.JAVA.OPTION.ADDITIONAL # ----------------------------- # Java command-line arguments added verbatim to the command line. lax.nl.java.option.additional=-Dorg.apache.commons.logging.Log=org.apache.commons .logging.impl.NoOpLog -Djava.endorsed.dirs= lax.nl.java.option.java.heap.size.initial=20000000 lax.nl.java.option.java.heap.size.max=120000000 # LAX.NL.JAVA.OPTION.JAVA.STACK.SIZE.MAX # -------------------------------------- # Set the Java stack size to 64K lax.nl.java.option.java.stack.size.max=65536 # LAX.NL.VALID.VM.LIST # -------------------- # a string containing one or more of [ ALL JDK JRE J1 J2 JRE_J1 JDK_J1 JRE_J2 JDK_J2 MSJ MRJ ] # delimited by spaces or commas. If the native launcher cannot find the current vm, # it will search for ones in this list lax.nl.valid.vm.list=JRE_J2 JDK_J2 MRJ # LAX.NL.WIN32.MICROSOFTVM.MIN.VERSION # ------------------------------------ # The minimum version of Microsoft's VM this application will run against lax.nl.win32.microsoftvm.min.version=2750 # LAX.ROOT.INSTALL.DIR # -------------------- # path to the installdir magic folder lax.root.install.dir=/Macintosh HD/Applications (Mac OS 9)/LimeWire # LAX.STDERR.REDIRECT # ------------------- # leave blank for no input, "console" to read from the console window, # and any path to a file to read from that file lax.stderr.redirect=err.txt # LAX.STDIN.REDIRECT # ------------------ # leave blank for no input, "console" to read from the console window, # and any path to a file to read from that file lax.stdin.redirect= # LAX.STDOUT.REDIRECT # ------------------- # leave blank for no input, "console" to read from the console window, # and any path to a file to read from that file lax.stdout.redirect=out.txt # LAX.USER.DIR # ------------ # left blank, this property will cause the native launcher to not # alter the platform default behavior for setting the user dir. # To override this you may set this property to a relative or absolute path. # Relative paths are relative to the launcher. lax.user.dir=. # LAX.VERSION # ----------- # version of LaunchAnywhere that created this properties file lax.version=5.0 |
| |||
zzz Zzzzhuh?! Oh... I just downloaded the newest version of Limwire Pro, wich is 4.0.2. for the OS.x. nice touch putting in the message about freezing the classic version at 4.0 AFTER paying, especially since that annoying pop-up tells me I can get a newer version... I could swear i had 4.0.7 before, I'm not sure, but that kinda sucks. Anyways, I cant find that line of code where I'm supposed to put in the "#" to fix the JIT problem. Do I have to download an older version? I'm really pleased to have paid another 18 bucks for a useless 30 seconds laggin' limewire. Woohoo! Angry Xmas Gnome |
| |||
slow slow running I definitely agree with Rent-A-Ninja: just downloaded Limewire Pro 4.5 is running on a G4, 450 Mhz, with 640 Mb Ram... (MacOs 9.2.2) and it is so slow...! I can't find that line of code where I'm supposed to put in the "#" to fix the JIT problem in the LimeWire.lax document. Can someone help??? |
| ||||
Umm ... I think you'll find it somewhere in the thread called 'For those who can't connect' in the connections section. It's 37 pages long but I'm sure it's within the 1st 25 pages somewhere. that's the last place I can remember seeing it. Have a look from p1 anyway. You might pick up some hints! |
| |||
so so slow... (part 2) Hi, can somebody understand what's going on??? As I said in a previous post I bought LW Pro 4 (no 4.5) for Mac Os 9, and it was extremely slow. As you suggested I started reading the forum on connections - where I lost myself, but found the tip to get faster response from the software (declicking auto connect at startup). The first time it got really better, but a second time never happened again... The software got stuck up at "Connecting..." for hours... After several days, several other installations - always without success - today I tried to remove everything from my hard disk, and download again LW BASIC, and it works!!! In the meantime I found that in LW Pro: 1. the uninstaller actually leaves some files on the hard disk 2. the file err.txt says what follows, maybe it is of some interest for you: ---- 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:1759) at com.limegroup.gnutella.gui.ErrorHandler$Error.run( ErrorHandler.java:70) 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) ----- And now... good night! p |
| |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Limewire runs too slowly | hoangtien | Open Discussion topics | 1 | December 2nd, 2006 01:51 AM |
Limewire running VERY slowly | EdMan218 | General Windows Support | 11 | January 7th, 2005 02:42 AM |
Limewire suddenly loading slowly | graffiti | General Mac OSX Support | 2 | November 11th, 2002 06:14 PM |
Limewire 1.7 on Mac (OS9.1) runs incredibly slowly | Unregistered | General Mac Support | 0 | October 30th, 2001 06:16 PM |