Set-up every time I launch

Every time I launch LimeWire 2.7, I have to go through a set-up. Is there a way for that not to happen?

I also have this problem.

Yep, me too! Here is what I submitted to Limewire bug reporting link.
So far I have heard nothing and I suspect I never will.
Maybe 2.7.4 will fix the problem ???

================================================== ==

I'm having an interesting problem with the new version 2.7.3 for the Mac.
I won't bother with system details except to tell you I'm running OS 9.1.
This bug looks more like a Limewire problem and not system related.

I was running 2.7.1 for about the last 2 weeks or so without any trouble, this started with the new install as of today 10-31-02. Maybe it's a Halloween joke ??

Anyway, every time I run Limewire, it asks me for the standard "first time" startup information. If I change anything under the options menu and then click OK, I don't get a write to the hard drive.

Further investigation shows that the props file is not being written to the System/preferences/.limewire/limewire props folder ! I saved my last props file and manually put it in that folder, Limewire won't read it at startup. It just keeps asking me for the first time startup data.

I also have the same problem.

Will these guys ever release a reasonably glitch-free app?

I had the same problem, too, until I did two things every Mac user should know to do when encountering errors:

Rebuild desktop, and
Delete Preferences

Well, good idea but didn't work.

I deleted the desktop and rebuilt it, still no props file created.

Life goes on, I wonder if anyone from Limewire actually reads this fourm.

[sphinxx]

A few of us have been discussing this on the "preferences" forum I haven't tried this yet but I do intend

to[URL=http://www.gnutellaforums.com/showthread.php?s=&postid=58946]

[Julie Z]

Check the LimeWire Beta Program thread. This has been discussed many times there. There's either a work-around or a fix coming. Not sure as I didn't have this problem. But give it a try.

Same **** here....never had that with previous versions????