All images are thumbnails and can be opened in a new tab or window for a larger version. These pages are very simplistic HTML 4.01 Strict source and have no JavaScript, Flash, cookies or other elements like IFRAMEs, and should render fine with Chrome, Safari and Firefox. Internet Explorer may be somewhat sketchy because of issues with CSS interpretation (and making a custom CSS for every IE version is not worth it).

Special thanks go out to the following members at 68kmla.org: phreakout (hardware help in the beginning days); JDW (for more information, particularly concerning 10.4), kingchops and thatsteve for hardware images; mcdermd for web hosting and invaluable assistance in the early HTML days, a bank of hardware and software for testing; protocol7 for clues concerning the esoteric Netatalk configuration; Cory5412 for maintaining 68kmla.org; and The Internet for providing various sources of software that is practically unobtainable otherwise.



Should any links expire, contact the author for a locally saved version (all links have been saved, save for certain download links) of the first page only; or use the WayBack Machine at http://archive.org/web/web.php. Legal: No warranty, guarantee of accuracy or completeness of any kind; both this page and the More Info page are for informational purposes only and the reader/user assumes all risk and responsibility, and the words and images herein are merely suggestions. We strived for accuracy and detail but we can only go so far in that regard. Privacy: This page and the More Info page do not collect any information about any individual user. Only the internal awstat feature of the server collects information, however this information is not shared with anyone. These two pages do not have any external tracking metrics of any kind.

To start things on a happy note, head here first. (Sooo true....)

First word

Because of the rapid hardware and software "advances" these days it is imperative that a couple of paragraphs about compatibility is presented.

The newer brands of computers, at the time of this writing specifically Apple computers, are making strides towards reducing backwards compatibility. For instance, the newer iMacs do not have onboard Ethernet (that is supplied via a USB > Ethernet adapter, or Thunderbolt > Ethernet) as far as hardware is concerned. In the software department, AFP is not going to be compatible most older machines by default. By the time you read this, the relevant versions of Mac OS X that are desirable for old hardware (like 10.2 Jaguar) are so old and obsolete that obtaining older versions of software for these operating systems can be quite a chore, unlike finding software for Windows 98 or something a bit more mainstream.

The Linux section should remain relevant for some time, but the author cannot guarantee this statement. For one, the Desktop Environment (DE) demonstrated is GNOME 2, which was the standard DE for Ubuntu and some Debian systems, and it is a nice looking DE for the times it was deployed. But GNOME 2 is depreciated and is only being carried on by the MATE project, and we don't know how long that will last. The point is that you may have to a bit of work to do in applying the principles here to your individual system. It is entirely possible to build a stripped down version of Linux that won't take up much space which will have all the important packages (Netatalk, uudeview, hfsutils, and so on) installed that is intended entirely for a VM, for legacy purposes at least.

The good news is that you won't have to do much research or experimentation on the classic Mac side -- that has already been sorted. These developments will probably mean that FTP over Ethernet, AFP over Ethernet inside a virtual machine (VM) like VirtualBox or its brothers, AFP over AppleTalk using an AFP bridge using a virtual machine with Netatalk installed, or worst case scenario, RS232 based file transfer and PPP passthrough techniques could be the only remaining methods (Mac OS X, particularly the older versions, can be somewhat dicey inside virtual machine programs, if it runs at all). So for all the documentation and illustration here, it could all be for naught, but at least it would be interesting from a historical perspective. (Someone is still out there fiddling with a working a DEC PDP-11 series or some VAX hardware, so...) The future is completely unknown from our point of view, so this word is warranted.

Hardware

Most electronic hardware of an age in excess of ten years will start to show signs of age. The image to the right shows one example of an increasingly common failure point with old hardware like this -- leaking clock batteries and electrolytic capacitors which have failed and then promptly disgorge caustic and acidic compounds onto the motherboard. Owners of genuinely desirable hardware such as SE/30s with socketed CPU motherboards, Macintosh Portables, the Macintosh IIfx, Quadra 840AV, et cetera should establish these repairs without delay and with extra diligence and care. The SE/30 logic board as shown is a total write-off and it is unfortunate that the heart of the system, the motherboard, is the usual target for these catastrophes. (Image credit goes out to volvo242gt at 68kmla.org.) Power supplies and analog boards (128K through the Classic II and Color Classic) are also vulnerable and it is only a matter of time before these incidents will increase in frequency and inevitably require due care and attention. Let's move on to the minimum hardware specifications to interact with modern networks:

Base Minimum: Serial Interlink: Macintosh 128K with MacTerminal 1.1, MacTerminal 2.2 or other 128K-compatible terminal emulators. A second 400KiB external drive is a strong recommendation. A 128K does not have enough memory to run any AppleShare networking software entirely; printing, however, is supported on a limited list of compatible printers (i.e. ImageWriter, see here). It also cannot run the HD20 INIT. AppleShare: Macintosh 512K with AppleShare WS 1.1, a DE-9 LocalTalk or PhoneNET adapter, and a Mac pre-OS X that can write 400KiB disks (sustained floppy disk work may best be suited by either a Mac that can boot into System 6, or a HD20 with the HD20 INIT). The 512Ke can run EasyShare, but there is no full version available, so the demo version will have be used. Use System 4.1/Finder 5.5. TCP Services: The 512Ke can run NCSA Telnet 2.5, which has an FTP server and its own TCP stack, and SLIP support, or TOPS Terminal. MacTCP 1.x will run on a 512Ke but then the dearth of TCP software that will run it makes it a very interesting subject (Fetch 2.1.2 returned an error saying it needs KSP or MacTCP even though MacTCP 1.1.1 was already installed). A TCP/IP compatible MacIP bridge will be required. The minimum to use any other TCP program via MacTCP or PPP is a Macintosh Plus.

Practical Minimum: Macintosh Plus 1MB1 with a HD20 or other hard drive solution, a SCSI to Ethernet converter, Ethernet crossover or straight depending on needs, and another Macintosh2 with a 800KiB compatible floppy drive and an Ethernet port.

Preferred: A Macintosh SE/30, IIsi, IIcx, IIci or higher in good working order, with a 80MiB hard drive or larger, working 1.44MB floppy drive, preferably 32MiB of memory for a 12-20MiB RAM Disk 3 , at least twenty floppy disks in good order, another Mac that can write floppy disks, Ethernet cross-over cable, Ethernet standard cable, and a RJ45 Ethernet expansion card 4 . A working CD drive is a bonus as well (or share it over the network); a Zip100 drive can be a useful gadget.

A Macintosh SE/30, IIsi, IIcx, IIci or higher in good working order, with a 80MiB hard drive or larger, working 1.44MB floppy drive, preferably 32MiB of memory for a 12-20MiB RAM Disk , at least twenty floppy disks in good order, another Mac that can write floppy disks, Ethernet cross-over cable, Ethernet standard cable, and a RJ45 Ethernet expansion card . A working CD drive is a bonus as well (or share it over the network); a Zip100 drive can be a useful gadget. Platinum Deluxe: A CompactFlash internal storage option5 (requires IDE bus or PCMCIA slots), using a USB capable machine that can boot into OS 9 and install and copy applications directly onto the CF card. Desktop and laptop configurations of adapters may vary. SCSI to IDE adapters are very expensive (like the

ACARD models) or are hobbyist affairs (like the SCSI2SD project); for PCMCIA, the adapter is simply a pass-through device. PCMCIA SD card adapters may or may not work.

Excellent: Simple Ethereal bi-directional reliable cross-platform self-configuring secure wireless network.

1 The maximum memory in this model is 4MiB and is highly recommended. The hard drive is not a mandatory requirement but is a very good idea.

2 Preferably this Mac should boot into Classic OS and have an internal floppy drive, with at least 7.5.5 but OS 9 would be better, and capable of booting into 10.2.8 would be best. Strongly recommended. (It also has other uses, such as older color games) Nearly all Mac machine specs are here . If all you have is a Windows box or Linux unit, then the difficulty of interaction with the vintage computer increases considerably, particularly with Macs without 1.44MB drives.

3 8 Megabytes is plenty if a RAM disk is not a requirement under System 7+. 6.0.8 can only address 8MiB by default, although Optima or Maxima could change that. WWW browsers demand lots of memory with System 7. (6.0.8L can address up to 10MiB.)

4 Varies. SCSI to Ethernet, LocalTalk to Ethernet, NuBus Ethernet, PCI Ethernet, and other configurations. Different machines may have different hardware configurations.

5 UDMA and Fixed Disk Mode enabled cards, like the Transcend Industrial series are recommended.

A machine with maxed memory is a sagacious option. Although the SE/30 or similar machines like the IIsi can address up to 128MiB, 32MiB is sufficient for even the most strenuous uses in this platform. Other machines like the PM 7600 could probably benefit from maxed memory, but the SE and Plus will probably benefit the most, because 1 or 2MiB is a rather tight squeeze, but networking can be done irregardless.

Hardware Network Options

The network adapters in question will vary based on the machine in question and the method of interfacing. As this Guide pertains to Ethernet and serial data methods, the machine itself and the software supported, plus the desired method of connecting to other machines will dictate the hardware available.

