MBRICE  LeopardAssist only supports Apple manufactured hardware with a G4 processor.  
(Version 2.3.1)

MBRICE  I picked up an eMac G4 and decided to do a bit of extra work on LeopardAssist. Did away with boot.txt as requested by beta testers, now writing the 867mhz script directly into the Parameter RAM. This should correct problems on many systems which previously had issues finding boot.txt on restart (a majority of cases).  
(Version 2.0)

MBRICE  Leopard sure won't speed on these older machines, although some of them have been upgraded, particularly those with aftermarket graphics cards which will allow Leopard's video acceleration.

Cheers to everyone who showed support, I really do wish I could have continued working on this but unfortunately my G4, my only testing machine had a logic board failure which severely damaged the progress of the project.  
(Version 1.2)

MBRICE  LeopardAssist's parent development group has ceased development of its entire product line, but LeopardAssist in its entirety has been open sourced and relocated to SourceForge.

Full details at the former website. http://mac.profusehost.net  
(Version 1.2 DR3)

MBRICE  The code base of this application is unable to be ported to newer releases of the RB Compiler, meaning it can not be adapted to run on Intel or even take advantage of the velocity engines in G4 or G5 microprocessors, that coupled with lack of development time or resources means unfortunately the development of this application will be halted.

In response to ghostwriter's reply regarding servers, the link WAS fixed but was later broken again due to server issues.  
(Version 1.0)

MBRICE  Unfortunately no, for 2 reasons. First being that Leopard screams out for at least 512, and second being that you can't fake the RAM count through Open Firmware like the CPU can.  
(Version 1.2 DR3)

MBRICE  So far the TiBook is on the supported list for benefit of the doubt, we have had positive reports from the original 400/500mhz models. Best way to try it is to test it out if possible.  
(Version 1.1)

MBRICE  Download link fixed. Unfortunately the app is somewhat of a black hole at the core and the attempts to resolve bugs aren't going well. Development is not dead though, I assure that.  
(Version 1.0)

MBRICE  I think Leopard is fairly dependent on AltiVec, so this won't help get it running on G3's. The machine we tested it on was a 400mhz Sawtooth G4 which seemed to work fine (although in comparison it wasn't as fast as newer models).  
(Version 0.9)

MBRICE  It seems to be a compiler issue as it compiles fine under an older version of the compiler. However the older one only compiles for PowerPC, not Intel.

May need to wait for a compiler update.  
(Version 1.0)

MBRICE  I'll look in to this. Quite unusual that the problem is still occuring despite complete changes and rewrites. Perhaps i'll forward the source on to another developer and let them take a look.  
(Version 1.0)

MBRICE  1.0 has run more efficiently and more stable on our test machines, and has a few last minute changes to improve it a little.

Source Code has been posted on the CrossWire site.  
(Version 1.0)

MBRICE  Last post for the night (1:36 AM here)... so here's a quoted text for all to read:

Currently the core is migrated to a more Acquisition style (Frostwire/Limewire) system which we plan to have fully operational with Xcode by 1.0. The UI will be receiving a major lift if all goes according to plan. Both visual and code wise. Connection code, controllers, graphics, etc will be rewritten in progression.

2 builds we have compiled, "2G96" which is the Cabos based majorly used version, and "6G72" which is a more internal code-from-scratch version. 2696 will be made fully open sourced ASAP, but 6G72 will remain closed due to it's very low/no dependence on Cabos code or architectures.

Both have the same UI, but may change during development.  
(Version 1.0b4)

MBRICE  Ok, verdict is that we're going to add some code here and there to 1.0, then all source will be released.

I've taken my own time into the source (being a bit of a programmer myself, although mostly a business manager) to add the Cabos links back in, including bundling versions of the CW Use License and GPL inside the application, accessible from the Apple Menu.  
(Version 1.0b4)

MBRICE  Indeed. I'll be sure to forward this to the head of the group (i'm just passing the details on via my MacUpdate account).

