--- On Wed, 11/10/10, Joshua Juran <[email protected]> wrote:
<clip>
> Make sure that AppleTalk is enabled in the Chooser and that
> the Network control panel is set to EtherTalk, not
> LocalTalk. Be warned that if you boot up without a
> network connected, Mac OS will helpfully switch AppleTalk to
> the Printer Port. (At least, Open Transport does
> that.)
Yup, so "helpful" that a Mac will always try to switch its networking away from
the Ethernet port and standard TCP/IP protocol to the Printer Port and
AppleTalk. :P
Another thing to note in any 'classic' Mac networking, you can't delete remote
shares unless the share exists and is connected.
The Mac during boot tries to connect to and mount all remote shares in the list
of them that have been mounted. If you've had a lot of shares mounted which
aren't available during boot, that will make your Mac take a looooong time to
boot because it waits for each one to time out.
For some reason, nobody ever saw fit to create a utility to edit the remote
shares list to delete unavailable ones. The only way to get rid of unavailable
shares is to delete the networking preferences file. Then you get to have the
fun of reconfiguring that Mac's networking all over again, including
re-establishing connections to your currently in use remote shares.
I tried many times to prod various individuals and companies into writing such
a program, but nobody would do it. :P I guess they all figured once an
individual or company had their MacNetwork set up they would never ever change
anything, or they just accepted ever increasing boot times in a changing
network environment, punctuated by times of having to setup everything from
scratch when boot times got insanely long as just the normal Macintosh way. (Or
perhaps the IT types saw it as job security? "My Mac takes 15 minutes to boot!
Fix it!")
One thing that can be done is to 'fake it' by setting up a Mac with the same IP
address and a shared volume with the same name as the 'dead' share you want to
remove from the list. Connect to it then delete it from the list. Of course to
do that you must know the IP and name of the departed Mac and share. (Or other
non-Mac host and share.)
Yup, definitely one area Windows had it over Mac, from 1995 until OS X.
Multiple protocols over multiple interfaces all at the same time VS Mac's one
protocol over one interface. IIRC Win9x could run up to six networking
interfaces at the same time, I dunno how many protocols it could handle at the
same time, at least four I can think of right now. Would be nice to know why
Apple waited until OS X to match that capability, without users having to
resort to 3rd party extra-cost software.
--
-----
You received this message because you are a member of the Vintage Macs group.
The list FAQ is at http://lowendmac.com/lists/vintagemacs.shtml and our
netiquette guide is at http://www.lowendmac.com/lists/netiquette.shtml
To post to this group, send email to [email protected]
To leave this group, send email to [email protected]
For more options, visit this group at
http://groups.google.com/group/vintage-macs
Support for older Macs: http://lowendmac.com/services/
