Quote:
Originally posted by Lord of the Rings
Hey listen JayG I promised I would review your situation (whether I'd be of any help or not), but I've been a bit slow. I do appologise. You know sometimes ticking & unticking/vice versa can actually swing LW into action to what it's supposed to do. |
But in this case it didn't. Nor does rebooting, nor does anything else. The previous version of Limewire worked well (I've ised it on the Mac and PC since it came out)
<<I noticed you have a G3 processor but at 500 mHz. Apple never released G3's at that speed but did offer upgrades>>
They did offer one at 450, and anyone with a pair of tweezers and a map of the clock block can overclock a B&W G3 motherboard by at least 50 meg (some chips support even more, but virtually all will support 50, reliably, if the machine is in an air-conditioned environment). This has never caused a problem. When the clock speed gets too high for that CPU to support the processor crashes, or fails to exicute one particular machine language instruction, which has far greater effects than what I've reported.
<<I have heard that the recent version of Java by Apple does in fact have some issues. That may/not have affected you.>>
True, and I thought that might be causing the memory leak, but the previous version of LW was a Java application, too, and should have have had the same problems. It didn't.