Path: utzoo!utgpu!water!watmath!clyde!bellcore!faline!thumper!ulysses!andante!princeton!njin!rutgers!mailrus!ames!oliveb!cygnet!will
From: will@cygnet.CYGNETSYSTEMS (Will Nelson)
Newsgroups: comp.unix.microport
Subject: Re: Can't backup to floppy
Summary: Version numbers
Keywords: /dev/tty, console, cpio, Merge386
Message-ID: <929@cygnet.CYGNETSYSTEMS>
Date: 20 Sep 88 14:22:03 GMT
References: <913@cygnet.CYGNETSYSTEMS> <547@micropen> <1716@ddsw1.UUCP> <473@uport.UUCP>
Organization: Cygnet Systems -- Sunnyvale, Ca
Lines: 36

In article <473@uport.UUCP>, plocher@uport.UUCP (John Plocher) writes:
> 
> Writing to a floppy from the console has been tested with the following
> (non-exhaustive) list of system configurations:  (All of them passed)
> 
> 	V/386 2.2  & Micom NP600A Pre-V1.0
> 	V/386 2.2  & Micom NP600A V1.0
> 	V/386 2.2  & Micom NP600A V1.0 & DosMerge 1.0
> 	V/386 3.0e & Micom NP600A V1.0
> 	V/386 3.0e & Micom NP600A V1.0 & DosMerge 1.1
> 
> Since I have not talked to Mr Nelson yet, I can't say what his problem is.
> I can say, though, that it is *not* because of a lack of QC for 3.0e and DM 1.1.
> 

My system configuration is

	V/386 Runtime System			Version 2.1
	V/386 Software Development System		2.2
	V/386 Link Kit					2.1
	/usr/include/sys files				2.2* (2.1 lacked buf.h)
	Network Services Extensions			2.2
	Micom-Interlan NP626				1.0
	Merge 386					1.0
	Merge 386 Link Kit				1.0A

Note that it's not writing to a floppy that is the problem;
it is writing a multi-floppy cpio archive that is the problem.
The first floppy gets written successfully.
The cpio program exits before I get a chance to write to the
second floppy.
-- 
Will Nelson		uucp: {decvax!decwrl}!pyramid!oliveb!cygnet!will
Cygnet Systems, Inc.
601 West California Avenue
Sunnyvale, CA  94086-4831	(408) 773-0770