Xref: utzoo comp.protocols.appletalk:2061 comp.unix.xenix:6213
Path: utzoo!attcan!uunet!ateng!chip
From: chip@ateng.ateng.com (Chip Salzenberg)
Newsgroups: comp.protocols.appletalk,comp.unix.xenix
Subject: CAP 5.0 ported to SCO Xenix/386!
Message-ID: <1989Jun1.200932.1878@ateng.ateng.com>
Date: 2 Jun 89 00:09:32 GMT
Organization: A T Engineering, Tampa, FL
Lines: 26

A report of success for a change.

[For comp.unix.xenix readers:  The CAP package lets a Unix system become a
file and print server for one or more Macintosh networks.  It requires the
use of a Kinetics FastPath or Cayman GatorBox for AppleTalk <--> TCP/IP
protocol translation.]

I've got CAP 5.0 working on a SCO Xenix/386 2.3 system with SCO TCP/IP.  Of
course, the filenames are truncated at 14 characters (*sigh*), but the
system otherwise runs like a champ.  Thanks to Columbia and Cayman, my Xenix
system is now an AppleShare server.

The port was fairly easy.  Using SVr3 sighold() and sigrelse() instead of
setsigmask() et al was no fun, and getting the locking to work was a bit
hairy, but it's okay now.

I wonder where I should send the CAP patches?

Incidentally, I'd like to put in a good word for SCO TCP/IP, which
apparently was done mostly by Lachman.  It's great.  The TCP/IP development
kit is actually a BSD compatibility library, all the way down to index() and
rindex().
-- 
Chip Salzenberg             <chip@ateng.com> or <uunet!ateng!chip>
A T Engineering             Me?  Speak for my company?  Surely you jest!
	  "It's no good.  They're tapping the lines."