🚀 go-pugleaf

Hi,

first of all, I would like to say how pleased I am with the Dnet-net:
program team.  I do, however have a problem.

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.
The problem occurs when I have mounted a device on the remote machine
and then call for a directory.  It will sometimes finish, but more
often than not, it will lock the network (and cli) up.  The network is
then dead to the other CLI's as well.

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 open dnet over a 300 foot+ 3 wire null-modem with the command:

run dnet -X -8 -bxxxxx -h0

I see two solutions... one hardware, one software (or configuration).
The Hardware solution would be to boost the signal (after all rs232 is
rated for 50 feet and my run is at least 6 times that), translate the
signal to something rated for longer runs (rs423?!? the mac
standard... I don't have a manual nearby, so I'm not sure of the exact
rs number), or even better... translate this new mac compatible signal
to "PHONENET" (mac's "listen in" network system) which would allow for
multiple node networking in the future, as well as pulls of nearly
1000 feet.

The software solution involves feedback from those more experienced
with dnet.  I hope that My hardware musings are wasted time.

If anyone has any advice, please email me the answer.

					Thanks in advance
					-henning
-- 
------------------------------------------------------------
All opinions are my own, as are the spellings any deviation
from the norm is just an effect of late nights and early
mornings, with little sleep between.