Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!rutgers!ames!amdcad!uport!admin!suprt!jmsully
From: jmsully@suprt.UUCP
Newsgroups: comp.unix.wizards,comp.unix.questions
Subject: Re: Microport Unix V/AT and 9600 baud
Message-ID: <105@suprt.UUCP>
Date: Mon, 21-Sep-87 16:37:26 EDT
Article-I.D.: suprt.105
Posted: Mon Sep 21 16:37:26 1987
Date-Received: Fri, 25-Sep-87 00:38:52 EDT
References: <1198@dasys1.UUCP> <207@eurifb.UUCP>
Organization: Microport Systems, Scotts Valley, CA
Lines: 20
Keywords: Microport Unix thrashed buffers
Summary: This bug has not been reported to us...
Xref: mnetor comp.unix.wizards:4417 comp.unix.questions:4219

In article <207@eurifb.UUCP>, wietse@eurifb.UUCP (Wietse Venema) writes:
> In article <1198@dasys1.UUCP>, manes@dasys1.UUCP (Steve Manes) writes:
> > [reading garbage at 9600 baud when ymodem block size is increased to 1k]
> 
> I had a similar problem when increasing the size of writes to floppy from
> 512 bytes to 1k (it was a small program that sits in a pipeline with tar
> and asks for a new floppy at the appropriate time). Tar will complain
> when the archive is read (directory checksum errors). There are no problems
> with 512-byte writes.

As of September 22, 1987 this bug had not been reported to us.  We have a 
program which we use in-house which writes to the floppy in ~60K chunks
and we do not have a problem with this.

It may also be possible that this is a problem with tar, you might try
using the block factor (b) option to read the disk.  Also make sure that
you are using the raw device when you read and write the diskette.

Please send us further details and, if possible, the code which reveals 
this problem.