🚀 go-pugleaf

In article <1990Mar2.122254.4259@NCoast.ORG>, davewt@NCoast.ORG (David Wright)
writes:
> 	I have had trouble with DNET too. I was running it on an 8-bit
> serial line through a 2400 baud modem, and after just a few minutes, it
> always seems to lock up. I was also using the NET: device. ALso, I
> once read an article, and it claimed the DNET was about a fast as Y or Z
> modem when it was only sending in one direction. I found it to be MUCH
> slower at sending directories to the other system than should have occured
> if it was as fast as Y modem. I am pretty sure that it was DNET that blew
> it, and not the NET: device, and attempts to run the NetStat utility also
> locked, and the modem was no longer polling....
> 	Any ideas?
> 
> 		Dave

The delay when you are doing remote directories with NET: is because a full
512 byte fileheader is being transmitted for each file in the directory.
This means that for a directory with 100 files, at least 50K needs to be
transmitted across the serial link (about 4 minutes at 2400 baud). Of course,
this would be much faster if NET: simply asked for the filenames themselves
and not the full fileheader, but then it wouldn't be as compatible with
AmigaDOS.

At 2400 baud, NET: is a lot of fun to play with but don't expect to use it
for anything serious... (it's much quicker to open a remote CLI and type
DIR for example :-)

No ideas on your Dnet lockups I'm afraid.

Eddy
--
Eddy Carroll             ----* Genuine MUD Wizard  | "You haven't lived until
INTER: ecarroll@vax1.tcd.ie                        |    you've died in MUD!"
 UUCP: {..uunet}!mcvax!ukc!vax1.tcd.ie!ecarroll    |  -- Richard Bartle