🚀 go-pugleaf

In article <simon-270193083951@archmac-163.arch.su.edu.au> Simon Hayman,
simon@archsci.arch.su.edu.au writes:
> As a satisfied user of SpeedyFinder and Now Utilities (V3 & 4) and about
> two dozen other "evil" inits, etc, I can vouch for the fact that there
have
> been no problems to my knowledge that hadn't been there beforehand. Of
> course, I am only rumnning a humble ClassicII :-). As far as I know
Victor
> is very prompt with bug fixes to registered users - I haven't had to ask
> for one it has just turned up in my email.

Count me in as another satisfied (registered) user of SF7.  I run
AutoDoubler and SpeedyFinder7 without any problems.  GateKeeper and the
background copies disagree a bit.  However, I do not like the potential
cataclysmic effects of a non-Finder background copier anyway; so, that
feature is inhibited on my setup.

About the only problem with the BH menu that I noticed is that MS Excel
4.0 with definitely crash if the menu is hidden.  It does not matter who
or what hid the menu, Excel will simply crash.  I wish the dweebs at
Microsoft would get their act together and stop cutting corners to save a
nanosecond per day at run time or two hours of development time.  Ahh,
but I digress.  Anyway, SpeedyFinder is worth the $20.

If anyone is interested, I ran copy speed tests between CopyDoubler and
SpeedyFinder's optimal memory allocation copying (I did not use the
background copier).  CopyDoubler was consistently 20%-30% faster on a
local Mac and across the network.  My guess is that the speed difference
is due to the fact that Finder waits for a copy
confirmation/verification, whereas CopyDoubler just lets it go.  It
appeared that the lag was most noticeable after the copy thermometer was
filled, i.e. after the actual transfer was finished.

Igor

_____
NCSA-UIUC,  e:igorl@uiuc.edu,  p:(217) 244-5606