Received: (from major@localhost)
	by minnie.cs.adfa.oz.au (8.8.5/8.8.5) id BAA20201
	for pups-liszt; Sat, 31 Jan 1998 01:46:41 +1100 (EST)
X-Authentication-Warning: minnie.cs.adfa.oz.au: major set sender to owner-pups@minnie.cs.adfa.oz.au using -f
Received: from europe.std.com (europe.std.com [199.172.62.20])
	by minnie.cs.adfa.oz.au (8.8.5/8.8.5) with ESMTP id BAA20195
	for <pups@minnie.cs.adfa.oz.au>; Sat, 31 Jan 1998 01:46:35 +1100 (EST)
Received: from world.std.com by europe.std.com (8.7.6/BZS-8-1.0)
	id JAA19168; Fri, 30 Jan 1998 09:46:32 -0500 (EST)
Received: by world.std.com (TheWorld/Spike-2.0)
	id AA19117; Fri, 30 Jan 1998 09:46:31 -0500
Date: Fri, 30 Jan 1998 09:46:31 -0500
From: allisonp@world.std.com (Allison J Parent)
Message-Id: <199801301446.AA19117@world.std.com>
To: pups@minnie.cs.adfa.oz.au
Subject: Re: Installing PDP-11 UNIX w. no tape - solution
Sender: owner-pups@minnie.cs.adfa.oz.au
Precedence: bulk


<I get some error messages with restor (``Missing address (header) block''
<which I believe are to do with the 10,240 byte record requests from resto
<My code expects 512-byte requests, and I'm doing 20 a time to fulfill th
<10,240 request, but still problems.

Try slowing down.  You may be overflowing the input buffer.  This was
a common problem on TU58s hooked to the 2nd DL on some systems at speeds
above either 4800 or 9600.  It only happend in the TU58 to host direction
(read) as the opposite path expected a handshake every 128 bytes(to allow 
the tu58 to actually do the write to tape).  It seems the tu58 would send 
a 512byte block as 4 128byte packets at a sustained rate fast enough to 
overrun the PDP-11 host input buffer; before it could be emptied.  You 
may be emulating a similar problem.  PCs do not service interrupts all 
that fast and OS overhead can make that longer.

Note PDP-11s can have enough overhead and higher priority stuff ahead of 
the 2nd DL that it cannot take data at greater than 4800 baud (sustained 
rate) without some kind of handshake to allow processing in between.
If the system is basically unloaded like my minimal 11/23 it can run at 
38.4!  The most likely time when this overrun can happen is while doing 
processing to write (via file system) to disk and recieving data at the 
same time.

Allison


