Apologies for the non sequitur, but it would be really good of one you developers to take a look at the posts on "Could not move to library". This is not in regard to low disk space, but a new, extremely troublesome problem introduced with the latest edition of Limewire. Until two days ago, I had few problems with limewire, and was considering paying the reasonable fee. I downloaded the new version (after dismissing the nag dialogue 5000 times), and now am stuck with inoperable software. This is not cool, and a few comments from you in some of these posts might point people in the right direction.

We'll have a look at it. Thanks. Does it happen for you with every download?

I have tried this numerous times, and it always returns an error, as follows:

STARTUP ERROR
LimeWire version 2.7.13 or above
Java version 1.3.1 from Apple Computer, Inc.
Mac OS X v. 10.2.2 on ppc
Free/total memory: 1692560/2031616

java.lang.ClassNotFoundException: com.limegroup.gnutella.gui.Main
at java.net.URLClassLoader$1.run(URLClassLoader.java: 195)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.j ava:183)
at java.lang.ClassLoader.loadClass(ClassLoader.java:2 94)
at java.lang.ClassLoader.loadClass(ClassLoader.java:2 50)
at RunLime.main(Unknown Source)




FILES IN CURRENT DIRECTORY:
/Users/lewinb/.CFUserTextEncoding
LAST MODIFIED: 1031648962000
SIZE: 3

/Users/lewinb/.DS_Store
LAST MODIFIED: 1039562719000
SIZE: 12292

/Users/lewinb/.lpoptions
LAST MODIFIED: 1039153228000
SIZE: 24

/Users/lewinb/.phoenix
LAST MODIFIED: 1036777983000
SIZE: 136

/Users/lewinb/.Trash
LAST MODIFIED: 1039562719000
SIZE: 102

/Users/lewinb/3838-3H839 Economiser.pdf
LAST MODIFIED: 1038617802000
SIZE: 61964

/Users/lewinb/Applications
LAST MODIFIED: 1037729113000
SIZE: 204

/Users/lewinb/Bayerisch Rundfunk
LAST MODIFIED: 1032410974000
SIZE: 714

/Users/lewinb/Desktop
LAST MODIFIED: 1039562719000
SIZE: 748

/Users/lewinb/Desktops
LAST MODIFIED: 1039413981000
SIZE: 3026

/Users/lewinb/Documents
LAST MODIFIED: 1039424774000
SIZE: 1122

/Users/lewinb/Drive 10 v.1.1.1 Serial
LAST MODIFIED: 1034147910000
SIZE: 15

/Users/lewinb/Dues Form.pdf
LAST MODIFIED: 1033619687000
SIZE: 190448

/Users/lewinb/EtherPeek SN
LAST MODIFIED: 1035101323000
SIZE: 17

/Users/lewinb/Face-Shirt edited.jpg
LAST MODIFIED: 1037185480000
SIZE: 58717

/Users/lewinb/Face-Shirt.jpg
LAST MODIFIED: 1037183679000
SIZE: 31384

/Users/lewinb/G-Force 2.1 Installer
LAST MODIFIED: 1034325924000
SIZE: 345969

/Users/lewinb/Incomplete
LAST MODIFIED: 1039556965000
SIZE: 25500

/Users/lewinb/Jf504demoHandango Folder
LAST MODIFIED: 1038696995000
SIZE: 306

/Users/lewinb/LexiDrugs2000 Install
LAST MODIFIED: 1038189240000
SIZE: 136

/Users/lewinb/Library
LAST MODIFIED: 1039553425000
SIZE: 1122

/Users/lewinb/Movies
LAST MODIFIED: 1030948108000
SIZE: 102

/Users/lewinb/Music
LAST MODIFIED: 1038123093000
SIZE: 816

/Users/lewinb/Not Shared
LAST MODIFIED: 1039557017000
SIZE: 1326

/Users/lewinb/Pictures
LAST MODIFIED: 1033370747000
SIZE: 170

/Users/lewinb/Political pictures
LAST MODIFIED: 1035094165000
SIZE: 1088

/Users/lewinb/Public
LAST MODIFIED: 1034012541000
SIZE: 170

/Users/lewinb/Shared
LAST MODIFIED: 1039557561000
SIZE: 1394

/Users/lewinb/Sites
LAST MODIFIED: 1035445854000
SIZE: 204

/Users/lewinb/Year Round School Research
LAST MODIFIED: 1034823584000
SIZE: 374

_____

Do you need to be logged in as root or something to get this to work? It appears to be searching only my home folder, rather than the applications folder, where Limewire actually resides.

That's very strange. What version was giving you the problems you mentioned previously? Have you tried 2.8.0?

Where the heck do you get 2.8? I just downloaded this from the Limewire site two days ago. Isn't this the most current edition?! I'm not sure I follow you. I'll be glad to try 2.8, if you can tell me where to get it.

Addendum:
I just went back and tried the first post... type "java -jar " then drag limewire.jar to it, [return]

That worked perfectly, whereas RunLime.jar didn't. Got any ideas? Should it work this way?


After working for a few minutes, I went to "about Limewire" to see what version this claims to be. It never came up, and after a few moments, Limewire quit. Terminal returned this:

lewinb% java -jar /Applications/LimeWire/LimeWire.jar
kCGErrorFailure : CGTranslateCTM is obsolete; use CGContextTranslateCTM instead.
CGGStack.c:87: failed assertion `stack->count > 0'
Abort


SO, I tried it a second time, and found that as soon as I clicked anywhere on the menubar (in this case to get stats), Terminal returned:
lewinb% java -jar /Applications/LimeWire/LimeWire.jar
kCGErrorFailure : CGTranslateCTM is obsolete; use CGContextTranslateCTM instead.

BUT, Limewire has not as yet quit.

OK, now, after letting it sit here for about an hour, it's pretty much at a standstill. The spinning beachball of death is continuous, and Termal has now returned the following:

java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>
java.lang.OutOfMemoryError
<<no stack trace available>>

Very interesting -- thanks for all of the debugging information. I assume you got all of these errors with LimeWire 2.8.0 beta?

The problem appears to be related to us using an outmoded API for the About and preferences window. Apple has changed the API for this a couple of times now, so we might not be doing everything we should.

I'm also starting to become convinced that there are serious problems with LimeWire on 10.2.2 (I'm using 10.2.1 here). Did you ever use LimeWire before you had 10.2.2, and did you experience these types of problems?

Thanks again.

Adam.

I'm still on 10.2.1 running LimeWire 2.8.0 Beta

1. impossible to launch LimeWire from the application. Window Manager claims 97% of the CPU and Forced Quit takes 5 minutes to complete.

2. launching from the Termianl Window allows LimeWire to run normally, but it may or maynot be possible to run other applications simultaneously. I haven't yet found a pattern for when Window Manager goes bonkers and when it doesn't.

3. Even if eveything runs OK, all (count them ALL) downloads end with the Unable to move to Library bug.

In short, 2.8.0 is unusable on Mac OS X.

Are you running a system with multiple users? Did you get these problems with 2.7.13?

Thanks.