Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!husc6!ginosko!uunet!cbmvax!grr
From: grr@cbmvax.UUCP (George Robbins)
Newsgroups: comp.unix.ultrix
Subject: Re: dump on old 1.2 Ultrix...
Message-ID: <7487@cbmvax.UUCP>
Date: 31 Jul 89 17:56:45 GMT
References: <412@wuee1.wustl.edu> <1226@gvgpsa.GVG.TEK.COM>
Reply-To: grr@cbmvax.UUCP (George Robbins)
Organization: Commodore Technology, West Chester, PA
Lines: 28

In article <1226@gvgpsa.GVG.TEK.COM> davew@gvgpsa.gvg.tek.com (David C. White) writes:
> In article <412@wuee1.wustl.edu> tjs@wuee1.wustl.edu.UUCP (tom sullivan) writes:
> >my biggest complaint with 1.2 is the speed (or lack there of) of
> >dumps. is there an optimal setting (density, lenght, blocking factor, etc.)
> >to do dumps onto a TK50 drive. as it is, it takes over 6 hours to perform
> >a level 0 dump of an 80 Meg partition.
> 
> I think you are out of luck.  If my memory serves me correctly, the
> driver was rewritten to drive the TK50 in streaming mode in 2.0.
> The driver in 1.X couldn't get data to the drive fast enough to
> keep it going in streaming mode, so it runs in start/stop mode
> which explains why it takes so long to do a small dump.  

Maybe one of the DEC folk could clarify this? 

> It may be possible to grab the driver out of the 3.0 you seem to
> imply that you have, but I haven't really looked into whether
> this is possible or not.  Another possiblilty to to see if you
> can find a way to get a 2.3 version if you really don't want the
> 3.0 features.

Drivers are generally not binary transportable across major releases and the
3.0 stuff especially, since kernel level memory allocation stuff changed.

-- 
George Robbins - now working for,	uucp: {uunet|pyramid|rutgers}!cbmvax!grr
but no way officially representing	arpa: cbmvax!grr@uunet.uu.net
Commodore, Engineering Department	fone: 215-431-9255 (only by moonlite)