Earlier I got an old Mac with a Maccelerate!750 G3 card in it. In my haste I didn't copy the "BCache Control" control panel for it before wiping the disk and now I see that it's vanished from the face of the internet. Not good.
Does anyone happen to have a copy of it?
Here's the old support page on archive.org (links are all dead sadly)
http://web.archive.org/web/20000118224319/http://www.phase5.de/mac/suppo...
Judging by the comments, this should work on OS 9.2.x & 10.1/10.2 (cannot vouch for anything above that!). I managed to download the driver/app from this site -- so can upload later if you have issues. At the very, very least, you should be able to enable/disable L2 (backside) cache on just about any ZIF CPU board upgrade.
"L2CacheConfig should work with any G3 or G4 processor, except for the G4 processors that have an L3 cache. Of course, if you are using the processor which originally shipped with your computer, you don't need this software, as Mac OS X (or, more accurately, your computer's firmware) will enable and configure your cache automatically. So this software is of most interest to those with upgraded processors."
Judging by the comments, this should work on OS 9.2.x & 10.1/10.2 (cannot vouch for anything above that!). I managed to download the driver/app from this site -- so can upload later if you have issues. At the very, very least, you should be able to enable/disable L2 (backside) cache on just about any ZIF CPU board upgrade.
http://web.archive.org/web/20061015194514/http://eshop.macsales.com/OSXC...
"L2CacheConfig should work with any G3 or G4 processor, except for the G4 processors that have an L3 cache. Of course, if you are using the processor which originally shipped with your computer, you don't need this software, as Mac OS X (or, more accurately, your computer's firmware) will enable and configure your cache automatically. So this software is of most interest to those with upgraded processors."
EDIT: OS9 cannot retrieve the L2 status from the system - It will always say "OK", something about a bug in the OS -- rest assured that the change did take place, you just won't know from the OS 
. Mac OS X seems to be able to retrieve a more accurate idea of what is really happening with the L2 cache status.
Also check out here - http://web.archive.org/web/20060301055331/http://www.macsonly.com/mclr8....
They use a control panel called BCache (possibly for the same card as yours). Good luck finding that software, as the term BCache (Buffer Cache?) is used in almost every piece of source code on the face of the planet!!
That last link looks to be my card alright. Now if only I could find the damn software...
I've been trying the Powerlogix G3 CacheEnabler and CPU Director tools but while they appear to work, running MiniBench with cache enabled and disabled gets me the same scores.
Please try the first download URL I posted. I would be interested to see if L2CacheConfig works!?
L2CacheConfig is for OS X. I'm running 8.6 here (it's only a 1GB hard disk).
I've tried a few others and it seems any tool that controls the cache will work. Powerlogix CPU Director, G3G4CacheProfiler and XLR8 MAChSpeed Control all do the trick. But I'd still really like to get the proper control panel. Especially as I should have saved it in the first place. Didn't think it would be so hard to find.
I must beg your pardon -- you must remember that the link I supplied was from a LONG time ago, and supposedly only JUST started support for OS X 10.2, which means, even if it is a .app, it may very well run on OS 9.2.2 (my version of Toast Titanium is a .app file/folder, and runs sweetly on 9.2.2!!!).
I would be interested if you would at least try and launch it. Many thanks.
I'll give it a try when I get 9.2.2 installed. So far the highest I've installed is 8.6.
Of the utils I've tried so far, XLR8 MACh Speed Control is the winner for me. It's the only one that showed the correct clock speed in the System Profiler and it even worked on 7.5.3.
So you found one - excellent!
Yep, it seems pretty much any of these tools will work. I was worried that they were specific to the card.
