Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!necntc!ames!ptsfa!hoptoad!dasys1!samperi
From: samperi@dasys1.UUCP (Dominick Samperi)
Newsgroups: comp.sys.att
Subject: Re: cpio for DOS and 3b2 - followup
Message-ID: <1802@dasys1.UUCP>
Date: Sun, 25-Oct-87 11:48:28 EST
Article-I.D.: dasys1.1802
Posted: Sun Oct 25 11:48:28 1987
Date-Received: Wed, 28-Oct-87 00:46:49 EST
References: <1647@dasys1.UUCP> <144800003@tiger.UUCP> <1261@uccba.UUCP> <1755@chinet.UUCP> <1264@uccba.UUCP>
Reply-To: samperi@dasys1.UUCP (Dominick Samperi)
Organization: Datamerica Systems, NYC
Lines: 23

>	Is there any documentation on the system specific goodies that thwart
>most attempts at unix-unix data transfer? I have access to some source for tar,
>etc., but not for any 3B2 device drivers. Did Microport & Altos make some deal
>with AT&T, and is that the only reason they are compatible? I realize someone 
>sells a product which does 3B2-DOS flopy transfer. Any ideas how they figured
>it out?

I've successfully transferred files between DOS and Microport with cpio (using
my own version of cpio for DOS), and I've also transferred files between
Microport and a 3B2 using cpio (720K floppy format). Microport cpio archives
do not contain the device driver-specififc information that is expected by
the 3b2 driver, but file transfers work anyway, provided that the last
cylinder is not used (there are a few problems with Microport's 720K floppy
driver). It should not be difficult to modify my DOS cpio
so that it can format/read/write cpio archives that can be read/written on
a 3B2, but I would need to determine how to format/read/write 720K format
floppies first (9 sectors/track, 80 tracks/side).

-- 
	Dominick Samperi, Manhattan College, New York, NY
		...!ihnp4!cmcl2!phri!dasys1!samperi
		...!ihnp4!cmcl2!manhat!samperi
		...!pur-ee!rutgers!unirot!samperi