Re: Help! System 6.0.1 is trying to talk!

[David A Lyons <dlyons@apple.com>]

In article <mark-141093111858@128.157.9.145> Mark Manning,
mark@trillian.jsc.nasa.gov writes:
> On the first - I never have asked it to do Appletalk.  I used the
> easyinstall and that was all.  I went through all of the files in
> the system folder and there aren't any for Appletalk.  What gives?

Get Info on your System: Drivers: SCC.Manager, and make it Inactive.  I
know, it's weird that you have to do that.

> On the ram problem, I _have_ set the min/max to be the same.  It
> shut up about it for a while, but now the message is back.

There is one other condition that will give you that message:  Even
though the sizes are the same, the system couldn't allocate all of the
RAM that the RAM Disk wanted (so, effectively, the minimum size is
smaller). -- This is based on looking at the RAM5 source code, not on
actually trying it out on a ROM 1 system.

Trying a smaller RAM Disk size may help...how big it it now?

> Both messages pop to the 40 column mode and both require a return
> to make them go away.  This is kind of dumb (waiting for a return).
> If nothing else, the software should wait a given length of time and
> then continue on with the boot.  A return should make it simply
> go faster.  Could someone at Apple think about making this change?

I hate messages that go away by themselves.  Certain messages deserve to
have a way of disabling them (user explicitly says "I know, I created
this condition on purpose").

The message can't tell when the user cares and when not.  Users read at
different speeds, -and- they get distracted (phone calls, earthquakes,
etc), so any time-delay messages tend to take control away from the user.

Dave Lyons, dlyons@apple.com
Mr Tangent

My opinions are my own, not Apple's.