Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!uakari.primate.wisc.edu!xanth!mcnc!rti!sas!walker
From: walker@sas.UUCP (Doug Walker)
Newsgroups: comp.sys.amiga.tech
Subject: Re: net: help
Keywords: locking
Message-ID: <1286@sas.UUCP>
Date: 18 Oct 89 19:38:52 GMT
References: <7222@thor.acc.stolaf.edu>
Reply-To: walker@sas.UUCP (Doug Walker)
Organization: SAS Institute Inc, Cary NC
Lines: 26

In article <7222@thor.acc.stolaf.edu> henning@thor.acc.stolaf.edu (Mark D. Henning) writes:
>I am able to get the net to work properly at speeds of 19200 and
>lower.  I am also able to get the net to work for a limited time at
>31250.  Dnet connects fterm at 57600, but netmount will not function.
This is exactly the behavior I have seen, and I mentioned it as such
in my documentation for NET:.

>From these facts, I conclude that I either have something incorrect in
>my dnet config files, or there is a bug in either dnet or net:  (I
>would assume that dnet would request mangled blocks over, if the
>checksums were bad.)
I don't know what DNET is seeing, but from the network's point of 
view I see:
  1) The handler submits a packet to DNET for writing;  it gets
     a successful return code.

  2) The server receives and processes the packet, then writes
     the result back via DNET again.  Successful return code.

  3) The handler never receives the packet.  It's dead in the
     water.

Maybe I'm misusing DNET, I don't know.  The source code is posted,
so y'all can second-guess me.

--Doug