There is a lot of themes changes that we are going to turn on for 3.0 I guess. These are like lightweight skins.

The real changes are invisible and mostly on the Ultrapeer (i.e. Dynamic Querying, Ultrapeer Query Routing on the last hop, Higher outdegree/lower TTL). These are what we are really trying to beta right now and fix (no doubt) lots of problems with. This is our big shot at changing the way Gnutella works by making it much more efficient (100x) and less resource consuming for messaging (selective broadcasts rather than pure broadcasts). Until these changes fully take hold, we need to work to tone down the messaging rate of the existing network. Thus, we need to make some of these changes (outdegree vs TTL) in stages.

Thanks
-greg

There is a root level process which at least involves the write_store and lsregister files (part of the LaunchServices.framework) showing up as unknown user or even “Zombie” (?) processes. Can’t be killed as usual admin user.

This may not be related to LW, but last week trying 2.9.0 I noticed unknown and oddly named (symbol font?) by user “???” processes triggering Console entries like “ Process Viewer[406] enumerateProcessesAndFetch couldn't scan time.” Tried as root user today to isolate it/them and now know it’s independent of LW and an internet connection. One such process led to a link with the write_store & lsregister files

After usual maintenance, including root user completely uninstalling any p2p stuff, replacing the write_store, LSRecentTool & lsregister files from the original OS 10.2 CD, deep cleaning caches by JCC (long overdue), I’ve only since seen one more ??? process.

The original CD write _store file does includes something about a corrupt write/time:

dyld_mod_term_funcs __dyld_make_delayed_module_initializer_calls The kernel support for the dynamic linker is not present to run this program.
usage: store_write <store-name> <path>
d_corrupt .24s : Wrote corrupt store file %.4096s
/var/tmp/csstore.log

Don’t know that it affects LW, but hope this saves someone troubleshooting time.

Oh, I didn't realize that the Mac Classic download links had been commented out. Those are back on the free beta page. I'm uploading the PRO beta now.

Thanks
-greg

2.9.4 PRO alpha is good to go. Mac Classic versions are back on the beta pages.

Thanks
-greg

The file size on the OSX beta needs an update.

Greg,

This might be a bug. In the download section of LimeWire, I have the chat column removed. I quit the program. When I open the application again the chat column is still there. I'm using version 2.9.4 of LimeWire.

LimeWire is not saving changes to the columns of the download table (yet).

__________________
Morgens ess ich Cornflakes und abends ess ich Brot
Und wenn ich lang genug gelebt hab, dann sterb ich und bin tot

--Fischmob