Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!zaphod.mps.ohio-state.edu!usc!ucsd!sdcsvax!amos!hartung
From: hartung@amos.ling.ucsd.edu (Jeff Hartung)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: Problem with ZOO & DOS 4.01
Message-ID: <7602@sdcsvax.UCSD.Edu>
Date: 12 Dec 89 00:22:09 GMT
References: <470007@hplsla.HP.COM> <9839@zodiac.ukc.ac.uk>
Sender: nobody@sdcsvax.UCSD.Edu
Reply-To: hartung@amos.UUCP (Jeff Hartung)
Organization: Univ. of Calif., San Diego
Lines: 21

<In article <470007@hplsla.HP.COM>, larrys@hplsla.HP.COM (Larry Sanders) writes:
<> On my daughter's 386sx machine with DOS 4.01 zoo ( and zoox ) creates 
<> zoo archives just fine.  The reverse is less reliable. Extracting 
<> files it skips some - and says it is skipping them.  The same zoo 
<> archive extracts correctly on my machine.

In article <9839@zodiac.ukc.ac.uk> cur022@zodiac.ukc.ac.uk (Bob Eager) writes:
<However, ZOO can be fooled (as can most other programs) by the use of APPEND or
<something like DPATH, which provides a 'path' for searching for non-executable
<files. It might then find the name somewhere along that path, assume (as it is
<meant to) that the file already exists, and skip it. 

I had a device driver installed at boot time called CONFIGUR which allowed
boot time changes in config.sys.  Any time I tried to extract programs called
'CONFIG' or similar names, it would do what you are describing.


 --Jeff Hartung--  	
 Disclaimer: My opinions only, etc., etc., BLAH! BLAH! BLAH!...
 ARPA - hartung@amos.ucsd.edu          
 UUCP - ucsd!amos.ucsd.edu!hartung