Path: utzoo!attcan!uunet!jarthur!usc!cs.utexas.edu!rutgers!mcnc!rti!sas!walker
From: walker@sas.UUCP (Doug Walker)
Newsgroups: comp.sys.amiga.tech
Subject: Re: DNET query
Message-ID: <1630@sas.UUCP>
Date: 20 Mar 90 15:54:58 GMT
References: <153102@<1990Mar1> <15600002@ux1.cso.uiuc.edu> <1990Mar2.122254.4259@NCoast.ORG> <5814.25f5c5f8@vax1.tcd.ie>
Reply-To: walker@sas.UUCP (Doug Walker)
Organization: SAS Institute Inc, Cary NC
Lines: 28

In article <5814.25f5c5f8@vax1.tcd.ie> ecarroll@vax1.tcd.ie writes:
>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.

It's impossible for NET: to just get the filenames.  NET: has no idea that 
the DIR command is the one asking for information about files;  it just
sees the request come over for a FileInfoBlock, and fills the request.

However, the FIB is only 220 bytes, not 512 bytes.  Add another 20 bytes or
so of NET: overhead per packet and you get less than 250 bytes/file, or about
25k.  Still 2 minutes, so it's not really usable at 2400 baud.

As to DNET lockups, I have seen this happen as well, but I have no idea what
causes it.  I use a null modem hookup, and it seems to work without lockups
at 9600 baud but with lockups at 19200, so I use 9600.


  *****
=*|_o_o|\\=====Doug Walker, Software Distiller====== BBS: (919)382-8265 =
 *|. o.| ||                                NOTE NEW BBS NUMBER!^^^^^^^^
  | o  |//     Got mole problems?  Call Avogadro: 602-1023!
  ====== 
usenet: ...mcnc!rti!sas!walker   plink: dwalker  bix: djwalker