Thanks!  
(Version 1.0b4)

MBRICE  I also forgot to mention that 1.0 Final/Beta 4 (yet to be seen) will have full support for Mac OS X 10.3 "Panther".  
(Version 1.0b3)

MBRICE  I'm working on CrossWire 1.0 Final now. A lot of work has been done to the core in the upcoming build, along with some UI refinements, a new search system and progress made toward recoding the Preferences Panel.

One thing I noticed is that a lot of crash reports make reference to "Application Enhancer". If you are using this, click "Application Enhancer" in System Preferences, then the "Master Exclude List" tab, and add CrossWire to this list. If possible, send feedback via the Bug Reporter to any notable stability improvements, etc.

Thanks.  
(Version 1.0b3)

MBRICE  The client is easy to use yet powerful, very extensible and customizable. To top it all off, the developers and user community are friendly and helpful. It's perfect! It represents the best of what software should be. Well worth the price, even though I agree, IRC should be free. But even if it's not the IRC you're paying for, it's the simplicity, capability and feel that's worth the small fee.  
(Version 1.1)

MBRICE  If you could send the Crash logs to imac600x@gmail.com that would be great. I haven't had any other issues reported with startup errors (at least in 1.0b3) so the logs could help pinpoint the issue.  
(Version 1.0b3)

MBRICE  Closest I could find to that is the open space where you can resize other items into. Can you drag the "Speed" column into it?  
(Version 1.0b3)

MBRICE  I also have reason to believe that the severe instability and lagging speed in 1.0b1 and 1.0b2 were linked to the corrupted Dylib, which is now fixed.  
(Version 1.0b3)

MBRICE  It saves its preferences and lists in the Library > Preferences folders under "CrossWire.plist" I believe. That's where it saves on my machine anyway, and where it -should- be saving to.  
(Version 1.0b2)

MBRICE  Pleased to announce that as soon as Public Beta 3 is up and on MacUpdate, which should be by the time you read this, you will have a Intel/PPC Universal Binary. That's right, it WORKS UNIVERSALLY, FINALLY.  
(Version 1.0b2)

MBRICE  It's coded on PowerPC based Macs to start with. We have a cross compiler to Intel, but it's not working at the moment due to a corrupted Dylib error, which I explain in an earlier review. Unfortunately the compiler update is $299 (money we don't have), so we're trying to repair the current one.

Some bug reports have come in, and i'll be looking into those ASAP.  
(Version 1.0b2)

MBRICE  Just letting you know that we've addressed a lot of issues in 2.0 onward, including the ones Prasys mentioned. So we are listening to your feedback... enjoy!  
(Version 2.0)

MBRICE  Update: i'm thinking it's the compiler. I'll need to forward to an Intel machine (which I don't have) to have it compiled, or try and update the compiler to a new version.  
(Version 1.0b1)

MBRICE  Cheers for the feedback regarding Intel processors... but this is kind of shocking. I'll forward it on to one of the other developers who takes care of the Intel side of things and hopefully release a working Intel Public Beta 2.

Thanks!  
(Version 1.0b1)

MBRICE  I should note that the new 2.0 is different from previous builds and doesn't yet take themes. iRCTunes DG requested we shift back to a more reasonable versioning system after the acquisition, and since we never had a 2.0 release before, we have named this build "iRCTunes 2.0 (Build 2000)".  
(Version 2.0rc1)

MBRICE  It's one of the machines I administrate on a network of about 25, a few of which are registered under my name. Ok, i'll get a new screenshot of my own desktop (which can be identified by only one disk drive).

Meanwhile, the primary use of the utility was the fact that per day, I had about 12 drives mounted. On some, 3 HD's, on mine, 1. Also, 1 CD, 1 iPod and the rest Network Services.

This utility got them off of the desktop. Simply I could have created an alias to /volumes, but the icons appeared as ALL network drives when shown there. It was better to just connect to the computer folder directly.  
(Version 1.0)