[comp.binaries.ibm.pc.d] Zoo utilities

frotz@drivax.UUCP (Frotz) (11/16/88)

In article <2486@m2-net.UUCP> mju@m-net.UUCP (Marc Unangst) writes:
>PKARC v3.5 and up has file and archive comments, too.  One of the
>prime reasons that ZOO will probably never gain wide acceptance
>is the fact that it isn't backward-compatable with PKARC.  

This could be considered a feature;-) in that the file format has
nothing to do with the arc-wars.  I believe that the functional
similarity (in novice) mode was intentional.

>People
>have to convert all their archives to ZOO.  For a BBS with several
>megabytes of files, this could take a very long while.  Perhaps
>if a person wrote a program to automatically re-pack all of a
>BBS's files with ZOO, it would help the changeover.  The sysop
>would take the board down for a day, run ARC2ZOO, and then
>put it back up.

The executables release of zoo comes with the following zoo utilities:

ATOZ.EXE:	Converts >>>ANY<<< other non-zoo file format to zoo as
		long as you have an archiver, zoo and atoz.  You specify
		what the source archive is, what executable unarcs it,
		whether or not to test the zoo archive after it is built
		and so forth.  If only some of the other arc-warriors 
		were as nice;-)

		I routinely convert all non-zoo archives to zoo with atoz
		in very short order.

STUFF.EXE:	Generates a list of files that match a search criterion.
		This seems to be a unix-find work-alike for generating
		lists of files to be zoo-ed.  (I haven't used this because
		I use to Metaware's Find for this and everything else.
		Why use one more tool;-)  Turbo-C Source is available.

BOOZ.EXE:	This is the basic zoo extractor.  This comes with source
		so that developers can create zoo-aware utilities.  This
		is not needed if you have zoo.

FIZ.EXE:	This is handy if you have moved a zoo archive onto a floppy
		that develops "lost" clusters.  There should be few other
		reasons to use this program, BUT IT IS SURE NICE TO HAVE
		AROUND.  Thanks Rahul!

LOOZ.EXE:	This is a fancy zoo extractor.  It has the ability to load
		an zoo-ed executable into memory and on top of itself.  This
		is nice because it allows users to execute programs from an
		archive without creating a temporary file on disk.  It also
		minimizes the memory impact of using looz.  Again, this
		program is not necessary if you have zoo.

ZOO.EXE:	If I understand current events correctly, this will remain
		the name of Rahul's Zoo archiver (with minor restrictions).
		I may be mistaken about the name of the "Free ZOO" program,
		but I think it is called FREEZOO.EXE.

		ZOO.EXE is the only program that can create archives ("Free
		ZOO" is considered to be ZOO here since there are only 
		supposed to be minor differences in features).  ZOO.EXE can
		create archives, extract archives, list archives, add
		comments, mark as deleted, unmark as deleted, pack (meaning
		"pack zoo by removing all files marked as deleted"), and a
		few other features that I don't use enough to remember;-).

BILF.EXE:	THIS IS A VMS PROGRAM ONLY!  It is only needed when converting
		slimy (sorry prejudices showing...tuck, tuck...there) file
		formats so that kermit can get zoo archives onto and off of
		VMS machines.  This program is only needed if you are using
		zoo on a VMS machine and move zoo archives to non-VMS machines.

Apologies to the net for this long windedness.  Thanks to Rahul Dhesi for all
of his great work on zoo and as moderator.

--Frotz @Digital Research, Incorporated		amdahl!drivax!frotz
	 70 Garden Court, B15			(408) 649-3896
	 Monterey, California  93940		Ask for John Fa'atuai

sas@bcd-dyn.UUCP (432 2370.00) (11/22/88)

I Think I may have found a bug in either zoo or stuff.  Does anyone know how
to use stuff/zoo to archive a tree with empty subdirectory entries?  Every time
I try, it leaves out the empty subdirectories.  Thanks, Scott

-- 
===============================================================================
Scott A. Sharkey                               UUCP: osu-cis!bcd-dyn!sas
I-LAN, Inc.                                    USPS: 640 Lakeview Plaza Bvld.
(614) 436-7651                                 Who?  Me? I just work here! 

thaler@speedy.cs.wisc.edu (Maurice Thaler) (11/23/88)