Caution: The DB-19 floppy port on compatible Macs (68040 and PPC Macs don't have it) is not compatible with Apple II 5.25" disk drives and doing so can destroy the floppy controller chip. The DB-25 SCSI port is also likewise completely incompatible with RS232 DB-25 serial or DB-25 parallel hardware like printers. Just would like to throw that out there because it's not always mentioned. (If the SCSI port having 25 pins seems unusual, it is because it's not standard. The SCSI standard specifies one ground for each signal line, but the Apple implementation merely ties all the ground pins together, contrary to the standard.)

The Macintosh 512K and 512Ke only support LocalTalk or AFP bridges and early terminal emulation software: as mentioned earlier, the 128K or 128Ke lacks sufficient memory to handle networking via AFP; though the MacTerminal 1.1 application runs under System 1.1 and can run from 50bps up to 19200bps, so that should work -- but file transfer is interesting due to the limit of 400KiB disks (and the HD20 will not work with the 128K, barring hacks to format it to MFS (along with a hacked driver), but might work with the 128Ke). All other Macs up to the iMac support LocalTalk and thusly can handle either LocalTalk or serial data transfer methods involving VT100-style terminal emulators. Nearly all of them supported some kind of Ethernet option, although this can vary based on the platform: and Ethernet is vastly superior to the serial methods, in both speed and flexibility.

Ethernet

Machines that sported SCSI ports can use SCSI to Ethernet adapters; such as the Macintosh Portable, which lacks any such upgrade cards; generally speaking this SCSI route can be a "last resort" (or use an AFP bridge, or pseudo-PPP dialup). Other Macintoshes with PDS (Processor Direct Slot) or expansion slots like the SE, SE/30 and Classic series can use proprietary (unique to the specific machine model) cards for Ethernet ports. For machines with AAUI ports like the Quadra 660AV, PowerBook 5300 series and so forth, AAUI to RJ45 adapters are relatively inexpensive and work fine. For Macs that came with NuBus slots (like the Mac II series (except the stock IIsi), the Quadra 700, Quadra 950, et cetera) then NuBus cards with Ethernet is a practical option (try to get ones with RJ45 plugs rather than AUI or 10BASE-2). Not all NuBus cards are the same length, just like PCI cards: there are full-length 12-inch (30.5cm) and "half-length" 7-inch (17.8cm) versions. (Image shows a IIci cache card, Radius Rocket 33 with DSP daughter card and Farallon NIC.)

Warning: Always make sure the pins on the NuBus or PDS card which mate to the motherboard slot are not knackered before the card is inserted: they are difficult to repair or replace and are quite vulnerable.

Testing an AsanteFAST 10/100 NuBus card as shown nearby indicated that while the link will be over 100BASE-T, the limitations of the older machine hold it back to basically the same as a regular 10BASE-T card. See the More Info page, Data Transfer Rates section for speed tests. (Install NSI software first, then the 10/100 driver if you nab one of these. Although the software indicates that it requires System 7, it'll work in System 6 regardless. Use a Custom Install to install the driver.)

Certain Macs like the LC 575, 580, the Power Macintosh 6200/75 and the Performa 5300CD series have Communications Slots on the motherboard for CommSlot Ethernet cards. The LC series like the LCII and the Color Classic use the proprietary LC PDS bus which can use LC PDS Ethernet cards. (Some Ethernet cards for the LC line may not conform to the height standard of 12.9mm, and may run into interference issues. There's also a difference in the PDS slots, some have 96 pin Euro-DIN connectors and others are of the 114 pin type; the 96 pin variant is a 16-bit bus and the 114 pin is a 32-bit bus. The "extra" 18 pins are merely a "add-on" and 96 pin cards will work fine, though the 68040 class of machines emulate 68030 PDS instructions. The Designing Cards and Drivers for the Macintosh Family book describes this subject in more detail: a PDF is around on the web, hosted by dec8.info.)

PowerBook Duos can obtain Ethernet capabilities either through a Duo Dock equipped with an Ethernet option, an EtherDock (the 280 and 2300c are not supported), Asante NetDock, Asante Micro EN/SC, or the ultimate minidock, the Newer Technologies UltraDock 16sce. The eMachines EtherDock is pretty similar to the standard Apple MiniDock but has a RJ-45 plug in place of the RJ-11 modem. The problem with PowerBook Duos (and Macintosh Classic I and II) is that the networking cards or docks tend to be somewhat rare and can be somewhat expensive: but there is some relief with AFP bridges -- see the next subsection below.

Other PowerBooks like the 1400 series usually have at least one PCMCIA expansion slot available. These present a special concern in that they are not 32-bit CardBus slots. All CardBus PCMCIA cards are 32-bit; otherwise, PCMCIA cards are 16-bit only. 32-bit cards are not supported on any PowerBook except the models listed here: but don't worry, it's not possible to insert a CardBus card all the way into a 16-bit slot. The easiest way to identify a CardBus card from a 16-bit card is to look at the end of the card. All CardBus cards have a strip with raised indents on the front edge. Before you buy, make sure that the respective driver is available first. Try to hunt down a model which has drivers that go back to System 7.5 or 7.6, like the Farallon EtherMac PC Card: part number 595, 595a, 895; the first two have a red arrow above "Insert This Side Up" and the latter has a blue arrow. Just so everybody knows, not all these PCMCIA cards will have all the pins present on the Ethernet jack (so an AFP bridge may not work). Some are wired as crossover, too.

Otherwise, there are three nominal kinds of Ethernet adapters that came in the PCMCIA format. The first is a version with the XJACK connector that Megahertz (subsidiary of 3Com) pushed. It is decent but a gentle hand is probably a good idea because excess force could damage the retractable jack (and some versions are missing some pins on the RJ45 jack). This adapter variant would be ideal for PowerBooks except they are a gigantic flop for Mac users because the driver situation is a total mess. The second kind, which is the most common, has a tiny connector on the end of the PC card and requires the appropriate dongle, so make sure that comes with the unit. Like the 30-pin Apple docking connector as was used in the early span of iPhone, iPad and iPod units, it is prone to weakening with use. The last version has a built-in extension which has the RJ45 plug but this also makes it vulnerable to being whacked by accident and unintentional application of force.

Most 10/100 cards are CardBus and thusly are only compatible with the later PowerBook G3 and G4 models -- which already have RJ45 Ethernet and some have AirPort cards already, though there are 10/100 16-bit cards. The PowerBook 500 series with the PCMCIA Rev. C "Card Cage" can use certain PCMCIA cards in 7.1.1, too.

At any rate, the fallback method for all PowerBooks with SCSI can use something like the Asante Micro EN/SC or AAUI adapters if they have AAUI onboard, like the 5300 series. A HDI-30 to DB-25 SCSI adapter may be required for certain SCSI to Ethernet adapters because PowerBooks don't come with ... Apple-sized DB-25 SCSI ports.



A PowerBook Duo mated to a UltraDock 16sce with Ethernet



A DaynaPort SCSI/Link-T Ethernet Adapter (courtesy kingchops at 68kmla.org)



Backside of a Plus with a HD20SC

and SCSI Ethernet adapter



A Farallon EtherMac 030 PDS card

for a SE/30 or IIsi



Notice how the Ethernet card pictured above (for the SE/30) has three ports: the first from the left is 10BASE-T in a 8P8C RJ-45 connector, the middle one is AUI, which is known as Attachment Unit Interface and can either be used for 10BASE-T or 10BASE-2 adapters, and finally 10BASE-2 in a BNC coax port. Some old NuBus cards and the like will only provide an AUI port, an additional dongle adapter is required to hook up with RJ45 based wiring, such as the Farallon StarConnector shown below. (The adapter might come with a driver disk -- the StarConnector is supposed to.) 10BASE-2 Ethernet waned after the increasing adoption of twisted-pair Ethernet; it is also known as ThinNet (and other names) and is simply Ethernet on coaxial cable with T connections for pass-through daisy chaining or vampire taps as needed. AUI was common on network interface cards (NIC) back then because the marketplace was chaotic with three or four competing Ethernet standards (and other standards like TokenRing) and it was not unusual for one place to have one interface (like 10BASE-5) and another might have something else (like 10BASE-2); an adapter converted the interface to coax, fiber, or twisted pair as necessary to the application. Eventually most places settled down on 10BASE-T and everybody lived happily thereafter. Warning: Do not plug in a Macintosh display connector into an AUI socket, or a AUI unit into the Macintosh display interface connector. They look the same (DB-15) but they are electrically incompatible and damage can result. Ofttimes there's a switch on the back of Farallon cards to toggle between Twisted Pair (TP) and ThickNet or ThinNet.

Certain SCSI to Ethernet adapters, like the Dayna Desktop EN/SC, will have major problems with proper operation unless something else is on the chain to terminate the SCSI bus properly. This adapter is not self-terminating so it will cause the Mac's SCSI bus to go haywire. Therefore, the SCSI chain should run like this: Mac -- Ethernet adapter -- SCSI device with internal termination or terminator on it. A useful SCSI device to have on hand is a Zip100 drive - it's not that big, it has a termination switch already on it, the drives and diskettes are usually very inexpensive and is a useful storage supplement - or can even be used as a primary boot device. SCSI CD-ROM drives are usually pretty slow (4x tops) and honestly it's better to just access it over the Ethernet network with CD/DVD drive sharing, although only a Mac can share HFS format CDs.

AAUI was featured on a number of machines, starting in the days of the Quadra 700 and is simply Apple's re-implementation of AUI into a smaller port (the cases of the NIH Syndrome were common back then, and still are today with Apple). The Quadra 610 DOS Compatible shown below has two adapters pictured: one is a simple RJ45 adapter and the other is a four-port hub meant for Workgroup purposes. For most individuals, an adapter alone should suffice. Fortunately 10BASE-T started showing up in later Macs and the AAUI connector was dropped. Incidentally enough IBM made some Ethernet cards that had AAUI, 10-BASE-T and 10BASE-2 on the same card for the PS/2 line. These had MCA bus connectors on full-length, full-height cards which look like ISA and PCI based cards. Otherwise, nobody really had intentions of adopting Apple's AAUI other than firms like Farallon which made AAUI adapters. (IBM called it "Mini AUI" rather than AAUI. Adapters were about 40-60$ USD, about the same price for PCI RJ45 cards, and a LC PDS card cost about 95$, based on a 1999 online ordering list from www.warehouse.com. Memory was also shockingly expensive -- a 128MiB PC100 SDRAM 100MHz module cost about 700$ (1200$ for a 256MiB variant), and a 4MiB 30-pin 80ns SIMM still cost about 80$ in 1999, and double the price there for a 16MiB module. Back in the early '90s, 16MiB modules cost about 500$ each, compared to about 200$ for a 4MiB 70ns non-parity SIMM.)



Rear view of a SE/30 with Ethernet



A Farallon StarConnector AUI to Ethernet adapter



Quadra 610 DOS Compatible with AAUI

(courtesy mcdermd at 68kmla.org)

Classic II with Asante Desktop EN/SC

and LaCie CD-ROM drive

Some routers will not work with the 10BASE-T 10Mbps interface that these machines use (both a Farallon iPrint LT and a UltraDock 16sce were identified in a router control window as using 10Mbps half-duplex mode). This can be avoided by either using a 10Mbps switch between them, or using an Ethernet cross-over cable if only two computers are involved. However, a router can be advantageous due to its ability to permit all units to access the Internet, and the author observed greater stability with a router rather than a cross-over cable.

When installing the Ethernet card or dongle, ensure the machine is off to avoid any gotchas or electrical problems, and discharging any static electricity is very good idea (a casual jolt of 400 volts is enough to cook ICs). For a compact like the SE/30, remove the four screws on the back of the SE/30 using a long (15 to 20cm shaft length) T-15 Torx: a dedicated screwdriver works better than a hobble-job of adapters that may not fit the holes near the carry handle. Do not use a hex Allen driver on these Torx screws. Compacts can vary in their difficulty of opening the case, so you may have to remove all the screws, invert the unit over something like a couch or a bed and shake the rear cover off. Install the 030 PDS card and replace the cover. Most other machines should be just simple plug-in affairs aside from NuBus cards, which are pretty much the same thing as installing PCI cards.

Once the hardware has been installed, the Ethernet wiring should be fairly straightforward. A cross-over cable is required for direct computer to computer connections (much like a null modem cable) and AFP bridges, but a straight cable is required for a router or switch. Follow the directions from the modem (if the modem and router are integrated), router or switch for configuration if any are in use, as this Guide will assume that these hardware units have already been configured beforehand. The Mac Driver Museum, if it's still online, has a nice library of drivers for a variety of old Mac cards and hardware upgrades like accelerators. The MacGUI website might also have some variants as well.

Serial Port Options

The serial ports on the older Macs are divided into the Printer and the Modem port. Later Macs incorporated both into a "Modem/Printer Port" and the last generation of machines with this interface had GeoPorts which have an additional pin to supply 5v at 350mA max. LocalTalk hardware mainly consists of either mini-DIN-8 cables, LocalTalk splitter boxes, or better, PhoneNET hardware. More information concerning this subject is found in the LocalTalk Networks section. However, there were a variety of LocalTalk to Ethernet bridges produced "back in the day". These include models like the Asante series, the Farallon iPrint LT (the SL model is apparently only for StyleWriter printers) and other models such as Dayna products; the Farallon units work directly with PhoneNET so they are more desirable; whereas the Asante boxes require a Mini-DIN-8 cable. They are fairly common and are a good tool to have around, but they only work with AFP over AppleTalk (not AFP over TCP/IP) and will not work with terminal applications like MacTerminal or ZTerm, nor TCP/IP services like FTP or WWW protocols.

The GeoPorts were originally intended to be used with GeoPort (Mini-DIN-9) compatible modems, but in actual practice these modems turned out to be so inferior that they were ditched en masse. The GeoPort "extra pin" draws power off the ADB power rail, just as a note: PowerBooks don't supply as much power to the ADB bus as the desktops do, and drawing more than 100mA is probably not a good idea. PhoneNET adapters do not use this pin, and do not support external clocking. Otherwise, most Macs have Mini-DIN-8 ports and are suitable enough for most purposes. The Macintosh 128K and the 512K/Ke are given DE-9 RS422 ports, these require a different adapter for PhoneNET and Apple official LocalTalk adapters, along with a different adapter for old RS232 DB-25 modems (as was used back in the day).

Other than the extra power supply pin, GeoPorts have the same identical pinout as a regular Mini-DIN-8 RS422 port found in every Mac from the Mac Plus forward (well, the chipset that controls the port is quite a bit different, but that's not a detail that is important right now) and can use all the same serial AFP bridges, PhoneNET adapters, et cetera that a normal Mini-DIN-8 port can use.

There are a couple of Ethernet bridges that communicate over the LocalTalk port which can route TCP/IP traffic, known as hardware MacIP routers. Sample models would be like the Cayman Systems GatorBox, Farallon StarRouter, the Shiva FastPath 5, the Farallon EtherWave Mac/PB adapter (some models are just AAUI to RJ45 adapters, so keep an eye out for that detail, and this unit will not work with OT), and a few other odd ones; some like the EtherWave Mac/PB adapter can also overclock the serial port. The GatorBox also requires pre-OpenTransport OSs to configure it, like System 7 or 7.1. Some hardware MacIP bridges may not work with System 6, or have other quirks.

For serial data transfer options involving terminals, this Guide will be tailored to connecting to newer computers because LocalTalk can work directly between the older Macs. For machines without RS232 ports, a proper USB to RS232 adapter is the first requirement. (Both the DE-9 ports on the 128K and 512K series, and the mini-DIN-8 ports on all other Macs are of the RS422 flavor.) Apparently some cheap junk RS232 adapters do not supply the proper +12V (logical 0) and -12V (logical 1, may vary depending on hardware arrangements) required by proper RS232 devices, may have inactive pins (like DCD) or counterfeit driver chips which won't work with certain hardware but for our purposes, they might work but no guarantees are offered. The cheap ones just convert USB into +5V/-5V hoping to capitalize on the wide signal-high and signal-low tolerance of RS232.

The next step is a straight DE-9 RS232 cable and a Mini-DIN-8 cable for a manually wired crossover DE-9 to mini-DIN-8 adapter. This subject will be expanded on in the Serial Data Interlinks section.

Typically the older desktop Macs had two serial ports, called "Printer" and "Modem", yet PowerBooks were usually assigned just one. The serial controller, of Zilog make on the older Macs, can support two serial ports off of one controller, basically PORT A and PORT B. In the PC world this would be mapped out to COM1 and COM2 by the BIOS, and reported in Windows or MS-DOS as the same, but in UNIX systems this may be mapped to something like /dev/ttyS0 and /dev/ttyS1. It's basically such so that a Mac user could have plugged his (typical 2400bps, depending on the timeframe and how much he could afford, the dialup provider also had to support the bitrate) modem into the Modem port, but connected to a LocalTalk network for simple communication with nearby Macs and compatible LocalTalk printers. Switching between the remote modem and the local area network then becomes just a matter of software. Functionally the Modem port appears to be identical to the Printer port, although the Printer port is assigned for LocalTalk purposes, unless it is turned off or manually switched to Modem when OpenTransport installed. There could be low-level hardware difference between the Printer and the Modem port, as Inside Macintosh explains, particularly relevant to the 128K and 512K series:

The printer port should be used for output-only connections to devices such as printers, or at low baud rates (300 baud or less). The modem port has no such restrictions. It may be used simultaneously with disk accesses without fear of hardware overrun errors, because whenever the Disk Driver must turn off interrupts for longer than 100 microseconds, it stores any data received via the modem port and later passes the data to the modem port's input driver. (Volume II, Chapter 9, page 246)

A IIci was tested at 57600bps with AppleTalk off and hardware handshaking enabled off the printer port with a ZModem transfer and worked fine. Later Macs like these shouldn't have any such concerns.

Wireless Access

There are a certain number of RJ-45 Ethernet to 802.11 WiFi bridges like the NetGear WNCE2001, or routers with custom firmware like "tomato" to enable a "Wireless Ethernet Bridge" feature, and these ought to work fine. Use a modern computer with a good browser to configure them because they have "bloated" configuration panels that are accessed via a browser, like most routers and modems are these days. Suppose it beats DIP switches and modem INIT strings, though.

For PowerBooks with PCMCIA cards, this feature hinges (apparently) on a small number of compatible cards and the whole process is best explained on this site intended for the 1400 and this other one here which seems likewise beneficial. AirPort cards were an option on some of the later PowerBooks, iBooks, and iMacs, and they only support 802.11b at 11Mbps data rate, and they only work with unencrypted, WEP, or WPA-TKIP networks. AirPort Extreme cards are required for the 802.11g (54Mbps) and WPA2 encryption, and they are not substitutable. Don't bother getting 802.11b CardBus cards: 802.11b can only handle 11Mbps, which is not even faster than USB 1.1 in high-speed mode. Instead, track down a 802.11b/g CardBus for Macs with CardBus, and for those with just PCMCIA 16-bit slots, a card which has drivers that will work with 7.5 or 7.6. Those can be hard to find. Cards compatible with OS X can be on shaky ground, as most drivers are kernel level, once they get unstable, they usually take the whole system down with them. It all depends on the driver.

A Lucent Technologies ORiNOCO Silver 802.11b card was examined and tested with a 1400cs in Mac OS 7.6.1. The notable points are: it requires a reboot if the WiFi Access Point is changed from one to another (it's entered into a text field, there's no list of accessible APs: make sure it gets entered correctly) and the control panel is rather crude in appearance. Encryption was not tested. As far as drivers go, the one named "WaveLAN Installer Disk" (download name is apt6041i.hqx) will be compatible with 7.5.2+ and either MacTCP or OpenTransport. Read the Read-Me file for instructions.

The other known drivers in circulation are the ORiNOCO 7.2 and 6.3 drivers. Version 7.2 won't work with 7.5.3, it will probably require 8.5 since it complains about the lack of "AppearenceLib" with OT on and "OTUtilityLib" with it off. Then in Mac OS 8.1 it says it can't find "ControlsLib"...so much for their spec sheet. On the other hand version 6.3 said it wants 8.5.1 or later. It's still a good card to have though, because it's on the Newton WiFi card list (assuming the custom driver) and because of its compatibility with 7.5.3, plus they're not that difficult to get.

Ad-hoc direct WiFi computer to computer networks can be functionally unreliable. Avoid using them to interface with these older systems.

Software

The following list details the software specifications that was used with success for the remainder of this Guide. More information and tips relating to the install procedures can be found in the More Info section.

Note: The installation of AppleShare Client 3.7.4 inhibits the use of Classic Networking in 7.5.3-7.5.5, because while ASC 3.7.4 is installed, OT 1.1.2 or later must be installed for it to be active, and MacTCP doesn't "provide" OpenTransport services. If you wish to use MacTCP in 7.5.3+, then do not install AS 3.7.4. Also, there is an update to OT 1.3, which apparently fixes some "dead space" inside the resource files. This is OT 1.3.1 Update, but it works fine without it. ASC 3.7.4 and OT 1.3 are really only required to hook up to 10.3 and 10.4 - otherwise, the standard install is fine to work with Jaguar.



Depending on the specific software setup in question, the standard NSI installations may not work for that hardware. For instance, the Newer Technologies UltraDock products require proprietary software drivers, as do most Asante Ethernet cards for the SE and SE/30 platforms. However the NSI software should be installed before the driver software, regardless. Technically MacTCP isn't required for local EtherTalk communication but it's a really good idea to install it for WWW, FTP and other services. Additionally, it was found that the default install of EtherTalk software from System 7.0.1 worked with two separate Farallon NICs and an Asante NuBus card: but installing the latest drivers is still suggested.

1 MacTCP v.2.1 is cleaner looking and should be used instead, although this is not mandatory.

2 Certain Macs require machine-specific (gray) discs that are unique to a particular machine model, such as the iBook G3 800/900MHz and the iMac G4 700/800MHz computers. These have system extensions and drivers that are required to permit them to operate correctly, usually concerning Mac OS 9.2.2.

Assorted Notes

The first recommendation of this Guide is to download, back up the .iso, and burn a copy of the Legacy Recovery CD here or from another source. It is a 7.6.1 bootable CD and is chock full of useful disk images and software versions like the System 7.1 binary for the Macintosh TV. This package of MacTest Pro has some helpful Emergency bootable disks for troublesome systems.

The Legacy Recovery CD is immensely helpful aside from the fact that it has all the disk images stored as NDIF Read-Only Compressed format. Only Disk Copy 6.1.2 or higher can process them. Use an emulator to convert them to NDIF Read-Only or Disk Copy 4.2 format if required. Browse the Working with Disk Images section of the More Info page for more detailed text on this issue. There are other mirrors and sources for software, when this Guide references software available, it usually can be found at www.macgui.com or the Macintosh Garden. At the present time, this dump of Apple's legacy downloads (just browse the contents by clicking the little [contents] link), max1zzz's mirror and this Australian mirror seem to be good to go. (The last one has FTP access, too. For Fetch 2.1.2, use ftp.iinet.net.au for the Host, username can be left alone at anonymous, password field empty, directory would be /pub/apple.)

Some quick transfer rate data for networks (individual usage figures may vary) can be found in the More Info section here. More trivia: The SE/30 can push memory around at about 5MiB/sec (spec says 15.67MiB/s, compared to a IIfx, which specs 60.69MiB/s), which is part of the reason for RAM disks running faster, plus there is no SCSI bus to go through; and a standard SCSI hard drive of this vintage has a throughtput of about 3MiB/sec maximum (more around 2.5MiB/sec).

In the former days when cathode-ray tubes (CRT) were dominate, screensavers were commonly used to provide insurance against burn-in. Burn-in is a concept where an image that gets too much continuous exposure on the display becomes "highlighted" against the display. The effect was not as pronounced in the later Trinitrons and other monitors made in the late 1990s and early 2000s but by that time TFT displays were starting to get cheap enough that CRTs, with their bulk and power disadvantages, were regulated to the dumpster bins. Among the vulnerable classes are Compacts because their 1-bit displays spend a lot of time drawing a white menu bar. Bad cases will have visible "ghosting" when the unit is off and really bad examples will have ghosting artifacts visible when the unit is on. The damage is permanent and cannot be repaired. LCD displays do not need screensavers, although they were sometimes used for aesthetic purposes. This also dates back in the golden years of After Dark with numerous creative modules, some were games (like Lunatic Fringe), others were iconic (like Starry Night and Flying Toasters), some were artistic with geometric and arithmetically inspired graphics, and so on.

Common screensaver utilities included After Dark, Flex, Pyro!, Basic Black and other programs. Some were simple and lightweight affairs meant to minimize space on disk. There are no known screensaver programs or DAs meant for the 128K series, so you'll just have to crank the brightness all the way down.

While we're discussing displays, passive matrix displays were often used on notebook computers. Commonly identified by their sluggish refresh rates, ghosting and weird lines projecting from objects. Contrast had to be adjusted on a semi-frequent basis (depending on the image on the display, color depth, the desktop background, environment, lighting, et cetera) but fortunately they usually had hardware based adjustment methods. Color passive matrix displays are even trickier to adjust the contrast to balance out the color elements to minimize artifacts but the panel on the 1400cs is noticeably better in grayscale than the Duo 230's. Not recommended for precision color work...Also the viewing angles, contrast ratios, color balance, et cetera were all rubbish by modern standards. Still, you won't see an equivalent of the 640x400 electro-luminescent yellow-on-black display of a Dynamac or the cool red gas plasma display of a Compaq Portable III (later Portable 386 as well) on a modern computer.



Dynamac with a 10-Year Apple Award

(for Apple employees)



Electro-luminescent display

close-up view



A prototype Colby Systems Walkmac



Gas plasma display



This particular Dynamac is owned by Haplain at 68kmla.org, as part of his collection. Few are known to exist, much less with the original box. It's based on a Macintosh Plus (not the rumored version based on a Macintosh SE) and features 4MiB of RAM and the original 40MiB hard drive, with a mouse just like it would have come from Dynamac Computer Products. Back in the day (around 1988), this unit as configured, would have cost over 6,490$, and that was with 1MiB of RAM and a 40MiB hard drive: adding more memory would have stacked the price tag even more. Memory was around 150$ per mebibyte back then. The Infoworld review (August 8th, 1988 publication, Volume 10 Issue 32) of this model doesn't say the memory capacity of the unit they tested. Another Chicago Tribune article says a Dynamac with 4MiB of RAM and a 40MiB hard drive could have been acquired for an eye-popping 8,000$, which could have been saved for a really nice upgraded SE/30 just six months later and which weighed just a little bit more. More of Haplain's personal collection can be found at his homepage. The clear backlit Macintosh Portable M5126 in his hands is certainly a thing of beauty, for sure.

Only 68000, 68020 and some 68030 processor equipped machines can boot System 6, practically the 512Ke is the lowest machine that can do so. There are no 68040 Macs that can boot System 6: although a 68030 host with a hot-shot 68040 accelerator like a Daystar Turbo 040 (especially if it is the 40MHz version with a 128KiB cache) will be "wicked fast": add plenty of RAM and run everything entirely in RAM for a new perspective on computing! System 6 is a good primary operating system for the older Macs like the Plus, with System 7.0.1 held in reserve for special cases; but 7.1 does offer additional benefits like a Scriptable Finder (v. 7.1.3, comes on the 7.1 Pro disks). For all other 68K Macs that can handle System 6, it is a good system to keep for special scenarios like handling 400KiB disks, and certain applications like Airborne! or Microsoft Works 2.0 which require System 6; otherwise, System 7.0.1 or 7.1 is a more useful primary operating system. Most of the later 68030s like the LCIII and the Duo 230 require System 7.0.1 or 7.1. Early PPC 601s usually want 7.1.2 minimum, but starting with the 603e they all wanted 7.5.3 minimum, as a general rule.

In Mac OS 7 thru 9.2.2, Program Linking is an option available in the Sharing Setup control panel (also known as File Sharing starting with Mac OS 8). Program Linking is for certain applications which can be linked over a network in certain ways. See this Apple KB for more on this. Generally, it is not required and is not needed to play network games, either. Remember that the application must be enabled as well in the File/Get Info menu (or File/Sharing...), and also should be compatible (i.e. SimpleText is not compatible, but WordPerfect 3.0 is).

There is a great library of Alexandria Type and Creator information within this software (best used with Mac OS 9 or early OS X like Jaguar). It must be stressed that the full database requires a purchase of a key, plus the Panorama DB software has to be registered as well. (Related version. Can be saved as a text file, then imported into a spreadsheet.) Creator Changer 2.8.4 or ResEdit with the "Get File/Folder Info..." can change these codes: Finder Info 1.1.1 and early versions of ResEdit like 1.3D1 can edit these in System 6 and some earlier systems. Creator Changer is not really necessary for the occasional tweak, and ResEdit has more utility. On the other hand Creator Changer (and a few others in its class) do let users store "kinds" so it can be faster, if that is important.

According to this site, MacTCP originally came with the Apple Internet Connection Kit (also known as the Macintosh TCP Connection Kit) and retailed for $50. It also included MacPPP for dialup and some other goodies.

It could have been had for a little as $25 with the Internet Starter Kit...or by buying 7.5, which retailed for about $99 to $129 back in the day...and plucking it out of the System Folder...as it is just a control panel...(7.5 did not include PPP though).

At Ease was an Apple product that was basically the Launcher control panel (System 7.5+) made into a Finder substitute. It would be easy to conclude that it was meant for setups like kiosk computers, library computers, and other reduced or simplified computing arrangements. There is a way to add a network share onto the list of applications/documents on inside At Ease, but the shares don't seem to be capable of browsing, but with proper permissions (and likely At Ease 2.0.x and up rather than At Ease 1.0) users can use the Open dialog inside applications to open documents inside remote servers.

According to the At Ease 2.0 documentation, file sharing is disabled under the At Ease environment, so other computers won't be able to access the At Ease enabled machine. The Chooser can be added to the Apple menu of course, but the remote share won't be navigable, so it's pretty much a waste of time. At Ease for Workgroups is supposed to have greater emphasis on multi-user situations with At Ease, and it is supposed to be slightly better in the remote share department, but the author couldn't quite figure out the process for actually navigating a remote share like the regular Finder.



At Ease 1.0 (2.0 and 3.0 similar)



Best that could be done (At Ease 1.0)



Launcher (7.6.1)



For System 6 and 7.0/7.1, try to avoid handling volumes that are larger than 2GiB (2,097,152KiB, 2048MiB) because HFS in these versions cannot address more than 2GiB volumes. 7.5 has support for 4GiB volumes, and 7.5.2 (immediately replaced by 7.5.3) supports up to 2TiB (see the External Links section for more on this).

Note that these older file systems used the "classical" interpretation of MB and KB where 1KB is 1024 bytes and 1MB is 1024KB (or 1024 x 1024 bytes), not the modern IEC-approved idea which says that 1KB is 1000 bytes and 1MB is 1000KB (or 1000 x 1000 bytes). The "modern" translation of the "classic" 1024 definition is the KiB, MiB, or GiB; this Guide will use the modern definition. (Obligatory comic here) The exception will be with 1.44MB floppies, because while they are actually 1,474,560 bytes, the math was calculated to mean 1474560 divided by 1024 and divided again by 1000 to produce a result of 1.44MB. So while this author would prefer to use 1.40MiB, convention will prevail for the sake of conformity. Plain and simple, 1KB is 1000 bytes, 1MB is 1000 KB, and 1GB is 1000MB; 1KiB is 1024 bytes, 1MiB is 1024KiB and 1GiB is 1024MiB.

A cheat for Windows 2K Server which seemed to have the most issues concerning this brick wall is to format an SD card or USB thumbdrive as NTFS (Windows XP can't do it, but Windows 2000 can, and only NTFS volumes can be shared with the SFM service: or use something like gParted in Linux) and put a share on that volume if it's less than 2GiB. Or, use Netatalk inside a VM. Certain Macs can create RAM disks through the Memory control panel, which then can be easily shared as long as it is 2MiB or greater in size. Jaguar can format a Flash volume, e.g. USB thumbdrive as HFS Standard but 10.3 Panther and above won't do it.

SharePoints is an addon to Mac OS X 10.1 thru 10.4 which allows the creation of additional share folders, just like in the old Finder of System 7 thru OS 9.2.2, where users could share any folder they desired. The addon can run as a program or as a .prefpane inside the System Preferences application. Folders can be easily configured for SMB (Windows, Linux) computers to access or AFP purposes. The images below give a sample of what it looks like under 10.2 Jaguar. An attempt was made to share a non-logical disk, a USB thumbdrive and a mounted disk image on the computer, without success.



Shares overview



Users and Public folders



Groups



AFP settings



SMB config



The name "Workstation" tends to be associated with "client" and in System 6 and earlier systems, two clients cannot communicate with each other. In such case, there must be a server (AppleShare Server 2+ or any System 7+ machine) to provide the files and the clients must use that as a central communication hub. AppleShare for clients was called AppleShare Workstation from version 1.0 up to 3.6.5, starting with version 3.7 it was renamed AppleShare Client but they are the same overall thing.

In the event that a program has frozen the computer, activating the programmer's interrupt (varies according to machine in question) and typing

G Finder can sometimes work. If Macsbug is installed, striking the interrupt switch calls up Macsbug. Typing es attempts to quit back to the Finder. Saving any important work and restarting the computer promptly is a highly recommended procedure because the memory is usually in a unstable fragmented state. An alternative technique is to use the ExitToShell trap. Some Macs do not have physical interrupt/reset buttons, like PowerBooks. Use the Command + Control + Power button reset (reboot) the machine: Command + Power is the same thing as the interrupt feature.

Gamba has prepared an interesting table here that describes some alternative applications that can mimic AFP networking. These avenues will not be explored as part of this Guide, except for EasyShare. JC Remote is very unstable and can only link up to another computer with JC Remote installed.

CheckNET is a utility developed by some Farallon developers to help diagnose AppleTalk networks, and it came as a DA for System 6 and a standalone program for System 7. It will report both EtherTalk (AFP over Ethernet) and LocalTalk traffic, but it has very limited usefulness. For instance, only a certain select few computers will be compatible with it, the rest will kick an error dialog saying that it can only query "Responder-compliant sockets". Responder was a system extension which would "respond" to diagnostic programs back in the former days. It's not necessary for regular network function and can be safely ignored and deleted. The nearby image shows what it looks like with Windows 2000 Server, Netatalk with Apple II services and a CD share, OS X 10.2.8 Jaguar and a Macintosh LC over LocalTalk. Of those systems, only the LC could provide any system information whatsoever, and a test with Mac OS 9 wouldn't respond to the system information query. Mac OS 9 does have a few additional entries, like "ARA - Personal...", "SharewayIP" and "Multi-User Cli...", but other than those it looks the same.

The utility comes on on a Compact Pro self-extracting archive on a Farallon EN Installer disk in the Utilities folder. It could probably be useful for really big AppleTalk networks but it won't be applicable to smaller ones like what most folks are going to be using these days.

About AppleTalk zones. A zone is a method of dividing up servers into manageable areas, generally used with big networks. For instance, a newspaper company may have a number of zones, such as Management, Research, Printing Department, Public Relations and so on. Computers were assigned into a specific zone based on their intended purpose. Zones are created in two nominal ways: software or hardware. A *NIX system with Netatalk, Windows Server with Services for Macintosh or a few other server or routing software are examples of software configured zones. They can be created in hardware with routers like the Cayman Systems GatorBox. While obtaining proper reading material which adequately discusses the subject is hard to find, it is fortunate that most users will never have to approach the subject, especially these days because few will make an AppleTalk network big enough to warrant zoning. A computer network with more than twenty computers is probably eligible, though. In TCP parlance, a AppleTalk zone is the same principle as a large network with different subnets for a multitude of smaller networks.

It has come to light that Mac OS 8 and later will unbless older Systems like System 6 if they are mounted (like a floppy disk). Make sure to have an extra bootable floppy or lock the disk to insure against this occurrence. The principle of "blessing" is designating a folder as bootable, and this is usually indicated by a tiny image of a Compact Mac inside the folder icon. A folder must have certain minimal elements to be bootable, two being System and Finder. Opening the folder and then closing it should update it. For emergency purposes, a Disk Tools disk can help, or the 7.5 Network Access disk, a bootable CD, or in extreme cases, imaging the disk, blessing the System Folder in an emulator, then writing it back out again. The OS X terminal command bless is mainly for OS 9 situations: read the man page.

When a device has driver support for "Mac OS 8" that usually applies to Mac OS 8.6, because that is when USB support came into fruitation. Also when most people mention "Carbon" programs for Mac OS 8, that essentially suggests 8.6, although 8.1 can also run some Carbonized applications.

And one last thing. Avoid using composite memory modules in Macs. They are easily identified as far as 30-pin SIMMs go because a regular SIMM has eight chips per SIMM, nine if it is a parity RAM module which most Macs won't even use the parity function. A composite SIMM has typically two chips per SIMM or three if it is a parity module. Unexplained crashes, freezes and other unusual events, if they are not related to bad traces, dying hard drives, shot capacitors or other common hardware issues, could point to the RAM modules.

So let's get started.

AFP is the default for Mac to Mac interconnection, and it went through quite a number of major versions, rendering some incompatible with others. The Chart, as we will call it, will be an attempt to showcase the various compatibility across various software versions. Start by picking a System Software version on the leftmost column and read the row across. The "connectible" OS is the one that the System can mount to its file system: for example, OS X 10.4 Tiger can mount Mac OS 9 or higher on its desktop; anything "lower" and it will not work. However the 10.4 Tiger platform can be mounted on a 7.5.3+ system if configured properly with TCP/IP services.

System Software Lowest connectible Mac OS via Apple Filing Protocol Highest connectible Mac OS via Apple Filing Protocol Windows 2000 Server with SFM; Linux (Netatalk) Other protocols compatible with all machines System 3.3, Finder 5.4 (512K, 512Ke) up to System 5.1 (S4.3, F6.0) with AppleShare WS 1.1

EasyShare Demo

AppleShare File Server (ASFS)

2.0.1 (see note); System 7 9.2; 10.2, except 10.0 (see note): AFP bridge may be required

AppleShare IP 5 & 6: read only Not compatible ; AFP bridge required Terminal Software; SLIP; TOPS Terminal System 6, 7.0, 7.1, 7.5.0-7.5.2

AppleShare WS 3.5 (see note below) EasyShare Demo

ASFS 2.0.1

System 7 10.0 lacks EtherTalk drivers

10.1, 10.2 AFP bridge, Ethernet; AFP bridge, Ethernet, Ethernet>WiFi bridge LocalTalk; LocalTalk PC; SLIP; PPP; FTP; Telnet; SSH in System 7+; Terminal Software System 7.5.3 to 7.6.1

ASC 3.7.4, OT 1.3 (7.5.3-7.5.5)

ASC 3.8.3, OT 1.3 (7.6.1) EasyShare Demo

ASFS 2.0.1

System 7 10.4 AFP bridge, Ethernet; AFP bridge, Ethernet, WiFi LocalTalk; LocalTalk PC; PPP; OT/PPP; FTP; Telnet; SSH; Terminal Software; this Apple KB Mac OS 8.1 to 8.6

ASC 3.8.3, OT 1.3 (8.1 only) EasyShare Demo

ASFS 2.0.1

System 7 10.4; 10.5 can be accessed only by Guest account

Modified: 10.10 AFP bridge, Ethernet; AFP bridge, Ethernet, WiFi LocalTalk; LocalTalk PC; OT/PPP; FTP; Telnet; SSH; Terminal Software; this Apple KB Mac OS 9.0, 9.1, 9.2 EasyShare Demo

ASFS 2.0.1

System 7 Default: 10.5

Modified: 10.10 AFP bridge, Ethernet; AFP bridge, Ethernet, WiFi LocalTalk; LocalTalk PC; OT/PPP; FTP; Telnet; SSH; Terminal Software; this Apple KB OS X 10.1 Puma

OS X 10.2 Jaguar

OS X 10.3 Panther 10.1 and 10.2: System 7

10.3: System 7, with FSE 7.6.2

AppleShare Server 3, 4, IP 5 & 6 10.10 Ethernet; Ethernet, WiFi SMB; FTP; SSH; Terminal Software; Samba (Linux) OS X 10.4 Tiger

OS X 10.5 Leopard

OS X 10.6 Snow Leopard Mac OS 9.0

AppleShare Server IP 5 & 6 10.10 Ethernet; Ethernet, WiFi SMB; FTP; SSH; Terminal Software; Samba (Linux) OS X 10.7 Lion

OS X 10.8 Mountain Lion

OS X 10.9 Mavericks

OS X 10.10 Yosemite OS X 10.10 Not compatible, use SMB; Ethernet, WiFi SMB; SMB2 (10.9+); FTP; SSH; Terminal Software; Samba (Linux)

Zip disks are good, if they work, and are reasonably fast. The only one the author got to play with had serious troubles formatting and using it, with system freezes and lockups with and without the Lido 7.56 driver. This sounds abnormal because many have spoken highly of the Zip drive peripheral. To sum up, if it works -- it is fantastic for a Plus. If not -- it can provide major headaches. Some form of preserving any valuable disks, such as with a disk image utility, is prudent. Use the Desktop Manager INIT for System 6 to stop it from needlessly rebuilding the Desktop File for those who have System 7 onboard with System 6. Always keep some recovery floppies on hand should things go haywire.

System 6 through Mac OS 9.2.2 Setup

Here are some important notes for this chart:

Classic Networking refers to the use of MacTCP for external communication over TCP networks. LocalTalk is independent of this, aside from MacIP routing which works differently than the other interfaces: the Network control panel (Classic Networking) or AppleTalk control panel (OpenTransport) is for selecting the interface for AFP to use and has nothing to do with TCP services except when AFP over TCP is used. LocalTalk could be used over the Printer port for instance, yet have TCP services going out through an Ethernet interface. Only with AppleShare IP, Mac OS 9 or OS X does the TCP/IP configuration become significant. MacTCP has no influence whatsoever on EtherTalk or LocalTalk traffic, and the same goes for OpenTransport -- until 8.x with AppleShare IP 5 or Mac OS 9 (with or without AppleShare IP 6).

System 7.5 can use either Classic Networking or Open Transport Networking through a switcher application called Network Software Selector. This application is proprietary to 7.5 and is not compatible with System 7.1 or below, or 7.6 and above. (The only way to switch to Classic Networking in 7.1 is to uninstall OT, or run two duplicate OSs, one with OT and the other without.) Open Transport gobbles more memory (about 760KiB in 7.5.5, which could pinch those running on 4MiB ceilings) and isn't required unless more powerful Internet requirements demand it, or hooking up to 10.4. System 7.6 and above have OT running full time and cannot use Classic Networking or MacTCP. Open Transport simplifies compatibility issues with modern Internet requirements. It is still possible to "go online" with a Plus and MacTCP but it is not very useful or pragmatic due to the memory limitations and the real performance drag. FTP still has a good presence though.

For historical purposes, copying MacTCP to a 7.6 OS (where OT was not installed from the Installer) in an attempt to run TCP services outside OpenTransport causes the operating system to immediately hide the control panel. This can be reversed by using ResEdit to unmark the Invisible flag. Then it turns out the OS changes the type to ???? from its proper designation of cdev (creator is ZTCP). Again this can be overridden with ResEdit but the System will promptly refuse to open the control panel and returns two error dialogs on the display (with a Duo 2300cTB); another experience produced two results: AppleShare wouldn't start because it complained about the OT deficiency, and Fetch 2.1.2 kicked an error saying it needs either KSP or MacTCP installed (even though MacTCP 2.1 was already installed and configured).

MacTCP

This subsection applies to System 6, System 7 and 7.5 with Classic Networking enabled (default after a fresh install of the OS). We'll set up this side first, and then we'll go into how we set up the other side(s).

For System 6, first head to the Chooser and turn on AppleTalk, then set a machine name in Chooser, then open the Control Panel DA. Open Network. Select EtherTalk. For SSW 7 and 7.5, enable AppleTalk in the Chooser, then open the Control Panels folder and bring up the Network control panel, set to EtherTalk. For both systems, open MacTCP.



For MacTCP 2.0.6, then under "Obtain Address" select Manually. Under "IP Address" set the Class to "C". LAN networks won't need anything for the DNS information, but for internet access, this information is required. (See the Internet section for more on this subject.) If you do know it, then put a period (full stop) under Domain, followed by the DNS address. For the example on the right, 192.168.0.1 is the address of the DSL modem and 192.168.1.1 is the address of the router, while 192.168.1.110 is the desired Internal IP address in the same subnet as the router. Individual addresses and setups vary.

Under "Routing Information" put in the router address, if you don't use one (cross-over cable) then just put the Internal IP address of the host computer. Technical users may want to give this link a read over for special situations where the Server (used with PPP) or Dynamically radio buttons are appropriate. (The EtherTalk mode in MacTCP appears to only work with LANs, while Ethernet works with both WANs and LANs. Some odd units like the Farallon EtherWave Mac/PB adapter or Ethernet PCMCIA PC cards may have a "Alternate Ethernet" icon. EtherTalk is AppleTalk packets over Ethernet. LocalTalk is AppleTalk over a serial port. AFP over TCP/IP is an arrangement where AppleTalk data is encapsulated inside TCP/IP packets.) It is a common mistake to associate the "Server" mode of MacTCP with "DHCP Server": this is not the case. Server mode is used with hardware MacIP routers like the GatorBox which assign the client a specified IP address from a pool of IP addresses, or with PPP which does a somewhat similar affair.

For MacTCP 2.1, select Manually, enter in 255.255.255.0 in Subnet mask, enter in the DNS info if you have it on hand, and press Okay.



After that dialog box, enter in the Internal IP address in the small text box below the connection options. If you're on a LAN and want to hook up to another Mac or computer, then both must be in same subnet. (Subnet example: 192.168. 2 .10). The node (last digit set) must be individually assigned to a different number. Two computers can't have the same internal IP address of 192.168.2.5, but rather set one to something like 192.168.2.5 and the other to 192.168.2.8. If the computers involved are going through a router, then they all must be on the same subnet as the router, lest they won't talk to each other. Should all this be still unclear, refer to this image which might clear things up.



MacTCP with System 6



System 7 using MacTCP



Users and Groups (System 7+)



Sharing "Transfer F" (System 7)



Accessing a CD volume in SSW6



To enable File Sharing in System 7, open Sharing Setup in the Control Panels folder, enter in a username, a password (recommended, even if it's just "123", some programs and clients don't work so hot without one), set your machine name, and turn on File Sharing. (File Sharing enables sharing of all volumes 2MiB and larger. This may prevent them from being removed or ejected, like Zip disks. Turn off File Sharing first. For OS X, just use lsof in the command line.) Next, open Users and Groups. If you want to add a new user or login for outside users, then head to the File menu and select New User or New Group as required (a group is just a pool of users). For Guests to connect (helps for greasing the wheels in a LAN) then open that profile and set the appropriate preferences. Head to the Finder. Select a folder or volume you wish to share on the network. Open the File menu, then Sharing... and configure it to the desired preferences.





From here, head into the Chooser to hook up via AFP. Select the target machine name and press OK to commence login. If you want to login with full owner privileges, then enter the target computer's Owner username and password, then press Okay. If you login as a different user, then enter in those details and continue. Multiple volumes can be mounted at the same time with by using the Shift key to select multiple mountable volumes, or re-logging in again.



Under System 6 (and earlier systems with AS 1.1) user privileges can be seen with the Access Privileges desk accessory in the Apple menu. It is not present in System 7+ and only works when the computer is connected to another server. Other folder or volume permissions can be examined with the "View Another" button. (System 4.1, Finder 5.4 with AppleShare 1.1 shown, all others identical.)

MacTCP and Systems earlier than 7.5.3 with an AppleShare version earlier than 3.7.4 do not have the "Server IP Address..." button in the Chooser (even 7.6.1 with OT 1.3 installed doesn't put it in, because the AppleShare extension included is version 3.6.4). AppleShare Client 3.7.4 requires OT 1.1.2 or later: the default install of OT in 7.5.3 is version 1.1. In AppleShare Client 3.7.4 and greater, hold the Option key whilst double-clicking a server to force an AppleTalk (EtherTalk, because it's AppleTalk over Ethernet) connection: the default in later servers and clients is AFP over TCP/IP.

Open Transport

Watch out for delayed File Sharing startup on 7.5.3 through 9.2.2. It can take five minutes or more to get File Sharing going.

Open Transport built into Mac OS 9 also included a special licensed limited edition of ShareWay IP Personal for tunneling AFP packets inside TCP/IP packets which can be activated from the File Sharing control panel.

Open Network Software Selector (7.5.3-7.5.5 only), and tick Using Open Transport Networking. Reboot the machine. (Classic Networking hides the TCP/IP and AppleTalk control panels when enabled, and replaces them with Network and MacTCP.)



Head to the Control Panels. From the AppleTalk control panel, choose Ethernet ("Alternate Ethernet" may be used in place of "Ethernet built-in" or just plain "Ethernet" for users of hardware like PCMCIA Ethernet cards for PowerBooks). Next, open the TCP/IP control panel and set TCP/IP to Ethernet, and Using DHCP Server. For a simple LAN file transfer, Manually works just as well and aids in connecting to from the client side (no hunting around for the IP address if it doesn't show up in the Chooser or Network "browser" in OS X).

Open Sharing Setup (also known as File Sharing in Mac OS 8 and above). Set machine and username, a password is recommended even if it's just "123". Start File Sharing. From the Finder, select the volume or folder you wish to share on the network, then head to the File menu, then Sharing...; on the newer systems, folder sharing is found under a tab in the Get Info window. The Guest login is enabled by finding the Guest user in the Users and Groups control panel and activating it by double-clicking on the user account. Otherwise, users login by entering the account details of a Registered User, which can either be the administrator or a custom profiled user which is created in the same control panel.





Now for all pre-OS X computers, they can mount each other on their respective desktops by using the Chooser (except System 6 and earlier computers, which have no file serving capabilities, only client access.)

Note: The Chooser does not permit passwords longer than eight characters unless the System version is 7.6 or higher with the Encrypted Password Transport method. In such a case, login as a Guest (if permitted) or temporarily change the password, or access from the other machine (if allowable). Sometimes the EPT method will be the only method of connection.

DHCP Server is used because it's the simplest, although it is not mandatory, though it is probably the better option for the broadest compatibility with Internet services. DHCP Server basically means the machine culls its IP address from a router or another computer. If you have difficulty making it all work, try setting things up manually, which works better for FTP and Windows, otherwise users have to hunt down the IP address when connecting as a client. As long as both computers are in the same subnet and have different nodes, they can work together -- and DHCP sometimes throws a curve ball by taking too long to assign IP addresses. If the Mac is "going online" to the Internet, then the Router Address field must be filled out with the address of the router or modem, otherwise it won't work.

Avoid relying too much on the TCP/IP control panel for internal network numbers. It might say "not available" or "will be supplied by server" but that doesn't mean it has no connection (see below, second image from left). Any IP address used by DHCP that starts with 169.254.xxx.yyy is a self-assigned IP address; therefore, if a router is being used, it means that it isn't connected to the router. Manual addressing can sometimes be better for those who know what they're doing.



Manual configuration



DHCP Server



Cleartext vs. Encrypted



Chooser view from client (Mac OS 9.2.2)



Under Mac OS 9 and higher, users can be allowed to connect over TCP/IP. Mac OS X uses the TCP/IP method, as previously the AFP data was straight over the AppleTalk protocol, but the TCP/IP method tunnels AFP packets inside the TCP/IP protocol instead. This setting is found in the File Sharing control panel. This setting can sometimes interfere with older System Software versions; in this case turn it off. Alternatively, try turning it off, mounting one computer, turning it back on, and mounting the other.



In Mac OS 8.5 and above, the Network Browser can be installed into the Applications folder. It's sort of a Chooser substitute.

File sharing locally and online Internet access simultaneously can be only done via special methods or by sharing the Internet connection over AFP in OS X.

Mac OS X Networking Setup and Establishment

For dual TCP/IP setups, ensure that the connection to the Internet has the Router Address field filled out, otherwise it won't be able to locate the router; because OS X can have a LAN on Ethernet for example, yet have WiFi out to the Internet. In this instance, leave the Router Address field blank in the Ethernet (if manually configured), and the DHCP setting in the WiFi configuration will automatically resolve the router address which has Internet access.

To share the Mac OS X's Internet connection over the network, enable Personal Web Sharing in the Sharing pane of System Preferences. Click the Internet tab. Set "Share your connection from: _____" to Airport, FireWire, Bluetooth or whatever is not Ethernet. Set "To computers using" to Ethernet. It is not possible to share an incoming Ethernet connection to an outgoing Ethernet connection: use a router for this instance.



Dual TCP/IP config (10.5)



Internet Sharing config (10.4)



10.4.11 Network pane with dual TCP/IP



Port 80 issue (7.6.1):

Fetch and Homer 0.94 can't

connect but Mosaic 2.0.1 can

Note that certain Mac OS versions will only accept Port 80 (http): it is not known at this time what the OS limitations are at this time, although 9.2.2 on an iMac G4 800MHz did not experience this issue (only HTTP, FTP and IRC ports were tested, others may slip through). Other computers running Ubuntu, OS X or Windows should work fine. Setting the host computer to manual addressing and the client to DHCP ought to work, though testing indicated that MacTCP can work as well. The client computers accessing the shared Internet will be assigned internal IP addresses as usual, but will share the external IP address with the host. For example, if the external IP address on the host Mac is 204.56.127.24, then the clients will also have this external address. (The image at top left shows a DNS address of 192.168.0.1, which is the address of the modem. The WiFi is enabled with DHCP and is going through a router with an address of 192.168.1.1.) For a manual client configuration, set the Internal IP address to one compatible with the host (i.e. a host of 192.168.2.2 and a client of 192.168.2.3), set the subnet mask 255.255.255.0 and the router address (gateway) and DNS server to whatever the host designates. Try using DHCP or a different computer to find out what the relevant settings are supposed to be for a manual configuration if you're using MacTCP (or use ifconfig from a Terminal window).

Mac OS X 10.1 Puma and 10.2 Jaguar

In the case of System 6 and 7, then go to NetInfo Manager (Utilities folder). Authenticate the user. Click config, then AppleFileServer. Scroll down until you see use_appletalk, and double-click the field next to it and change the value from 0 (false) to 1 (true). (Panther has this too, it may be needed for printers.) Save the changes with Command + S or from the Domain menu, then click the lock. Reboot the Mac. AppleTalk should have already been on prior to this, but this step enables a backwards-compatible version of AppleTalk for use with older computers.

(The remainder of this section pertains to 10.2, although 10.1 isn't that different) Next, open System Preferences. Click Network. Select "Show" to Built-in Ethernet. Set as either DHCP, or configure it manually with a compatible Internal IP address and a subnet mask of 255.255.255.0. If a cross-over cable is used between this Mac and the vintage machine, then set both to have the same subnet, but different nodes (such as 192.168.4.8 for one and 192.168.4.9 for the other); if a router is used, then both will share the same subnet as the router designates but maintain different nodes. Then enable AppleTalk under the AppleTalk tab. Head to the Sharing pane. Turn on Personal File Sharing. Enabling the Personal Web Sharing permits Internet sharing, which also needs to be activated in the Internet tab. For Guests to connect, set the proper permissions under Get Info for the volume or folder to share.

Open the Go menu, and select Connect to Server...; the target machine should show up after a little bit (System 6 cannot be mounted to 10.2's desktop because it has no server element). Double click it or click Connect and login. Easy as cake layered on pie.

From the other side, open the Chooser on the classic Mac and mount the volume.

In System 6, it appears that all mountable folders and volumes may locked (read only) in some cases. The Public Folder (write only permissions) may be the sole mountable volume unless SharePoints is used to enable additional folders. For System 7 and above, any shared folder or volume is available as a network share. Guests will only be able to mount the Public Folder unless full permissions are granted for Guests (Everyone). Be advised of the 2GiB volume limitation under System 6 and 7 as noted earlier in the Notes.

In 10.2 and above, while connecting to a server, the Options button can set some additional toggles, as shown below for a host of OS X Tiger.



Network configuration pane



NetInfo Manager editor



Connect to Server from Go menu



OS X Drop Box mounted on System 6



Connection options prompt



Mac OS X 10.3 Panther and 10.4 Tiger

Open System Preferences. Click Network. Select "Using DHCP" protocol, alternatively, setup a manual configuration with a compatible Internal IP address and a subnet mask of 255.255.255.0. Click the AppleTalk tab, and make it active. If AppleTalk cannot be enabled, then open Directory Access (Utilities folder) and enable it there, then go back and make it active: if it still cannot be active, then it is because AppleTalk can only be active on one interface at a time (i.e. WiFi or Ethernet, but not both).

For 10.4 Tiger only (10.3 does not need this step), click the Sharing pane. Disable Personal File Sharing. Open Terminal. Paste this into the command line:

sudo defaults write /Library/Preferences/com.apple.AppleFileServer TCPQuantum -int 327680

Enter the administrator's password. If it is successful, nothing unusual should appear.



10.4.11 Network pane



Network pane using DHCP



Terminal TCP Quantum hack



Sharing pane



Go back to Sharing. Enable Personal File Sharing. Then find the Home folder (~/Public/Drop\ Box for the Unix nerds) and open the Public folder, then Drop Box. Right click it or press Command + I for Get Info. Look down to "Ownership and Permission" and make sure that these settings are in line with the desired properties. For read/write access, "Others" should be set to "Read and Write", or set it up as the intended application allows. Alternatively, create users with various permissions, logging in as a Registered User.

Open Chooser on the Mac, and click AppleShare. The host Mac should appear; if it does not, click the "Server IP Address..." button and enter in the Internal Ethernet address. Select it and click the OK button, then login and mount the volume.



Password dialogue box



Mounted Drop Box (Guest login)



Shared Internet access with AFP



Mounted CD volume



As stated in the Chart, 10.3 Panther can mount a System 7+ server, even over an AFP bridge. If the System version is 7.0.1 or 7.1, then upgrade the File Sharing Extension to the one from SSW 7.5.3, version number is 7.6.2. Or, use AppleShare Server 3 or 4. 7.5.3+ won't need any such modifications. In Tiger, Mac OS 9 must enable the check box in the File Sharing control panel which will permit clients to connect over TCP/IP, otherwise it won't work.

Mac OS X 10.5 Leopard and 10.6 Snow Leopard

Mac OS 9 must have the "Enable file sharing clients to connect over TCP/IP" check box ticked to work with these systems as a server. If the check box is dimmed out, then dig into the install CD for the path /Mac OS 9/CD Extras/File Sharing Extras/ShareWay IP 3.0/ShareWay Applications/ and drag the ShareWay IP Personal Background into the Extensions Folder of the hard drive and reboot. Or, install the regular program there, but it's a 10-day trial version. Keep in mind that ShareWay IP Personal Bgnd can cause problems when the system is coming up from sleep. (Sleep can be hairy on pre-OS X systems. Some INITs and CDEVs are fine, others get destabilized and can lock up the system. File Sharing can also lock up the Finder when waking up. The author would go out on a venture and say that after Jaguar was when sleeping became "safe".)

Begin by opening System Preferences. Click the Network control panel. If you want to use DHCP for your network settings, then under the "Configure:" selection, choose Using DHCP; conversely, to configure things manually, select "Manually" and enter a compatible Internal IP Address as discussed earlier, followed by a Subnet Mask of 255.255.255.0. Click the Show All button or go back, and select the Sharing pane.

Then in the Services field, turn File Sharing on with the checkbox. Near the right area, click Options. Click the "Share files and folders using AFP" button. Click Done, then local access permissions can be tweaked in the field for this subject.

From the OS 9 system, set up the system as directed in the OpenTransport section earlier. Open File Sharing. Click the "Allow users to connect over TCP/IP" button. Open the Chooser. If the target computer does not appear in the AppleShare field, try entering the target address manually; then various directories or volumes depending on permissions are accessible.

To mount the OS 9 system on the OS X side, use the Connect to Server feature in the Go menu and use the internal IP address, like afp://192.168.3.21, as it won't appear in the Network "browser" viewable from any root level volume window.



Network pane



Sharing windows



Enabling AFP, SMB or FTP



File Sharing: TCP/IP setting



Editing folder privileges (10.5)



Sharing to pre-OS 9 systems with 10.5 Leopard, specifically concerning 8.1 through 8.6, has to be executed differently, because these older Mac OS versions can't log in as a user. Once AFP File Sharing has been activated, get the properties for a desired folder to share with the Get Info (Cmd+I) command. There's a checkbox for "Shared Folder" in the General field. Enable it, then click the little drop-down arrow toggle for Sharing and Permissions. Authenticate as an administrator by clicking the little lock icon in the lower right corner, then change the privilege for Everyone (meaning Guest users) to Read & Write for full access, or Read Only, or as desired. Click the lock icon and close the window when you're finished. The Public Folder is probably convenient enough to remember and use as a general share directory but remember to change the permissions back to No Access if you're going onto an insecure network or sensitive LAN. The Sharing pane inside System Preferences, as shown, allows convenient access to these properties and there is a little + button to add a new share directory, which will bring a prompt dialog to select one. 10.6 Snow Leopard will not work in this fashion because the AFP protocols are incompatible.

To enable file sharing with legacy systems with these platforms we'll have to make a slight change to the underlying operating system's AFP server program. Don't worry, it will be distilled down to Novice level. All credit goes to the users here (the actual process is explained on page 3, and has some technical detail which Expert users will appreciate).

For this operation, the AppleFileServer.app from 10.5 Leopard will have to be obtained. There are two ways of doing this: extracting it from a 10.5 install and then there is using a utility like Pacifist to extract it from the 10.5.8 Combo update from Apple. This section will go along the path of extracting it from a regular install. The procedure in twenty-five words or less is: Downgrade the AppleFileServer.app by copying it from 10.5 Leopard to the 10.6 through 10.10 OS X operating system. In the future, there is a possibility that this method could still work, but at the time of release, 10.10 is current.





Open System Preferences. Turn off File Sharing on the left hand side. Open the Leopard volume in the Finder, then navigate to the System folder, then Library, and lastly CoreServices. Keep this window on hand, then open the same path on the Lion or Mountain Lion volume or platform (/System/Library/CoreServices). Drag the 10.7 or 10.8's AppleFileServer to the desktop which copies it, then right-click (or Control+click for one-button pointing devices) and choose "Compress AppleFileServer". Drag the result, AppleFileServer.zip back into the Lion's directory (specifically, /System/Library/CoreServices) in case the original needs to be restored. Administrator authentication will be required. Delete the AppleFileServer on the Lion's volume, then copy the Leopard AppleFileServer into the Lion's aforementioned path.

Assuming the system has already been configured with the appropriate interface in the Network control panel (it's a lot like 10.5 and 10.6's), simply turn File Sharing back on and from there, the system is ready to be mounted on a older Mac client with Mac OS 8.1 or greater (8.0 was not tested because 8.0 is known for instability). Advanced users: Compressing into the Zip archive removes the ownership of the ... directory from its ownership by root. sudo chown root -hR AppleFileServer.app could do the trick, but attempts by the author to verify the integrity of said command line entry were not exactly successful. (Linux folks: Mac OS X programs, like TextEdit.app, are technically directories with various binary files inside. Most replies indicated preference for using Disk Utility's Repair Permissions widget. Another valid method is to just use tar with the preserve permissions argument. In testing, the feature worked fine without fixing the permissions.)

Caution: These systems do not like Classic Mac files with type/creator codes and stuff like icon data. In some cases it will say that a disk error has occurred just before it finishes copying the file. The easiest way to check this is to copy a small program like Disk Copy 4.2 into the target directory and see if it brings up the error dialog. In testing, Mac OS 8.1 would simply copy very slowly, about 200KiB/sec or less, whereas Mac OS 9, 9.1 and 9.2 would transfer at normal speed, then pop the error. It would be wise to use Stuffit, Compact Pro, MacBinary or BinHex style encoding for insurance reasons. (The testing indicated that raw programs like Disk Copy 6.3.3, Marine Aquarium 2, TomeViewer 1.3D3 and so on would cause this error, but .dmg, .bin, .sit, .hqx, .rtf and .txt files were fine.)

10.7 and 10.8 have a reduced set of enabled UAMs (User Authentication Modules, basically methods of authentication, such as cleartext, two way random number exchange, DHX, and so forth) which could preclude the mounting of certain older machines, such as older NAS units. Try reading this Apple KB on enabling less secure UAMs. As part of testing for this Guide, running through the procedure did not change any of the restrictions of servers (such as 7.5.5, 8.1, 7.0.1, et cetera) listed in the Chart: the procedure doesn't work with 10.5 or 10.6, yet 10.9 might apply because it works with the command to read the list of disabled UAMs.

Windows Server 2000 and 2003 support the Services for Macintosh feature to share out AFP volumes to Mac client computers. There are some third-party Windows software available (like Novell's Netware) which can provide server features as well to other Windows versions, however these additional software suites are not examined as part of this Guide. In this demonstration, we'll set up 2000 Server up and prepare it to accessible to other Macs. At this present time, 2003 Server will not be explored because it is too expensive on the open market. The Server editions of Windows have many other useful features like Telnet server, WWW server, FTP server, DNS server services, and more.

During a fresh install of the Software, the Windows Components Wizard appears where optional elements can be installed or removed. (The image shown is post-install, because screenshots cannot be captured during the install process of Windows without hardware video capture tools or the use of virtual machines.) Scroll halfway down through the list until the "Other Network File and Print Services" component is shown. Tick the box. To install the FTP Server option, first find the "Internet Information Services (IIS)" component, click the Details button, then scroll until the FTP Server option is located. Tick the box and it should be taken care of. If any of these options were not installed the first time, they can be reinstalled afterwards by heading to the Start menu, then Programs, then Administrative Tools, then the Configure Your Server app. Hit the Advanced option on the left toolpane, then tick the Optional Components hyperlink, then the start the wizard. Alternatively, this wizard can be found in the Add/Remove Programs in the Control Panel, on the left pane.





Installing components



Completing server setup



Configuring a shared folder



SFM service properties



The Configure Your Server app is started by default on a fresh install of the OS and some quick configuring is all that is necessary to configure some settings, then dismiss it. Windows 2000 Server has a host of features but we'll just demonstrate SFM over Ethernet. LocalTalk access is not supported unless a LocalTalk PC card is installed or a Ethernet to LocalTalk bridge is used.

To start the SFM service, from the Configure Your Server app (if it is lost, it's in the /Start/Programs/Administrative Tools area), click the File Server option on the left toolpane. Start the Shared Folder wizard. Browse for a folder to share, we'll use the My Documents folder to start off with. Name the share. Tick the "Apple Macintosh" client option, then fill in the Macintosh share name. Click Next. To simplify setup and because we are not worried about Internet malware (LAN only), you may select the "All users have full control" option, or the preferences may tweaked as needed. Click Finish.

From the Component Services app (Start/Programs/Administrative Tools/) the service may be stopped or started as the situation merits: shares can also be added or removed from that application. To configure Ethernet to be used, open the "Network and Dial-up Connections" applet. Double click Local Area Network. Scroll down in the little component area in the window until you find the Internet Protocol option at the bottom. Hit the Properties button. The "automatic" option is DHCP Server -- for manual setup, tick the "Use the following IP address", then fill it out -- for our example, 192.168.3.5 and a subnet of 255.255.255.0 was used (via a cross-over cable). If the machine is hooked to a router that goes out to the Internet, then fill out the router's internal address (like 192.168.1.1) for the gateway.



Guest properties settings



Configuring TCP/IP



Viewing available shares



W2S SFM under 10.5.8



Because the Services for Macintosh is a file server feature only, it won't be able to access any Macs and mount them in the Network Connections area. To mount the Server on a Mac, first configure the Mac side as demonstrated earlier with the MacTCP and/or OpenTransport setup instructions (and the Ethernet cable is connected, with a straight cable for a router, or cross-over for direct computer-computer connection). Then head to the Chooser and mount the volume -- in OS X, open the Go menu and mount it from there. It is possible to share the CD drive if the volume is CDFS -- HFS disks will not work. (A note: the "shared folder" representing the CD drive may have to be removed and replaced with a new share if a different disk is inserted. OS X does not have this abnormality while sharing its CD drive.)

For a Guest user to connect, the shared folder must be in the root path of the hard drive (for instance, "D:/SharedF") as directories and files in the user folders cannot be made accessible to Guest user accounts: ensure the checkbox for Guest access in the folder properties is marked, lest it won't work. Also the Guest user account will have to be activated (see the image above, to the far left). Only NTFS based partitions or volumes can be shared, FAT32 is not accessible to SFM client users. For all users, the UAM volume is available to be mounted. This is a suite of networking software meant for AppleShare 3.6 and 3.8 intended for semi-secure password transport and login into 2000 Server. It won't work with AFP over TCP/IP. Logging in as a user or an administrator will mount the shared volume (Fun Folder in our case) and the machine name is broadcast over the network. In pre-OS X systems, the Chooser will work fine, however in OS X you must use the Connect to Server feature and enter in the IP address (such as afp://192.168.3.8) because the advertising doesn't work under OS X. All read/write/access permissions are administered on the Server.

In Windows 2000 Server and possibly later versions of Windows Server, the Macfile utility, accessed from the command line (or Command Prompt) can perform some interesting functions, such as the forkize feature which can join a resource fork to a data fork to make a single file, while also setting the type and creator data. It's probably rarely used, but it's worth a mention. The command copy can also combine (known as concatenate; use copy /? or see the Windows Help documentation on the copy command; or here) one or more files together, but it's not the same thing as the Macfile utility.

For Linux, the Netatalk stack is used for file server services, and the afpfs-ng Terminal-driven stack is used as a client to access AFP shares. First the Netatalk portion will be discussed.

For users of older distros, the repository sources may have to be updated. In Ubuntu for instance, older releases have the repository sources at old-releases.ubuntu.com, and the Software Sources manager will not know of such a location (perhaps excepting newer distros at the time of this writing, like 12.10 Quantal), so the sources.list file will have to be manually updated to the new locations. To do this, type the next command into a Terminal window: sudo gedit /etc/apt/sources.list

Comment out every single line as shown in the image (or delete them, same thing), and add the proper repository sources as shown, or directed. For example, 7.10 Gutsy would get the first line of the source to look like this: deb http://old-releases.ubuntu.com/ubuntu/ gutsy main restricted universe multiverse The whole list of archived repository data is located here for reference, so it's just a matter of editing the file to look similar to the previous image, so that the Software Sources will look like the image to the right, with proper pointers. Do take notice that as old releases, they will not receive any updates, security patches, fixes or any other maintenance.

The lower limit of this Netatalk package to work successfully is not known (concerning Ubuntu, like if it will work with 4.10 Warty), and depending on alternative distros like KDE or Slackware, this may or may not be a concern. If the Linux system has no repository support, then the difficulty of this work can quickly ratchet up to Expert Grade -- not for the average user. Actually, being forced to compile some old distro to use modern programs using nothing but source code and man pages could constitute cruel and unusual punishment...

Netatalk 2.1.6 Server

Owing to the perplexing complexity of the Linux platform, it can be considered reasonable that only two distros are demonstrated -- in this case, Ubuntu 10.04.4LTS "lucid" and 9.10 "karmic". (They'll look the same, because the 10.04 system has been back-themed to look like 9.10.) Refer to this site for Slackware specific information.

The Netatalk stack must be installed from source because using sudo apt-get install netatalk will not set the --enable-ddp flag which is required for systems not using AFP over TCP/IP, however this depends on the repository. Some will have it already enabled, but it isn't very hard to compile from source anyways. Netatalk 3.x dropped AppleTalk support (DDP) and will not work entirely in this manner of this section. The Netatalk service is a server only and cannot access any other AFP servers as a client. Specifically, Netatalk 3.x is designed for OS X 10.4+, not for older Mac clients and includes OS X specific features such as Time Machine support.

Although this section prescribes the use of Netatalk 2.1.6, any version of 2.2 ought to work. In testing under Ubuntu 10.04.4LTS x64 however, 2.2.3 with Zeroconf enabled kicked an error on the client saying that it didn't have a recognizable logon sequence, 2.2.4 worked fine, but Zeroconf was not enabled, and 2.2.5 had a build error. Therefore, should 2.2.x not work on your platform, simply default back to 2.1.6.

The very first commands to be run are the following (the second one is more or less optional...depending on the case at hand)... sudo apt-get update sudo apt-get upgrade

Then the next step is to install each of the following libraries, from either source (common-man need not apply) or from the repositories for the distro in question:

libavahi-client-dev; libcups2-dev; libdb-dev; libssl-dev

On a Debian system as we have here (Ubuntu is based on Debian), we type:

sudo apt-get install libavahi-client-dev libcups2-dev libdb-dev libssl-dev

Multiple libraries can be installed with a single command, as shown. Avahi is an open-source implementation of Zeroconf (Rendezvous/Bonjour in Applespeak) and helps advertise computers over networks; libcups2 is part of the Common Unix Printer Service; libdb-dev is the Berkeley DB stack from Oracle for managing databases; and libssl is for SSL encrypted networking services. Next, we get to build Netatalk from source code.

Point a browser to this website. Click the version 2.1.6 directory. Download the netatalk-2.1.6-tar.gz file (the tar.bz2 can be used also, just a different Terminal command to unpack it). Open the Terminal application.

Use the cd command to navigate to the directory where the tarball (.tar.gz) was downloaded. For example, if the tarball was downloaded to the user's Downloads folder in the Home Directory, then type:

cd ~/Downloads

...to navigate to that directory. cd .. goes back one directory, if needed, and ls lists the contents (mostly... ls -al lists everything) of the folder in question (and clear clears the terminal). Once the download has been located, type the following:

tar -zxvf netatalk[tab key][enter key]

The tab key is an auto-completion helper, which DOS must have surely envied. The Enter key completes the command. If the .tar.bz2 was downloaded instead, then replace the "z" with a "j".

Newbie pointers:

tar: Tape ARchiver, dates back to the old UNIX days when data was commonly stored on tape media.

Tape ARchiver, dates back to the old UNIX days when data was commonly stored on tape media. x: eXtracts the archive. The opposite of this is the "c" flag, which is what would be used to create a tarball archive of the name that just follows after the "f" flag; like this: tar -czf SystemNADs.tar.gz System701NAD.image.hqx System608NAD.image.hqx for a gzip compressed archive with multiple contents.

eXtracts the archive. The opposite of this is the "c" flag, which is what would be used to create a tarball archive of the name that just follows after the "f" flag; like this: for a gzip compressed archive with multiple contents. j: Runs the archive through the bzip2 archive utility.

Runs the archive through the bzip2 archive utility. v: Verbose mode, shows the list of files as they are processed. Optional.

Verbose mode, shows the list of files as they are processed. Optional. f: Indicates that the file is just after this character.

Indicates that the file is just after this character. z: Pushes the archive through the gzip utility.

Coming along? Good. Once the archive has decompressed, there should be a folder named "netatalk 2.1.6" in the source directory where the archive was located. Navigate to that directory by typing: cd netatalk[tab key][enter] Now let's get even more ornate by entering in the following for a Debian based distro; but read the next paragraph before completing the command:

./configure --enable-debian --sysconfdir=/etc --with-uams-path=/usr/lib/netatalk --with-ssl-dir=/usr/lib/

Notice! Triple-check the command matches as it is written here, as it generates a Makefile which tells the compiler how to build the stack. Any errors will appear just after the command is entered, usually like warning: --enable-ssl not understood. If it was configured incorrectly, redo it. Distros with install directories other than the kind used here may have to change the --with-uams-path and --with-ssl-dir paths: see the image above of how the /lib/ssl path may have to be located manually, which is a highly suggested step to make sure that the reference path is correct. The varieties of Linux inhibit a comprehensive list here other than Debian systems. Both Debian and Ubuntu systems get the --enable-debian flag. Other systems like SUSE get a different one -- see the netatalk manual page; or type ./configure --help to see what flags like --enable-suse to use. Here are some additional flags which may be needed depending on the case at hand:

Apple II: Add the --enable-a2boot flag if you're expecting to netboot a II GS ; the Apple II Networking section has additional details. Based on the developments of the A2SERVER project, the Apple II compatibility could be a bit rough on the edges.

Add the flag if you're expecting to netboot a II ; the Apple II Networking section has additional details. Based on the developments of the A2SERVER project, the Apple II compatibility cou