I have placed the beta versions of LimeWire 1.6b in the LimeWire beta directory at:

http://www.limewire.com/beta/1.6b/

You will find installers for the various operating systems there. The OSX installer is not there yet, but will be by tomorrow.

The changes in this version are relatively minor. The most significant change was a bug fix on the Mac where LimeWire would crash if users tried to share a top-level directory. There was also a bug that would occasionally arise on various platforms with accessing some configuration files on startup.

It would be a tremendous help if anyone who has a spare moment could give the new installers a try and report any problems back on the forum.

Many thanks to all.

-LimeWire Team

1.6b wont let me exit on Redhat 7.0. I get the following stack trace:

java.lang.NullPointerException
at a.a.a.bx.k(bx.java:352)
at a.a.a.c.Initializer.c(Initializer.java:170)
at a.a.a.c.r.actionPerformed(r.java:153)
at javax.swing.AbstractButton.fireActionPerformed(Abs tractButton.java:1450)
at javax.swing.AbstractButton$ForwardActionEvents.act ionPerformed(AbstractButton.java:1504)
at javax.swing.DefaultButtonModel.fireActionPerformed (DefaultButtonModel.java:378)
at javax.swing.DefaultButtonModel.setPressed(DefaultB uttonModel.java:250)
at javax.swing.plaf.basic.BasicButtonListener.mouseRe leased(BasicButtonListener.java:216)
at java.awt.AWTEventMulticaster.mouseReleased(AWTEven tMulticaster.java:230)
at java.awt.Component.processMouseEvent(Component.jav a:3715)
at java.awt.Component.processEvent(Component.java:354 4)
at java.awt.Container.processEvent(Container.java:116 4)
at java.awt.Component.dispatchEventImpl(Component.jav a:2593)
at java.awt.Container.dispatchEventImpl(Container.jav a:1213)
at java.awt.Component.dispatchEvent(Component.java:24 97)
at java.awt.LightweightDispatcher.retargetMouseEvent( Container.java:2451)
at java.awt.LightweightDispatcher.processMouseEvent(C ontainer.java:2216) at java.awt.LightweightDispatcher.dispatchEvent(Conta iner.java:2125)
at java.awt.Container.dispatchEventImpl(Container.jav a:1200)
at java.awt.Window.dispatchEventImpl(Window.java:914)
at java.awt.Component.dispatchEvent(Component.java:24 97)
at java.awt.EventQueue.dispatchEvent(EventQueue.java: 339)
at java.awt.EventDispatchThread.pumpOneEventForHierar chy(EventDispatchThread.java:131)
at java.awt.EventDispatchThread.pumpEventsForHierarch y(EventDispatchThread.java:98)
at java.awt.Dialog.show(Dialog.java:380)
at java.awt.Component.show(Component.java:946)
at java.awt.Component.setVisible(Component.java:903)
at a.a.a.c.o.a(o.java:118)
at a.a.a.c.MainFrame.shutdown(MainFrame.java:491)
at a.a.a.c.cj.actionPerformed(cj.java:151)
at javax.swing.AbstractButton.fireActionPerformed(Abs tractButton.java:1450)
at javax.swing.AbstractButton$ForwardActionEvents.act ionPerformed(AbstractButton.java:1504)
at javax.swing.DefaultButtonModel.fireActionPerformed (DefaultButtonModel.java:378)
at javax.swing.DefaultButtonModel.setPressed(DefaultB uttonModel.java:250)
at javax.swing.AbstractButton.doClick(AbstractButton. java:279)
at javax.swing.plaf.basic.BasicMenuItemUI$MouseInputH andler.mouseReleased(BasicMenuItemUI.java:886)
at java.awt.Component.processMouseEvent(Component.jav a:3715)
at java.awt.Component.processEvent(Component.java:354 4)
at java.awt.Container.processEvent(Container.java:116 4)
at java.awt.Component.dispatchEventImpl(Component.jav a:2593)
at java.awt.Container.dispatchEventImpl(Container.jav a:1213)
at java.awt.Component.dispatchEvent(Component.java:24 97)
at java.awt.LightweightDispatcher.retargetMouseEvent( Container.java:2451)
at java.awt.LightweightDispatcher.processMouseEvent(C ontainer.java:2216) at java.awt.LightweightDispatcher.dispatchEvent(Conta iner.java:2125)
at java.awt.Container.dispatchEventImpl(Container.jav a:1200)
at java.awt.Window.dispatchEventImpl(Window.java:914)
at java.awt.Component.dispatchEvent(Component.java:24 97)
at java.awt.EventQueue.dispatchEvent(EventQueue.java: 339)
at java.awt.EventDispatchThread.pumpOneEventForHierar chy(EventDispatchThread.java:131)
at java.awt.EventDispatchThread.pumpEventsForHierarch y(EventDispatchThread.java:98)
at java.awt.EventDispatchThread.pumpEvents(EventDispa tchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThre ad.java:85)