I don't think you could call it a bug. If a subdir is empty, there are
no files, so why should stuff list it? Fastback is the same way. My
solution to both of these is to creat a 1 BYTE bogus file to hold the
subdir.

dhesi@bsu-cs.UUCP (Rahul Dhesi) (11/23/88)

In article <6719@spool.cs.wisc.edu> thaler@speedy.cs.wisc.edu (Maurice Thaler)
writes:
>If a subdir is empty, there are
>no files, so why should stuff list it? Fastback is the same way. My
>solution to both of these is to creat a 1 BYTE bogus file to hold the
>subdir.

The original intent of zoo was to store *files*, and the only purpose
of storing directory names was to be able to put back the *files* where
they came from.  So failure to archive empty directories should be
thought of as a feature.  However, now that people are using zoo for
making backups (not an originally-intended use), I agree that empty
directories should be preserved.  It will come.

Meanwhile, don't create a one-byte bogus file to hold the subdirectory.
Create a zero-byte bogus file instead, and save yourself a cluster's
worth of disk space.

A zero-byte file may be created using DEBUG.COM as follows:

     C:/SCR> debug bogus.fil
     File not found
     -w
     Writing 0000 bytes
     -q
     C:/SCR>

You type "debug bogus.fil" at the MS-DOS prompt, and you also type
"w" and "q" to DEBUG.

You could do the same with a proper implementation of the TOUCH
command.
-- 
Rahul Dhesi         UUCP:  <backbones>!{iuvax,pur-ee}!bsu-cs!dhesi

ralf@b.gp.cs.cmu.edu (Ralf Brown) (11/24/88)

In article <4858@bsu-cs.UUCP> dhesi@bsu-cs.UUCP (Rahul Dhesi) writes:
[creating a 0-byte file with DEBUG, or...]
}You could do the same with a proper implementation of the TOUCH
}command.

Or, if you don't have a "touch", just type
	TYPE NUL >FOO
to create a 0-byte file called FOO.  Much easier than DEBUG.... (unlike the
other methods, it does clobber any existing file.  Using >>FOO preserves
the file, but doesn't update its time)

-- 
{harvard,uunet,ucbvax}!b.gp.cs.cmu.edu!ralf -=-=- AT&T: (412)268-3053 (school) 
ARPA: RALF@B.GP.CS.CMU.EDU |"Tolerance means excusing the mistakes others make.
FIDO: Ralf Brown at 129/31 | Tact means not noticing them." --Arthur Schnitzler
BITnet: RALF%B.GP.CS.CMU.EDU@CMUCCVMA -=-=- DISCLAIMER? I claimed something?
-- 

greggy@infmx.UUCP (greg yachuk) (11/24/88)

In article <4858@bsu-cs.UUCP> dhesi@bsu-cs.UUCP (Rahul Dhesi) writes:
>A zero-byte file may be created using DEBUG.COM as follows:
 ...

A much easier (though not exactly intuitive) way is to
	REM > fred.out

(pretty silly, huh?)

	-greg

Greg Yachuk		Informix Software Inc., Menlo Park, CA	(415) 322-4100
{uunet,pyramid}!infmx!greggy		why yes, I DID choose that login myself

leonard@bucket.UUCP (Leonard Erickson) (11/27/88)

In article <6719@spool.cs.wisc.edu> thaler@speedy.cs.wisc.edu (Maurice Thaler) writes:
<I don't think you could call it a bug. If a subdir is empty, there are
<no files, so why should stuff list it? Fastback is the same way. My
<solution to both of these is to creat a 1 BYTE bogus file to hold the
<subdir.

I don't know if this will work with ZOO, but FASTBACK will happily backup
a *zero* byte file. (We install a 0 byte default config file for one program
so it will skip an annoying prompt). 

A 0 byte file is much better as it doesn't waste a cluster of disk space,
just a directory entry. They are easily created with some versions of TOUCH.
Or you can get creative with NU...
-- 
Leonard Erickson		...!tektronix!reed!percival!bucket!leonard
CIS: [70465,203]
"I used to be a hacker. Now I'm a 'microcomputer specialist'.
You know... I'd rather be a hacker."

swh@hpsmtc1.HP.COM (Steve Harrold) (11/29/88)

Re: Creating a 0-byte bogus file

An easier way is to enter:

	mode >bogus

or any command that does NOT write to stdout.