Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!cbatt!ihnp4!inuxc!pur-ee!uiucdcs!convex!mcomp!p40001
From: p40001@mcomp.UUCP
Newsgroups: net.sources.d
Subject: Re: unarchiving the small C posting
Message-ID: 
Date: Tue, 9-Sep-86 10:59:00 EDT
Article-I.D.: mcomp.77400002
Posted: Tue Sep  9 10:59:00 1986
Date-Received: Fri, 12-Sep-86 05:31:04 EDT
References: 
Lines: 34
Nf-ID: #R:topaz.RUTGERS.EDU:5710:mcomp:77400002:000:1316
Nf-From: mcomp.UUCP!p40001    Sep  9 09:59:00 1986


> as indicated in the appended message, around the 25th of July a Small
> C source was posted to net.sources.d .  unfortunately, i am just now
> getting around to processing it.  it was preprocessed by some archiver
> and uuencode.  when i uudecode it i get one file called smallc.arc
> which contains unprintable control characters.  my question is what
> archiver on what type of unix system was used to produce this file?

In all likelyhood this program was archived not on a UNIX system but on
an MS-DOS machine, using the ARC 5.1 program which has become a sort of
standard in this environment. This would also indicate to me that any
assembler source and object files would be 8086/8 & MS-DOS compatible,
rather than UNIX-compatible.

To use on a PC/clone system: download the smallc.arc file using Xmodem or Kermit
in BINARY mode (otherwise the high bit gets stripped) and un-arc using
the commandline

	arc e smallc
or
	arc x smallc

To list what files make up the *.arc file without actually extracting them,
use

	arc l smallc

If you need a copy of ARC 5.1 email me and I will send you a uuencoded
executable.

-----------------------------------------------------
Wolf N. Paul, 290 Dogwood, Plano, Tx. 75075
UUCP:   { convex, infoswx, texsun!rrm }!mcomp!p40001
Phone: (214) 578-8023  W.U.ESL: 6283-2882