[permalink] [id link]
AppleTalk support was finally removed from the MacOS in Mac OS X v10. 6 in 2009.
from
Wikipedia
Some Related Sentences
AppleTalk and support
AppleTalk support was also available in most networked printers ( especially laser printers ), some file servers and a number of routers.
The rise of TCP / IP during the 1990s led to a re-implementation of most of these types of support on that protocol, and AppleTalk became unsupported as of the release of Mac OS X v10. 6 in 2009.
Support was added to OS X in order to provide support for the large number of existing AppleTalk devices, notably laser printers and file shares, but alternate connection solutions common in this era, notably USB for printers, limited their demand.
However, the LaserWriter featured AppleTalk support that allowed the printer to be shared among as many as sixteen Macs, meaning that its per-user price could fall to under $ 450, far less expensive than HPs less-advanced model.
It did not support AppleTalk.
* For midrange users, the LaserWriter II NT provided PostScript support and AppleTalk networking.
The upgraded ROM added rudimentary support for an external AppleTalk networking device which was yet to be developed.
The new firmware removed the code for the cancelled AppleTalk networking device and replaced it with support for memory cards.
Bumping out the non-supported AppleTalk functionality, memory now lived in virtual slot 4, and mouse support moved to slot 7.
The first popular videogaming title to release a LAN version was Spectre in 1991 for the Apple Macintosh, featuring AppleTalk support for up to eight game players.
One example was the support of AppleTalk on Macintosh computers during the brief period in which Apple Computer supported the Open Transport networking system.
Thousands of Mac programs were based on the AppleTalk protocol ; in order to support these programs, AppleTalk was re-implemented as an OpenTransport " stack ", and then re-implemented as an API shim on top of this new library.
Apple also added its own implementation of AppleTalk to the stack to support legacy networks.
It also presented two practical advantages to the company ; STREAMS ' multiprotocol support would allow them to support both TCP / IP and AppleTalk from a single interface, and a portable cross-platform version of STREAMS was available for purchase commercially, one that included a high-quality TCP implementation.
# Mac OS X v10. 4 and later eliminates support for AFP servers that rely solely on AppleTalk for communication.
In its first release the NetBlazer software supported TCP / IP using SLIP, but a later upgrade added Point-to-Point Protocol ( PPP ) and support for IPX and AppleTalk.
All versions of Mac OS are capable of acting as a client to an AppleShare server ( via AFP and later SMB ) over AppleTalk and TCP / IP protocols, although more recent versions of OS X have gradually removed support for AppleTalk in favor of the standard TCP / IP.
Some versions may also support Internetwork Packet Exchange Control Protocol ( IPXCP ) and AppleTalk Control Protocol ( ATCP ) for routing IPX or Appletalk over the link.
AppleTalk and was
AppleTalk was released for the original Macintosh in 1985, and was the primary protocol used by Apple devices through the 1980s and 90s.
Additionally, AppleTalk was designed from the start to allow use with any potential underlying physical link.
AppleTalk was so easy to use that ad-hoc networks tended to appear whenever multiple Macs were in the same room.
With its release, AppleTalk Personal Network was renamed LocalTalk.
AppleTalk was at that time the most used networking system in the world, with over three times the installations of any other vendor.
A significant re-design was released in 1989 as AppleTalk Phase II.
With the purchase of NeXT and subsequent development of Mac OS X, AppleTalk was strictly a legacy system.
Unlike most of the early LAN systems, AppleTalk was not built using the archetypal Xerox XNS system.
One key differentiation for AppleTalk was it contained two protocols aimed at making the system completely self-configuring.
The AppleTalk address resolution protocol ( AARP ) allowed AppleTalk hosts to automatically generate their own network addresses, and the Name Binding Protocol ( NBP ) was a dynamic system for mapping network addresses to user-readable names.
An AppleTalk address was a 4-byte quantity.
Note that, because a name translated to an address, which included a socket number as well as a node number, a name in AppleTalk mapped directly to a service being provided by a machine, which was entirely separate from the name of the machine itself.
This was a comparatively late addition to the AppleTalk protocol suite, done when it became clear that a TCP-style reliable connection-oriented transport was needed.
ATP was the original reliable transport-level protocol for AppleTalk, built on top of DDP.
At the time it was being developed, a full, reliable connection-oriented protocol like TCP was considered to be too expensive to implement for most of the intended uses of AppleTalk.
NBP was a dynamic, distributed system for managing AppleTalk names.
This was the only part of AppleTalk that required periodic unsolicited broadcasts: every 10 seconds, each router had to send out a list of all the network numbers it knew about and how far away it thought they were.
ZIP was the protocol by which AppleTalk network numbers were associated with zone names.
AppleTalk and removed
Instead of using RS-422's balanced transmit and receive circuits, the AppleTalk Personal Network cabling used a single common electrical ground, which limited speeds to about 500 kbit / s, but allowed one conductor to be removed.
Windows NT Server ( 3 and 4 ) only supported AppleTalk, 2000 added AppleShare over IP ; Services for Macintosh ( SFM ), was removed from Windows Server 2008 onwards.
AppleTalk and from
This led to the OpenTransport efforts, which re-implemented both MacTCP and AppleTalk on an entirely new code base adapted from the standard STREAMS.
When powered on, an AppleTalk machine broadcasts an AARP probe packet asking for a network address, intending to hear back from controllers such as routers.
LocalTalk is a particular implementation of the physical layer of the AppleTalk networking system from Apple Computer.
AppleTalk relied on clocking from the CPU that was divided down to produce an output at roughly 230. 4 kbit / s.
The IIGS also supported booting from an AppleShare server, via the AppleTalk protocol, over LocalTalk cabling.
Cheshire subsequently joined Apple and authored IETF draft proposals for Multicast DNS and DNS based Service Discovery, supporting the transition from AppleTalk to IP networking.
( Versions up to 7. 5 could boot from a floppy, but there would be no room for other applications, although it was possible to access an AFP server on an AppleTalk network.
* Columbia AppleTalk Protocol ( CAP ) was an open source implementation of AFP and AppleTalk from Columbia University that has been discontinued and has fallen out of use.
The game distinguished itself from other games of its time by including a multiplayer mode that functioned over the AppleTalk protocol or Point-to-Point Protocol.
The Banyan VINES, AppleTalk, ServerNet, IPX / SPX, Giganet, and RPC Net-Libs were dropped from MDAC 2. 5 onwards.
0.099 seconds.