Ethernet for Atari Systems


ExtenDOS and CD Writer Suite were both originally developed because we needed (well, wanted :-)) CD-ROM and CD recorder access on our systems. Ethernet support is something else we wanted for a time, but since we don't have a Milan or a Hades, the available options all seemed to involve connecting circuit boards outside the machine, which is something we'd rather avoid.

A while back we discovered the Daynaport SCSI/Link, a small box which connects a SCSI interface to an Ethernet. This is no longer manufactured, but since it was originally developed for the Mac, there are lots of used ones available. A few months of development, and now we have Atari software to allow you to use one to connect your Atari to an Ethernet!

Available drivers

Drivers are available for the following stacks:

bulletSTinG: this has had extensive use and seems stable.
bulletMintNet: this has had some use and seems relatively stable.

The drivers are being released as free copyrighted software; we intend to support and improve them on an ongoing basis, so please report any problems to us and we will do our best to resolve them.

Current driver versions

bulletSTinG drivers
bulletdownload v0.71 (fix system crash when used with HDDRIVER v8.xx)
bulletdownload v0.80 (fix problem when changing MAC address)
bulletMintNet drivers
bulletdownload v0.50 (first public beta release)
bulletdownload v0.60 (fixes problem with ARP when using 1.4a firmware)

Please make sure you don't mix components from different versions; they probably won't be compatible, and that may cause a system crash.

What you will need

bulleta Daynaport SCSI/Link-T (model DP0801) or SCSI/Link-3 (model DP0802); users have also reported success with the Pocket SCSI/Link-T (model DP0901) and Pocket SCSI/Link (model DP0902); and with the Farallon EtherMac SCSI (model 572-2) (apparently a rebadged Daynaport)
bulleta SCSI port that supports arbitration
bulleta recent version of HDDRIVER (v7.xx or v8.xx) or other SCSIDRV support
bulleta TCP/IP stack (see above)
bulletthe SCSI/Link drivers themselves

If you do not have a source for the Daynaport hardware, we suggest asking in the appropriate Mac newsgroup, or checking on eBay. If all else fails, contact us; we may be able to suggest other sources from our researches.

A note on voltage: the SCSI/Link (like many other small devices) uses an external power supply. The voltage required for models DP0801 & DP0802 is 12V DC, centre positive. The DP0901 & DP0902 use a different supply, which a helpful user tells us is 5V DC, centre positive.

Tested environments

bulletAnodyne Software
bulletTT030 (4MB ST RAM, 16MB TT RAM) running TOS 3.06 or MagiC 6.10
bulletHDDRIVER v7.83
bulletDaynaport SCSI/Link-T (model DP0801) or SCSI/Link-3 (model DP0802) with firmware version 1.4a or 2.0f, connected to the SCSI port or the ACSI port (see note below)
bulletthe STinG TCP/IP stack (v1.26) with v1.13 of the STNGPORT.CPX (earlier versions of this CPX may not work properly with the drivers)
bulletan Ethernet with two nodes: the TT and a PC running Windows 98 SE.
bulletUser report #1
bulletFalcon running TOS 4.04
bulletHDDRIVER (version unknown)
bulletDaynaport Pocket SCSI/Link (model DP0902) with firmware version 2.0f
bulletthe STinG TCP/IP stack (v1.26)
bulletan Ethernet with two nodes: the Falcon and a PC running Windows 2000
bulletUser report #2
bulletTT030 (unknown OS software)
bulletHDDRIVER v7.90 demo
bulletFarallon EtherMac SCSI PN572-2 with firmware v1.4
bulletthe STinG TCP/IP stack (unknown version)
bulletUser report #3
bulletFalcon running TOS 4.04
bulletHDDRIVER v7.93
bulletDaynaport Pocket SCSI/Link (model DP0901)
bulletthe STinG TCP/IP stack (unknown version)
bulletUser report #4
bulletTT030 running TOS 3.06
bulletHDDRIVER v8.21
bulletDaynaport Pocket SCSI/Link (model DP0901) connected to SCSI port
bulletthe STinG TCP/IP stack (v1.26)
bulletAnodyne Software
bulletTT030 (10MB ST RAM, 16MB TT RAM) running MiNT 1.16
bulletHDDRIVER v8.16
bulletDaynaport SCSI/Link-3 (model DP0802) with firmware version 2.0f, connected to the SCSI port
bulletthe MintNet TCP/IP stack
bulletan Ethernet with two nodes: the TT and a PC running Windows 98 SE
bulletUser report #1
bulletTT030 (4 MB ST RAM / 16 MB TT RAM)
bulletHDDRIVER v8.20
bulletFreeMiNT 1.16.3-alpha (EasyMiNT 1.7)
bulletDaynaport DP0901
bulletthe MintNet TCP/IP stack
bulletBound directly to wireless router using ethernet cable (using dhcp client)
bulletUser report #2
bulletTT030 (4 MB ST RAM / 32 MB TT RAM)
bulletHDDRIVER v8.21
bulletFreeMiNT 1.16.3-alpha (EasyMiNT 1.7)
bulletDaynaport DP0901 connected to the SCSI port
bulletthe MintNet TCP/IP stack

