Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!wuarchive!csus.edu!ucdavis!ucbvax!SUN.SOE.CLARKSON.EDU!nelson
From: nelson@SUN.SOE.CLARKSON.EDU (Russ Nelson)
Newsgroups: comp.protocols.tcp-ip
Subject: Diagnosis: Xenix <--> SunOS Noninterop
Message-ID: <9011161934.AA13530@sun.soe.clarkson.edu>
Date: 16 Nov 90 19:34:09 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: "aka NELSON@CLUTX.BITNET" <nelson@clutx.clarkson.edu>
Organization: The Internet
Lines: 22

I said:

   I said:

      Can anyone give me some hints as solve my problem with Xenix <--> SunOS
      NONinteroperability?

   OR to make the window size smaller.  SCO doesn't make that easy,
   but I've got a call in on it, and hopefully they'll deign to tell
   me how I can properly configure my TCP/IP.

Hee hee.  Hackers 1, SCO 0.  I did a 'strings' on SCO's ifconfig
program.  Darned if it doesn't have an undocumented parameter,
onepacket.  "onepacket", "-onepacket" and "ioctl (set one-packet mode
params)".  What the heck, let's try it: "ifconfig 3comA0 onepacket".
Hey!  It works!

Summary: If you're using a 3c501 in your Xenix system, you must put it
in onepacket mode, otherwise you won't be able to talk to Suns.

Thanks to all who offered assistance.
-russ