All attempts to download fail (displaying the message "Couldn't download") on Redhat 7.0

Thank you very much for posting about these issues.

Do downloads fail at the end of the download, or do they simply never succeed fully? I recommend trying 4 star downloads whenever possible, as this will dramatically increase your success rate.

Could you possibly send me the limewire.props file located in the directory where you expanded LimeWire? My address is afisk@limewire.com. That would be a tremendous help.

Also, what directory did you choose as the directory to save files?

Thanks again.

Use a download application with strong download resume (e.g., Interachy), but doesn't work with Internet Explorer.

It may take several resume attempts, but it eventually comes through.

The latest Mac Beta version (1.6b released 7/17) is still missing the last two "Options" tabs (Filters, Advanced) on one of my machines (iMac 233), but they are still present on my other machine (PowerBase with G3 accelerator). On the latter machine everything works perfectly and completely, and this strange situation has been the case for all betas since version 1.4b, including released 1.6.

However with 1.6b, Limewire on the iMac now preserves changes to the other options involving typing in a value--that is, the cancel, apply, and OK buttons now work, whereas before they would just turn dark colored with a click and nothing else happened. With the exception of the two missing Options tabs, Limewire works fine on iMac.

Both machines run OS 8.6 with _all_ latest Apple software updates, and they are connected to a LinkSys Cable Router with latest firmware. I use the most minimal extension set (that is, to get online) for both machines, using latest version of Conflict Catcher. Limewire folders on each machine have an identical installation of files and file sizes.

I always install with no extensions loaded (shift-key down). I always give application at least 40mb memory.

Thanks to badger for posting regarding the options tabs.

In LimeWire 1.6, we added some logic where we reduce the size o(particularly the height) of the options window if we detect that your screen size/resolution will not allow us to display the entire window. If we sized the window normally in these cases, the OK, Cancel, and Apply buttons would often be pushed completely off the screen, making it impossible to change your settings.

To solve this problem, we had to remove the two tabs with the largest y value (the tallest ones), which were the "Filters" and the "Advanced" tabs. These tabs were likely two of the less frequently used tabs, so we chose to go ahead with this change.

In LimeWire 1.6, there was a bug were applying changes on this reduced-size tab would cause an error. That is now fixed in LimeWire 1.6b.

In future version, we will likely move to a more extensible solution for the tab user interface so that you can have all of the options in a way that is not dependent on screen real estate.

Without being critical of the devoted developers of such excellent software, I can only say that I _really_ hope you reconsider and find a way to make all options readily available in future releases. Those options are extremely useful, and for those of us on a network or behind a firewall, they can be critical.

In summary, would you agree with this as a (hopefully) temporary workaround?:

If you have a screen resolution of 800x600 or less,
Temporarily increase your screen resolution (via Monitors control panel) so options for 'Filters' and 'Advanced' will "appear",
Set desired options for 'Filters' and 'Advanced',
Quit Limewire,
Reset screen resolution,
Restart Limewire.

The option settings should hold until the next time you want to change them. Note, that the missing two options appear at screen resolutions of 832x624 or greater, right?

We will be making the options window independent of screen size in a future release, switching to a tree structure similar to that in Netscape.

For the time being, however, the solution that you mentioned will not work -- the sizing is determined dynamically at runtime and is not persistent between LimeWire sessions.

There is another option, however, although I would advise proceding with some caution.

The Options window changes the settings in the "limewire.props" file located in your installation directory. You can edit this file directly if you wish. The keys for the Advanced and Filters tabs are:

FORCE_IP_ADDRESS,
BANNED_WORDS,
FILTER_HTML
FORCED_IP_ADDRESS_STRING,
BLACK_LISTED_IP_ADDRESSES,
FREELOADER_FILES,
FILTER_ADULT,
FILTER_GREEDY_QUERIES,
FORCED_PORT,
FILTER_VBS,
FORCED_IP_ADDRESS,
FREELOADER_ALLOWED,
FILTER_DUPLICATES,
CONNECT_OK_STRING,
CONNECT_STRING,
FILTER_HIGHBIT_QUERIES


I may have missed some, but I don't think so. I can't go into the details of each one, but hopefully you can figure it out by looking at the file. LimeWire reads in these settings when it starts up.

One option would be to copy your limewire.props file from your other computer, or at least copying the settings you want.

I hope this helps.

I've seen this issue come up with a few people with the recent version of Limewire. For me, Limewire won't connect. When I start Limewire, it tells me that it can't find a port for incomming connections, and when I try to change the port it says that all ports are unavailable, even the default 6346. I didn't have this problem with previous versions of Limewire (specifically 14b), and now, after I installed the recent version of limewire, bearshare and other gnutella programs can't connect for the same reason (port 6346 unavailable). Any ideas or help?