Re: 20 Years Later: What storage options for IIgs?

[dempson@actrix.gen.nz (David Empson)]

rglen herrmannsfeldt <gah@ugcs.caltech.edu> wrote:

> David Empson wrote:
> (snip)
> 
> > Not exactly. Tiger and Leopard still support the AppleTalk protocol
> > stack for two applications: printing and name binding (service
> > discovery). Specifically, EtherTalk and all higher layer protocols up to
> > and including PAP - Printer Access Protocol and NBP - Name Binding
> > Protocol.
> 
> > They don't support AFP (Apple File Protocol) over AppleTalk. I don't
> > know whether they retained support for other high-level AppleTalk
> > protocols, such as ADSP (Data Stream) and ASP (Session) - unlikely. PAP
> > only requires the slightly lower level ATP (Transaction).
> 
> As far as I know, Win2K server still supports AFP and PAP.

PAP isn't an issue - it is fully supported by all versions of Mac OS X.

It looks like Windows Server 2003 still supported AFP over AppleTalk. As
did Apple's operating system released in 2003 (Mac OS X 10.3).

Apple scaled back support for the AppleTalk protocols in their 2005
operating system (Mac OS X 10.4), but it still supports AFP over TCP/IP
(which is the native file sharing protocol for Mac OS X).

I'm not familiar with recent Windows servers - what was after Server
2003, and does it still support AppleTalk for file sharing, or just AFP
over TCP/IP?

The last Mac OS version which required the use of AFP over AppleTalk on
the client side was 7.5.5 (1996), if I remember right. Hardly seems
relevant in 2007, at least from Apple's point of view.

Those with legacy hardware (such as networked Apple IIs) simply need to
maintain a legacy server to go along with it.

netatalk on Linux is another option, of course.
-- 
David Empson
dempson@actrix.gen.nz