On Nov 6, 2012, at 5:19 PM, Liam Proven wrote:
Some of the
Now utils
(clock in the menu bar, drop-down Apple Menu items) were quite
handy before they were absorbed into the OS, and didn't really
take all that many resources.
I forget whose or what I used. I don't think they were anything to do
with NUTD, if that's the Now you meant?
Same company. They had a utilities package which I think Apple
ended up buying outright to do all the things you take for granted
in later versions of System 7 and further (like the menu bar
clock, or hierarchical menus in the Apple Menu).
System 7 works
on my SE (4 MB RAM) for a number of things, including
quite a few games, but it doesn't leave a lot of room for things like
MacTCP. I have a switch to choose between 7.0.1 and 6.0.8 (if you
don't have it already, System Switcher is a REALLY handy util).
I just attach multiple SCSI drives. :?) It's not like you need very big ones!
Handy if you've got them. I don't, and I don't have the money to go
about grabbing more, so System Switcher is quite nice (also makes
for a nice setup on an all-in-one like the SE).
I think 7.6 is
the absolute best OS to run on a PowerPC. I haven't
run it on an '040 any time recently, though I imagine it would be
acceptable, but I see very few downsides vs. running 7.5.x on a 68K
machine.
Could not disagree more. I run/ran my PPCs on 9.1 or 9.2.2 if they can
take it, as a rule.
It's a matter of personal preference, I imagine.
For what
it's worth, I feel like the Mac OS peaked at 7.6, and it's
all been (non-monotonically) downhill from there.
Again, I disagree. 7.6 is the best OS for 68030s, but for 68040s I
much value the facilities of 8.1 - pop-up folders, drawers (damned
near essential on smaller screens), HFS+ for bigger disks and so on. I
also think the 8.1 Finder looks better.
I would love to have 7.6 with HFS+. I never really cared for the
new look of OS 8; I liked the crisp look of 7.x. Not everyone is
likely to agree, obviously, and I wouldn't assert that it was the
*only* way to go (unless you were me, which you're not).
Cameron also pointed out the improved Unicode support in later
versions, which I had forgotten. That can be rather important,
depending on what you're trying to do.
I feel like
there
was another local maximum at 10.4 (and another somewhat lower one
at 10.6), but it's kind of apples vs. oranges at that point.
I miss Classic mode, but I find the facilities of Leopard - Spaces,
for instance - so very useful that I have pretty much abandoned Tiger
now.
Again, personal preference; I never had a use for Expos? or Spaces,
the equivalent of which had been available to me for years under
Linux. I'm a corner case in a lot of ways, though; I always used
command-tab and ran everything at full screen.
You may find
running Netatalk 2.x on your server alongside FTP to be
a MUCH more pleasant way to transfer files.
That'll be tricky, it runs Windows Server 2008. :?D
Ah, well, there's that. There used to be an AppleTalk package for
Windows, and it might still be maintained, but it was commercial
and expensive.
FTP works,
more or less,
but it trashes resource forks and just isn't as nice to work with,
even with a nice client like Fetch.
I move binaries around inside Zips or Sits. For text files or Word
docs, it doesn't matter too much.
Sure. It's nice to not have to (for example, when doing NetBSD
kernel development for my LCIII, I have the LCIII Finder attach
to an AppleShare partition (hosted on my cross-compile Linux
machine) on boot and load the kernel from there. Nothing to do
with resource forks, but it cuts quite a bit of overhead from
test-swear-compile-reboot cycle.
Ditto goes for
OS X
machines; my MDD G4 runs twice as fast with the first version of
Tiger on it as it does with the last version, which is appalling.
As in, 10.4.0 versus 10.4.11? I noticed no difference. Never really
have with point-releases.
Gradually, no. Try 'em side-by-side and you might notice.
Oh! Well that's good to know. I thought recent
versions of Netatalk
dropped Appletalk support and only ran AFS over TCP.
3.x did, yes, but 2.2.x is still maintained until they finally
decide to drop support for it. It's still readily available
from most package managers.
OIC. So I wasn't totally wrong. That's good. :?)
I was sad to see it go, but Frank Lahm pointed out that the
last maintainers that understood AppleTalk were long-gone
from the project and no one had stepped up to take
their
place, and the demand just wasn't there. I'm inclined to
believe him, since I fixed a bug in the NetBSD AppleTalk
stack that kept it from working that had been there for at
least a year without anyone noticing.
Ha! I ran one
of those on my SE a long time ago (I managed to
find an SE Ethernet card a while back, though, which solved
the problem rather better). I have an Asant? Ethernet-to-
LocalTalk bridge that someone gave me with a LocalTalk-only
printer, but it's not entirely satisfactory (in particular,
it's weird about enumerating the LocalTalk side). I'm almost
of a mind to build a bridge of my own with a small Ethernet-
capable micro and an external 8530, but I keep making my
queue longer with other projects. :-\
If I can persuade or bribe Tony into fixing my SE/30, I shall be
looking for an Ethernet board. And an external-monitor adaptor, lots
of RAM and AU/X. ;?)
The Ethernet cards are easy enough to get, at least over
here. The SE/30 shared a PDS with the IIsi, so they're
a little more common.
- Dave