Re: A little more information

[Fraser Farrell <fraser@trilobytes.com.au>]

>       Again, ethernet is the most likely, though I don't know of any
>       cheap controller card with on-board ethernet.  This is probably
>       the most practical path, and easiest to farm out to some list 
member
>       who is interested in low-level programming.  The advantage here is
>       that most embedded controller boards come with built-in libraries
>       of functions, especially if ethernet is included, so the software
>       effort decreases.

There's a lot of low-level source code already available for Ethernet 
programming. Examples include the Linux network card drivers written by 
Donald Becker and others; and the Crynwr Packet Driver library. I've 
written a few DOS networking utilities using Turbo Pascal + Crynwr, so 
it's certainly doable. Last time I checked the Crynwr stuff was free for 
noncommercial use.

At the computer end, just about every Ethernet card sold nowadays 
includes a Crynwr driver, and many manufacturers now include Linux 
drivers.

Just curious. How hard would it be to put an Ethernet interface into the 
Mark IV? Or even a generic PCI expansion slot (for an Ethernet or 
"enhanced parallel" card)?


cheers,
Fraser Farrell