Ethernet with multiple nodes behind firewall and connecting to internet from TT

Other environments

We expect (but cannot guarantee) that the drivers will also work:

bulleton other original Atari systems (see Restrictions below for minimum requirements when connecting to an ACSI port)
bulletwith other firmware revisions of the above Daynaport hardware
bulletwith other releases of the operating system
bulletto communicate with other systems (e.g. Linux, cable modems) on the Ethernet

In addition, the drivers will probably work with other SCSI/Link devices from Daynaport, but since we do not have any of the other devices, we are unable to test this.


bulletwhen connecting to the ACSI port, you will also need:
bulleta Link96 or Link97 host adapter, since the SCSI/Link requires arbitration
bulleta device (such as a hard disk) connected to the ACSI port in order to provide termination power for the host adapter; the SCSI/Link does not do this
bullet(STiNG only) if the SCSI/Link is connected to the Falcon's SCSI port or the ACSI port of other Atari systems, access to the floppy drive is effectively prevented while the driver is active. This is because the driver polls the SCSI/Link hardware from a routine running under the timer interrupt, and the ports concerned share hardware with the floppy disk controller. You can use STiNG's CPX to deactivate the driver temporarily if you need to gain access to the floppy drive.
bullet(SCSI/Link-3 only) the SCSI/Link-3 has three ports: AUI, coax (10base2), and RJ45 (10baseT). If you connect to a hub/switch/router port that supports both 10Mbps and 100Mbps, the SCSI/Link-3 seems unable to determine which of the three ports to use, and will not establish a connection. This is a hardware compatibility issue that cannot be fixed by software. Either use a 10Mbps-only hub/switch/router, or connect a 10baseT MAU to the AUI port and use that to connect to the rest of the network. This problem does not occur with the SCSI/Link-T, which has only one port (10baseT).


Please note that these drivers have not been subjected to the extensive testing of our commercial software. Therefore you should take the normal precautions when using beta software. In particular, since this device may share the bus with your hard disk(s), it is possible that the driver could interfere with I/O to them. We strongly recommend backing up your hard disk on a regular basis to ensure that you do not lose important data. (If you need backup software, you know where to come :-)).

Developer documentation

In order to help others trying to develop drivers for Daynaport SCSI/Link devices, we have decided to release the information that we have deduced, concerning the SCSI command set used by the SCSI/Link. Note that this information was derived by experimentation with the devices, and was not provided by the manufacturer. Although it is believed to be correct, we disclaim any liability for direct or indirect damage due to the use of the information. You are on your own! However, we will be glad to get any additions or corrections to the documentation, and intend to maintain the latest version of the documentation on this page.

bulletDownload v1.20 of the SCSI/Link command set documentation


Last updated 24 December 2008 by Roger Burrows